Use case 1
Application architecture threat modeling
- Application architects
- AppSec teams
- Software engineering teams
The situation
A team is designing a new application, or a significant feature, and wants to know what could go wrong before code is written. Application threat modeling looks at the components, the data flowing between them and the trust boundaries they cross, then asks which threats apply at each point and what should be done about them.
- Typical inputs
- OpenAPI / SwaggerVisiodraw.ioGitHubDescription
- Typical framework
- STRIDE, for its six general threat categories
- Who decides
- Your reviewers accept, adjust or reject each finding
How Astrix supports it
Import the API specification, a Visio or draw.io diagram, or the GitHub repository, or describe the application in plain language. Run the STRIDE analyzer, or another supported framework, to generate a draft threat model. Your team then reviews the findings, each scored with CVSS, mapped to CWE and MITRE ATT&CK, and accompanied by mitigation guidance.