AIM SHIELD Emergency
CRA kit · Free

CRA kit for small manufacturers

If you make a product with software that connects to another device or to a network, the Cyber Resilience Act asks specific things of you, with dates. Here they are in plain language, with the article for each one, and a ZIP of templates to get you started. We keep nothing.

Download the kit (ZIP)

This is not legal advice. It summarises Regulation (EU) 2024/2847 in plain language and offers starting templates. Check each article in the official text and consult your adviser before deciding.

The calendar

20 Nov 2024

The Regulation is published in the Official Journal of the EU.

OJEU header

10 Dec 2024

It enters into force (twenty days after publication). Almost nothing has to be complied with yet.

Art. 71.1

11 Jun 2026

The rules for the bodies that assess conformity begin to apply (Chapter IV). If you manufacture, it doesn't affect you for now.

Art. 71.2, Chapter IV (arts. 35 to 51)

11 Sep 2026

You must now notify ENISA and the CSIRT of actively exploited vulnerabilities and serious incidents, including for products you were already selling before.

Art. 71.2, arts. 14 and 69.3

11 Dec 2027

Everything else applies: the requirements of Annex I, technical documentation, the EU declaration of conformity and CE marking for whatever you place on the market from that date.

Art. 71.2 and art. 69.2

Not sure whether your product is covered? First do the CRA Diagnosis.

From 11 September 2026: report if something happens (Article 14)

At 24 hours

Early warning

Without delay and, in any case, within 24 hours of finding out. If it is an incident, say at least whether you suspect unlawful or malicious acts; and, where relevant, in which Member States the product is sold.

Art. 14.2.a and 14.4.a

At 72 hours

Notification

At 72 hours: general information about the product, the nature of the vulnerability or incident, how it is exploited, what measures you have taken and which ones users can take.

Art. 14.2.b and 14.4.b

Final report

Vulnerability: 14 days; incident: one month

Exploited vulnerability: no later than fourteen days after a corrective or mitigating measure is available. Serious incident: within one month after the 72-hour notification.

Art. 14.2.c and 14.4.c

  • It is notified through the single reporting platform, to the coordinating CSIRT of the Member State where your main establishment is and to ENISA at the same time (art. 14.1, 14.3 and 14.7). In Spain, the coordinating CSIRT is INCIBE-CERT, according to ENISA's list.
  • “Serious” is an incident that affects or may adversely affect the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led or may lead to the introduction or execution of malicious code in the product or in a user's network (art. 14.5).
  • You must also alert the affected users, and everyone where appropriate, and tell them what they can do; in a structured, machine-readable format where appropriate (art. 14.8). A CSAF advisory serves that purpose.
  • Art. 14 already applies to every product with digital elements that falls under the Regulation, even if you sold it before December 2027 (art. 69.3).

To work out your deadlines and prepare the drafts, use the CRA notice. The platform: ENISA portal.

What the ZIP contains

  • LEEME.md: How to use the kit and what it does not do.
  • security.txt: Template for /.well-known/security.txt (RFC 9116).
  • politica-divulgacion.md: Coordinated disclosure policy, based on disclose.io (CC0).
  • csaf-aviso-ejemplo.json: Example security advisory in CSAF 2.0 (“security advisory” profile).
  • vex-ejemplo.json: Example VEX in CSAF 2.0 (“VEX” profile).
  • guia-sbom.md: Step-by-step guide to the software bill of materials (SBOM).
  • plan-notificacion-24-72-14.md: Plan for notifying within 24 hours, 72 hours and the final report.

It is generated when you download it, always the same, and contains nobody's data: you fill it in on your own computer. Our own disclosure policy and our security notices are an example in use.

Download the kit (ZIP)

What Article 13 asks of you

  • Assess your product's cybersecurity risks (Art. 13.2 and 13.3). Before selling it and for as long as you support it: what can go wrong, what it is used for and in what environment. It is documented and kept up to date. It goes inside the technical documentation.
  • Keep an eye on what you bring in from others (Art. 13.5 and 13.6). If your product includes third-party or open-source libraries, you have to take care that they don't compromise its security. If you find a flaw in one of those components, tell whoever maintains it and fix it in your product.
  • Document what you know about security (Art. 13.7). Including known vulnerabilities and what third parties tell you, in proportion to your product.
  • Set a support period of at least five years (Art. 13.8). During that time you fix the vulnerabilities. If you expect the product to be used for less than five years, support lasts as long as its expected use. And you must have a coordinated vulnerability disclosure policy.
  • Keep security updates available (Art. 13.9). Every security update you release during the support period must remain available for at least ten years, or for the rest of the support period if that is longer.
  • Technical documentation and EU declaration of conformity (Art. 13.12, 13.13 and 13.20). Before selling: technical documentation, conformity assessment, EU declaration and CE marking. Keep them for ten years from when you place the product on the market, or the support period if that is longer.
  • Identify your product and put your name to it (Art. 13.15 to 13.19). A type, batch or serial number; your name and contact address; a single point of contact for vulnerability reports that anyone can easily find and that is not limited to automated forms; the instructions in Annex II; and the date on which support ends (month and year), visible at the time of purchase.
  • If something doesn't comply, fix it now (Art. 13.21). If you know or have reason to believe that your product or your processes do not comply, you immediately take corrective measures, or withdraw or recall it.

Annex I: essential requirements

Part I: what the product must be like (summary)

  • That the product ships with no known exploitable vulnerabilities and with a secure default configuration.
  • That it can be updated (with automatic security updates switched on by default where appropriate).
  • That it protects against unauthorised access, and the confidentiality and integrity of the data (encryption, for example).
  • That it processes only the data needed (minimisation).
  • That it keeps working in the essentials after an incident, limits its attack surface and reduces the impact of an incident.
  • That it logs the activity relevant to security and lets the user delete their data securely.

Part II: how you manage vulnerabilities

  • 1. Identify and document vulnerabilities and components, with a list of components (SBOM) in a common, machine-readable format that includes, as a minimum, the top-level dependencies.
  • 2. Fix vulnerabilities without delay with security updates; where technically feasible, separate from feature updates.
  • 3. Carry out effective, regular security tests and reviews.
  • 4. When an update is available, publish information about the vulnerabilities fixed: what they are, which products they affect, their impact, their severity and what to do.
  • 5. Put a coordinated vulnerability disclosure policy in place.
  • 6. Make it easy to share information about vulnerabilities, with a contact address for alerting you.
  • 7. Distribute updates securely (and automatically where appropriate).
  • 8. Release security updates without delay, free of charge (unless otherwise agreed for bespoke products) and with messages that say what to do.

Annex II: what must accompany the product

  1. Your name, postal address and email (or digital contact), and your website.
  2. The single point of contact for vulnerability reports and where your disclosure policy is.
  3. Name and type of the product, and how to identify it precisely.
  4. What it is for, its security environment and its security properties.
  5. Any known or foreseeable circumstance that may give rise to significant risks.
  6. Where the EU declaration of conformity is.
  7. What security support you offer and until when.
  8. Instructions for putting into service, updating, safe withdrawal and how to switch off automatic updates.
  9. If you make the SBOM available to users, where it can be consulted.

Fines for failing to comply with Annex I and Articles 13 and 14: up to EUR 15,000,000 or 2.5% of worldwide annual turnover, whichever is higher (Art. 64.2).

Frequently asked questions

Does the Regulation apply to me?

It applies to products with digital elements whose intended purpose or reasonably foreseeable use includes a direct or indirect data connection to a device or a network (art. 2.1). Excluded, among others, are those already regulated by other rules, such as medical devices, in vitro diagnostic devices and vehicles (art. 2.2), and those for national security or defence (art. 2.7). First do the CRA Diagnosis: /diagnostico-cra.

What do I have to do NOW?

From 11 September 2026, notify actively exploited vulnerabilities and severe incidents in your products (art. 14). The rest, from 11 December 2027. But it is best to start earlier, because support, the list of components and the disclosure policy take time.

Is it compulsory to publish the SBOM?

No. Annex I, Part II, point 1, requires you to draw it up and have it documented; Annex II, point 9, only says where to find it if you decide to make it available to users. The authorities can ask you for it.

What if I am a micro-business?

The Regulation takes size into account when setting fines (art. 64.5.c) and provides for the Commission to establish a simplified technical documentation form for micro and small enterprises (recitals), but the substantive obligations are the same.

Do you keep what I fill in?

No. The ZIP is generated when you download it, contains no data of yours or ours, and you fill it in yourself on your computer. We save nothing.

Is this legal advice?

No. It is a plain-language guide and some starting templates. What applies to you and how to comply depends on your product: consult your adviser or the market surveillance authority.