Skip to content
EU AI Act · EU-AI-ACT-ART-55-SYSTEMIC-ADVERSARIAL

EU AI Act Article 55(1)(a) - Obligations for providers of general-purpose AI models with systemic risk: model evaluation and ad…

Systemic risk GPAI providers must conduct adversarial testing (red-teaming) using state-of-the-art protocols and document the results, with a view to identifying and mitigating systemic risks

CRITICALAssessment dutyRisk assessmentBinding regulationIn forceEnforceable from 2 August 2025

Where this comes from

Provision: Article 55(1)(a) - Obligations for providers of general-purpose AI models with systemic risk: model evaluation and adversarial testing

Instrument: EU Artificial Intelligence Act (Regulation (EU) 2024/1689)

Citation: Article 55(1)(a), Regulation (EU) 2024/1689

Text version: Regulation (EU) 2024/1689, consolidated 27 July 2026; original OJ L 12 July 2024 and amendment (EU) 2026/1744

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

GPAI model provider in scope (Art. 2, Art. 3(63)) — all of these:

  • Project involves providing a general-purpose AI model (GPAI)
  • GPAI assessed Union model scope: YES
  • GPAI assessed Article 51 classification: YES

What engineering work it implies

  • AI Risk Management File (Living Register with Release Thresholds)Foundation only

    A continuously-updated risk register under Article 9, with accuracy and robustness thresholds recorded per release under Article 15 and post-market monitoring hooks...

Sample acceptance criteria Landfall generates for this obligation:

  • Record evaluation protocols and tools reflecting the state of the art, model version and evaluation results
  • Conduct and document adversarial testing aimed at identifying and mitigating systemic risks under Article 55(1)(a)
  • Keep the Article 55(1)(b) systemic-risk assessment distinct from Article 55(1)(c) incident reporting
  • Record the model-provider scope, relevant model version and Article 111(3) placement-date transition before an enforcement conclusion
  • Record the model, evaluation protocol and tools, adversarial-testing results, limitations and mitigation follow-up

Evidence an auditor expects

  • Test resultsDocument review

    Model evaluation and documented adversarial testing (Article 55(1)(a))

    Identify the evaluated model version, standardised protocol and tools, testing methods and results, limitations, systemic risks found and mitigation follow-up. Explain how methods reflect the state of the art. Independent testing and a particular cadence require a separate basis, not an automatic statutory claim.

  • Assessment documentDocument review

    Related systemic-risk assessment and mitigation record (Article 55(1)(b))

    Assess Union-level systemic risks and sources from development, market placement or use, with mitigations and their evidence. This is a distinct Article 55(1)(b) duty; the dedicated scope record remains to be added under L02.

Questions people ask

Does EU AI Act Article 55(1)(a) - Obligations for providers of general-purpose AI… apply to my service?
It applies when Project involves providing a general-purpose AI model (GPAI); GPAI assessed Union model scope: YES; GPAI assessed Article 51 classification: YES.
When does this become enforceable?
EU AI Act Article 55(1)(a) - Obligations for providers of general-purpose AI… is enforceable from 2 August 2025. Its current status is: in force.
What evidence does an auditor expect?
Model evaluation and documented adversarial testing (Article 55(1)(a)); Related systemic-risk assessment and mitigation record (Article 55(1)(b)).

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations