!! DO NOT SUBSCRIBE - WE HAVE MOVED !!

!! DO NOT SUBSCRIBE - WE HAVE MOVED !!

Share this post

!! DO NOT SUBSCRIBE - WE HAVE MOVED !!
!! DO NOT SUBSCRIBE - WE HAVE MOVED !!
5 Reasons Why Every Developer Should Incorporate Common Weakness Enumeration (CWE) into Their Software Development Life Cycle (SDLC)

5 Reasons Why Every Developer Should Incorporate Common Weakness Enumeration (CWE) into Their Software Development Life Cycle (SDLC)

Unlocking Security and Efficiency: How CWE Enhances Development Practices.

Xavier «X» Santolaria's avatar
Xavier «X» Santolaria
May 22, 2024
∙ Paid

Share this post

!! DO NOT SUBSCRIBE - WE HAVE MOVED !!
!! DO NOT SUBSCRIBE - WE HAVE MOVED !!
5 Reasons Why Every Developer Should Incorporate Common Weakness Enumeration (CWE) into Their Software Development Life Cycle (SDLC)
Share

After finishing reading Chris Hughes and Nikki Robinson’s excellent book titled “Effective Vulnerability Management: Managing Risk in the Vulnerable Digital Ecosystem”, I thought I’d write a piece on the less(er) known community-developed Common Weakness Enumeration (CWE™) project and why it’s important to all. Let’s go!

Keep reading with a 7-day free trial

Subscribe to !! DO NOT SUBSCRIBE - WE HAVE MOVED !! to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Xavier «X» Santolaria
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share