Security practitioners, implementers of \u00a0at Secure Development Life cycle (SDL), I urge you ask yourself the following question:<\/p>\n
What am I doing to enable developers to innovate securely<\/em> while they are designing and writing software?<\/strong><\/p>\n The developer-centric manifesto attempts to crystalize this question into the follow precepts:<\/p>\n As I wrote in\u00a0Core Software Security<\/a>,\u00a0<\/em>developers, development teams must execute the SDL. Delivery of security is not executed by security people. Besides, there aren’t enough of us to scale to the tens of thousands of developers who design, code, and validate the millions of lines of code upon which we in the Internet Age depend.<\/p>\n We can let security’s dependence on developer execution lead to ever more restricting policies, standards, and mandates – but in doing so, we strangle the very innovation that is our collective lifeblood, organizational mandates, and upon which we have become dependent.<\/p>\n Or, we can<\/p>\n Let’s start a movement. You have an open invitation to contribute, refine, and practice developer-centric security.<\/p>\n cheers,<\/p>\n \/brook<\/p>\n","protected":false},"excerpt":{"rendered":" Security practitioners, implementers of \u00a0at Secure Development Life cycle (SDL), I urge you ask yourself the following question: What am I doing to enable developers to innovate securely while they are designing and writing software? The developer-centric manifesto attempts to … Continue reading \n
\n