> AI Act vs DORA side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# AI Act vs DORA

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[AI Act](https://grc.plus/regulation/artificial-intelligence-act-ai-act/)Providers and deployers of AI systems

[DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/)Financial entities

## At a Glance

They differ on 32 of 41 topics. Each verdict names what it rests on; read the wording before relying on it.

- **AI Act** Asks more on 0 topics Alone on 8 topics More detailed on 2 topics
- **DORA** Asks more on 0 topics Alone on 19 topics More detailed on 3 topics

| Topic | AI Act | DORA | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Roles and independence | AI Act: 3 | DORA: 1 | **AI Act more detailed**more requirements on this, not necessarily stricter |
| Security policy | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Awareness and training | AI Act: 1 | DORA: 2 | **Both cover it**read the wording below |
| Risk management |  |  |  |
| Risk management framework | AI Act: 1 | DORA: 2 | **Both cover it**read the wording below |
| Risk assessment | AI Act: 1 | DORA: 3 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Review, audit and improvement | AI Act: 1 | DORA: 4 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Asset management | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Authentication | AI Act: – | DORA: 2 | **Only DORA**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | AI Act: – | DORA: 2 | **Only DORA**no specific requirement on the other side in the acts covered |
| Data security | AI Act: 1 | DORA: 3 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Network security | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | AI Act: 1 | DORA: 2 | **Both cover it**read the wording below |
| Configuration, change and patch management | AI Act: – | DORA: 5 | **Only DORA**no specific requirement on the other side in the acts covered |
| Vulnerability handling | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Human resources security | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Physical and environmental security | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | AI Act: 2 | DORA: 3 | **Both cover it**read the wording below |
| Incident handling | AI Act: 2 | DORA: 3 | **Both cover it**read the wording below |
| Incident classification | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Reporting to authorities | AI Act: 4 | DORA: 5 | **Both cover it**read the wording below |
| Informing customers and the public | AI Act: – | DORA: 2 | **Only DORA**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | AI Act: – | DORA: 2 | **Only DORA**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Backup and recovery | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Security testing | AI Act: – | DORA: 3 | **Only DORA**no specific requirement on the other side in the acts covered |
| Threat-led penetration testing | AI Act: 1 | DORA: 1 | **Both cover it**read the wording below |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | AI Act: 2 | DORA: 2 | **Both cover it**read the wording below |
| Contract requirements | AI Act: 1 | DORA: 2 | **Both cover it**read the wording below |
| Register of third-party arrangements | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Exit and termination | AI Act: – | DORA: 1 | **Only DORA**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Impact assessment | AI Act: 1 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Artificial intelligence |  |  |  |
| Risk classification of AI systems | AI Act: 4 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Data and data governance | AI Act: 3 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Transparency to users | AI Act: 6 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Human oversight | AI Act: 2 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Conformity assessment and monitoring | AI Act: 5 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | AI Act: 2 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | AI Act: 1 | DORA: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Penalties and liability | AI Act: 4 | DORA: 1 | **AI Act more detailed**more requirements on this, not necessarily stricter |

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

- [AI Act](https://grc.plus/regulation/artificial-intelligence-act-ai-act/) Articles 4 to 6, 8 to 27, 43, 47 to 50, 53, 55, 72, 73, 99, 101, 111 · 49 requirements
- [KI-loven](https://grc.plus/regulation/norway-artificial-intelligence-act-ki-loven/) Draft act on artificial intelligence (KI-loven), consultation of 30 June 2025 Articles 5, 50 · 4 requirements
- [Decreet 16 oktober 2026](https://grc.plus/regulation/flanders-media-decree-ai-act-amendment/) Decreet van 16 oktober 2026, Belgisch Staatsblad 19 November 2026, numac 2026008360 3 requirements
- [No. 31/2026](https://grc.plus/regulation/ireland-regulation-of-artificial-intelligence-act/) Regulation of Artificial Intelligence Act 2026 (No. 31 of 2026) 5 requirements

Status

Reviewed against the official texts.

Included

- [DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/) Regulation (EU) 2022/2554 Articles 5, 6, 8 to 14, 16 to 19, 24 to 26, 28, 30, 45, 50 · 43 requirements
- [DORA ICT Risk Management RTS](https://grc.plus/regulation/dora-rts-ict-risk-management/) Commission Delegated Regulation (EU) 2024/1774 Articles 2 to 31, 33 to 41 · 26 requirements Applies to: Financial entities, except those on the simplified framework
- [JC 2024 34](https://grc.plus/regulation/dora-guidelines-incident-costs-and-losses/) Joint Guidelines on the estimation of aggregated annual costs and losses caused by major ICT-related incidents under Regulation (EU) 2022/2554, JC 2024 34 (Final Report of 17 July 2024), issued under Article 11(11) of Regulation (EU) 2022/2554 5 requirements

Not yet included

- [DORA Third-Party Policy RTS](https://grc.plus/regulation/dora-rts-ict-third-party-policy/)
- [DORA Subcontracting RTS](https://grc.plus/regulation/dora-rts-subcontracting/)
- [DORA Register of Information ITS](https://grc.plus/regulation/dora-its-register-of-information/)
- [DORA Incident Classification RTS](https://grc.plus/regulation/dora-rts-incident-classification/)
- [DORA Incident Reporting RTS](https://grc.plus/regulation/dora-rts-incident-reporting/)
- [DORA Incident Reporting ITS](https://grc.plus/regulation/dora-its-incident-reporting-templates/)
- [DORA TLPT RTS](https://grc.plus/regulation/dora-rts-tlpt/)
- [DORA Critical Provider Criteria](https://grc.plus/regulation/dora-da-critical-provider-criteria/)
- [DORA Oversight Conditions RTS](https://grc.plus/regulation/dora-rts-oversight-conditions/)

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

AI Act: Immediately on identifying a serious incident (Deployers of high-risk AI systems); Without undue delay (Providers of general-purpose AI models with systemic risk); Within 2 days of becoming aware (Providers of high-risk AI systems); Within 10 days of becoming aware (Providers of high-risk AI systems)

DORA: Not in the acts covered

### Goes to

AI Act: Market surveillance authorities and, where applicable, the notified body (Providers of high-risk AI systems); Provider first, then importer or distributor and market surveillance authorities (Deployers of high-risk AI systems); Market surveillance authority (Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems)

DORA: Not in the acts covered

### Evidence to keep

AI Act: Documented assessment, provided on request (Providers of Annex III AI systems they consider not high-risk); Annex IV technical documentation (Providers of high-risk AI systems); Automatically generated logs, at least six months (Providers of high-risk AI systems); Documentation, 10 years after placing on the market or putting into service (Providers of high-risk AI systems); Provider contact details, EU declaration, technical documentation and any notified body certificate, 10 years (Providers of high-risk AI systems established in third countries); Certificate, instructions and EU declaration, 10 years (Importers of high-risk AI systems); Logs under the deployer's control, at least six months (Deployers of high-risk AI systems); EU declaration of conformity, 10 years (Providers of high-risk AI systems); Annex XI and Annex XII documentation (Providers of general-purpose AI models); Post-market monitoring plan in the technical documentation (Providers of high-risk AI systems)

DORA: Not in the acts covered

### Incident reports go to

AI Act: AI Office and, as appropriate, national competent authorities (Providers of general-purpose AI models with systemic risk); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems)

DORA: Financial supervisor (competent authority)

### First notice of an incident

AI Act: Within 2 days of becoming aware for a widespread infringement or critical infrastructure disruption; 10 days for a death; 15 days otherwise (Providers of high-risk AI systems)

DORA: Within 4 hours of classifying it as major, and no later than 24 hours of becoming aware; if classified as major after that, within 4 hours of classifying it Shortest stated

### Intermediate report

AI Act: Not in the acts covered

DORA: Within 72 hours of the initial notification

### Final report

AI Act: Not in the acts covered

DORA: Within one month of the latest intermediate report

### Deadline to have the measures in place

AI Act: By 2 December 2026 (Operators of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (Providers of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (Providers of high-risk AI systems); By 2 December 2026 for systems on the market before 2 August 2026 (Providers of AI systems, including general-purpose AI systems, that generate synthetic content)

DORA: Not in the acts covered

### External assessment or certification

AI Act: Internal control, or a notified body where Article 43 requires one (Providers of high-risk AI systems)

DORA: Not in the acts covered

### Review of the risk framework

AI Act: Regular systematic review throughout the lifecycle (Providers of high-risk AI systems)

DORA: At least once a year (periodically for microenterprises), and after major incidents

### Testing of critical systems

AI Act: Not in the acts covered

DORA: At least yearly, for systems supporting critical or important functions

### Threat-led penetration testing

AI Act: Not in the acts covered

DORA: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency

### Register of third-party arrangements

AI Act: Not in the acts covered

DORA: Required, for every ICT service arrangement

### Registration with the authority

AI Act: EU database, under Article 49(2) (Providers of Annex III AI systems they consider not high-risk); EU database under Article 71, before placing on the market or putting into service (Providers of Annex III AI systems or their authorised representatives); EU database under Article 71, before putting into service or use (Deployers that are public authorities, Union bodies or persons acting on their behalf)

DORA: Not in the acts covered

### Management body training

AI Act: Not in the acts covered

DORA: Required, on a regular basis

### Management body liability

AI Act: Not in the acts covered

DORA: Ultimate responsibility for ICT risk; penalties on members are subject to national law (Article 50(5))

### Maximum fines

AI Act: Up to EUR 35,000,000 or 7% of worldwide annual turnover, whichever is higher (Operators of AI systems); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Operators of AI systems and notified bodies); Up to EUR 7,500,000 or 1% of worldwide annual turnover, whichever is higher (Anyone supplying information to notified bodies or national competent authorities in reply to a request); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Providers of general-purpose AI models)

DORA: Set by each Member State (Competent authorities and Member States)

## Governance

### Management accountability

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

- Management body responsibility
  The management body defines, approves, oversees and is responsible for implementing every arrangement of the ICT risk management framework, and bears ultimate responsibility for managing ICT risk.
  [DORA, Article 5(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Budget for resilience
  The management body allocates and reviews the budget for digital operational resilience, including awareness programmes, training and ICT skills for all staff.
  [DORA, Article 5(2)(g)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Governance (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Governance and organisation of the simplified ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 28](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Roles and independence

**AI Act more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

- Provider obligations
  Applies to: Providers of high-risk AI systems
  Ensure the system meets the Section 2 requirements, taking account of its intended purpose and the state of the art. Show your name and contact address, run a quality management system, keep documentation and logs, complete conformity assessment, the EU declaration and CE marking, register, take corrective action, demonstrate conformity on request and meet accessibility requirements.
  [AI Act, Articles 8(1), 16](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Appoint an authorised representative
  Applies to: Providers of high-risk AI systems established in third countries
  Before making a high-risk system available in the Union, appoint an EU-established authorised representative by written mandate. The representative verifies the conformity documents, keeps them for 10 years, deals with authorities and ends the mandate, informing the authority, if the provider acts against the Regulation.
  [AI Act, Article 22(1), (3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- When others become the provider
  Applies to: Distributors, importers, deployers, other third parties and initial providers
  A distributor, importer, deployer or other third party takes on provider obligations if it puts its name or trademark on a high-risk system (unless a contract allocates them otherwise), substantially modifies one, or changes the purpose of an AI system so that it becomes high-risk. The initial provider then stops being the provider of that system but cooperates and hands over information and access, unless it clearly specified that the system is not to be changed into a high-risk one.
  [AI Act, Article 25(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Independent control function
  A control function with appropriate independence manages and oversees ICT risk (not required of microenterprises). Risk management, control and internal audit functions are kept appropriately segregated and independent.
  [DORA, Article 6(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Security policy

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

Nothing in the acts covered.

- Information security policy
  A documented information security policy with requirements to protect the availability, authenticity, integrity and confidentiality of data and assets, including customers' where applicable.
  [DORA, Article 9(4)(a)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT security policies
  Applies to: Financial entities, except those on the simplified framework
  ICT security policies, procedures, protocols and tools, with their general elements, approved and reviewed as part of the framework.
  [DORA ICT Risk Management RTS, Article 2](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Information security policy (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An information security policy and measures.
  [DORA ICT Risk Management RTS, Article 29](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Awareness and training

**Both cover it** read the wording below

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Support AI literacy
  Take measures to support the AI literacy of staff and others who operate or use AI systems on your behalf, taking account of their knowledge, experience and training, the context of use and the people affected. The duty does not require you to guarantee a specific level of literacy for any individual.
  [AI Act, Article 4(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Management body training
  Members of the management body keep their knowledge and skills on ICT risk up to date, including by following specific training regularly.
  [DORA, Article 5(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Staff awareness and training
  ICT security awareness programmes and digital operational resilience training are compulsory for all employees and senior management.
  [DORA, Article 13(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

## Risk management

### Risk management framework

**Both cover it** read the wording below

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

- Risk management system
  Applies to: Providers of high-risk AI systems
  Establish, implement, document and maintain a risk management system for each high-risk AI system. Run it as a continuous, iterative process across the whole lifecycle, with regular systematic review and updating.
  [AI Act, Article 9(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- ICT risk management framework
  A sound, comprehensive and well-documented ICT risk management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICT assets.
  [DORA, Article 6(1) and (2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Simplified ICT risk management framework
  Applies to: Entities on the simplified framework (DORA Article 16)
  Small and non-interconnected investment firms, exempted payment and e-money institutions, small occupational pension funds, and institutions exempted under Directive 2013/36/EU that their Member State has not excluded under Article 2(4) follow a simplified framework instead of Articles 5 to 15.
  [DORA, Article 16(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Risk assessment

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

- Assess, treat and test for risk
  Applies to: Providers of high-risk AI systems
  Identify and evaluate known and foreseeable risks to health, safety and fundamental rights, including under foreseeable misuse and from post-market data, and adopt targeted measures until residual risk is acceptable. Consider the effect on under-18s and other vulnerable groups. Test against predefined metrics and probabilistic thresholds, in any event before placing the system on the market or putting it into service.
  [AI Act, Article 9(2), (5), (6), (8), (9)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Identify ICT risk
  Identify all sources of ICT risk continuously, assess cyber threats and vulnerabilities, and review risk scenarios at least yearly.
  [DORA, Article 8(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT risk management policy
  Applies to: Financial entities, except those on the simplified framework
  A policy and procedures for ICT risk management: risk tolerance, identification, assessment and treatment of risks, and the monitoring of residual risk.
  [DORA ICT Risk Management RTS, Article 3](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT risk management (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Identification and management of ICT risk.
  [DORA ICT Risk Management RTS, Article 31](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Review, audit and improvement

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Quality management system
  Applies to: Providers of high-risk AI systems
  Run a documented quality management system with written policies and procedures, covering regulatory strategy, design and development controls, testing, data management, risk management, post-market monitoring, incident reporting, record-keeping, resources and an accountability framework for management and staff. Scale it to the size of the organisation, without lowering the level of protection.
  [AI Act, Article 17(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Yearly review of the framework
  The framework is documented and reviewed at least once a year (periodically for microenterprises), after major ICT-related incidents and following supervisory instructions or conclusions from testing or audits, and improved continuously.
  [DORA, Article 6(5)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Internal audit
  Auditors with sufficient ICT risk expertise audit the framework regularly, in line with the audit plan. Not required of microenterprises.
  [DORA, Article 6(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Report on the framework review
  Applies to: Financial entities, except those on the simplified framework
  The format and content of the report on the review of the ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 27](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Framework review report (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  The format and content of the report on the review of the simplified framework.
  [DORA ICT Risk Management RTS, Article 41](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Asset management

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

Nothing in the acts covered.

- Identify and classify assets
  Identify, classify and document all ICT-supported business functions, information and ICT assets and their dependencies, and review the classification at least yearly.
  [DORA, Article 8(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT asset management
  Applies to: Financial entities, except those on the simplified framework
  An ICT asset management policy and procedure, including an inventory of assets and their criticality.
  [DORA ICT Risk Management RTS, Articles 4 and 5](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Asset classification (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Classification of information assets and ICT assets.
  [DORA ICT Risk Management RTS, Article 30](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

## Protection

### Access control

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

- Limit access
  Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.
  [DORA, Article 9(4)(c)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Access control (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Access control.
  [DORA ICT Risk Management RTS, Article 33](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Authentication

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

Nothing in the acts covered.

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Cryptography and encryption

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

Nothing in the acts covered.

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Encryption and key management
  Applies to: Financial entities, except those on the simplified framework
  Encryption and cryptographic controls, and the management of cryptographic keys through their whole life cycle.
  [DORA ICT Risk Management RTS, Articles 6 and 7](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Data security

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Protect the model and its infrastructure
  Applies to: Providers of general-purpose AI models with systemic risk
  Ensure an adequate level of cybersecurity protection for the model and its physical infrastructure.
  [AI Act, Article 55(1)(d)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Protect data
  Policies, protocols and tools that keep data available, authentic, intact and confidential at rest, in use and in transit.
  [DORA, Article 9(2) and (3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT operations and data security
  Applies to: Financial entities, except those on the simplified framework
  Policies and procedures for ICT operations, capacity and performance management, and data and system security.
  [DORA ICT Risk Management RTS, Articles 8, 9 and 11](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Network security

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

Nothing in the acts covered.

- Network and infrastructure management
  Network and infrastructure management on a risk basis, designed so that connections can be severed or segmented instantly to stop contagion.
  [DORA, Article 9(4)(b)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Network security
  Applies to: Financial entities, except those on the simplified framework
  Network security management and the protection of information in transit.
  [DORA ICT Risk Management RTS, Articles 13 and 14](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Secure acquisition and development

**Both cover it** read the wording below

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

- Accuracy, robustness and cybersecurity
  Applies to: Providers of high-risk AI systems
  Achieve an appropriate level of accuracy, robustness and cybersecurity throughout the lifecycle and declare accuracy metrics in the instructions. Make the system resilient to errors and to attempts to alter its use or output, with measures where appropriate against data poisoning, model poisoning, adversarial examples, confidentiality attacks and model flaws.
  [AI Act, Article 15(1), (3) to (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Projects, acquisition and development
  Applies to: Financial entities, except those on the simplified framework
  ICT project management, and the acquisition, development and maintenance of ICT systems.
  [DORA ICT Risk Management RTS, Articles 15 and 16](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Configuration, change and patch management

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

Nothing in the acts covered.

- Change management
  Documented change management, so that every change to software, hardware, firmware, systems or security parameters is recorded, tested, assessed, approved, implemented and verified.
  [DORA, Article 9(4)(e)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT change management
  Applies to: Financial entities, except those on the simplified framework
  ICT change management procedures.
  [DORA ICT Risk Management RTS, Article 17](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Vulnerability handling

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

Nothing in the acts covered.

- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Human resources security

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

Nothing in the acts covered.

- Human resources policy
  Applies to: Financial entities, except those on the simplified framework
  A human resources policy covering ICT security.
  [DORA ICT Risk Management RTS, Article 19](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Physical and environmental security

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

Nothing in the acts covered.

- Physical and environmental security
  Applies to: Financial entities, except those on the simplified framework
  A physical and environmental security policy.
  [DORA ICT Risk Management RTS, Article 18](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

## Detection and response

### Monitoring and detection

**Both cover it** read the wording below

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

- Automatic logs
  Applies to: Providers of high-risk AI systems
  Build the system so it records events automatically over its lifetime, supporting risk identification, post-market monitoring and deployer monitoring. Keep the logs under your control for a period that suits the intended purpose and is at least six months, unless other law says otherwise.
  [AI Act, Articles 12(1), (2), 19(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Keep deployer logs
  Applies to: Deployers of high-risk AI systems
  Keep the logs generated by the system, to the extent you control them, for a period that suits the intended purpose and is at least six months, unless other law says otherwise. Financial institutions keep them with their financial services documentation.
  [AI Act, Article 26(6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Detect anomalous activity
  Mechanisms to detect anomalous activity promptly, with several layers of control, alert thresholds and automatic alerts, tested regularly.
  [DORA, Article 10](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Logging
  Applies to: Financial entities, except those on the simplified framework
  Logging procedures, protocols and tools: what is logged, how logs are protected and how long they are kept.
  [DORA ICT Risk Management RTS, Article 12](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Incident handling

**Both cover it** read the wording below

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

- Corrective action and duty to inform
  Applies to: Providers of high-risk AI systems
  If a system may not conform, immediately correct, withdraw, disable or recall it and tell distributors and, where applicable, deployers, the authorised representative and importers. If it presents a risk under Article 79(1), immediately investigate the causes and inform the market surveillance authorities and, where applicable, the notified body.
  [AI Act, Article 20](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Investigate a serious incident
  Applies to: Providers of high-risk AI systems
  After reporting, investigate without delay, including a risk assessment and corrective action, and cooperate with authorities. Do not alter the system in a way that could affect later evaluation of the causes without first informing the authorities.
  [AI Act, Article 73(6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Post-incident reviews
  A review after a major ICT-related incident disrupts core activities, to find the causes and the improvements needed.
  [DORA, Article 13(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management process
  A process to detect, manage and notify ICT-related incidents: record all incidents and significant cyber threats, assign roles, escalate, and find and fix root causes.
  [DORA, Article 17](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Incident classification

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

Nothing in the acts covered.

- Classify incidents
  Classify incidents by the clients affected, reputational impact, duration, geographical spread, data losses, critical services affected and economic impact. The thresholds are in Delegated Regulation (EU) 2024/1772.
  [DORA, Article 18(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Reporting to authorities

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Report serious incidents on models
  Applies to: Providers of general-purpose AI models with systemic risk
  Track, document and report relevant information about serious incidents and possible corrective measures without undue delay.
  [AI Act, Article 55(1)(c)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report a serious incident
  Applies to: Providers of high-risk AI systems
  Report any serious incident immediately after establishing a causal link, or its reasonable likelihood, between the system and the incident, taking account of its severity. An incomplete initial report may be followed by a complete one.
  [AI Act, Article 73(1), (2), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report widespread infringements and critical infrastructure disruption
  Applies to: Providers of high-risk AI systems
  Report immediately in the event of a widespread infringement, or a serious and irreversible disruption of the management or operation of critical infrastructure.
  [AI Act, Article 73(3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report a death
  Applies to: Providers of high-risk AI systems
  Where a person dies, report immediately after establishing, or as soon as you suspect, a causal relationship between the system and the incident.
  [AI Act, Article 73(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Report major incidents
  Report major ICT-related incidents to the competent authority, using the common templates.
  [DORA, Article 19(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Initial notification
  An initial notification once the incident is classified as major.
  [DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Intermediate report
  An intermediate report, updated when regular activities have been recovered.
  [DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Final report
  A final report once the root cause analysis is complete, whether or not mitigation is in place, and actual impact figures are available to replace estimates.
  [DORA, Article 19(4)(c); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Voluntary notice of cyber threats Optional
  Significant cyber threats may be notified to the competent authority.
  [DORA, Article 19(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Informing customers and the public

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

Nothing in the acts covered.

- Crisis communication
  Crisis communication plans to disclose major incidents or vulnerabilities to clients, counterparts and the public, and a person in charge of public and media communication.
  [DORA, Article 14](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Inform affected clients
  When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.
  [DORA, Article 19(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Threat intelligence and information sharing

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

Nothing in the acts covered.

- Threat and vulnerability intelligence
  Capabilities and staff to gather information on vulnerabilities, cyber threats and incidents and to analyse their likely impact.
  [DORA, Article 13(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Information-sharing arrangements Optional
  Financial entities may exchange cyber threat information within trusted communities, under arrangements that protect confidentiality and personal data. They must tell the competent authority when they join or leave.
  [DORA, Article 45](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

## Continuity and resilience

### Business continuity and crisis management

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

Nothing in the acts covered.

- ICT business continuity
  An ICT business continuity policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functions, and a business impact analysis.
  [DORA, Article 11](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT business continuity
  Applies to: Financial entities, except those on the simplified framework
  The components of the ICT business continuity policy, the testing of continuity plans, and ICT response and recovery plans.
  [DORA ICT Risk Management RTS, Articles 24 to 26](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Business continuity (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An ICT business continuity plan and its testing.
  [DORA ICT Risk Management RTS, Articles 39 and 40](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Backup and recovery

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

Nothing in the acts covered.

- Backup and restoration
  Backup policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICT capacity (microenterprises assess the need based on their risk profile).
  [DORA, Article 12](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Security testing

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

Nothing in the acts covered.

- Resilience testing programme
  A risk-based testing programme run by independent testers, with all ICT systems and applications supporting critical or important functions tested at least yearly. Not required of microenterprises.
  [DORA, Article 24](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Security testing (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT security testing.
  [DORA ICT Risk Management RTS, Article 36](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

### Threat-led penetration testing

**Both cover it** read the wording below

NIST CSF 2.0 ID.IM

- Evaluate models and mitigate systemic risk
  Applies to: Providers of general-purpose AI models with systemic risk
  Evaluate the model using standardised protocols and tools reflecting the state of the art, including documented adversarial testing. Assess and mitigate possible systemic risks at Union level and their sources.
  [AI Act, Article 55(1)(a), (b)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Threat-led penetration testing
  Entities identified by the competent authority, other than microenterprises and Article 16(1) entities, run threat-led penetration tests on live production systems. Details are in Delegated Regulation (EU) 2025/1190.
  [DORA, Article 26(1), (2) and (8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

- Importer checks
  Applies to: Importers of high-risk AI systems
  Before placing a high-risk system on the market, verify the conformity assessment, technical documentation, CE marking, EU declaration, instructions and authorised representative. Hold back a system you have reason to think is non-conforming or falsified, and report risks. Keep the certificate, instructions and declaration for 10 years and cooperate with authorities.
  [AI Act, Article 23(1), (2), (5) to (7)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Distributor checks
  Applies to: Distributors of high-risk AI systems
  Before making a high-risk system available, verify the CE marking, EU declaration and instructions, that the provider and importer show their name and contact address, and that the provider has a quality management system. Hold back a system you consider non-conforming. If one is already on the market, ensure it is corrected, withdrawn or recalled, inform the provider or importer and authorities of any risk, and cooperate with them.
  [AI Act, Article 24(1), (2), (4) to (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Manage ICT third-party risk
  ICT third-party risk is managed within the ICT risk management framework, and the entity stays fully responsible for compliance.
  [DORA, Article 28(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Third-party risk strategy
  A regularly reviewed strategy on ICT third-party risk, with a policy on ICT services supporting critical or important functions. The management body regularly reviews the risks from those arrangements. Not required of microenterprises or Article 16 entities.
  [DORA, Article 28(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Contract requirements

**Both cover it** read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Written agreements with suppliers
  Applies to: Providers of high-risk AI systems and their third-party suppliers
  Specify by written agreement the information, capabilities, technical access and other assistance a supplier of AI systems, models, tools, services, components or processes gives so that the provider can comply. This does not apply to open-source tools, services, processes or components that are made public, other than general-purpose AI models.
  [AI Act, Article 25(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Minimum contract terms
  Contracts set out the services, locations of service and data, data protection, access and return of data, service levels, incident assistance, cooperation with authorities, termination rights and participation in training.
  [DORA, Article 30(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Terms for critical or important functions
  Contracts for services supporting critical or important functions add full service level descriptions, notice periods, business contingency plans, participation in TLPT, unrestricted rights of access, inspection and audit (microenterprises may agree to delegate these to an independent third party), and exit strategies with a transition period.
  [DORA, Article 30(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Register of third-party arrangements

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Register of information
  A register of all contractual arrangements for ICT services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements supporting critical or important functions.
  [DORA, Article 28(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

### Exit and termination

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Exit strategies
  Exit strategies for ICT services supporting critical or important functions, covering provider failure, falling quality and business disruption.
  [DORA, Article 28(8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

## Privacy and data protection

### Impact assessment

**Only AI Act** no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

- Fundamental rights impact assessment
  Applies to: Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems
  Before first use, assess the impact on fundamental rights: the processes involved, period and frequency of use, people affected, specific risks of harm, human oversight, and measures if risks materialise, including governance and complaints. Update it when elements change and notify the market surveillance authority of the results. You may cross-refer to an existing data protection impact assessment.
  [AI Act, Article 27(1) to (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Artificial intelligence

### Risk classification of AI systems

**Only AI Act** no specific requirement on the other side in the acts covered

- Prohibited AI practices
  Applies to: Operators of AI systems
  Do not place on the market, put into service or use AI that manipulates people or exploits their vulnerabilities causing, or likely to cause, significant harm, scores people socially leading to unjustified or out-of-context detriment, predicts crime from profiling alone, builds facial recognition databases by untargeted scraping, infers emotions at work or in education other than for medical or safety reasons, or categorises people biometrically to infer sensitive traits. Real-time remote biometric identification in public spaces for law enforcement is banned outside narrow exceptions.
  [AI Act, Article 5(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Intimate imagery and child sexual abuse material
  Applies to: Operators of AI systems
  Do not place on the market, put into service or use AI that generates or manipulates realistic non-consensual intimate or sexually explicit material of an identifiable person, or child sexual abuse material unless a national 'without right' defence applies. For providers the ban bites where this is the intended purpose, or a foreseeable and reproducible outcome without adequate safeguards. For deployers it bites where the system is used for that purpose. Manipulation that adds no exposure and does not alter the nature of the activity is outside the ban.
  [AI Act, Article 5(1)(ba), (bb), (1a), (1b)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Classify high-risk AI systems
  Applies to: Providers of AI systems
  Treat an AI system as high-risk where it is a safety component of a product, or is itself a product, under Annex I legislation that requires third-party conformity assessment, or where it falls in an Annex III use case. A third-party assessment required only for risks other than health and safety does not count. AI used only for non-safety assistance, optimisation, efficiency, convenience or quality control is not a safety component, unless its failure would endanger health and safety.
  [AI Act, Article 6(1), (1a) to (1c), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Document an Annex III opt-out
  Applies to: Providers of Annex III AI systems they consider not high-risk
  An Annex III system is not high-risk only if it poses no significant risk and meets one of four conditions, such as a narrow procedural or preparatory task. It is always high-risk if it profiles people. A provider relying on this documents its assessment before placing the system on the market or putting it into service, registers it and gives the assessment to authorities on request.
  [AI Act, Article 6(3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Data and data governance

**Only AI Act** no specific requirement on the other side in the acts covered

- Special category data for bias correction Optional
  Providers may exceptionally process special categories of personal data where strictly necessary to detect and correct bias. Other data, including synthetic or anonymised data, must not be able to do the job, and the data must be secured, not passed to others, deleted once the bias is corrected or the retention period ends, and the reasons recorded.
  [AI Act, Article 4a(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Data sets and data governance
  Applies to: Providers of high-risk AI systems
  Apply governance to training, validation and testing data covering design choices, origin, preparation, data gaps and examination for bias, with measures to detect, prevent and mitigate it. Data sets must be relevant, sufficiently representative, as error-free and complete as possible, and fit the intended setting. Where no model is trained, this applies to testing data only.
  [AI Act, Article 10(1) to (4), (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Copyright policy and training content summary
  Applies to: Providers of general-purpose AI models
  Put in place a policy to comply with Union copyright law, including identifying and respecting rights reservations. Publish a sufficiently detailed summary of the content used for training, using the AI Office template.
  [AI Act, Article 53(1)(c), (d)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Transparency to users

**Only AI Act** no specific requirement on the other side in the acts covered

- Transparency and instructions for use
  Applies to: Providers of high-risk AI systems
  Design the system so deployers can interpret its output and use it properly. Supply clear instructions covering the provider's identity, intended purpose, tested accuracy, robustness and cybersecurity, foreseeable risks, human oversight measures, maintenance needs and how to collect and interpret logs.
  [AI Act, Article 13(1) to (3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Tell workers and affected people
  Applies to: Deployers of high-risk AI systems, including employers
  Before using a high-risk system at the workplace, employers inform workers' representatives and affected workers. Deployers of Annex III systems that make or assist decisions about people tell those people that the system is used.
  [AI Act, Article 26(7), (11)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Disclose interaction with AI
  Applies to: Providers of AI systems that interact directly with people
  Design systems that interact directly with people so those people are told they are dealing with AI, unless this is obvious to a reasonably well-informed person. Give the information clearly at the latest at the first interaction, in an accessible form.
  [AI Act, Article 50(1), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Mark synthetic content
  Applies to: Providers of AI systems, including general-purpose AI systems, that generate synthetic content
  Ensure outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, with solutions that are effective, interoperable, robust and reliable as far as technically feasible. This does not apply to assistive standard editing or where the input is not substantially altered.
  [AI Act, Articles 50(2), 111(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Disclose emotion recognition and deep fakes
  Applies to: Deployers of emotion recognition, biometric categorisation or content-generating AI systems
  Inform people exposed to emotion recognition or biometric categorisation. Disclose that deep fake content, and text published to inform the public on matters of public interest, is artificially generated or manipulated. Artistic works carry a limited disclosure, and reviewed text under editorial responsibility is exempt.
  [AI Act, Article 50(3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Model documentation
  Applies to: Providers of general-purpose AI models
  Keep up-to-date technical documentation of the model for the AI Office and national authorities (Annex XI), and information for providers integrating the model (Annex XII). Open-source models with public parameters are exempt unless they carry systemic risk.
  [AI Act, Article 53(1)(a), (b), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Human oversight

**Only AI Act** no specific requirement on the other side in the acts covered

- Design for human oversight
  Applies to: Providers of high-risk AI systems
  Design the system so people can effectively oversee it in use: understand its limits, watch for automation bias, interpret output, disregard or override it, and stop it safely. For remote biometric identification under Annex III, point 1(a), no action is taken on an identification unless at least two competent people verify it separately. This does not apply in law enforcement, migration, border control or asylum where Union or national law considers it disproportionate.
  [AI Act, Article 14(1), (3) to (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Use as instructed and assign oversight
  Applies to: Deployers of high-risk AI systems
  Use the system in line with its instructions through appropriate technical and organisational measures. Assign human oversight to people with the necessary competence, training, authority and support. Where you control input data, ensure it is relevant and sufficiently representative for the intended purpose.
  [AI Act, Article 26(1), (2), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Conformity assessment and monitoring

**Only AI Act** no specific requirement on the other side in the acts covered

- Technical documentation
  Applies to: Providers of high-risk AI systems
  Draw up technical documentation with at least the Annex IV elements before placing the system on the market or putting it into service, and keep it up to date. SMEs and small mid-caps may use the Commission's simplified form. Products under Annex I, Section A legislation need a single set of documentation.
  [AI Act, Article 11(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Monitor use and report problems
  Applies to: Deployers of high-risk AI systems
  Monitor operation on the basis of the instructions. If use may present a risk, inform the provider or distributor and the market surveillance authority without undue delay and suspend use. If you identify a serious incident, immediately inform the provider first, then the importer or distributor and the market surveillance authorities.
  [AI Act, Article 26(5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Conformity assessment
  Applies to: Providers of high-risk AI systems
  Annex III, point 1 systems may choose internal control or a notified body where harmonised standards or common specifications are fully applied, and otherwise use a notified body. Annex III, points 2 to 8 use internal control, and Annex I, Section A systems follow the sectoral procedure. A substantial modification needs a new assessment. For systems that continue to learn, changes pre-determined at the initial assessment and documented are not a substantial modification.
  [AI Act, Article 43(1) to (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- EU declaration of conformity and CE marking
  Applies to: Providers of high-risk AI systems
  Draw up an EU declaration for each system with the Annex V content, keep it up to date and available for 10 years, and accept responsibility for compliance by drawing it up. Affix the CE marking visibly, legibly and indelibly, or digitally for systems provided digitally, with the notified body number where applicable.
  [AI Act, Articles 47, 48](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Post-market monitoring
  Applies to: Providers of high-risk AI systems
  Establish and document a post-market monitoring system, proportionate to the technology and risk, that actively collects and analyses performance data throughout the system's lifetime to evaluate continuing compliance. Base it on a plan held in the technical documentation.
  [AI Act, Article 72(1) to (3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

**Only AI Act** no specific requirement on the other side in the acts covered

- Register in the EU database
  Applies to: Providers of Annex III AI systems or their authorised representatives
  Before placing on the market or putting into service an Annex III high-risk system, or a system you concluded is not high-risk under Article 6(3), register yourself and the system in the EU database. Critical infrastructure systems under Annex III, point 2 are registered at national level.
  [AI Act, Article 49(1), (2), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Public bodies register their use
  Applies to: Deployers that are public authorities, Union bodies or persons acting on their behalf
  Before putting into service or using an Annex III high-risk system, other than a critical infrastructure system under point 2, register yourself, select the system and register its use in the EU database. Do not use a system that is not registered, and inform the provider or distributor.
  [AI Act, Articles 26(8), 49(3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Cooperation with supervisors

**Only AI Act** no specific requirement on the other side in the acts covered

- Keep documents and cooperate with authorities
  Applies to: Providers of high-risk AI systems
  Keep technical and quality system documentation, notified body decisions and the EU declaration available to authorities for 10 years. On a reasoned request, give the authority the information needed to show conformity and access to logs under your control.
  [AI Act, Articles 18(1), 21](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Penalties and liability

**AI Act more detailed** more requirements on this, not necessarily stricter

- Fines for prohibited practices
  Applies to: Operators of AI systems
  Breach of the Article 5 prohibitions carries fines of up to EUR 35 million or 7% of total worldwide annual turnover, whichever is higher. For SMEs and start-ups the lower of the two applies.
  [AI Act, Article 99(3), (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for operator obligations
  Applies to: Operators of AI systems and notified bodies
  Breach of the obligations of providers, authorised representatives, importers, distributors, deployers and notified bodies, or of Article 50 transparency, carries fines of up to EUR 15 million or 3% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
  [AI Act, Article 99(4), (6), (6a)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for misleading information
  Applies to: Anyone supplying information to notified bodies or national competent authorities in reply to a request
  Supplying incorrect, incomplete or misleading information to notified bodies or national authorities in reply to a request carries fines of up to EUR 7.5 million or 1% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
  [AI Act, Article 99(5), (6), (6a)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for general-purpose AI model providers Optional
  Applies to: Providers of general-purpose AI models
  The Commission may fine a provider that intentionally or negligently infringes the Regulation, fails to answer an information request correctly, or does not comply with a requested measure or evaluation access, up to 3% of annual total worldwide turnover or EUR 15 million, whichever is higher.
  [AI Act, Article 101(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Administrative penalties
  Applies to: Competent authorities and Member States
  Competent authorities have supervisory, investigatory and sanctioning powers; Member States set the administrative penalties and remedial measures.
  [DORA, Article 50](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare AI Act](https://grc.plus/compare/ai-act/)
- [Compare DORA](https://grc.plus/compare/dora/)

Source: https://grc.plus/compare/ai-act-vs-dora/
