AI Blue · Module 4 · The Team in the Organisation

Operating Models: In-House, Managed, Hybrid and Sovereign Security Operations

The lesson treats the operating models open to a European organisation, in-house, MSSP, MDR and hybrid, with follow-the-sun and sovereign variants, across all five blue team functions. Participants learn what AI changes in the choice, what must be kept in every model, how the six terms of annex MS-2 make a provider's AI visible, what DORA, NIS 2 and the GDPR ask of the arrangement, how sovereignty is tested, how to procure on evidence and how to test exit.

Lesson 16 of 28Chapter 16105 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Blue / Module 4 / Chapter 16

Learning objectives

After the lesson the participant can:

Key concepts

Hybrid model
The organisation keeps some functions and buys others. In the Nordvik pattern it keeps detection content, the incident commander role and the case record, and buys round-the-clock monitoring and first triage.
Unrecorded delegation
The third change AI brings to operating models: when a provider's AI closes or acts on the customer's behalf, it does so at a level of autonomy nobody on the customer's side has decided, and the customer's record does not show who.
Six terms of annex MS-2
Levels and actions, quarterly sampling, audit rights, evidence for every closure or action, tuning and test rights, and 20 working days' notice of model change, plus conditions for data and exit.
Four properties of sovereignty
Sovereignty as verifiable properties, not a location: knowing where workloads run, which law governs them, being able to move them and being able to continue if a provider fails.
Tested exit
A one-day switch-off in which the customer revokes the provider's credentials, runs the manual queue from the day-one runbook and measures time to first triage of a seeded alert, visible sources, untakeable actions and time to restore.

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

Sovereignty as four testable questions

Match each of the four properties of sovereignty with the question the chapter asks of a managed SOC service under it.

Interactive exercise 2 · Scenario

A new closure class by newsletter

Apply the terms of annex MS-2 as the chapter sets them out.

Teaching plan

15 minTeacher names the four models and two variants and presents the table of who does what in each, with the three changes AI brings.
15 minGroups argue for each of the five retained items in turn: what the organisation loses if it gives that item to a provider.
40 minExercise: groups write an annex for a managed-service agreement following the nine steps of the practical guide, using Nordvik Region or their own provider.
20 minProcurement role play: one group acts as buyer with the five evidence points, another as supplier answering the statement of AI and the seeded replay.
15 minDebrief on sovereignty, model origin as a question separate from hosting, and the comparison that Nordvik buys time while Hansa buys jurisdiction.

Discussion

  1. A model that keeps detection content in the provider's platform produces an estate only the provider can read, whatever the contract says about ownership. How would you test ownership in practice?
  2. Nordvik Region's six analysts cannot run the manual queue for a full night, so its exit test is partial. What should an organisation do when it fails its own exit test?
  3. The chapter's procurement criteria reward the ability to be checked, with price weighted so that it cannot outweigh the others. What resistance would you expect, and from whom?

Written exercise

Exercise · 40 minutes

The annex that makes a provider's AI visible

Write an annex to a managed-service agreement for your own provider or for Nordvik Region's agreement NR-2025-044. First write the questions you would put to the provider in writing: which AI acts, on which classes, with what actions, at which model version and in which location. Then list the classes and set a level for each, with Level 3 Bounded only for narrow, reversible classes whose evidence to close is stated in fields. Name the evidence to close, set the quarterly sample, write the notice period for model, rule or threshold changes, the stop right with a time target, the audit and data terms and the exit schedule. Name the list of what the provider's AI may never do.

Deliverable: A draft annex with the six terms, a class list with levels and evidence fields, a never list, a stop right with a time target and an exit schedule.

Self-test

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

  1. Which of these does the chapter say must stay with the organisation whichever operating model it chooses?

    Show the answer

    C. Detection content, with its logic in a repository the organisation owns
    Detection content, decision rights for containment and disclosure, the case record, the ability to leave and enough skill to supervise stay with the organisation. Monitoring and first triage are what a hybrid model buys.

  2. What does the sixth term of annex MS-2 require?

    Show the answer

    A. 20 working days' notice before a model, rule or threshold affecting closure changes
    The sixth term is notice of model change: 20 working days before a change that affects closure or action, with a shorter after-the-fact notice for emergency security changes.

  3. Why does the evidence to close for bulk mail in annex MS-2 include the gateway click log?

    Show the answer

    B. Because the closure of CASE-NR-0231 rested on a sender-reputation score although a recipient had clicked
    The annex carries the lesson of the Region's own case: a closure that rests on a classifier score alone is the pattern of CASE-NR-0231, so the evidence fields are taken from last year's failures.