Financial entities follow DORA for their AI agents; it takes precedence over NIS2 on ICT risk management and incident reporting. Essential and important entities in other sectors, such as health, energy or transport, follow NIS2. The agent platform vendor may fall under NIS2 in its own right, whichever regime its customers are in.
What does each regime require, in plain words?
DORA (Regulation (EU) 2022/2554), applying from 17 January 2025, is a regulation for the financial sector. It sets duties on ICT risk management, ICT incident reporting, digital operational resilience testing and ICT third-party risk, with direct oversight of critical ICT third-party providers. For background, see what DORA is.
NIS2 is a directive for cybersecurity across many sectors. It requires essential and important entities to take appropriate cybersecurity risk management measures, report significant incidents to national authorities, and hold management bodies accountable for cybersecurity. Being a directive, it works through national laws, which vary in detail. The duties for agents are set out in NIS2 and AI agents: cybersecurity duties for essential entities.
Both are technology-neutral. Neither mentions AI agents, and both apply to them as ICT systems.
Who does each apply to?
Work through three questions.
- Is your organisation a financial entity in DORA's scope? Banks, payment and e-money institutions, investment firms, insurers and the other listed types follow DORA. Banking and financial market infrastructure also appear in NIS2's sector list, but where sector-specific EU law sets at least equivalent requirements, as DORA does, those NIS2 provisions give way. A bank's agents are governed by DORA.
- If not, are you an essential or important entity under NIS2? Organisations above the size thresholds in listed sectors, such as health, energy, transport, water, digital infrastructure, public administration and many manufacturers, follow their national NIS2 law. A hospital's scheduling agent falls here.
- Are you the vendor? A provider of an agent platform delivered as a managed or cloud service may itself be an entity under NIS2, depending on its size and the services it provides. That is a separate question from which regime its customers face, covered in does NIS2 apply to AI agent platforms.
A group can sit in both: an insurer follows DORA, while its group's health services business follows NIS2. Where one shared agent serves both businesses, apply the stricter requirement to the shared parts, such as access control and incident detection, and report under whichever regime governs the entity whose service was affected.
How do the two regimes differ for an agent?
For an agent, the practical differences are these:
- Incident reporting. DORA reports major ICT-related incidents to financial supervisors using DORA's classification criteria. NIS2 reports significant incidents to national authorities or response teams on its own test and stages, set out in NIS2 incident reporting when an AI agent is involved.
- Third-party risk. DORA prescribes contract terms, a register of information and exit strategies in detail. NIS2 requires supply chain security as part of risk management, with less prescription.
- Testing. DORA requires a testing programme and, for some entities, threat-led penetration testing. NIS2 requires assessing the effectiveness of measures without DORA's testing structure.
- Supervision. DORA is supervised by financial supervisors. NIS2 by national cybersecurity authorities.
Which controls satisfy both?
Most controls an agent needs are the same under both. Build them once and map them to whichever regime applies.
| Requirement | Control | Evidence it leaves |
|---|---|---|
| Risk management covering agents | Agent register with capabilities, sources, access and providers | Register reconciled to production |
| Access control | Least-privilege agent identities; every action checked against its bounds | Access reviews and filed verdicts |
| Supply chain security | Vendor and model provider assessed, contracted and monitored | Due diligence and contract terms |
| Incident handling | Agent incidents detected from behaviour, scoped from the action record | Incident records with case lists |
| Incident reporting | Classification against the applicable regime's test | Classification and reports |
| Effectiveness testing | Scenarios for outage, injected instructions and authority limits | Test results |
| Management accountability | Management body briefed on agent risk | Board papers |
What will a supervisor ask?
- Which regime applies to your entity, and to each entity in your group?
- If you are a financial entity, how have you treated NIS2 for your agents?
- Does your agent vendor fall under NIS2 itself, and what has it told you about its obligations?
- How do you classify agent incidents under the regime that applies?
What do the two regimes not cover?
Neither regulates whether an agent's decisions are fair, lawful or accurate; the EU AI Act, GDPR and sector conduct rules do. Neither applies outside the EU: UK and US entities face their own frameworks, and the US position is summarised in which US laws apply to AI agents. And national NIS2 laws vary, so confirm the transposition in each member state where you operate. For the full map, see AI agent regulation mapped to controls.
This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
Where Pryme fits
Pryme's controls are the same whichever regime applies: each action is checked against five bounds at the moment it is taken, and every verdict is filed in an append-only record. That record gives the evidence both regimes ask for on access, incidents and testing, mapped to whichever one governs the customer.
Questions people ask
Does a bank ever need to apply NIS2 to its agents?
For ICT risk management and incident reporting, DORA takes precedence. Some national rules or group structures may still bring NIS2 into view for non-financial parts of the group.
Can an agent vendor be under both?
A vendor can fall under NIS2 as a digital service provider and, if designated as a critical ICT third-party provider for the financial sector, under DORA oversight as well.
Is one regime stricter for agents?
DORA is more prescriptive on third-party arrangements and testing. NIS2 covers more sectors and leaves more to national law. The underlying controls for agents are much the same, so the real work is mapping one set of controls to the reporting and supervisory route that applies.