All courses / AI Purple / Module 2 / Chapter 5
Learning objectives
After the lesson the participant can:
- Explain what each of the four inputs to a scenario supplies and why the proposer is not the selector.
- Rank candidate techniques by impact, relevance and uncertainty about the defence into priority tiers.
- Draft a scenario record with source, expected outcome per layer, safety class, evidence rule and exclusions.
- Review a scenario library for selection bias and record exclusions in an exclusion register.
Key concepts
- Priority technique
- A technique chosen for regular testing by the sum of three coarse tiers: impact on critical assets, relevance to this organisation or sector, and uncertainty about whether the defence would stop it. The result is an order and a tier, with reasons.
- Scenario record
- The testable statement built from one or more techniques and held as code (SCN-NR, SCN-HM): identity and owner, source, technique set and parameters, expected outcome per layer, safety class and environment, evidence rule, exclusions and sensitivity.
- Scenario curator
- An agent or drafting assistant that reads intelligence, register entries and incident reviews and proposes scenario drafts at Level 1 Assisted. A named person accepts each draft, sources are treated as untrusted input, and the reviewer's work is measured.
- Selection bias
- The tendency of a library to fill with scenarios that are cheap to run. The guards are gaps reported as gaps, a reserved share for hard techniques, a check of the curator's mix and a protected class of human-authored scenarios.
- Exclusion register
- The record of what is deliberately not tested: out of scope, unsafe, unauthorised or not worth testing, each with the reason, the decider and a review date. An excluded technique is untested, and untested is not covered.
Interactive exercises
Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.
Interactive exercise 1 · Sort
What not to test, and why
Each line describes a scenario that stays out of a library. Sort it into the category of exclusion the chapter would record for it.
Interactive exercise 2 · Scenario
A hard technique on the priority list
Apply the chapter's rules on selection bias and exclusions to Nordvik Region's priority list.
Teaching plan
| 15 min | The teacher presents the four inputs and the four vocabulary rules, using T1110.003 and T1110.001 to show why sub-techniques matter where the detection differs. |
| 15 min | Worked reading of PRI-NR-2028-01 and of the two scenario records SCN-NR-0001 and SCN-HM-0007; participants name what each record says and what it deliberately omits. |
| 35 min | Exercise in groups: build a first priority list for one service and write one scenario record from its top entry. |
| 15 min | Groups check one another's lists for selection bias: which entries can run benign and tagged, which need a mirror or the red team, and which are reported as gaps. |
| 10 min | Plenary on the curator at Hansa Mutual: 17 drafts, six accepted, none on T1486 or T1490, and what that confirms about drafts drawn from public reporting. |
Discussion
- At Hansa Mutual the detection-engineering team may nominate techniques but cannot remove one. What would the priority list look like after two years if the tested side could remove entries?
- Nordvik Region reported T1190 and T1486 as untested when their mirror evidence had expired. What pressures push an organisation to report such techniques differently?
- The curator's proposals favoured well-documented techniques. How would you design the review so that a reviewer who sees mostly good drafts still reads each one?
Written exercise
Exercise · 35 minutes
A first priority list and one scenario record
Choose one service of your own organisation, or Nordvik Region's benefits-triage service. Following the practical guide, collect candidate techniques from intelligence tags, your own incidents and findings, and the exposure of the service. Give each candidate an impact tier, a relevance tier and an uncertainty tier from 1 to 3, sort by the sum, break ties by uncertainty and cut the list. For the first twenty entries record how the technique can be emulated safely and mark the hard ones. Then write a scenario record for the top entry by ATT&CK identifier only: source, parameters, expected outcome per layer, safety class, evidence rule and exclusions. Include no procedure.
Deliverable: A priority list with tiers, reasons, owners, emulation routes and a review date, plus one scenario record at the level of identifier and parameter.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
Which three factors does the chapter combine to rank priority techniques?
Show the answer
C. Impact, relevance and uncertainty about the defence.
The ranking sums three coarse ordinal tiers, impact, relevance and uncertainty about the defence, to give an order and a tier with reasons. The chapter says explicitly that techniques are not chosen by novelty.What is the ceiling for AI at P1 Target, and who decides what enters the scenario library?
Show the answer
A. Level 1 Assisted; a named owner accepts or rejects each draft.
The chapter sets the ceiling at P1 Target at Level 1 Assisted: a proposal made by a system is not a decision, and a draft enters the library only when the named owner accepts it. Scenario selection is not delegated to a Mode 5 agent.How does the chapter treat a priority technique that has been placed on the exclusion register?
Show the answer
D. As untested, and untested is not covered.
All four categories of exclusion end in a record with a reason, a decider and a review date. The chapter's rule is that an excluded technique is untested, and untested is not covered.