All courses / AI Blue / Module 4 / Chapter 19
Learning objectives
After the lesson the participant can:
- Map the instruments and articles the chapter names to what a blue team must be able to show for each
- Build an incident clock with two awareness timestamps, an owner and a deputy per clock and reasons for closing
- Explain what a management body may delegate and what it may not, as the chapter reads NIS 2 Article 20 and DORA Article 5
- Design the separation between the evidence view and the management view of an analyst action log
Key concepts
- Reporting clock
- The interval between the moment an organisation is regarded as aware of an incident and the moment each notification is due. One incident can open several clocks that start at different moments and have different owners.
- Two awareness timestamps
- The case system writes first_flag_at when a detection fires or a provider's page arrives and human_confirmed_at when a named analyst confirms. Clocks open at the earlier moment; whether a flag counts as awareness is for counsel and the supervisor.
- NIS 2 Article 23 timings
- As the chapter gives them: an early warning of a significant incident within 24 hours of becoming aware, an incident notification within 72 hours and a final report within one month.
- Closed clock with reasons
- A clock that does not apply is closed with the classification, the time and the name of the person. The closed clocks are part of the evidence.
- Evidence view and management view
- Incident roles and auditors see the action-level record of who did what. Management reports show aggregates only, by team and period, with no figure by name, and the purpose is written into the agreement and the tool.
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
Instrument, article and what must be shown
Match each instrument and article with what the chapter's map says the blue team must be able to show under it. This is an architectural reading, not legal advice.
Interactive exercise 2 · Sort
A rule of the case system, or an AI draft?
Sort each regulatory activity by how the chapter's table across the degrees of delegation treats it.
Teaching plan
| 15 min | Teacher presents the map of obligations by instrument, addressee and what the team must show, and stresses that the framing is architectural implication, not legal advice. |
| 20 min | Four-clocks walkthrough: one incident touching personal data in a financial entity through a vendor's product, with start, limit, addressee and owner for each clock. |
| 40 min | Exercise: groups build a clock profile for an incident-class case, modelled on CLK-HM-01, for their own entities or the two fictional organisations. |
| 15 min | Discussion of the Friday 17:30 problem at Nordvik Region and of CASE-NR-0231, where the Region had no record of the first moment of awareness. |
| 15 min | Input on employee data in monitoring and on the position of the SOC's AI under the AI Act, including Article 26 on informing workers' representatives. |
Discussion
- The architecture should not try to settle whether an AI system's flag counts as awareness. What does it mean in practice to make the question answerable instead?
- A management body cannot be accountable for what it cannot see. What would a quarterly report need to contain for your board to oversee the SOC's delegation?
- The same log serves accountability under the regulations and must never become a score under the works agreement. Which design choice does most to keep the two apart?
Written exercise
Exercise · 40 minutes
Building the incident clock
Follow the seven steps of the practical guide. For each legal entity of your organisation, or for Hansa Mutual's EU entities and Nordvik Region, list the regimes that apply and the authority or CSIRT that receives the report. Define which events write the first-flag timestamp and which write the human-confirmed timestamp. Write the rule by which the case system opens every clock that could apply at the earlier moment. Name an owner and a deputy for each clock and say how they are reached out of hours. Specify the notification templates that AI drafts at Level 1 Assisted and a person checks, the rule for closing a clock with reasons, and a quarterly rehearsal using a closed case.
Deliverable: A clock profile listing regimes per entity, the two awareness timestamps, start rules, limits as the instrument gives them, owners, deputies and closing rules.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
At which moment do the clocks open in the chapter's design?
Show the answer
B. At the earlier of the first flag and the human confirmation, by a rule of the case system
Opening is a deterministic rule of the case system, not an action of an AI agent, and due times are counted from the first flag so the record never claims more time than the conservative reading allows.How does the book read the AI Act's Annex III in relation to AI used for security operations?
Show the answer
D. No listed use describes security operations, though the SOC's AI is an AI system under the Act
As the book reads Annex III, no listed use describes security operations, but the SOC's AI is an AI system, with the organisation as provider or deployer, and Article 4 on AI literacy applies.What is the AI ceiling for sending a notification to an authority, in the chapter's table across the degrees of delegation?
Show the answer
A. Not delegated: a named person sends it, because the duty cannot be held by a system
Sending is an AC-4 action and is not delegated. The AI drafts at Level 1 Assisted, citing the record, and a named person checks and sends.