DevOps

Recommendations

Info

The Rugged Manifesto I am rugged and, more importantly, my code is rugged. I recognize that software has become a foundation of our modern world. I recognize the awesome responsibility that comes with this foundational role. I recognize that my code will be used in ways I cannot anticipate, in ways it was not designed, and for longer than it was ever intended. I recognize that my code will be attacked by talented and persistent adversaries who threaten our physical, economic and national security. I recognize these things – and I choose to be rugged. I am rugged because I refuse to be a source of vulnerability or weakness. I am rugged because I assure my code will support its mission. I am rugged because my code can face these challenges and persist in spite of them. I am rugged, not because it is easy, but because it is necessary and I am up for the challenge. -From www.ruggedsoftware.org
DevOps cycle times can seem impossibly, dangerously fast to security veterans, who may hold the belief that code can’t possibly be secured without days-long static and dynamic analysis. But rule number one of achieving a more rugged DevOps process is not taking the ball away and going home when you don’t get your way. “You don’t throw up your hands and say ‘If they’re doing a daily build and it takes four days for feedback, I give up,’” says Josh Corman, CTO at Sonatype. “You ask if there’s some sniff test or some subset of tests we can do that conforms to the compressed cycle time. And maybe once a week, once a month or once a quarter we do a deeper thing.” Don’t Throw Up Your Hands Rather than entrenching themselves against new waves of continuous deployment and automation, security professionals need to “get clever about how to adapt,” says Corman. Organizations are finding as much as a 10x improvement in development speed through continuous delivery. They’re bringing new features to customers more quickly, freeing up resources to develop new lines of business fueled by digital innovation and clearing up their application backlogs. Security should be participating. “If you’re a speed bump, everyone will go around you,” warns Mogull. “Security leaders need to figure out the best way to get into the rugged DevOps process.” SECURITY was named as the number one DevOps obstacle by 28 percent of enterprises
Page 1 and 2: RUGGED DevOps: 10 WAYS TO START EMB
Page 3: Attackers are already using their o
Page 7 and 8: Coming to a mutual understanding co
Page 9 and 10: AT THE SPEED PEOPLE WANT TO MOVE, R
Page 11 and 12: Improve application quality and per
Page 13 and 14: help speak in the universal languag
Page 15 and 16: Take Advantage of “Accidental”

DevOps

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?