Rugged DevOps ensures security in coding from the start of the development process, with the aim of in creating solid and secure code with fewer revisions. The methodology rebalances the priorities of development, IT operations and security.
Rugged DevOps takes the lean thinking and Agile mindset that DevOps embraces and applies it to "ruggedizing" software. In the context of security, the process of software development is reexamined and security is built in into the development process rather than operating with security as a secondary or post-development consideration. To do so, security staff works in tandem with developers to speed overall development safely through a competitive, collaborative environment between the teams. The code is “ruggedized” by ensuring it is secure throughout the process, resulting in secure code from the start.
Rugged DevOps is often used in software development for secure environments or highly-targeted code. With the increasing use of continuous software development, more code is produced and used for longer than expected or in unintended ways. Rugged DevOps allows for secure code to be produced more reliably with fewer revisions.
Rugged DevOps is also often referred to as DevSecOps or Secure DevOps, but the three are not the same. While both DevSecOps and Secure DevOps tend to rely on automation tools to test and secure code at the end of version development, the rugged DevOps process starts with security as a priority, pen tests throughout development and tends to produce a hardened end product.