Threat Modelling Standards

Standard Metadata

• Area: Security
• Owner: Security group
• Last reviewed: 2026-09-09
• Next review due from: 2026-12-01
• Enforcement: Code review
• Status: Active

Overview

These standards define when threat modelling must be performed and how identified threats must be handled, to ensure security risks are identified and addressed early in a project’s lifecycle.

All software projects must undergo threat modelling during discovery · TM-01 · MUST · DEV/TEST

Perform threat modelling during the discovery phase so that security risks inform the architecture and design of the system, and threats are addressed in the backlog.

Guidance for conducting threat modelling can be found here.

Each threat identified during discovery must be managed or accepted · TM-02 · MUST · DEV/TEST

For each threat identified, either manage it if possible, or formally accept the risk. A risk can be managed via one of the following:

• Elimination: avoiding the risk entirely by taking a different approach, e.g. redesigning a feature that adds high/unnecessary risk.
• Transfer: formally passing the risk to the client or a third party.
• Mitigation, often delivered through backlog items, but may also be achieved through system architecture decisions.

Risk acceptance must be agreed by both the client and a technical stakeholder at Audacia. Document the decision and, where a risk is accepted, the rationale and the stakeholders who approved it.