Artificial Intelligence Policy Tracker
Legal requirement Accuracy, robustness and cybersecurity European Union Partially applicable

Providers of systemic-risk GPAI models must secure the model and its infrastructure

Download: JSON · MarkdownUnder EU AI Act, Article 55(1)(d)

Verified against the official source 26 Sep 2026 (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Providers of systemic-risk GPAI models must secure the model and its infrastructure is a legal requirement under the EU AI Act in the European Union (Article 55(1)(d)). It applies from 2 August 2025. The record carries 2 evidence examples and mappings to 3 frameworks.

Instrument
EU AI Act
Jurisdiction
European Union
Nature
Legal requirement
Source reference
Article 55(1)(d)
Applies from
2 August 2025
Who it binds
General-purpose AI model provider
Evidence examples
2
Framework mappings
ISO/IEC 27001:2022, NIST AI Risk Management Framework 1.0, MITRE ATLAS
Controls that meet it
2
Official source
Open official text
Verification
Verified against the official source 26 Sep 2026

What does it require?

Providers of general-purpose AI models with systemic risk must ensure an adequate level of cybersecurity protection for the model and for the physical infrastructure it runs on, which in practice covers protection of model weights, training and inference environments, and access controls against theft, tampering and unauthorised release. Codes of practice and harmonised standards may be used to show compliance.

Practical action

Apply a documented security standard to weight storage, training clusters and inference endpoints, with penetration tests and insider-risk controls.

Who does it apply to?

Providers of general-purpose AI models classified as having systemic risk under Article 51.

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesTechnical measureQuality or testing lead · at launch and on material change
    Accuracy, robustness, fairness and security testing

    Serves 15 recorded duties · evidence: Pre-release test report, Test plan and acceptance criteria, Release test sign-off

    Security testing of the model and its serving infrastructure.

  • supportsPolicyHead of AI safety · annual
    Frontier model safety and security framework

    Serves 9 recorded duties · evidence: Published frontier safety framework, Dangerous-capability evaluation report, Threshold notification to an authority

    Framework commits to the weight-security measures.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 7 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Model and infrastructure security assessmentreport
Weight access control recordsrecord

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every European Union duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 27001:2022Clause 8.1; Annex A 5.15, A 8.24Access control and cryptography applied to model assets.medium
NIST AI RMF 1.0MEASURE 2.7, MANAGE 2.2Security and resilience of the system.medium
MITRE ATLASAML.M0005, AML.M0001Control access to models and limit artifact release.medium

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under EU AI Act (Article 55(1)(d)).

Who must comply with this obligation?

Providers of general-purpose AI models classified as having systemic risk under Article 51.

When does this obligation apply?

It applies from 2 August 2025.

What evidence shows compliance?

A reviewer would expect: Model and infrastructure security assessment; Weight access control records.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 27001:2022 Clause 8.1; Annex A 5.15, A 8.24, NIST AI Risk Management Framework 1.0 MEASURE 2.7, MANAGE 2.2, MITRE ATLAS AML.M0005, AML.M0001. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Accuracy, robustness, fairness and security testing; Frontier model safety and security framework.

What should an organisation do in practice?

Apply a documented security standard to weight storage, training clusters and inference endpoints, with penetration tests and insider-risk controls.

Cite this record

AIPolicyTracker (2026). “Providers of systemic-risk GPAI models must secure the model and its infrastructure (EU AI Act)” [AIPT-OBL-0046, verified 26 September 2026]. https://aipolicytracker.org/id/AIPT-OBL-0046 (accessed 8 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0046: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.

BibTeX
@misc{aipolicytracker2026_providersofsystemicriskg,
  author       = {{AIPolicyTracker}},
  title        = {{Providers of systemic-risk GPAI models must secure the model and its infrastructure (EU AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-art-55-systemic-risk-cybersecurity}},
  url          = {https://aipolicytracker.org/obligations/eu-ai-act-art-55-systemic-risk-cybersecurity},
  urldate      = {2026-11-08},
  note         = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.