Definition

What is a severe incident under the CRA?

Severe incident having an impact on the security of the product · also: Severe incident

Short answer

An incident that negatively affects the product's ability to protect sensitive data or functions, or introduces malicious code — reportable under Article 14.

An incident having an impact on the security of a product with digital elements that negatively affects or is capable of negatively affecting the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led to the introduction or execution of malicious code in the product or in the network and information systems of its users. Severe incidents follow the same 24-hour and 72-hour reporting steps as exploited vulnerabilities, with a final report one month after the notification.

Reference: Art. 3(45); Art. 14(4)–(5)

Updated · Paraphrase for orientation, not legal advice.

Share:LinkedInXE-mail

Frequently asked questions

What are the reporting deadlines for a severe incident?
An early warning within 24 hours of awareness (including whether malicious or unlawful acts are suspected), a notification within 72 hours, and a final report within one month after the 72-hour notification.
Is a compromised build server a severe incident?
It can be: an incident that leads to malicious code being introduced into the product, or that compromises the product's ability to protect important data or functions, meets the definition even if no customer has yet been harmed. Assess and record the reasoning with the awareness time.

In practice

Related terms

Know your Article 14 deadlines before you need them.

Enter an awareness time and get the 24-hour, 72-hour and final-report deadlines in your timezone.