shipcra

Guides for shipping an app or game under the Cyber Resilience Act

Plain explanations for small software teams, in the order you’ll need them. Every guide links to the regulation and is reviewed when the rules or guidance change.

Start here

  • Cyber Resilience Act: what it is, key dates and what it asks of software makers

    The Cyber Resilience Act (CRA) is the EU law that sets cybersecurity requirements for hardware and software sold in the EU. It entered into force on 10 December 2024. Reporting of actively exploited vulnerabilities has applied since 11 September 2026, and the rest of the regulation, including the essential requirements and CE marking, applies from 11 December 2027.

  • Does the Cyber Resilience Act apply to your app or game?

    Most apps and games sold or monetised in the EU are products with digital elements under the CRA. If the product’s core function isn’t on the lists in Annex III or IV, it is in the default category and you can assess it yourself under Module A. A password manager, VPN or browser is an important product and needs a stricter route.

  • The Cyber Resilience Act and open source: manufacturer, steward or contributor?

    Free and open-source software is only covered by the Cyber Resilience Act when it is made available in the course of a commercial activity. Publishing a project that isn’t monetised doesn’t make you a manufacturer, and neither does contributing code to someone else’s project. Organisations that systematically support open source intended for commercial use can be open-source software stewards, with lighter duties and no administrative fines.

Build the inventory

  • What is an SBOM? Software bill of materials explained, with an example

    An SBOM, or software bill of materials, is a machine-readable list of the components inside a piece of software: their names, versions, suppliers, licences and how they depend on each other. Under the Cyber Resilience Act, manufacturers must draw one up covering at least the top-level dependencies. They don’t have to publish it.

  • How to generate an SBOM from a lockfile

    A lockfile already records every resolved dependency with its exact version, so it is the quickest input for an SBOM. Convert it to CycloneDX with a generator for your ecosystem, add your product’s name and version, check the output for components the lockfile can’t see, and regenerate it for every release.

Prepare the documents

  • CRA Annex I checklist: the essential cybersecurity requirements, item by item

    Annex I lists the essential cybersecurity requirements that every product in scope must meet from 11 December 2027. Part I covers the product itself, such as secure defaults, security updates and data protection. Part II covers how you handle vulnerabilities, including the SBOM, a disclosure policy and free security updates.

  • EU declaration of conformity and CE marking for software under the CRA

    From 11 December 2027, before you place an in-scope product on the EU market, you complete a conformity assessment, draw up an EU declaration of conformity that follows Annex V of the Cyber Resilience Act, and affix the CE marking. For software, the CE marking goes on the declaration or on the website that accompanies the product.

After release

  • CRA Article 14: reporting actively exploited vulnerabilities and severe incidents

    Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting their products. The sequence is an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days of a fix for a vulnerability, or within one month for an incident. Reports go through the EU single reporting platform.

  • Vulnerability disclosure policy template for a small software team

    A vulnerability disclosure policy tells security researchers how to report a flaw to you and what happens next. The Cyber Resilience Act requires manufacturers to put a coordinated vulnerability disclosure policy in place and to provide a contact address for reports. For a small team, one clear page is enough.

  • security.txt: what it is, an example file and how to publish it

    security.txt is a plain-text file published at /.well-known/security.txt that tells people how to report a security issue to you. RFC 9116 defines it: Contact and Expires are required, and fields such as Policy, Encryption and Preferred-Languages are optional. It takes five minutes to write.

Find out where your product stands.

The free check asks 8 to 12 questions and tells you whether the CRA applies and in which category.

Run the free check