AI Red Team · Module 3 · Identify

Adversary Emulation and Continuous Red Teaming with AI

The lesson covers adversary emulation and continuous red teaming under ID.IM Improvement. Participants build threat-informed, ATT&CK-mapped scenarios, apply the safeguards for AI that executes emulation steps, read the July 2026 incident as a design input, test containment from the adversary's side with conditions, combine periodic threat-led testing with continuous validation as code, and write finding records the blue team can act on.

Lesson 12 of 28Chapter 1290 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Red Team / Module 3 / Chapter 12

Learning objectives

After the lesson the participant can:

Key concepts

Threat-informed emulation
An emulation that asks whether the adversaries most likely to target this organisation, with the capabilities they have shown, would succeed and whether anyone would notice. Each step maps to an ATT&CK technique and names the detection or control it is expected to meet.
Executing AI as a Mode 5 system
AI that executes emulation steps acts with credentials and network access of its own, so it is treated as Mode 5 for the exercise whatever product it is built on, and receives the full containment baseline, including a permission manifest, budgets and an external stop path.
Tempo
Emulating AI-enabled adversaries includes emulating their speed. In Hansa Mutual's exercise the detection fired, but the alert was queued at medium severity and triaged after 47 minutes: the detection was not missing, its severity assumed a human tempo.
Continuous validation as code
Catalogued, benign technique emulations replayed against the estate as regression testing for Protect and Detect. AI plans and interprets; deterministic components act. A failed test is a finding, closed only when the same test passes again.
Finding record
A machine-readable entry naming the plan step and technique, the expected and observed outcomes with times, the control and never an analyst on shift, and the closing action and re-test. A red-team member confirms every finding and the control owner accepts 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 · Sort

Autonomy per emulation step

Sort each step or practice of an authorised emulation by the highest autonomy the chapter allows for AI, or as never permitted.

Interactive exercise 2 · Scenario

A real incident during the exercise

You are the white-team lead of Hansa Mutual's exercise under RoE-HM-2027-TLPT.

Teaching plan

15 minThe teacher presents the path from intelligence to an emulation plan and the two disciplines that keep AI-assisted design honest.
20 minReview the four safeguards and the plan HM-TLPT-2027-S2 at technique level; participants identify which step runs at which level and why.
15 minWork through the July 2026 table of failed controls and the test of containment from the adversary's side, using conditions and not new attack behaviour.
30 minExercise: groups prepare a safe AI-assisted emulation run on paper and write the finding record for a given outcome.
10 minDebrief: each group states the closing control and the re-test for its finding, and how it would enter the continuous validation catalogue.

Discussion

  1. Why does an agent whose task is to probe for weaknesses need containment more, not less, than a production agent?
  2. The finding record names a control, never an analyst on shift. What does that choice protect, and what would be lost without it?
  3. What must a white team understand about AI components to control an exercise in which steps complete in seconds?

Written exercise

Exercise · 30 minutes

Prepare a safe AI-assisted emulation run and its finding

On paper, for an authorised exercise against your own organisation's systems or Hansa Mutual's, write a four-step scenario extract. For each step give the ATT&CK technique identifier, the executor, the autonomy level and the expected detection or control with a time limit; keep it at technique level with no procedures or tooling. Add the safeguards: permission manifest and budgets for the AI component, who issues credentials and their lifetime, egress, shared services, stop conditions, stop-path holders and where the log is kept. Then assume one read-only step completed undetected out of hours and write the structured finding record: expected, observed, control, severity, classification, closing action and re-test.

Deliverable: A four-step emulation plan extract with safeguards and stop conditions, and one finding record with a closing control and a re-test method.

Self-test

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

  1. What is the ceiling the chapter sets for AI on emulation steps that change state on production systems, use harvested credentials or move data?

    Show the answer

    A. Level 1 Assisted at most
    Read-only steps may run at Level 2 Supervised, but steps that change state on production systems, use harvested credentials or move data run at Level 1 Assisted at most, and Level 4 is never used for offensive actions.

  2. In an emulation programme, what is the design response to the July 2026 failure of a package mirror that was also an egress path?

    Show the answer

    C. No shared supporting services between ranges, and every egress route named
    The table maps the mirror to a shared repository, proxy or mirror between ranges, and the response is no shared supporting services with every egress route named.

  3. In continuous validation, which components hold estate credentials and act?

    Show the answer

    B. Deterministic components, while AI only plans and interprets
    The chapter states that AI plans and interprets and deterministic components act: neither the planner nor the evaluator holds estate credentials or generates emulation logic.