Secure Code Review and Application Security
Threat Modeling
We identify abuse cases for a new product or feature at the design stage, before any code is written. Security requirements are defined before development begins.
What it is
Threat modeling systematically examines how a system could be abused based on its design. First, a data flow diagram is created and trust boundaries are defined. Each flow is analyzed using a method such as STRIDE for spoofing, tampering, or privilege escalation. The result is a set of security requirements that developers can implement and test.
Scope
- Data flow diagram and trust boundaries
- Working sessions with product, development, and operations teams
- Abuse cases prioritized by likelihood and impact
- Design decision and security requirement for each significant case
- Requirements entered into your issue tracker as tickets and test cases
The need
When organizations need it
- When designing a new API to be opened to partners.
- When adding payment or AI features to an existing product.
- When a tender requires security requirements to be defined at the design stage.
Method
How we work
-
Preparation
We review architecture documents and user scenarios and identify session participants.
-
Model
We create the data flow diagram with your teams and define trust boundaries.
-
Threats
We analyze each flow with a structured method and prioritize abuse cases.
-
Requirements
For each significant case, we document the design decision and a testable security requirement.
Outcome
What you have at the end
You receive your product's threat model and the resulting security requirements. The model is delivered in a format your teams can update as the product evolves.
Frequently asked questions
How long does threat modeling take?
A few sessions are usually sufficient for a single feature. For a full product, the duration depends on the number of components and integrations.
Can our teams do this themselves?
Yes, that is one of the objectives. We create the initial models together and provide the template and method for your teams to use for future features.
Can it be done after the code is written?
Yes, and it reveals risky design decisions in existing systems. The greatest benefit is achieved while the design can still be changed.
Secure Code Review and Application Security
Other services in this area
Let's talk about this service.
Tell us briefly what you need. We will agree on the scope and timing together in the first meeting.
Schedule a Meeting