Organizations shift to DevSecOps to combine the advantages of Agile development practices, powerful cloud platforms, and shared data infrastructure. But a DevSecOps transformation requires more than just developing skills and adding tools. A cultural shift is needed to make the most of DevSecOps methodology and truly fuse the three pillars of software development, security, and IT operations to deliver superior digital solutions.
Contributors may be asked to take joint responsibility for a result or a KPI that was previously unknown to them or viewed simply as “somebody else’s problem.” At the grassroots level, developers can model behavior but cannot enforce it in others. Middle managers can incentivize, reward, or punish, but ultimately do not set the tone for the entire organization. Those who do must make clear that the DevSecOps shift is both meaningful to the overall mission, and permanent.
This means leading with material support, not just rhetoric. Executive sponsors should be prepared to provide adequate and (if necessary) increased budgets for the talent, skills, and tools identified by practitioners and team leaders as essential to supporting a DevSecOps regime. This includes adequate budgetary support for separate test and production environments, and a cultural understanding that a smooth transition from test to production is a top organizational priority.
Executives should also work with department heads to expand the range of upskilling and learning opportunities to help propagate better understanding of best practices in information security, comprehension of new languages, and opportunities in development and deployment models. As hiring and retention needs change, top leadership should reassess expenditures and standards in those areas as well.
A strong initial gambit is to present security with a way to onboard other contributors into security work while reducing a burden. Consider giving security the opportunity to mentor developers and operations experts on the most effective ways they can contribute to code review and improvement. This can help empower security, with the understanding that security-trained developers can be used to make initial vulnerability assessment a shared responsibility at the earliest possibility.
DevSecOps culture needs technological support to turn a spark into a sustainable engine. Guidehouse is a vendor-neutral DevSecOps practitioner and consultant, so these are just a sample of the effective approaches we have successfully used and implemented for others.
STRIDE — Short for spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege, this acronym provides a handy guide for the six top security attack vectors a bad actor is likely to use. It can be used as a checklist during security test cycles, as well as an accessible reminder for non-security professionals who need to brush up on security principles.
LINDDUN — Similar to STRIDE, the LINDDUN mnemonic targets privacy threats. It stands for linkability, identifiability, non-repudiation, detectability, disclosure of information, unawareness, and non-compliance. Privacy and security threats are frequently but not universally linked with one another, and so familiarizing development professionals with both provides important complementary insight.
PASTA — A process for attack simulation and threat analysis that helps developers structure hypothetical attacks on systems with a seven-step process, from defining a target’s objective to executing a model attack and analyzing the results.
Security Modeling Frameworks Including Cairis, Threagile, and Microsoft Threat Modeling Tool — Although different in execution, a wide variety of systems can help DevSecOps organizations map potential threats and weave protections into ongoing projects.
Code-Sharing and Version Control Platforms Such as GitHub — Infrastructure to help contributors from several disciplines share the same codebase has dramatically improved in recent years. Whichever your organization chooses, keeping your contributors trained and actively participating in the platform should be a top priority.
Code Linting Tools — These check for programming and style errors that can lead to vulnerabilities, loops, or other lurking, hard-to-kill bugs. Today these are frequently integrated directly into the IDEs used by developers.
Continuous Improvement Enablers Such as Pytest, CircleCI, Jenkins, and GitHub Actions — These solutions manage and automatically run unit and integration tests, which can save significant amounts of development time and angst by identifying issues early.
The Threat Modeling Manifesto — This document provides a set of high-level values and principles to consider when deciding which threat modeling methods and tools best fit your organization.
For more guidance on tools and methodologies that can assist with both the technical and cultural challenges of DevSecOps, look to the Open Web Application Security Project (OWASP), a nonprofit organization that provides timely analysis and advice on a wide range of threats.
The cross-pollination in DevSecOps is a matter of people as much as one of process. Bringing the two together effectively takes a cultural commitment from all involved. Contact us to learn more about how to best blend leadership, individual effort, team mindset, and technological advances to meet your DevSecOps goals.
Complexity demands a trusted guide with the unique expertise and cross-sector versatility to deliver unwavering success. We work with organizations across regulated commercial and public sectors to catalyze transformation and pioneer new directions for the future.