Threat Modeling for Agile Teams
The so-called shift-left testing is an increasingly popular requirement for developing secure software. It ensures the earliest possible consideration and review of security aspects within the software development life cycle.
Why threat modeling
There are a number of classical frameworks implementing shift-left testing, such as OWASP, SAMM, or Microsoft SDL, and others. Still, we believe threat modeling to be one of the most practically useful and efficient solutions for Agile teams.
That’s why at Iterasec, we offer unique threat modeling to help them:
- kick-start threat modeling
- mitigate the identified risks
- educate them on supporting this process on their own
How it works
We start with a kick-off meeting, followed by or combined with a threat modeling workshop. An experienced threat modeling expert from Iterasec is participating in every stage, supporting and guiding the team.
1. The kick-off meeting
- Members of the architecture and dev team
- Iterasec expert
- To explain threat modeling concepts and implementation options.
- To ask questions about the agile process and your product.
- To come up with the most efficient threat modeling process for your team.
2.Threat modeling workshop
- Key members of the team working on the functionality
- Iterasec expert
- To brainstorm on the possible threats
- To estimate possible risk levels.
- To decide which security requirements or controls to apply.
Benefits
So, why threat modeling? The answer is simple: it allows making rational security decisions, resulting in a secure and trustworthy product. Moreover, threat modeling ensures:
Fewer security issues by design and, as a result, saved costs on potential criticalsecurity issues
Immediate understanding of your product security posture and relevant threats
Boosted security awareness of your team
In other words, threat modeling is a critical component of the security development process.