Difference between revisions of "Rugged Software"

Jump to: navigation, search
(The Rugged Software Manifesto)
Line 1: Line 1:
<table align="center" border="1" width="80%"><tr><td bgcolor="lightblue">
<div align="center">
<div align="center">
<table align="center" border="1" width="80%"><tr><td bgcolor="lightblue">
Line 31: Line 31:

Revision as of 15:29, 5 February 2010


The Rugged Software 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.


The official announcement presentation


If you want Rugged Software, join us and help define the principles, activities, and technologies that will help others become Rugged too. Our first project is to define how people and organizations can know if they are Rugged

Read Rugged (Blog)

Follow Rugged (Twitter)

Discuss Rugged (Forum)


Contact the Founders (email us)

- Joshua Corman
Enterprise Security Practice Research Director - The 451 Group
- David Rice
Executive Director - The Monterey Group
- Jeff Williams (bio)
CEO - Aspect Security
Chairman - The OWASP Foundation