AI Purple · Module 3 · The Loop Meets AI Systems

Purple for AI Systems and Agents: Attacks on Models and Detections That Catch Them

The lesson applies the purple loop to the organisation's own AI systems and agents. Participants choose scenarios by ATLAS technique against four classes of target, read what each telemetry source can and cannot tell the SOC, write a detection record for an agent that exceeds its permission ceiling, carry an AI red-teaming finding to a detection and a regression case, and distinguish a passing evaluation from a running detection.

Lesson 12 of 29Chapter 1290 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Purple / Module 3 / Chapter 12

Learning objectives

After the lesson the participant can:

Key concepts

Four classes of target
The model and its instructions (AML.T0051 LLM Prompt Injection), retrieval and the index (AML.T0070 RAG Poisoning), tools and actions (AML.T0053 AI Agent Tool Invocation), and data and outputs (AML.T0057 LLM Data Leakage).
Compound system
The unit of test and of detection: the model, the tools it can call, the data it can read and the identity it acts under. The weak link is often not the model but the control or identity around it.
Permission-ceiling breach
A call outside the agent's manifest. A call the policy point denies shows the control worked and is a detection input; an allowed call outside the ceiling is more severe. The two conditions are kept separate in the detection record.
Evaluation versus detection
An evaluation asks whether a version resists chosen cases at a gate; a detection asks whether something is happening in production that should not be and who hears of it. A passing evaluation is not a running detection.
Three families of agent detection
Tool misuse, anomalous retrieval and permission-ceiling breaches. Expected behaviour is written in the manifest, and a baseline is added only for what the manifest cannot state.

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

Telemetry sources and their blind spots

Match each source of platform telemetry with the blind spot the chapter's table gives for it.

Interactive exercise 2 · Scenario

An allowed call outside the ceiling

Apply the chapter's detection record for an agent that exceeds its permission ceiling to an alert at Hansa Mutual.

Teaching plan

15 minThe teacher presents the four classes of target and the three rules for AI-system scenarios: a test range with synthetic data or a catalogued benign form, what can be undone stated before the run, and a stop outside the system.
15 minGroups work through the telemetry table: for each of the six sources, name one thing a detection can read and the blind spot.
35 minExercise: write a detection record for an agent that exceeds its permission ceiling, from a supplied or real permission manifest.
15 minCase reading of FND-NR-2027-019 and DET-NR-0011: a withdrawn page still in the citizen-service index, and the simulation that counted minutes to the alert.
10 minPlenary on evaluation versus detection and on the usage-mode table: why Modes 1 to 3 are detected as the person.

Discussion

  1. Nordvik Region holds a declared, not verified, position for the supplier's scoring component. What would it take, in contract and in test, to move that position to verified?
  2. The chapter concludes that detections cover an agent acting beyond its mandate but not an agent steered within it. What follows for how narrowly a mandate should be written?
  3. When a team reports that its AI system has been red-teamed, which follow-up questions separate an evaluation result from a detection that works today?

Written exercise

Exercise · 35 minutes

A detection record for a ceiling breach

Take the permission manifest of an agent in your organisation, or the description of Hansa Mutual's claims-triage agent, whose tool calls are bound to the market of each claim. Following the practical guide, list each permitted tool, action, resource scope and budget and write one adjacent action that must be refused. Confirm which telemetry must be present: the policy log and the tool-side audit log, each with a maximum silence. Write two separate conditions, A for a policy deny under a ceiling rule and B for an allowed call outside the ceiling, with severity and routing for each, including who may revoke the agent's credentials. State the positive and negative tests, the owner, an approver who did not write the scenario, and the coverage expiry.

Deliverable: A detection record with two conditions, data sources with maximum silence, tests, routing, owner, approver and a 90-day expiry for a priority agent.

Self-test

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

  1. A scenario tests whether a tool can be invoked with parameters the permission manifest does not allow. Which class of target and ATLAS technique does the chapter assign?

    Show the answer

    B. Tools and actions; AML.T0053 AI Agent Tool Invocation.
    A tool invoked with parameters, a sequence or a destination that the permission manifest does not allow belongs to the class tools and actions, identified as AML.T0053 AI Agent Tool Invocation.

  2. Why does the chapter say the agent's narrative is not telemetry?

    Show the answer

    D. Because an agent's summary of its own work is a model output that can be wrong.
    An agent's account of its work is an output of the model and can be wrong or steered. Detection therefore relies on the runtime, the policy decision point and the tool-side audit log, which record the effect whatever the runtime reported.

  3. What does a pass mean for a detection, in the chapter's comparison of evaluation and detection?

    Show the answer

    A. Nothing fired; the absence of an alert is not evidence of absence.
    For a detection, a quiet period means only that nothing fired. Evidence that a detection works is a recent simulation that fired the alert in time, which is why the coverage claim carries a date and an expiry.