Tools · Module 4 · Securing and Testing

The Verification Loop: Purple, Chaos and Coverage Tools

The lesson covers the tools that turn a written finding into a verified control: the purple loop with its five stages, the purple session plan and record, the coverage record and its status rule, the regression case, the five kinds of independence between tester and tested, and security chaos engineering with its experiment manifest and safety-boundary policy. Participants learn to replace a heat map with records that carry age.

Lesson 14 of 25Chapter 1490 minutes

Read the chapterThe whitepaperThe slides

All courses / Tools / Module 4 / Chapter 14

Learning objectives

After the lesson the participant can:

Key concepts

Purple loop
A method of AI Purple with five stages, P1 Target, P2 Emulate, P3 Observe, P4 Improve and P5 Verify, in which every finding ends as a verified control, detection and re-test with evidence, and closed findings return as regression cases.
Coverage record
An artefact, family COV, stating per technique and environment what was tested, when, how, with what outcome and when the evidence expires. It is derived, and its status is computed from its fields and never edited by hand.
Regression case
A closed finding kept as a repeatable test, family REG, with the base scenario, variants, a held-out variant, a negative control and a cadence. Re-testing only the exact scenario protects the path and not the technique.
Independence between tester and tested
A principle of AI Purple with five kinds of shared dependency that can hide failure: model, data, authorship, vendor and time. Each has its own control, and the kinds are not interchangeable.
Security chaos experiment manifest
A catalogue entry, family SCE, that injects a condition, not an attacker technique, to verify one control property, with rollback, blast radius and failure routing. On failure a finding goes to the purple backlog.

Interactive exercises

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

Interactive exercise 1 · Put in order

The five stages of the purple loop

Put the stages of the purple loop in the order that AI Purple, Chapter 4, fixes.

Interactive exercise 2 · Match

Shared dependencies and their controls

Match each kind of independence between tester and tested with the control the chapter's table gives for it.

Teaching plan

15 minPresent Figure 14.1, the purple loop with the coverage record, independence statement and stop path outside it. Explain why the expectation is written, hashed and sealed before the run.
20 minRead the coverage record COV-HM-0112 and the status rule in which the first match wins. Participants compute statuses for three invented field combinations.
15 minTeach regression cases and independence, then security chaos engineering: the steady-state hypothesis, the experiment SCE-DE-014 on a silent log source, and the safety-boundary policy.
30 minExercise: participants convert a small heat map into coverage records and write one regression case and one chaos hypothesis.
10 minDebrief: how many cells of each heat map survived as tested with unexpired evidence.

Discussion

  1. Nordvik Region's coverage page reports nine techniques as five tested, two asserted by the provider and two not tested. Why is this page more useful than a fully green map?
  2. A re-test run straight after the fix shares a dependency with the fix in time. Which of your current re-tests would fail the independence table, and on which kind?
  3. The chapter says the chaos platform that injects the conditions is itself a tier-0 asset that is tested. What follows for who may operate it and how its credentials are issued?

Written exercise

Exercise · 30 minutes

From heat map to coverage records

Take five techniques your organisation currently shows as covered, or five priority techniques for the benefits-triage service of Nordvik Region. For each, write a coverage record in outline: technique and knowledge-base version, environment, what was tested, when, by which method, with what outcome, who other than the detection owner verified it, and when the evidence expires. Give each a status using an ordered rule in which the first match wins: untested, failed, implemented-unverified, asserted, expired, verified. For one tested technique write a regression case with three variants and a negative control. For one untested technique write a steady-state hypothesis for a benign chaos experiment, with rollback and stop holder.

Deliverable: Five coverage record outlines with computed status and expiry, one regression case and one chaos hypothesis with rollback and stop holder.

Self-test

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

  1. What is the distinguishing feature of the purple session method of AI Purple?

    Show the answer

    D. The expectation is written, hashed and sealed before the run
    The expectation is written, hashed and sealed before the run, so that the session compares a result with a commitment, not with a memory. The charter excludes audio or video recording.

  2. How does the coverage-status rule file treat a manual override of a computed status?

    Show the answer

    A. No override is allowed; an extension is a recorded decision with a named person, a reason and a new date
    In the rule file the first rule that matches wins and no override is allowed. If evidence must be extended, that is a recorded decision with a named person, a reason and a new date.

  3. What does a security chaos experiment manifest inject, according to AI Red Team?

    Show the answer

    B. A condition, such as log forwarding from one host stopping
    The entry injects a condition, not an attacker technique. In the example, log forwarding from one host stops, and the hypothesis is that the security operations queue shows a silent-source alert within the stated time.