Answer yes if your organisation conducts threat modelling when designing each app or system. Describe in the notes how threat modelling is integrated throughout your SDLC or upload a supporting document (for example, a template threat modelling report) as evidence.
What is it?
Threat modelling is a proactive security exercise to understand the mindset of a malicious actor and how they might attempt to exploit an application or system. Modern security best practices recommend threat modelling to be integrated throughout the entire Software Development Life Cycle (SDLC). This ensures that as code changes and new features are added throughout the application’s lifespan, the security posture evolves alongside the application.
Why should I have it?
Unlike input/output validation, vulnerability scans, and other code-related security checks, threat modelling typically applies primarily to the architectural aspects of software. While the former helps protect individual functions by making sure they are used as intended, ongoing threat modelling helps guide the overall architectural design and identify the individual functions to be checked and validated.
Continuously updating your threat model ensures that your security controls remain up to date against an ever-evolving set of tools, tactics, and procedures used by malicious actors.
In order to implement effective threat modelling, any software development project should have defined security requirements as per your existing policies. The requirements brief should include all types of data used by the application and all the requirements of the application itself in order to properly assess the security risks.
A threat modelling approach that suits your project and development framework should be defined and then applied in an iterative and continuous fashion throughout the SDLC. This ensures that the architecture remains secure against current and emerging threats even as the application changes.
This process should be repeated for every project and major update until a final secure architecture is agreed and all important functions are validated for security robustness.There are numerous consultancies or individual consultants that will be able to assist in crafting a policy and implementing a secure SDLC that includes continuous threat modelling in a way that meets your business and technical requirements.
If you would like to contribute to this article or provide feedback, please email knowledge@riskledger.com. Contributors will be recognised on our contributors page.