Reporting of vulnerabilities and incidents in accordance with the CRA Regulation
The Cyber Resilience Act (CRA) requires manufacturers to report actively exploited vulnerabilities and severe incidents affecting the security of their products with digital elements. Mandatory notifications are submitted through ENISA's Single Reporting Platform (SRP).
INCIBE-CERT is currently the CSIRT designated as coordinator for Spain, responsible for handling notifications through the SRP established by ENISA. It receives and handles notifications falling within its remit under Article 14(7) and coordinates them with ENISA and the other affected CSIRTs.
Who is this procedure intended for?
Manufacturers placing products with digital elements covered by the CRA on the European Union market. The obligation under Article 14 has applied since 11 September 2026, including to products placed on the market before that date. The person submitting the notification acts on behalf of the manufacturer, which remains responsible for complying with the obligation.
The competent CSIRT is determined primarily by the establishment where decisions on the cybersecurity of the products are taken, in accordance with Article 14(7). Where Spain is the relevant Member State, select “CSIRT Spain”. For manufacturers without a main establishment in the Union, the fallback rules set out in that Article apply.
What must be reported?
Actively exploited vulnerabilities. There must be reliable evidence that a malicious actor has exploited a vulnerability in the product without the system owner's permission.
Severe incidents. These must affect the security of the product and meet at least one of the following criteria:
- Negatively affect, or be capable of negatively affecting, the protection of the availability, authenticity, integrity or confidentiality of sensitive or important data or functions of the product.
- Have led, or be capable of leading, to the introduction or execution of malicious code in the product or in a user's network and information systems.
Which cases do not, on their own, trigger this obligation?
- The discovery of a vulnerability without reliable evidence of malicious exploitation, including its identification through good-faith research.
- The publication of a CVE or a proof of concept without evidence of active exploitation.
- Corporate incidents that neither affect the security of the product nor meet the CRA's severity criteria.
For third-party components, the impact on the product must be assessed and the conclusion documented. These cases may require vulnerability management, coordination or communication through other channels, even where mandatory notification under Article 14 is not required.
What are the deadlines?
- Early warning: without undue delay and no later than 24 hours after becoming aware of the event.
- Notification: without undue delay and no later than 72 hours after that same point in time, providing the available information required for the type of event.
- Final vulnerability report: no later than 14 days after a corrective or mitigating measure becomes available.
- Final severe incident report: within one month of submitting the 72-hour notification.
The investigation must begin immediately. Submission must not be postponed until all information is available or a definitive solution has been found. Information is completed progressively.
How do you access the platform and submit a notification?
- Create an EU Login account and enable multi-factor authentication.
- Access the SRP, choose Assigned Representative and select the competent CSIRT.
- Register the representative's and manufacturer's details and follow the verification procedure. Pending verification does not prevent the submission of notifications permitted by the platform.
- Create a notification, identify whether it concerns an actively exploited vulnerability or a severe incident, and complete the early warning.
- Submit the notification and retain its identifier. Proceed with the 72-hour notification and final report phases, updating the information as appropriate.
What information should be prepared?
The manufacturer's and representative's details; identification of the product, model and affected versions; the components involved; the date and time when the manufacturer became aware of the event; the evidence and impact; the Member States where the product has been made available; and the corrective or mitigating measures and recommended actions for users. The level of detail required depends on the event and the reporting phase. If a CVE identifier exists, it must be included; its absence does not justify delaying the notification.
Handling and follow-up
INCIBE-CERT analyses the notifications received and coordinates information with the relevant authorities. The manufacturer must respond to requests for information and communicate relevant developments. If it considers the information sensitive, it must provide justification through the mechanisms available on the SRP. A request to delay dissemination does not suspend the reporting deadlines.
The manufacturer must also inform affected users about the event and the measures they can take to mitigate its effects.
Guide, support channels and official documentation
Consult the practical guide for manufacturers on CRA reporting through the SRP, developed by INCIBE, for details of the complete procedure.
VIEW THE GUIDE
The following official resources provide further information on the CRA and help you prepare notifications. Check each document's last update date and use the latest available version.
INCIBE-CERT support channels
In addition to the practical guide for manufacturers on CRA reporting through the SRP, INCIBE-CERT provides the email address
for technical enquiries or questions about the European Cyber Resilience Act (CRA) and the SRP reporting platform.
Other relevant channels and services:
- INCIBE-CERT incident response: to report cybersecurity incidents and request support for their management and response, within the scope of INCIBE-CERT’s remit as set out in the National Guide to the Reporting and Management of Cyber Incidents.
- Vulnerability coordination and CVE assignment: to report vulnerabilities, facilitate their handling and coordinated disclosure with the parties involved, and request the assignment and publication of a CVE identifier where appropriate.
These channels do not replace mandatory notification through the SRP where required under the CRA.
Frequently asked questions
- SRP frequently asked questions — ENISA (English): answers about access, manufacturers' representatives, CSIRT selection, deadlines and notification follow-up.
- Frequently asked questions about CRA implementation — European Commission (English): general clarification on the implementation of the Regulation and access to the Commission's frequently asked questions document.
Supporting documentation for reporting
- CRA reporting obligations — European Commission (English): information on the events that must be reported, deadlines and communication through the SRP.
- SRP manuals, tutorials and documentation — ENISA (English): access to the user manual, video tutorial and instructions for registration and for submitting and updating notifications. Includes a factsheet available in Spanish.
- SRP field glossary — ENISA (English): descriptions of form fields, expected formats and the information required at each reporting phase.
- For further information on manufacturers' obligations throughout the product lifecycle, consult the European Commission's page on the CRA for manufacturers.
- Commission Guidelines on the application of Regulation (EU) 2024/2847 (Cyber Resilience Regulation)
Legal references and guidance
- Regulation (EU) 2024/2847 — Spanish text (BOE) (EUR-Lex): Full legal text of the CRA. Articles 14 and 16 govern reporting obligations and the Single Reporting Platform; Articles 69 and 71 set out the transitional provisions and application dates.
- Guidance on CRA implementation — European Commission (English): access to Communication C(2026) 5252 and its annex, providing guidance and practical examples on the scope and obligations of the CRA. This guidance is non-binding.


