> AI Act vs NIS2 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 NIS2

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

[NIS2](https://grc.plus/regulation/nis2/)Essential and important entities

## At a Glance

They differ on 33 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 10 topics More detailed on 2 topics
- **NIS2** Asks more on 0 topics Alone on 19 topics More detailed on 2 topics

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

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

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)

NIS2: 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)

NIS2: 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)

NIS2: 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)

NIS2: CSIRT or 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)

NIS2: Without undue delay and in any event within 24 hours of becoming aware Shortest stated

### Incident notification

AI Act: Not in the acts covered

NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

AI Act: Not in the acts covered

NIS2: On request

### Final report

AI Act: Not in the acts covered

NIS2: Within one month of the incident notification

### 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)

NIS2: 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)

NIS2: Not in the acts covered

### Review of the risk framework

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

NIS2: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Register of third-party arrangements

AI Act: Not in the acts covered

NIS2: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### 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)

NIS2: Required; changes without delay and in any event within two weeks

### Management body training

AI Act: Not in the acts covered

NIS2: Required

### Management body liability

AI Act: Not in the acts covered

NIS2: Yes, for infringements of Article 21

### 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) Highest stated

NIS2: Essential entities: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

## Governance

### Management accountability

**Only NIS2** 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 approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#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)

- Roles, responsibilities and authorities
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Security policy

**Only NIS2** 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.

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Network and information system security policy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A security policy approved by the management body, reviewed at least annually and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#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 follow training to identify risks and assess cybersecurity risk-management practices. Entities are encouraged to offer similar training to employees regularly.
  [NIS2, Article 20(2)](https://grc.plus/regulation/nis2/#requirements)
- Cyber hygiene and training
  Basic cyber hygiene practices and cybersecurity training.
  [NIS2, Article 21(2)(g)](https://grc.plus/regulation/nis2/#requirements)

## Risk management

### Risk management framework

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

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)

- Appropriate and proportionate measures
  Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.
  [NIS2, Article 21(1)](https://grc.plus/regulation/nis2/#requirements)
- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Risk assessment

**Both cover it** read the wording below

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)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Review, audit and improvement

**NIS2 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)

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements)
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements)
- Independent review
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Independent reviews of network and information security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Asset management

**Only NIS2** 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.

- Asset management
  Asset management.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Asset inventory
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.
  [NIS2 Implementing Regulation, Annex, point 12.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

## Protection

### Access control

**Only NIS2** 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.

- Access control policies
  Access control policies.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Access rights and privileged accounts
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Management of access rights, and stricter controls on privileged and system administration accounts.
  [NIS2 Implementing Regulation, Annex, points 11.2 and 11.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Authentication

**Only NIS2** 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.

- Multi-factor authentication
  Multi-factor or continuous authentication solutions, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)
- Multi-factor authentication
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Multi-factor or continuous authentication where appropriate, in line with the classification of the asset accessed.
  [NIS2 Implementing Regulation, Annex, point 11.7](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Cryptography and encryption

**Only NIS2** 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.

- Cryptography
  Policies and procedures on the use of cryptography and, where appropriate, encryption.
  [NIS2, Article 21(2)(h)](https://grc.plus/regulation/nis2/#requirements)

### Data security

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

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)

Nothing in the acts covered.

### Network security

**Only NIS2** 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 security and segmentation
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.
  [NIS2 Implementing Regulation, Annex, points 6.7 and 6.8](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Secure communications

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

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

Nothing in the acts covered.

- Secured communications
  Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#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)

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

### Configuration, change and patch management

**Only NIS2** 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.

- Configuration, change and patch management
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurity benefits and the reasons are documented.
  [NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Vulnerability handling

**Only NIS2** 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.

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

### Human resources security

**Only NIS2** 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 security
  Human resources security.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Background verification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.
  [NIS2 Implementing Regulation, Annex, point 10.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Physical and environmental security

**Only NIS2** 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.

- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Physical and environmental security
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Supporting utilities, protection against physical and environmental threats, and perimeter and physical access control.
  [NIS2 Implementing Regulation, Annex, points 13.1 to 13.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#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)

- Monitoring and logging
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Monitoring and logging of network and information systems to detect events that could be incidents.
  [NIS2 Implementing Regulation, Annex, point 3.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#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)

- Incident handling
  Procedures to handle incidents.
  [NIS2, Article 21(2)(b)](https://grc.plus/regulation/nis2/#requirements)

### Incident classification

**Only NIS2** 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.

- When an incident is significant
  An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.
  [NIS2, Article 23(3)](https://grc.plus/regulation/nis2/#requirements)
- Event assessment and classification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.
  [NIS2 Implementing Regulation, Annex, point 3.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)
- When an incident is significant
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).
  [NIS2 Implementing Regulation, Articles 3 to 14](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#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)

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Early warning
  An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  [NIS2, Article 23(4)(a)](https://grc.plus/regulation/nis2/#requirements)
- Incident notification
  An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
  [NIS2, Article 23(4)(b)](https://grc.plus/regulation/nis2/#requirements)
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements)
- Final report
  A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements)

### Informing customers and the public

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

NIST CSF 2.0 RS.CO, RC.CO

Nothing in the acts covered.

- Inform affected recipients
  Where appropriate, notify recipients of the services without undue delay of significant incidents likely to affect the provision of those services.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Warn of significant cyber threats
  Where applicable, tell recipients potentially affected by a significant cyber threat, without undue delay, what they can do about it and, where appropriate, about the threat itself.
  [NIS2, Article 23(2)](https://grc.plus/regulation/nis2/#requirements)

### Threat intelligence and information sharing

**Only NIS2** 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.

- Information-sharing arrangements Optional
  Entities may exchange cybersecurity information such as threats, vulnerabilities and indicators of compromise within information-sharing arrangements. Essential and important entities notify the competent authority when they join or withdraw.
  [NIS2, Article 29](https://grc.plus/regulation/nis2/#requirements)

## Continuity and resilience

### Business continuity and crisis management

**Only NIS2** 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.

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)

### Backup and recovery

**Only NIS2** 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.

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)
- Backup and redundancy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Backup copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.
  [NIS2 Implementing Regulation, Annex, point 4.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Security testing

**Only NIS2** 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.

- Security testing
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A policy and procedures for security testing of network and information systems.
  [NIS2 Implementing Regulation, Annex, point 6.5](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Threat-led penetration testing

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

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)

Nothing in the acts covered.

## 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)

- Supply chain security
  Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
  [NIS2, Article 21(2)(d)](https://grc.plus/regulation/nis2/#requirements)
- What to weigh for each supplier and service provider
  Entities weigh the specific vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
  [NIS2, Article 21(3)](https://grc.plus/regulation/nis2/#requirements)

### Contract requirements

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

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)

Nothing in the acts covered.

### Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Directory of suppliers
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A directory of direct suppliers and service providers, kept up to date.
  [NIS2 Implementing Regulation, Annex, point 5.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#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

**Both cover it** read the wording below

- 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)

- Register with the authority
  Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.
  [NIS2, Article 3(4)](https://grc.plus/regulation/nis2/#requirements)
- Registry of digital providers
  DNS, TLD, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements)

### 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)

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)
- Administrative fines
  Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
  [NIS2, Article 34(4) and (5)](https://grc.plus/regulation/nis2/#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 NIS2](https://grc.plus/compare/nis2/)

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