Skip to content
Reporting obligations

Setting up access to ENISA’s single reporting platform

4 min read

Notifications under Art. 14 CRA are submitted exclusively via ENISA’s Single Reporting Platform (SRP). With a 24-hour deadline there is no time to create accounts first. This guide shows what you can prepare and how registration works – based on the ENISA FAQ, as of 15 October 2026.

What the platform is for

The manufacturer notifies actively exploited vulnerabilities and severe incidents simultaneously to the CSIRT designated as coordinator and to ENISA – via the single reporting platform under Article 16 CRA (Art. 14(1), (3) and (7)). The platform has been running since 11 September 2026 at portal.cra-srp.enisa.europa.eu.

  • The platform is only available in English.
  • Its first release has no interface (API); notifications are entered in the web interface. You may still automate your internal processes.
  • The platform does not yet accept voluntary reports under Article 15 – only mandatory notifications under Article 14.

Source: Art. 14(1), (3), (7) CRA · ENISA FAQ on the Single Reporting Platform, No 15, 24, 27 · ENISA: CRA Single Reporting Platform

Step 1: Create EU Login accounts with multi-factor authentication

Whoever reports for the manufacturer is called an “Assigned Representative” (AR) on the platform. Each AR needs their own EU Login account with multi-factor authentication switched on. The accounts are personal; each AR should report with their own account. The platform does not currently require any additional authentication of the company.

The EU Login account can be created in advance. This is the part you can do today without burdening the CSIRTs.

Source: ENISA FAQ on the Single Reporting Platform, No 9

Step 2: Define roles

Per manufacturer there is exactly one primary AR and up to 20 further ones (Secondary ARs):

  • The primary AR registers the manufacturer, manages the association and invites or removes further ARs.
  • The primary AR can only invite further ARs once the association with the manufacturer has been confirmed (“Verified”).
  • All ARs of a manufacturer can see, continue and update its notifications – including the follow-up stages. Exception: drafts are stored only in the account of the AR concerned.
  • A further AR can take over the role of primary AR; the competent CSIRT must confirm this.

Plan for at least one deputy. Because drafts are not shared, a notification that has been started should not be left as a draft if someone is unavailable.

Source: ENISA FAQ on the Single Reporting Platform, No 9

Step 3: Determine the competent CSIRT

When registering, you choose the CSIRT designated as coordinator (on the platform “CSIRT Designated as Coordinator”, CDaC). Under Art. 14(7), the competent CSIRT is that of the Member State of the main establishment – where the decisions related to the cybersecurity of the products are predominantly taken; otherwise the Member State of the establishment with the highest number of employees in the Union. For manufacturers established in Germany, this is CERT-Bund at the BSI.

The choice is your responsibility. If the wrong CSIRT is selected, the notification may be declared invalid and has to be resubmitted to the correct CSIRT.

Source: Art. 14(7) CRA · ENISA FAQ on the Single Reporting Platform, No 18 · ENISA: list of CSIRTs designated as coordinators

Step 4: Register – when and how

  1. On portal.cra-srp.enisa.europa.eu, choose “Assigned Representative” and sign in with the EU Login account.
  2. As primary AR, select the competent CSIRT and enter the manufacturer’s details. This creates the first association with the manufacturer.
  3. Further ARs receive an invitation after confirmation and confirm the pre-filled manufacturer details.

ENISA advises registering and triggering the verification only when a notification is actually needed – to relieve the CSIRTs. According to ENISA, registration takes only a few minutes with an existing EU Login account.

Mistyped the manufacturer’s name? Simply register the manufacturer again with the correct name. If the wrong entry was confirmed by mistake, ask the CSIRT to reject it.

Source: ENISA FAQ on the Single Reporting Platform, No 9, 28, 32

Step 5: Confirmation by the CSIRT

The competent CSIRT verifies the association between AR and manufacturer. Each CSIRT sets its own procedure and timing. Verification runs in parallel with reporting: until confirmation, an AR can submit up to 20 notifications for the manufacturer. You can see the status under Settings > Association Management.

Source: ENISA FAQ on the Single Reporting Platform, No 9

In an emergency: what you should know

  • Deadlines: the platform’s 72-hour counter currently shows a deadline 48 hours after the early warning notification – not 72 hours after becoming aware. There is no counter for the final report on a vulnerability, because the deadline depends on the availability of a correction; for severe incidents it shows one month after the incident notification. The counters do not replace your own deadline monitoring.
  • Outage: if the platform is not reachable, wait and then report. If immediate notice is needed, contact the CSIRT directly – the notification must still be submitted via the platform afterwards.
  • Erroneous notification: only the competent CSIRT can close a notification. Ask it directly or via the field for additional comments.

Source: ENISA FAQ on the Single Reporting Platform, No 25, 26, 34

Checklist

  • Appoint the primary AR and at least one deputy.
  • Create a personal EU Login account with multi-factor authentication for each of them and test the sign-in once.
  • Record the competent CSIRT and fix the exact manufacturer name for registration.
  • Prepare text modules for the early warning notification and the notification in English.
  • Note the contact route to the CSIRT in case the platform is unavailable.

Related guides

Terms in the Cyber Resilience Act glossary

Sources

First published 19 Oct 2026, last updated 19 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.