© 2018 RSM US LLP. All rights reserved.
Secure Software Development Life Cycle (SecSDLC)
A secure software development life cycle (SecSDLC) process enables organizations to fully integrate security into their existing SDLC from initial development through maintenance and obsolescence.
Business software applications make enticing targets for attackers as many of these applications transmit and/or process sensitive data, such as personally identiﬁable information (PII), credit cards and other proprietary data. To protect this information from attackers, applications should be built with security industry standard practices in mind. In addition, various compliance frameworks such as the payment card industry (PCI) data security standards (DSS) require that applications be developed under the guidance of a formalized secure software development life cycle (SecSDLC).
The practice’s main objective is to prevent common vulnerabilities—such as those listed within the Open Web Application Security Project (OWASP) Top 10—from ever appearing in a production environment. A SecSDLC process enables your organization to meet or exceed these requirements and protect your data.
RSM’s SecSDLC development assistance is designed to create effective processes that help clients avoid security ﬂaws and mitigate risks throughout the entire development process. These processes can be applied to any software development methodology, including Waterfall, Spiral or Agile. Additionally, this process can cover internally developed, commercial, open source and outsourced applications.
A SecSDLC will present comprehensive, repeatable and consistent procedures for integrating security into your application development process. It will involve:
- Deﬁning requirements
- Designing the application architecture
- Building and testing the application
- Deploying to production
- Maintaining the application in production
Implementing a SecSDLC at the earliest stages of application development is more cost effective than attempting to remediate issues after the application goes into production, or, worse, after an attacker has already exploited them.