AIM SHIELD Emergency
CRA notice · Free

An exploited flaw or a serious incident in your product? Notify it on time

Since 11 September 2026, if you make software or connected devices, you have to notify the authorities through ENISA's platform in three steps: 24 hours, 72 hours and a final report. Here you have the clock for the three deadlines and the three drafts, with the platform's fields. Everything is written in your browser: nothing reaches us.

How it works, in five steps

  1. Write down the time you found out. The deadlines run from when you become aware, not from when it happened: they are consecutive hours from that moment. If you do not know the exact time, give your best estimate and say in the description that it is an estimate.
  2. Early warning, within 24 hours. The essentials: what it is, which product and version, in which countries it is sold and when you found out. Do not wait until you know everything.
  3. Notification, within 72 hours. The general information and when it happened; for an incident, also a first assessment.
  4. Final report. For a vulnerability, at the latest 14 days after a patch or other measure is available; for a serious incident, within a month of the 72-hour notification. With the measures, the severity and the impact.
  5. All through ENISA's platform. Just once, to the CSIRT of the country of your main establishment; ENISA receives it at the same time. You need an EU Login account with two-step verification.

The platform is at portal.cra-srp.enisa.europa.eu. Not sure whether your product falls under the CRA? First do the CRA Diagnostic.

1. What has happened?

2. When did you find out?

If your browser doesn't show the calendar, write it like this: 14/10/2026 10:30. If you don't know the exact time, put the best estimate and say in the summary that it is estimated.

3. The product

4. What you already know

Do you suspect an unlawful or malicious act?
Will there soon be a patch or other measure?

5. For the 72-hour notification

6. For the final report (you can fill it in later)

None of this leaves your browser. If you close the page, it is lost: download or print the drafts.

Early warning (24 hours)

Each line is a field on the platform, with its name in English: copy it into its place. “required” is mandatory at this step; what is missing comes out as “[to be completed]”.

Notification (72 hours)

Each line is a field on the platform, with its name in English: copy it into its place. “required” is mandatory at this step; what is missing comes out as “[to be completed]”.

Final report

Each line is a field on the platform, with its name in English: copy it into its place. “required” is mandatory at this step; what is missing comes out as “[to be completed]”.

Frequently asked questions

Does it affect me if my product was sold before 11 September 2026?

Yes. The obligation applies from 11 September 2026 to all products with digital elements within the CRA, including those already on the market. An actively exploited vulnerability that you knew about before that date does not have to be notified retroactively; if you find out afterwards that it is being exploited, you do, even if the flaw was already known.

Which CSIRT does the notification go to?

To the one in the Member State of your main establishment in the EU, and you choose it on the platform. In Spain it is INCIBE-CERT, according to ENISA's list of coordinator CSIRTs. If it isn't clear, to the one in the EU country where you have most employees. If you are outside the EU, ENISA gives an order: your authorised representative, your importer, your distributor and, lastly, where you have most users. If you choose the wrong one, the notification may be invalidated and you will have to submit it again.

What do I need to log in to the platform?

A personal EU Login account with two-step verification (not a shared account). The first person to register for your company is the main representative; once the company shows as verified, they can invite up to 20 more. You can send notifications while your registration is being verified. ENISA advises registering on the platform when a notification is needed. Our advice: since the clock runs from the first minute, have at least the EU Login account with two-step verification ready from today.

What language is the platform in?

For now, in English only. That is why the drafts carry each field's name in English, so you can copy each answer into its place.

The platform marks my 72-hour notification as late. Why?

Its counter sets the deadline 48 hours after the early warning is sent, so it may mark it ahead of time; and if you sent the early warning late, its counter will give you more margin than you really have. What counts is the moment you became aware: go by the clock on this page, which starts from there.

I am a micro or small business: what happens if I don't make it within 24 hours?

The European Commission states that micro and small enterprises cannot be fined for missing the 24-hour early warning deadline. The obligation to notify is still there: send it as soon as you can, and the 72-hour notification and the final report within their deadlines.

What if the platform doesn't work?

ENISA says to wait until it comes back and then send the notification; meanwhile, you can contact your CSIRT directly. Even so, it has to be submitted through the platform. Write down the time of each attempt.

Can I notify a flaw that isn't being exploited?

Voluntary notification will come in a later phase of the platform, according to ENISA. Today the platform collects the mandatory ones: actively exploited vulnerabilities and serious incidents.

Do I have to warn my customers too?

Yes. When you learn of an actively exploited vulnerability or a serious incident, the Regulation asks you to inform the affected users of your product (and, where relevant, all of them) and, if needed, of the measures they can take to reduce the harm, in a structured, machine-readable format where appropriate (for example, a security advisory in CSAF). If you don't do it in time, the CSIRT may warn them itself when it considers it proportionate and necessary. A good notice says which products and versions are affected, what the risk is, what to do now (update, turn something off, change passwords) and when there will be a fix.

When is an incident “serious”?

When it affects, or may adversely affect, your product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions; or when it has led, or may lead, to malicious code being introduced or run in your product or in the network and systems of whoever uses it. For example: someone publishes a fake update with your signature, or your customers' keys are leaked.

Do you keep it?

No. Everything is written in your browser and nothing reaches us. Download or print the drafts before closing the page: we will not be able to recover them.

Does this replace my adviser or my security team?

No. It saves you the blank page and reminds you of the deadlines and the platform's fields; what is notified and when is your decision. If you are not sure whether your product falls under the CRA, start with the CRA diagnostic: /diagnostico-cra

Official sources

Consulted on 14 October 2026. The deadlines and fields are those of the platform on that date: ENISA warns that its material may change, so check the platform when you notify.