Tools · Module 4 · Securing and Testing

Threat Modelling and Adversary Frameworks

The lesson covers the vocabularies and methods of threat modelling: STRIDE, MITRE ATT&CK, ATLAS and D3FEND, the OWASP lists of AI security risks, the methods that generate and review candidate threats, the threat model as code in its three schemas, and the priority list of AI Purple. Participants learn that a framework names, a model records, and only a test named in the model turns a threat from a belief into evidence.

Lesson 10 of 25Chapter 1075 minutes

Read the chapterThe whitepaperThe slides

All courses / Tools / Module 4 / Chapter 10

Learning objectives

After the lesson the participant can:

Key concepts

Working rule of the vocabularies
STRIDE names the harm at a boundary, ATT&CK and ATLAS name how an adversary produces it, and D3FEND names the class of countermeasure that answers it. ATT&CK itself does not say whether a technique is relevant to a service or whether a detection exists.
Threat model as code
A versioned file of kind ThreatModel that declares assets, trust boundaries, threats and linked controls, with reviewer decisions and a pointer to the test that verifies each threat. Three books define it with different schemas.
Soundness checks
Seven reviewer questions from AI Red Team, each with an automated part: grounding, classification, mitigation family, likelihood basis, impact basis, completeness and stability. Completeness flags a changed boundary that has no candidate threat.
Priority list
An artefact of AI Purple, family PRI: the 20 to 40 ATT&CK or ATLAS techniques that matter most for a service, each with tiers for impact, relevance and uncertainty from 1 to 3, an emulation route and the scenarios that test it.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

What each vocabulary contributes

Match each vocabulary of Chapter 10 with what it contributes to a threat model.

Interactive exercise 2 · Scenario

A control inside the model

Review a candidate threat as the named reviewer, using the soundness checks of the chapter.

Teaching plan

15 minPresent Figure 10.1, from framework to threat model to test, and the table of five vocabularies with the limit of each. Stress pinning catalogue versions.
15 minWalk through the seven soundness checks using the Nordvik Region citizen-service assistant example, including the rejected candidate that stays in the file with its reason.
10 minPresent the priority list and the usage-mode table: who judges and with whose identity. Explain why Mode 5 agents are scored as if an adversary held their permissions.
25 minExercise: participants write three threat entries for one trust boundary and review a neighbour's entries against the soundness checks.
10 minDebrief: which threats had no verifying test, and which would go on a priority list first.

Discussion

  1. AI Purple calls the ATT&CK Navigator a sensible tool for planning and a poor tool for asserting. What does a coloured cell fail to tell a board?
  2. Why does the series keep a rejected candidate threat in the model file with its reason instead of deleting it?
  3. The OWASP lists describe observed weaknesses and so describe the past. How should a team use them without mistaking them for a complete threat model?

Written exercise

Exercise · 25 minutes

Three threats at one boundary, reviewed

Choose one trust boundary in a system you know, or the boundary between the retrieval sources and the citizen-service assistant of Nordvik Region. Write three threat entries at the level of design, with no attack content: the STRIDE category, the ATT&CK or ATLAS technique identifier you would look up and pin, the control with its owner, and the test that would verify it. Mark where a control acts outside the model. Then exchange entries with a neighbour and apply four of the soundness checks: grounding, classification, mitigation family and completeness. Record each check as passed or failed with one sentence of reason.

Deliverable: Three threat entries with category, technique reference, owned control and verifying test, plus a neighbour's four-check review of each.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. Which failure does the completeness check catch that a reviewer reading only the candidate threats would never see?

    Show the answer

    C. A boundary that changed in the pull request without any candidate threat
    The completeness check asks whether every boundary changed in the pull request has threats considered; its automated part flags changed boundaries without candidates, a gap invisible to someone who reads only the candidates.

  2. What limit does the series state for MITRE ATLAS when it is used in a threat model?

    Show the answer

    A. It is young and still changing, so identifiers are pinned and checked against a named data release
    ATLAS is described by the originating book as young and still changing, so identifiers must be pinned. The other limits belong to D3FEND, attack trees and STRIDE respectively.

  3. How are Mode 5 Autonomous production agents treated when a threat model is written?

    Show the answer

    B. As well-meaning insiders that can be manipulated, with permissions scored as if an adversary held them
    The chapter states that Mode 5 agents are modelled as well-meaning insiders that can be manipulated or compromised, so their permissions are scored as if an adversary held them.