All courses / AI Red Team / Module 1 / Chapter 4
Learning objectives
After the lesson the participant can:
- Compare the three placements of security AI and state what each loses.
- Explain why proposal, approval and execution of an action are kept in different components.
- Classify security data into the chapter's four classes and derive the permitted hosting for models.
- Design the placement of a new security AI capability, including range, identity, containment profile and untrusted inputs.
Key concepts
- Security AI is AI
- A triage assistant, a containment agent and an adversarial test harness all call models, read content they did not write and invoke tools. They run on the governed AI platform under the same controls as other AI systems, not beside it.
- Proposed, approved, executed
- An action is proposed in the agent layer, approved in the approval service outside the agent, by a person at Level 1 and Level 2 or by a codified playbook at Level 3 Bounded, and executed by the tool gateway, which re-checks the policy decision.
- Classes of security data
- Public intelligence, restricted intelligence, operational telemetry and sensitive case data, classified by content and not by the tool that produced it. The gateway reads the class and routes the request only to serving the policy permits; sensitive case data is self-hosted only.
- Separated ranges
- Production estate, blue tooling, red range and AI test range, each with its own network boundary, identities, credentials, tooling and evidence store. The red range has no standing route into production or blue tooling, and the AI test range runs copies, never production instances.
- Findings are the only route
- The one sanctioned route from the red range and the AI test range into blue tooling is the finding, a versioned record closed by a control and verified by re-running the scenario. Offensive tooling never crosses, but the detections derived from it do.
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 runs in which range
Sort each item into the range where the reference architecture places it.
Interactive exercise 2 · Put in order
Six layers from evidence to action
Put the six layers of the AI-enabled security operation in the order of Figure 4.1, from evidence to action.
Teaching plan
| 15 min | The teacher shows how security AI arrives by side doors and compares the three placements; participants identify which placement each of their current capabilities has. |
| 15 min | Walk through the six layers and the containment profile of HM-SEC-001: no credentials in the sandbox, alert content as untrusted data, an out-of-band stop path. |
| 10 min | Review the data classes with DORA Article 30(2)(b) and NIS 2 Article 21(2)(d) as architectural implications, then the four ranges and their routes. |
| 25 min | Exercise: groups place a new security AI capability on the reference architecture using the eight steps of the practical guide. |
| 10 min | Groups state one chaos experiment that would verify their placement, with a steady-state hypothesis, and compare. |
Discussion
- Why does the chapter argue that security AI needs the platform's controls more, not less, than other AI systems?
- The chapter says a capability that needs both a defensive and an offensive range is two capabilities. What practical difficulties does that separation create, and why accept them?
- In what sense is keeping alerts on controlled capacity a defence and not only a compliance matter?
Written exercise
Exercise · 25 minutes
Place a security AI capability on the reference architecture
Take a capability your organisation plans or runs, or Nordvik Region's SOC triage assistant NR-SEC-001. Follow the practical guide: name the capability, its usage mode and starting autonomy level; classify each data source by its highest class and derive the permitted hosting; choose the range; list read tools and action tools separately; write the main lines of the containment profile, noting any departure from the defaults of five-minute tokens, no standing privileges, default-deny egress, protected artefacts and an out-of-band stop path with named holders; declare untrusted inputs and where instructions may come from; and state the pre-production test, including indirect injection through representative alert content.
Deliverable: A placement record covering mode and level, data classes and hosting, range, tool lists, containment profile lines, untrusted inputs, the promotion test and the decision record that would accept it.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
What is lost when security AI is placed beside the platform, with the security team running its own model endpoints and direct API keys?
Show the answer
C. Gateway, policy point, evidence and containment
The placement table says that beside the platform the gateway, policy point, evidence and containment are lost, and the security estate becomes the least governed AI in the organisation.Under the default hosting in the chapter's class table, where may a model run on sensitive case data such as special-category data or employee investigations?
Show the answer
A. On self-hosted serving only
The class table gives self-hosted only as the default for sensitive case data, and the gateway routes by classification whatever the analyst would prefer.Why do Mode 3 Agentic work tools used by detection engineers and red-teamers run only in isolated ranges?
Show the answer
D. Because an agent with an engineer's credentials should not hold any that reach production
The chapter states that an agent acting with an engineer's credentials should not hold credentials that reach production, so Mode 3 tools are confined to isolated ranges.