> AI Act vs GDPR Lithuania 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 GDPR Lithuania

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

[GDPR Lithuania](https://grc.plus/regulation/general-data-protection-regulation-gdpr/lithuania/)Controllers and processors

## At a Glance

They differ on 13 of 22 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 Lithuania** Asks more on 0 topics Alone on 0 topics More detailed on 1 topic

| Topic | AI Act | GDPR Lithuania | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | AI Act: 3 | GDPR Lithuania: 2 | **Both cover it**read the wording below |
| Awareness and training | AI Act: 1 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | AI Act: 1 | GDPR Lithuania: 1 | **Both cover it**read the wording below |
| Risk assessment | AI Act: 1 | GDPR Lithuania: 1 | **Both cover it**read the wording below |
| Review, audit and improvement | AI Act: 1 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Data security | AI Act: 1 | GDPR Lithuania: 2 | **Both cover it**read the wording below |
| Secure acquisition and development | AI Act: 1 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | AI Act: 2 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Incident handling | AI Act: 2 | GDPR Lithuania: 1 | **Both cover it**read the wording below |
| Reporting to authorities | AI Act: 4 | GDPR Lithuania: 3 | **Both cover it**read the wording below |
| Continuity and resilience |  |  |  |
| Threat-led penetration testing | AI Act: 1 | GDPR Lithuania: – | **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 | GDPR Lithuania: 2 | **Both cover it**read the wording below |
| Contract requirements | AI Act: 1 | GDPR Lithuania: 1 | **Both cover it**read the wording below |
| Privacy and data protection |  |  |  |
| Impact assessment | AI Act: 1 | GDPR Lithuania: 3 | **GDPR Lithuania more detailed**more requirements on this, not necessarily stricter |
| Artificial intelligence |  |  |  |
| Risk classification of AI systems | AI Act: 4 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Data and data governance | AI Act: 3 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Transparency to users | AI Act: 6 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Human oversight | AI Act: 2 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Conformity assessment and monitoring | AI Act: 5 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | AI Act: 2 | GDPR Lithuania: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | AI Act: 1 | GDPR Lithuania: 1 | **Both cover it**read the wording below |
| Penalties and liability | AI Act: 4 | GDPR Lithuania: 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

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

National requirements

None recorded yet, so the Directive is shown as it is. The national law may go further.

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 Lithuania: At the time the data are obtained (Controllers); 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 (Controllers); 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 (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); 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 (Controllers)

### Threshold

AI Act: Not in the acts covered

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

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

GDPR Lithuania: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

### 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 Lithuania: Competent supervisory authority (Controllers)

### First notice of an incident

AI Act: Immediately, and within 15 days of becoming aware; within 2 days for a widespread infringement or a serious and irreversible disruption of critical infrastructure; within 10 days where a person has died (Providers of high-risk AI systems)

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

### Intermediate report

AI Act: Not in the acts covered

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

GDPR Lithuania: 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 Lithuania: Approved code of conduct or certification may help show compliance (Controllers)

### Review of the risk framework

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

GDPR Lithuania: Where necessary (Controllers)

### Testing of critical systems

AI Act: Not in the acts covered

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

- 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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### 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)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

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)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Measures to ensure and show compliance
  Applies to: Controllers
  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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

Nothing in the acts covered.

## Protection

### 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)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Integrity and confidentiality
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

Nothing in the acts covered.

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

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

- Document every breach
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### 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 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

## Continuity and resilience

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

- Use only processors with sufficient guarantees
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Contract requirements

**Both cover it** read the wording below

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

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

- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

## Privacy and data protection

### Impact assessment

**GDPR Lithuania 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)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- When an impact assessment is needed
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- What the assessment contains
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Prior consultation
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

## Artificial intelligence

### Risk classification of AI systems

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

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

Nothing in the acts covered.

### Data and data governance

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

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

Nothing in the acts covered.

### Transparency to users

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

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

Nothing in the acts covered.

### Human oversight

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

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

Nothing in the acts covered.

### Conformity assessment and monitoring

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

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

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

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

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

Nothing in the acts covered.

### Cooperation with supervisors

**Both cover it** read the wording below

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

- 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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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. 12 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare AI Act](https://grc.plus/compare/ai-act/)
- [Compare GDPR Lithuania](https://grc.plus/compare/gdpr-lithuania/)

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