Application security and threat modelling

We model the threats to your application, then look at how it is designed and written, not only how it behaves from the outside. We work through it with your developers, so the fixes fit how they build.

Ask about this service All services

Who it is for

  • Your own code handles payments, health records or other sensitive data.
  • You are designing a new product or a major feature and want security in the design.
  • Penetration tests keep finding the same kinds of bug.

What you get

  • A threat model of the application: what could go wrong, where, and what stops it
  • Secure code review findings, with the lines of code and suggested fixes
  • Design recommendations, ordered by risk
  • A session with your developers on the patterns behind the findings

How it runs

  1. Understand

    We walk through the architecture, data flows and riskiest features with your team.

  2. Model threats

    We map what could go wrong and where the controls should be.

  3. Review

    Manual review of the high-risk code, helped by static analysis tools, and a review of the design.

  4. Work through

    We go through the findings with your developers and agree the fixes.

Typical length
Two to four weeks, depending on the size of the codebase. Lengths are typical. We confirm them when we agree the scope.
What we need from you
Read access to the code repositories, any architecture documents, and time with a lead developer.

Frameworks it helps with

  • ISO/IEC 27001
  • SOC 2

Both expect secure development. Threat models and review records show that it happens, not only that a policy says it should.

Tell us what you need, and we will suggest a scope.

Ask about this service