Incident to report to a regulator?Incident to report? Intake Line

AI Act vs GDPR

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

AI ActProviders and deployers of AI systems

GDPRControllers and processors

At a Glance

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

  • AI Act Asks more on 0 topics Alone on 11 topics More detailed on 1 topic
  • GDPR Asks more on 0 topics Alone on 12 topics More detailed on 1 topic
Requirements per topic and verdict
Topic AI ActGDPR Verdict
Governance
Roles and independence AI Act: 3 GDPR: 2 Both cover itread the wording below
Awareness and training AI Act: 1 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Risk management
Risk management framework AI Act: 1 GDPR: 1 Both cover itread the wording below
Risk assessment AI Act: 1 GDPR: 1 Both cover itread the wording below
Review, audit and improvement AI Act: 1 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Protection
Cryptography and encryption AI Act: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Data security AI Act: 1 GDPR: 2 Both cover itread the wording below
Secure acquisition and development AI Act: 1 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Human resources security AI Act: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection AI Act: 2 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Incident handling AI Act: 2 GDPR: 1 Both cover itread the wording below
Reporting to authorities AI Act: 4 GDPR: 3 Both cover itread the wording below
Informing customers and the public AI Act: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Continuity and resilience
Backup and recovery AI Act: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Security testing AI Act: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Threat-led penetration testing AI Act: 1 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk AI Act: 2 GDPR: 2 Both cover itread the wording below
Contract requirements AI Act: 1 GDPR: 1 Both cover itread the wording below
Privacy and data protection
Lawful processing AI Act: – GDPR: 7 Only GDPRno specific requirement on the other side in the acts covered
Transparency AI Act: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Rights of individuals AI Act: – GDPR: 7 Only GDPRno specific requirement on the other side in the acts covered
Privacy by design and by default AI Act: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Impact assessment AI Act: 1 GDPR: 3 GDPR more detailedmore requirements on this, not necessarily stricter
Records of processing AI Act: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Data protection officer AI Act: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
International transfers AI Act: – GDPR: 4 Only GDPRno specific requirement on the other side in the acts covered
Artificial intelligence
Risk classification of AI systems AI Act: 4 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Data and data governance AI Act: 3 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Transparency to users AI Act: 6 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Human oversight AI Act: 2 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Conformity assessment and monitoring AI Act: 5 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities AI Act: 2 GDPR: – Only AI Actno specific requirement on the other side in the acts covered
Cooperation with supervisors AI Act: 1 GDPR: 1 Both cover itread the wording below
Penalties and liability AI Act: 4 GDPR: 2 AI Act more detailedmore 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 Articles 4 to 6, 8 to 27, 43, 47 to 50, 53, 55, 72, 73, 99, 101, 111 · 49 requirements
  • KI-loven Draft act on artificial intelligence (KI-loven), consultation of 30 June 2025 Articles 5, 50 · 4 requirements
  • Decreet 16 oktober 2026 Decreet van 16 oktober 2026, Belgisch Staatsblad 19 November 2026, numac 2026008360 3 requirements
  • No. 31/2026 Regulation of Artificial Intelligence Act 2026 (No. 31 of 2026) 5 requirements

Status

Reviewed against the official texts.

Included

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

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)

GDPR: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Threshold

AI Act: Not in the acts covered

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

Goes to

AI Act: Market surveillance authorities and, where applicable, the notified body (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); 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)

GDPR: Controller (Processors); Data subjects (Controllers)

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 (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); Documentation, 10 years after placing on the market or putting into service (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); 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)

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

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)

GDPR: Competent supervisory authority (Controllers)

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

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

Intermediate report

AI Act: Not in the acts covered

GDPR: In phases, without undue further delay (Controllers)

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) (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); 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)

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

GDPR: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Review of the risk framework

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

GDPR: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Testing of critical systems

AI Act: Not in the acts covered

GDPR: Regularly

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)

GDPR: Not in the acts covered

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

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

Governance

Roles and independence

Both cover it read the wording below

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

  • Provider obligations

    Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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

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

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

  • Joint controllers

    Applies to: Joint controllers

    Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.

    GDPR, Article 26

  • EU representative

    Applies to: Controllers and processors not established in the EU, under Article 3(2)

    A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.

    GDPR, Article 27

Awareness and training

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

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)

Nothing in the acts covered.

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)

  • Measures to ensure and show compliance

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.

    GDPR, Article 24

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)

  • Assess security risk

    When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.

    GDPR, Article 32(2)

Review, audit and improvement

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

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: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

Nothing in the acts covered.

Protection

Cryptography and encryption

Only GDPR 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.

  • Pseudonymisation and encryption

    Apply pseudonymisation and encryption of personal data, as appropriate to the risk.

    GDPR, Article 32(1)(a)

Data security

Both cover it read the wording below

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)

  • Integrity and confidentiality

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.

    GDPR, Article 5(1)(f)

  • Security of systems and services

    Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.

    GDPR, Article 32(1)(b)

Secure acquisition and development

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

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

  • Accuracy, robustness and cybersecurity

    Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

Nothing in the acts covered.

Human resources security

Only GDPR 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.

  • Staff act only on instructions

    Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.

    GDPR, Articles 29 and 32(4)

Detection and response

Monitoring and detection

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

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

  • Automatic logs

    Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

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

Nothing in the acts covered.

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: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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

  • Investigate a serious incident

    Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

  • Document every breach

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.

    GDPR, Article 33(5)

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)

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

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

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

  • Notify a personal data breach

    Applies to: Controllers

    Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.

    GDPR, Article 33(1)

  • Processor tells the controller

    Applies to: Processors

    Tell the controller of a personal data breach without undue delay after becoming aware of it.

    GDPR, Article 33(2)

  • What the breach notice contains

    Applies to: Controllers

    Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.

    GDPR, Article 33(3) and (4)

Informing customers and the public

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

Nothing in the acts covered.

  • Tell the people affected

    Applies to: Controllers

    Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.

    GDPR, Article 34(1) to (4)

Continuity and resilience

Backup and recovery

Only GDPR 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.

  • Restoring access after an incident

    Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.

    GDPR, Article 32(1)(c)

Security testing

Only GDPR 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.

  • Testing the measures

    Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.

    GDPR, Article 32(1)(d)

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)

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)

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

  • Use only processors with sufficient guarantees

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.

    GDPR, Article 28(1)

  • Sub-processors

    Applies to: Processors

    Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.

    GDPR, Article 28(2) and (4)

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)

  • Processing contract

    Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.

    GDPR, Article 28(3) and (9)

Privacy and data protection

Lawful processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

  • Purpose limitation and data minimisation

    Applies to: Controllers

    Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.

    GDPR, Article 5(1)(b) and (c)

  • Accuracy and storage limitation

    Applies to: Controllers

    Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.

    GDPR, Article 5(1)(d) and (e)

  • Accountability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.

    GDPR, Article 5(2)

  • Lawful basis

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.

    GDPR, Articles 5(1)(a) and 6(1)

  • Conditions for consent

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.

    GDPR, Article 7

  • Children's consent to online services

    Applies to: Controllers offering information society services directly to children

    Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.

    GDPR, Article 8(1) and (2)

  • Special category and criminal offence data

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.

    GDPR, Articles 9 and 10

Transparency

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

  • Information when collecting from the person

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.

    GDPR, Articles 12(1) and 13

  • Information when data comes from elsewhere

    Applies to: Controllers

    Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.

    GDPR, Article 14

Rights of individuals

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

  • Answer rights requests in time

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.

    GDPR, Article 12(3) to (5)

  • Right of access

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.

    GDPR, Article 15

  • Rectification, restriction and telling recipients

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.

    GDPR, Articles 16, 18 and 19

  • Right to erasure

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.

    GDPR, Article 17

  • Right to data portability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.

    GDPR, Article 20

  • Right to object

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.

    GDPR, Article 21

  • Solely automated decisions

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.

    GDPR, Article 22

Privacy by design and by default

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

Nothing in the acts covered.

  • Data protection by design

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.

    GDPR, Article 25(1)

  • Data protection by default

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.

    GDPR, Article 25(2)

Impact assessment

GDPR more detailed more requirements on this, not necessarily stricter

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)

  • When an impact assessment is needed

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.

    GDPR, Article 35(1) and (3)

  • What the assessment contains

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.

    GDPR, Article 35(2), (7), (9) and (11)

  • Prior consultation

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.

    GDPR, Article 36(1) to (3)

Records of processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.IM-P

Nothing in the acts covered.

  • Controller's record of processing

    Applies to: Controllers

    Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.

    GDPR, Article 30(1), (3), (4) and (5)

  • Processor's record of processing

    Applies to: Processors

    Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.

    GDPR, Article 30(2) to (5)

Data protection officer

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework GV.PO-P

Nothing in the acts covered.

  • Designate a data protection officer

    Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.

    GDPR, Article 37(1), (5) and (7)

  • Position and tasks of the DPO

    Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.

    GDPR, Articles 38 and 39

International transfers

Only GDPR no specific requirement on the other side in the acts covered

Nothing in the acts covered.

  • Transfers need a Chapter V ground

    Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.

    GDPR, Articles 44 and 45

  • Appropriate safeguards

    Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.

    GDPR, Articles 46 and 47

  • Third-country orders

    Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.

    GDPR, Article 48

  • Derogations for specific situations

    Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.

    GDPR, Article 49

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)

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

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

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

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)

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

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

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: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

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

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

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

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

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

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: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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)

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

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)

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

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

  • 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

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

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)

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

Nothing in the acts covered.

Cooperation with supervisors

Both cover it read the wording below

  • Keep documents and cooperate with authorities

    Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.

    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

  • Cooperate with supervisory authority powers

    Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.

    GDPR, Articles 31 and 58

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)

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

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

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

  • Fines for operational obligations

    Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.

    GDPR, Article 83(1) to (4)

  • Fines for principles, rights and transfers

    Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.

    GDPR, Article 83(5) and (6)

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

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…