AI and cybersecurity: the overlap of the Cyber Resilience Act and the AI Act
AI products must be both safe and cyber-resilient. The Cyber Resilience Act sets security requirements for products with digital elements, while the AI Act requires cybersecurity of high-risk systems — two frameworks meeting on one product.
Short answer: An AI product must not only function safely but also withstand attacks. The Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) sets cybersecurity requirements for virtually all products with digital elements. The AI Act additionally requires an appropriate level of cybersecurity for high-risk AI systems (Article 15). Both frameworks can apply to the same product.
What the Cyber Resilience Act governs
The CRA is a horizontal framework: it applies to products with digital elements, from software to connected devices. Core obligations are:
- Security by design: products are designed and supplied without known exploitable vulnerabilities.
- Vulnerability handling: manufacturers provide security updates during a support period.
- Reporting duty: actively exploited vulnerabilities and serious incidents must be reported.
Many AI systems are supplied as or within such products and thus fall under the CRA.
The requirements apply throughout the lifecycle, not only at first sale. A manufacturer must keep monitoring vulnerabilities and roll out patches for as long as the product is supported. This reflects the idea that security is a continuous obligation, not a one-off test.
What the AI Act requires
The AI Act approaches cybersecurity from the risk of the AI system itself. Article 15 requires that high-risk systems have an appropriate level of accuracy, robustness and cybersecurity.
This includes AI-specific threats: data poisoning (corrupting training data), adversarial attacks (deceptive input) and model evasion. These are risks that a classic security approach does not automatically cover.
An attacker need not crack the software to undermine an AI system; manipulating input or training data can be enough to force wrong outcomes. That is why the AI Act requires robustness and cybersecurity to be built into the design from the start.
One product, two conformity tracks
The big challenge is overlap without duplicated work. The CRA and the AI Act both pursue safe products, but from different starting points: the CRA generic, the AI Act AI-specific. The legislator intended alignment, so that a product subject to both does not have to run two entirely separate processes.
In practice this means: one risk assessment covering both angles, linked to the right transparency and documentation. As with sustainability reporting, it pays to bundle frameworks rather than run them in parallel.
What to do
- Map both frameworks: does your product fall under the CRA, the AI Act, or both?
- Apply security by design: ship without known exploitable vulnerabilities.
- Address AI-specific threats: test for data poisoning and adversarial attacks.
- Set up vulnerability and reporting processes in line with the CRA.
- Integrate the risk assessments of the CRA and AI Act into one coherent process.
Cyber resilience is not a separate layer on top of AI, but part of the robustness that both frameworks require.
Sources
- https://eur-lex.europa.eu/eli/reg/2024/2847/oj
Regulation (EU) 2024/2847 (Cyber Resilience Act); horizontal cybersecurity requirements for products with digital elements. - https://eur-lex.europa.eu/eli/reg/2024/1689/oj
Regulation (EU) 2024/1689 (AI Act); Art. 15 requires an appropriate level of cybersecurity for high-risk AI systems.
Read next
Securing AI in critical infrastructure: where the AI Act, Cyber Resilience Act and NIS2 meet
A single AI system in a port often falls under three frameworks at once: the AI Act (Art. 15) secures the AI system itself, the Cyber Resilience Act the product, and NIS2 obliges the operator as an essential entity. This piece explains how they meet and who is responsible for what.
The EU declaration of conformity under the AI Act (Article 47)
The EU declaration of conformity is the written statement by which the provider itself confirms that a high-risk AI system meets the AI Act. Article 47 sets out its content, language and retention; the provider bears full responsibility for it.
Distributor duties under the AI Act (Article 24)
A distributor makes a high-risk AI system available without being its provider or importer. Article 24 asks for a lighter but real check: confirm CE marking, declaration of conformity and documentation are present, and do not pass it on where there is doubt.