Rugged Devops Manifesto

Rugged devops takes the lean thinking and agile mindset that devops embraces and applies it to ruggedizing software and making sure that security is not a post development consideration.

Rugged devops manifesto.

Security innovation speed scale via devsecops. 2016 rugged devops rsa. Rugged is a mindset that brings tougher controls and it thrives in an environment where developers are motivated to continually make code more secure. How did the rugged devops movement originate.

Rugged devops is an approach to software development that places a priority on ensuring that code is secure at all stages of the software development lifecycle. Embracing devsecops to support rugged innovation at speed and scale. In order to help developers realize the importance of rugged software and the path to reach there joshua corman david rice and jeff williams founded the rugged software manifesto. Rewind to 2009 or so and there are the first signs of devops kind of coming through.

Its rugged software manifesto put forward by joshua corman david rice and jeff williams attempts to bring light to what developers and software organizations often don t adequately plan for. Rugged describes software development organizations that have a culture of rapidly evolving their ability to create available survivable defensible secure and resilient software. The rugged manifesto puts it this way. They were talking about a devops manifesto at devopsdays hamburg and it got me to thinking what s wrong with the existing agile development manifesto.

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. Recognizing that software has become a foundation of our modern world and will be attacked by talented and persistent. Rugged devops is the combination of devops with the rugged manifesto. There is the agile operations thing.

Go read the top level of the agile software development manifesto. Rugged organizations use competition cooperation and experimentation to learn and improve rather than making the same mistakes over and over. Can t we largely uptake that as a unifying guiding principle. The fact that their software is likely to be used in ways they don t expect or didn t intend and may be subject to active unrelenting attacks by bad actors.