AI Purple · Module 2 · The Stages of the Loop

Rules of Engagement and Safe Emulation: Scope, Blast Radius and the Stop Path

The lesson treats rules of engagement as the first design question of the loop. Participants separate the rules of engagement from the mandate manifest and the decision record, express scope as code that a policy decision point enforces, assign safety classes S1 to S4, record third-party consent and the handling of personal data, and design a stop path that runs outside the emulating system and is drilled. The white team owns the manifest.

Lesson 6 of 29Chapter 690 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Purple / Module 2 / Chapter 6

Learning objectives

After the lesson the participant can:

Key concepts

Rules-of-engagement manifest
A signed, versioned file (RoE) that says what may be done to which systems, when, with whose consent and under what stop conditions. It belongs to the exercise or programme and is enforced by a policy decision point outside the agent.
Scope as code
Scope in a form read at every action: default deny, exclusions checked before inclusions, the manifest outside the agent's reach, and refusal tested by three dry runs against an out-of-scope target, after the window and with a stop flag set.
Safety classes S1 to S4
S1 is benign, reversible and tagged; S2 is reversible with bounded side effects; S3 needs realistic state or may disturb service and never runs in production; S4 has impact or irreversible effect, or involves staff or third parties.
Stop path
The mechanism, held by named people outside the emulating system, that denies further actions at the policy point, revokes the system's credentials and egress, and invokes the clean-up. It needs no approval to use and is drilled.
White team
The control group that governs the exercise: it owns the manifest and its versions, holds or delegates the stop path, runs deconfliction and keeps the record. It lies outside both the red team and the SOC so that it can stop either.

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

Safety classes S1 to S4

Sort each property or rule into the safety class of Hansa Mutual's class table that it belongs to.

Interactive exercise 2 · Scenario

Real personal data in an authorised exercise

Apply the chapter's rules on data and on the stop path to an authorised exercise at Nordvik Region.

Teaching plan

15 minThe teacher explains why the rules come before the scenario and walks through the three documents, with the rule that the lowest ceiling governs.
15 minParticipants sort twelve short scenario descriptions, given by technique identifier only, into safety classes S1 to S4 and state the environment and ceiling for each.
35 minExercise: draft a rules-of-engagement manifest for a three-scenario exercise at Nordvik Region or in the participant's own organisation.
15 minTabletop on the stop path: the teacher raises a synthetic stop condition and groups say who acts, what is revoked and what is cleaned up, without the emulating system.
10 minClose on third parties, personal data and staff: consent in contracts and notices, synthetic data by design, and S4 for any scenario involving people.

Discussion

  1. The chapter says a control that has never refused anything has not been shown to work. Which controls around your own testing have never been seen to refuse?
  2. Nordvik Region's risk is a manifest signed once and treated as a formality; Hansa Mutual's is a pipeline running inside rules nobody has re-read. Which is closer to your organisation, and what keeps the rules alive?
  3. A managed provider is on the blue side of an exercise and also holds a stop path. How should the two roles be reconciled in a contract?

Written exercise

Exercise · 35 minutes

A manifest a policy point can enforce

Write a rules-of-engagement manifest for an authorised exercise of three scenarios against your own organisation's systems or Nordvik Region's benefits-triage service. Follow the ten steps of the practical guide: name the question and the scenario identifiers; list exclusions first, then inclusions with their owners; give permitted techniques by ATT&CK identifier with a safety class each; set the window, the blackouts and who may shorten the window; set the autonomy ceiling per class; require short-lived credentials, tagging and synthetic accounts; record third-party consent; write machine-detectable stop conditions with named holders and deputies; and state data classification, legal basis and the rule for real personal data met by accident. Write every line so that a policy point could evaluate it.

Deliverable: A signed-ready manifest of one to two pages, with the three dry-run refusals and the stop-path test listed as conditions of its definition of done.

Self-test

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

  1. A manifest allows Level 3 Bounded for class S1 scenarios, but the agent's mandate allows only Level 2 Supervised. At which level does the agent run?

    Show the answer

    B. Level 2 Supervised, because the lowest ceiling governs.
    The chapter keeps the rules of engagement and the mandate manifest apart and states that the lowest ceiling governs. With a mandate at Level 2 Supervised, the agent runs at Level 2 whatever the manifest would allow.

  2. What does the stop path do, in order, when a halt is called?

    Show the answer

    D. It denies further actions, revokes credentials and egress, and invokes the clean-up.
    The stop path sets the stop flag at the policy point, revokes the emulating system's credentials and egress and triggers the deterministic clean-up. The emulating system takes no part in any of the three, and stopping needs no approval.

  3. Which safety class does the chapter assign to a scenario that involves staff, such as a social-engineering test?

    Show the answer

    A. S4, with AI limited to Level 0 Advisory and named people acting.
    Exercises that involve people are class S4. For S4 the ceiling is Level 0 Advisory: AI may plan only, and a named operator acts with per-step white-team approval, under the agreements with employee representatives.