NIS2 and AI flows
Regulation · NIS2
NIS2 and AI agents: prepare risks, incidents and continuation of work
An agent mission depends on model services, identities, document stores and business tools. For a client within NIS2’s scope, examine those dependencies within the security and continuity of its systems rather than keeping a separate AI file disconnected from operations.
The integrator can prepare useful facts and responsibilities. Scope, measures and reporting still depend on the entity, services and applicable texts. DUBSAR does not provide the client’s NIS2 classification.
In brief
The question and the useful result.
- Question
- How should an agent mission fit into the organisation’s risk, incident and continuity processes?
- Useful result
- A dependency and incident-handover record covering known facts, impacts, responsibilities and recovery conditions.
NIS2 and AI flows
Separate the directive, national law and preparation
Directive (EU) 2022/2555 establishes scope criteria, essential and important entities and relevant sectors (Articles 2 and 3, Annexes I and II). Using AI alone neither brings every organisation within scope nor excludes it.
Articles 20 and 21 concern governance and risk-management measures, including incident handling, continuity, supply-chain security and access control. Buying software does not transfer management responsibilities to its vendor.
For France, consult ANSSI’s transposition information and the national texts actually published. ReCyF v2.5 of 17 March 2026 is presented as a preparation working document. Do not treat it as legislation, an implementing decree or an established national application date. NIS2 is an EU directive, not UK cyber law.
NIS2 and AI flows
Connect the mission to organisational risks
| Item | Information for review |
|---|---|
| Supported service | Business purpose, affected users and consequences of interruption or incorrect results. |
| Dependencies | Providers, identities, data, tools and the owner of each connection. |
| Measures | Selected controls, coverage, checks performed and limits. |
| Incident handover | Contacts, chronology, known or unknown impacts and accessible material. |
| Continuity | Suspended operations, proposed alternative work arrangements and authorised decision-maker. |
| Recovery | Conditions to verify, external outcomes to reconcile and a documented next-step decision. |
This record can be used in the client’s existing tools. It supports discussion with security and operations teams; it replaces neither risk assessment nor a tested continuity plan.
NIS2 and AI flows
Scenario: a provider’s access is suspended
In this illustrative example, a mission stops after access to a service is withdrawn. The team separates the observed fact from its unknown cause. It identifies affected missions, the last confirmed operations and those with unresolved outcomes.
The security owner reviews facts, service impact and available evidence to decide next steps. A failed request is not automatically a significant incident under NIS2. Conversely, the absence of a workflow alert does not establish that no incident occurred.
To continue, the team does not improvise a new route using different data or permissions. It has the permitted scope reviewed and retains the decision. Before resuming a business action, it also checks attempts whose effects remain uncertain. No automatic DUBSAR detection or reporting mechanism is assumed.
NIS2 and AI flows
Prepare reporting without deciding for the entity
For relevant significant incidents, Article 23 provides for early warning within 24 hours and notification within 72 hours of becoming aware, without undue delay. It generally requires a final report no later than one month after notification, with special cases including certain trust services and ongoing incidents.
The client must assess criteria, national law, the competent authority and applicable sector-specific rules. Reporting a personal-data breach under the GDPR is a separate mechanism to assess where relevant.
Mission and attempt references can help establish a chronology and understand remaining unknowns. DUBSAR’s intended role is to connect state, authorisations and decisions about continuation. It does not itself establish incident classification or demonstrated regulatory reporting.
NIS2 and AI flows
Frequently asked questions
Must every agent failure be reported under NIS2?
No. Assess scope, the service and significant-incident criteria under the applicable texts. A failure can also require other client procedures without constituting this specific notification.
Does ReCyF replace French transposing legislation?
No. The cited working document supports security preparation and understanding of the objectives. Establish obligations and dates from relevant national and European texts, without turning a recommendation into a universal duty.
Does DUBSAR make the organisation compliant or report its incidents?
Neither capability is established here. DUBSAR aims to provide mission governance with evidence and recovery decisions. Security, continuity and reporting responsibilities remain with the relevant actors.
NIS2 and AI flows
Where DUBSAR fits
DUBSAR is developing a governance foundation for integrators and teams deploying agents for clients: durable mission state, explicit authorisations, human decisions, evidence and continuation of work. It aims to connect what was requested, what was permitted and what is established about the outcome.
Selected components and workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.
NIS2 and AI flows
Sources and scope of review
Official sources reviewed on 20 October 2026. Scenarios and records are preparation methods that can be used without DUBSAR. They establish neither an available integration nor compliance.
- EUR-Lex — Directive (EU) 2022/2555 (NIS2) — Articles 2, 3, 20, 21, 23 and 41; Annexes I and II.
- ANSSI — La directive NIS 2 — French transposition information and preparation resources.
- ANSSI — ReCyF, document de travail v2.5, 17 mars 2026 — Preparation working document; does not itself constitute transposing legislation.
NIS2 and AI flows