| 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. As more organizations embrace the concepts of containerization and continuous software development, code is being re-used in unanticipated ways. The rugged DevOps approach seeks to develop secure code on a regular basis and reduce the need for developers to have to revise code once it has been released. Rugged DevOps is sometimes referred to as DevSecOps or Secure DevOps, but not everyone agrees the three terms are synonymous. While all three approaches value security as a component of the development process, the rugged DevOps approach consistently makes "security first" a priority, shifting automated penetration testing left to the beginning of each project and continuing it throughout the entire software development lifecycle. The rugged approach requires programmers and operations team members to automate testing throughout the software development lifecycle. To sync security with DevOps cycles, a rugged DevOps team must log integration and delivery processes at a very granular level, so security issues can be identified as they arise. For example, the more granular the records are, the easier it becomes to identify security holes that might pose compliance risks. Both Jira and Cucumber are popular tools for keeping logs in rugged DevOps environments. For automated DevOps and security testing, there's a large portfolio of product types, including static application security testing, dynamic application security testing, interactive application security testing and runtime application security testing. Vendors include Contrast Security, Fortify, Veracode and Waratek. | 
Posts
No comments:
Post a Comment