Skip to content

Latest commit

 

History

History
399 lines (294 loc) · 51.1 KB

File metadata and controls

399 lines (294 loc) · 51.1 KB

Awesome CRA Compliance Awesome

A curated list of resources for the EU Cyber Resilience Act — Regulation (EU) 2024/2847 — covering the regulation itself, harmonised standards, conformity assessment, vulnerability handling, sector-specific guidance, research, tools, and community projects.

License: CC0-1.0 PRs Welcome

The CRA is the first EU-wide horizontal regulation setting mandatory cybersecurity requirements for all hardware and software products with digital elements placed on the Union market. It entered into force on 10 December 2024, its vulnerability-reporting duties start 11 September 2026, and its full requirements apply from 11 December 2027. This list gathers the most useful public resources for engineers, assessors, lawyers, and managers working on CRA compliance.

Disclaimer: This list curates and describes publicly available resources related to the EU Cyber Resilience Act. Copyrighted materials (ISO/IEC, ETSI, BSI, IEEE standards, and published books) are linked to their official catalogue pages only — no copyrighted content is hosted in this repository. The PDFs stored in presentations/ and docs/eu/ are either (a) official EU publications published under the Commission's reuse policy (Decision 2011/833/EU), or (b) webinar slide decks released publicly by CEN, CENELEC, ETSI, ENISA, or other EU projects. All descriptions are factual summaries for informational purposes.


Contents


The Cyber Resilience Act

Official Regulation & Legislation

The authoritative sources. Always read these before secondary material.

Commission Guidance & FAQ

Non-binding but highly influential. Notified bodies and market-surveillance authorities will reference these.

Delegated & Implementing Acts

Timeline & Milestones

Date Milestone
10 December 2024 CRA entered into force
11 June 2026 Notifying authorities designate notified bodies (Art. 35 onwards)
11 September 2026 Reporting obligations apply (Art. 14: actively exploited vulnerabilities, severe incidents)
11 December 2027 All other obligations apply — full CE marking requirement
Until 11 December 2027 Existing RED cybersecurity regime (Delegated Regulation 2022/30) remains valid for in-scope radio equipment

Standards & Standardisation

M/606 Standardisation Request

The M/606 mandate defines 40+ harmonised standards — 4 horizontal (applicable to all products) and 36+ vertical (per product category). Compliance with a harmonised standard creates a presumption of conformity with the CRA essential requirements it covers (Art. 27).

  • STAN4CRA Portal — The official tracking portal where CEN, CENELEC, and ETSI publish development progress of every CRA harmonised standard. Bookmark this.
  • CYBERSTAND Project — EU-funded initiative onboarding 200+ experts to contribute to CRA standards; tracks expert participation and working-group outputs.

Horizontal Standards (CEN/CLC JTC 13)

The prEN 40000-1-x family covers requirements that apply across all CRA products. Drafts are currently under public enquiry; final versions will be cited in the Official Journal.

Vertical Standards (ETSI EN 304-6xx series)

Per-product-category standards under ETSI TC CYBER. These map to Annex III (Important products) classes. Final versions will be published at no cost via the ETSI standards portal.

📥 Current drafts are publicly downloadable from the ETSI docbox at https://docbox.etsi.org/CYBER/EUSR/Open — this is the authoritative source for the latest working versions of every EN 304-6xx standard while they are under public enquiry.

Reference Standards (ISO/IEC, IEC 62443, BSI TR-03183)

These standards are widely referenced by CRA guidance but are not the harmonised standards themselves. They provide methodology and good practice. All are copyrighted — purchase from the official catalogue.


Conformity Assessment & Certification

EUCC (Common Criteria)

For critical products (Annex IV: HSMs, smart-meter gateways, smartcards) and optionally for important products, EUCC certification at "substantial" assurance level provides a presumption of conformity with CRA essential requirements (Art. 27(8)-(9)).

Conformity Assessment Procedures (Modules A, B+C, H)


Vulnerability Handling & Reporting

SBOM & Transparency

CRA Annex I Part II (1) obliges manufacturers to identify and document the components and vulnerabilities in their products, including through a software bill of materials. The draft horizontal harmonised standard prEN 40000-1-3 (CEN/CLC JTC 13) gives that obligation operational shape through normative requirements in clauses 5.3.8 (software) and 5.3.9 (hardware); for authoritative wording, consult the published draft from your national standards body.

ID What the requirement covers (paraphrased)
[PRE-7-RQ-01] Every software component in the product must be inventoried and documented.
[PRE-7-RQ-03] Direct dependencies are mandatory; indirect (transitive) dependencies are recommended.
[PRE-7-RQ-04] The SBOM has to be machine-readable; SPDX and CycloneDX are the formats explicitly named.
[PRE-7-RQ-06] SBOM metadata must include author, version, and ISO-8601 timestamp.
[PRE-7-RQ-07] Each component requires a unique identifier — PURL, CPE, and SWHID are given as examples.
[PRE-7-RQ-07-RE] Where an upstream vendor supplies a component hash, it must be carried through into the SBOM.
[PRE-8-RQ-02] Hardware must also be inventoried: producer, component name, identifier, and firmware version where applicable.
[RLS-2-RQ-03-RE] After a vulnerability is fixed, the disclosure must be issued in a machine-readable advisory format; CSAF v2.0 (ISO/IEC 20153:2025) is the named reference.

Summaries paraphrased from the public draft of prEN 40000-1-3 (© CEN-CENELEC); editorial commentary only.

Specifications and reference publications:

Generation tools (open source):

  • cdxgen - Fast multi-language CycloneDX SBOM generator with monorepo and reachability support. Apache-2.0.
  • CycloneDX build plugins - Native build-time SBOM generators for Maven, Gradle, npm, Python, .NET, Go, Rust, and PHP. Open-source; highest-fidelity Build SBOMs per BSI TR-03183-2.
  • Microsoft sbom-tool - Enterprise SPDX 2.2 / 3.0 generator using Microsoft Component Detection libraries. MIT.
  • OSS Review Toolkit (ORT) - End-to-end analyse-scan-report pipeline for SBOM and licence compliance, used across automotive and telecom. Apache-2.0.
  • Syft - Multi-ecosystem SBOM generator for source, containers, and filesystems, outputting SPDX and CycloneDX. Apache-2.0.
  • Tern - Deep container-layer analyser for Dockerfile-based images, hosted by the Linux Foundation. BSD-2-Clause.
  • Trivy - Container and filesystem SBOM generator combined with a vulnerability scanner in one binary. Apache-2.0.
  • Yocto Project SPDX generation - Native SPDX SBOM output for embedded and IoT builds using the Yocto/OpenEmbedded framework. Open-source.
  • CRANE - Open-source CRA compliance evidence engine that evaluates SBOMs and related artefacts against machine-readable CRA requirements and produces structured compliance evidence. AGPL-3.0.

Validation and quality scoring:

  • bomber - SBOM vulnerability scanner with pluggable data-provider backends. Apache-2.0.
  • cra-sbom-evidence - CRA Annex I Part II (1) preflight: scores a CycloneDX/SPDX SBOM against BSI TR-03183-2 mandatory fields and emits an Article 14 evidence bundle. MIT.
  • CycloneDX CLI - Schema validation, format conversion, and SBOM merge/diff operations. Apache-2.0.
  • ntia-conformance-checker - Automated NTIA Minimum Elements verification for SPDX SBOMs. Apache-2.0.
  • sbomqs - Quality and compliance scorer with built-in profiles for BSI TR-03183-2, NTIA Minimum Elements, FSCT v3, and OpenChain Telco. Apache-2.0.
  • sbom-tools - Semantic SBOM/CBOM diff and scoring tool with CRA, NTIA, and NIST SSDF profiles plus VEX state tracking. MIT.
  • SPDX Tools - Reference SPDX validator, converter, and model toolkit. Apache-2.0.

Vulnerability analysis and disclosure:

  • Cosign (sigstore) - Signs and attests SBOMs and attaches them to OCI artifacts for supply-chain integrity. Apache-2.0.
  • Dependency-Track (OWASP) - Continuous SBOM-based component analysis platform with policy engine and VEX support. Apache-2.0.
  • Grype - CVE scanner that consumes CycloneDX and SPDX SBOMs. Apache-2.0.
  • Secvisogram - CSAF v2.0 advisory editor mapping to prEN 40000-1-3 [RLS-2-RQ-03-RE]; maintained with BSI involvement. MIT.

Firmware and binary analysis (IoT / embedded):

  • Binwalk - Firmware extraction and filesystem-layer analysis tool. MIT.
  • EMBA - Automated embedded-firmware security analyser with component identification and CVE matching. GPL-3.0.
  • FACT (Fraunhofer FKIE) - Firmware Analysis and Comparison Tool used by BSI and European CERTs. GPL-3.0.
  • ScanCode Toolkit (nexB) - Licence and origin detection for binary and source trees. Apache-2.0.

Commercial SCA / SBOM platforms:

  • Black Duck (Synopsys) - Binary-code fingerprinting and snippet detection, common in automotive and medical compliance programmes. Commercial.
  • FOSSA - Software composition analysis combining licence compliance with SBOM generation. Commercial.
  • Insignary Clarity - Binary-level fingerprinting without source-code access. Commercial.
  • Mend - Binary hash matching, policy engine, and vulnerability management. Commercial.
  • Snyk - Developer-centric SCA with SBOM export and vulnerability detection. Commercial.

Coordinated Vulnerability Disclosure

  • ENISA — Good practice guide on vulnerability disclosure - ENISA's multi-stakeholder guide, often cited by Art. 13(8) and Annex I Part II (5). Free download.
  • FIRST — PSIRT Services Framework - Framework for operating a Product Security Incident Response Team; critical for CRA vulnerability-handling obligations. Free.
  • OASIS CSAF (Common Security Advisory Framework) - Machine-readable security advisory format used by Siemens, Red Hat, Cisco and others for CVD automation. Free and open.
  • ENISA — Single Reporting Platform (not yet released — placeholder) - Art. 14 requires early warning, incident, and vulnerability reports to be routed through a single reporting platform run by ENISA. ENISA has not yet published the platform or its technical interface; monitor ENISA announcements for release news.

ENISA Guidelines

  • ENISA - The EU Agency for Cybersecurity. Operates the CSIRTs Network, coordinates CRA reporting, runs the EUCC scheme, and publishes technical guidance. Primary institutional source.
  • EU CSIRT Network - Coordinated incident response across member states; designated CSIRTs are recipients of Art. 14 reports.

Product-Category Deep Dives (Webinars & Slides)

The following webinars were produced by the European Standardisation Organisations (CEN, CENELEC, ETSI) and the STAN4CRA project. Slide decks are public; YouTube recordings are linked directly. All PDFs are mirrored locally in presentations/.

CEN-CENELEC Horizontal Webinars

ETSI Vertical-Standard Deep Dives (STAN4CRA)

Per-product-category deep dives produced by the STAN4CRA project for each ETSI EN 304-6xx draft.

Q&A and Workshop Reports


Relationship to Other EU Regulation

The CRA does not sit in isolation. These neighbouring regimes carve out, pre-empt, or overlap with CRA obligations.


EU CRA Cluster Projects

Twelve EU-funded projects supporting CRA roll-out — from standards development to SME tooling. Managed via CYBERSTAND and SECURE initiatives.

  • CYBERSTAND - Cybersecurity Standardisation. Empowers European stakeholders to engage in CRA standards development. Selects 200+ experts with €1.5M funding for harmonised-standard working groups. Coordinates CEN/CENELEC/ETSI. Primary gateway if you want to contribute to a standard.
  • STAN4CRA - Standards for the Cyber Resilience Act. The ESO portal tracking all harmonised-standard development progress under M/606.
  • CRA-AI - AI-powered CRA compliance platform for product inventory, risk assessment, testing, documentation, vulnerability reporting. Focus on SME needs with training modules.
  • OSCRAT / OCCTET - Open-source CRA tooling: FOSS SBOM generation, vulnerability tracking, and automated compliance for open-source components in digital products.
  • CONFIRMATE - Conformity assessment, metrics, compliance automation. Develops open-source tools on the Clouditor framework, penetration-testing methodology, multilingual training. Partners: Fraunhofer, CYEN, DNSC Romania.
  • CURIUM - Cybersecurity resilience for IoT and microelectronics. Harmonised regulatory framework for ICT products under EUCSA and CRA; focus on certification of IoT and microelectronic components.
  • SECURE - €22M budget including €16M cascade funding for MSMEs. First open call January 2026 (€5M). Direct financial support, compliance tools, training for small businesses.
  • CRACoWi - CRA Compliance Wizard. Step-by-step digital assistant guiding SMEs through secure design, lifecycle, and post-market compliance.
  • CYBERFORT - Strengthening Cyber Defences of SMEs for CRA. Co-funded under Digital Europe Programme. Automated open-source compliance tools. Romania-Cyprus partnership coordinated by DNSC.
  • CRACY - CRA Made Easy. Consortium of 11 European cybersecurity technology providers. Belgium-Romania-Greece-Estonia partnership. Practical CRA tools for the supply chain.
  • TRUSTBOOST - CyberBoost SaaS platform for real-time cybersecurity conformity and certification aligned with CRA, RED-DA, NIS2, CSA. Coordinated by NSAI (Ireland).

Books & Long-Form References

These books are copyrighted. Links go to publishers or neutral reference pages; no content is hosted here.

  • Designing Secure Software: A Guide for Developers by Loren Kohnfelder — The engineering handbook behind CRA essential requirements. Part I covers the conceptual foundation (Trust, Authenticate/Authorize/Audit "Gold Standard", mitigation, design patterns, cryptography); Part II integrates security into design and the 6-step Security Design Review process that notified bodies will examine under Art. 32(2)(a); Part III drills into concrete practices — the GotoFail and Heartbleed case studies, untrusted-input handling, web security, security testing — that eliminate the vulnerability classes Annex I Part I (2)(a) targets. Essential reading for engineers. (No Starch Press, 2021)
  • Practical Vulnerability Management by Andrew Magnusson — Operational handbook for running a vulnerability-management programme — exactly the day-to-day practice CRA Annex I Part II demands. Covers component and CVE data collection, Cull-Rank triage, the five response types (patch, mitigation, systemic, accept, defence-in-depth with validation), and PSIRT stakeholder management. Part II builds a working system with free tools (Nmap, OpenVAS, cve-search, Metasploit). The operational playbook for Annex I Part II (1)-(8). (No Starch Press, 2020)
  • Threat Modeling Best Practices by Derek Fisher — 322-page engineering-facing threat-modelling handbook covering STRIDE, DREAD, ISO 27005, NIST SP 800-30, FAIR, OCTAVE, RMF; cloud/supply-chain/IoT/AI threat modelling with formal adversary models (Dolev-Yao, Byzantine, honest-but-curious); building a threat-modelling practice (SMART, maturity models, CoE/CoP). Maps directly onto CRA Art. 13(2) risk-assessment obligation. (Packt Publishing, 2025)
  • NIST SP 800-30 Rev. 1 — Guide for Conducting Risk Assessments by NIST — The most widely-adopted risk-assessment methodology: threat identification, vulnerability analysis, likelihood, impact, risk determination. CRA Art. 13(2) requires a risk assessment, Art. 13(3) requires it documented and updated; NIST SP 800-30 provides a defensible structured approach. Free PDF from NIST. (NIST, 2012)
  • OWASP Developer Guide v4 — Broad free developer guide covering secure-design principles, threat modelling, implementation, testing, operations. Useful complement to Kohnfelder. Free; OWASP.
  • OWASP CycloneDX — Authoritative Guide to SBOM — Free deep guide to SBOM production and consumption; directly relevant to Annex I Part II (1). Free; OWASP.

Academic & Research


Community, Portals & Further Reading


Contributing

Contributions are welcome. Please:

  1. Read CONTRIBUTING.md first.
  2. Only add resources that are publicly available and relevant to the CRA (regulation text, harmonised standards, official guidance, research, open-source tools, public webinars, books).
  3. Respect copyright: link to the official catalogue page for paid standards and published books; do not submit PDF uploads of copyrighted material.
  4. Follow the existing entry format: - [Title](URL) - One or two factual sentences about the resource and its CRA relevance. *Paid/free/draft notes.*
  5. Keep descriptions factual, not promotional.
  6. Open a pull request with a clear title (e.g., add EN 304-624 deep-dive by STAN4CRA).

License

CC0

To the extent possible under law, the maintainer has waived all copyright and related or neighbouring rights to this list. The curation and descriptions are released into the public domain via CC0 1.0 Universal.

The PDFs mirrored in docs/eu/ and presentations/ retain the rights of their original authors. EU publications are reused under Commission Decision 2011/833/EU; presentation slides are mirrored as released by CEN, CENELEC, ETSI, ENISA, and the STAN4CRA/CYBERSTAND projects. If you are the rights-holder of any mirrored material and wish it removed, please open an issue.


Maintainer

This list is curated and maintained by Jeans Koo at The One Testing Technology Co., Ltd — an ISO/IEC 17025 accredited testing laboratory supporting manufacturers through the EU Cyber Resilience Act lifecycle: scoping, risk assessment, security-by-design review, vulnerability management, and conformity assessment.

For questions, corrections, or to contribute a resource, open an issue or pull request — see CONTRIBUTING.md.