Cyber Resilience Act (CRA)
ETSI EN 303 645
CRA vs. ETSI EN 303 645
From voluntary IoT standard to binding EU law
Legally binding for all products with digital elements — non-conformity has legal consequences
Voluntary standard for consumer IoT security — covers 13 security provisions but is not legally binding
ETSI EN 303 645 is a good foundation but not a law. The CRA goes significantly further: SBOM obligation, ENISA reporting, CE marking, and formal conformity assessment are not covered by the ETSI standard.
You comply with ETSI EN 303 645 — what else do you need for CRA?
ETSI EN 303 645 is the best-aligned existing standard for CRA in the consumer IoT space. The 13 provisions cover many CRA requirements — but the CRA goes significantly further in several EU-specific areas.
No universal default passwordsCovered
ETSI Provision 5.1 prohibits universal default passwords — this fully covers the corresponding CRA requirement in Annex I.
Software update mechanismsCovered
ETSI Provision 5.3 requires secure update mechanisms. This largely covers the CRA's security update requirement.
Secure communicationCovered
ETSI Provision 5.5 requires encrypted communication. This aligns with CRA data confidentiality requirements in Annex I.
Attack surface minimizationCovered
ETSI Provision 5.6 requires minimizing exposed attack surfaces. This covers the corresponding CRA requirement.
Most of the 13 ETSI provisionsCovered
Most of the 13 ETSI provisions on data protection, integrity, resilience, and secure initial setup cover parts of CRA Annex I requirements.
SBOM obligationNot covered
ETSI EN 303 645 contains no SBOM requirement. The CRA requires a machine-readable Software Bill of Materials for every product.
ENISA vulnerability reporting (24h/72h)Not covered
ETSI EN 303 645 has no external reporting obligation. The CRA requires reporting actively exploited vulnerabilities to ENISA within 24 hours.
EU Declaration of ConformityNot covered
ETSI is a voluntary standard with no EU Declaration of Conformity. The CRA requires a formal declaration per Annex V.
CE markingNot covered
ETSI conformity does not lead to CE marking. The CRA requires CE marking as a market access prerequisite.
Formal support period declarationNot covered
ETSI recommends a defined support period; the CRA makes it mandatory (minimum 5 years) with formal declaration.
CRA-specific documentation requirementsNot covered
The CRA requires extensive technical documentation per Annex VII — beyond ETSI implementation reports.
Product classification (Annex III/IV)Not covered
The CRA product classification (Default, Class I, Class II) determines the conformity assessment pathway — no ETSI equivalent.
ETSI EN 303 645 as CRA Precursor
ETSI EN 303 645 was a key CRA precursor. Many of its 13 provisions are reflected in CRA Annex I. ETSI is being developed as a harmonized standard (hEN) under the CRA.
- Provision 1 (No default passwords) maps to CRA Annex I, Part I, No. 1
- Provision 2 (Vulnerability disclosure) maps to CRA Art. 13(6)
- Provision 3 (Keep software updated) maps to CRA Annex I, Part II, No. 2
- Provisions 4+5 (Data protection, secure communication) map to CRA Annex I, Part I, No. 3
- Presumption of conformity: Upon successful harmonization, ETSI covers CRA requirements for consumer IoT
What the CRA Requires Beyond ETSI
Even with full ETSI conformity, essential CRA requirements remain that go beyond the standard.
- SBOM obligation: CRA requires machine-readable SBOM — no ETSI equivalent
- ENISA reporting (Art. 14): 24h reporting to ENISA — ETSI only recommends vulnerability disclosure policy
- Support period declaration (Art. 13(16)): Formal indication on packaging — ETSI only a recommendation
- CE marking (Art. 13(12), Art. 20): EU Declaration of Conformity — no ETSI equivalent
- Technical documentation (Annex V): More extensive than ETSI TS 103 701
The Path to Harmonization
ETSI is working to adapt EN 303 645 as a harmonized standard (hEN) under the CRA. Until harmonization: use ETSI as foundation, address CRA gaps separately.
- Step 1: Commission issues standardization request to ETSI
- Step 2: ETSI revises EN 303 645 (supplements e.g. SBOM requirements)
- Step 3: Publication in EU Official Journal after Commission review
- Step 4: Presumption of conformity — full application of the hEN serves as CRA evidence
Practical Recommendations for IoT Manufacturers
ETSI EN 303 645-compliant manufacturers have a strong baseline. The path to CRA requires targeted additions.
- Step 1: Use ETSI conformity as starting point — covers significant portion of CRA requirements
- Step 2: Conduct CRA gap analysis — identify SBOM, ENISA reporting, support period, CE marking gaps
- Step 3: Build SBOM processes — automated generation in build pipelines, CVE monitoring
- Step 4: Determine product classification (Default/Class I/II) and conformity assessment pathway
- Step 5: Track ETSI harmonization — hEN recognition enables presumption of conformity
Synergies Between CRA and ETSI EN 303 645
ETSI EN 303 645 provides a solid foundation for CRA conformity in the consumer IoT space.
Presumption of Conformity
When recognized as a harmonized standard, ETSI conformity establishes a CRA presumption of conformity.
Proven Best Practices
The 13 ETSI provisions cover a significant portion of CRA requirements for consumer IoT.
Global Recognition
ETSI EN 303 645 is referenced globally — from the UK PSTI Act to IoT standards in Australia and Singapore.
Your Next Steps
Add SBOM process
Integrate automated SBOM generation into your development process. Your existing ETSI-compliant software management provides a solid foundation.
Implement formal ENISA reporting
Extend your ETSI 5.2-compliant vulnerability process with the CRA-specific reporting channel to ENISA with 24h/72h deadlines.
Prepare conformity documentation
Create the CRA Declaration of Conformity (Annex V) and technical documentation (Annex VII). Use existing ETSI documentation as a starting point.
Set up CE marking process
Plan the CRA conformity assessment pathway based on product classification and prepare CE marking.
Frequently Asked Questions
Does the CRA replace ETSI EN 303 645?
Is ETSI EN 303 645 certification sufficient for CRA conformity?
What additional CRA requirements exist beyond ETSI EN 303 645?
When will ETSI EN 303 645 be recognized as a harmonized standard under the CRA?
Does ETSI EN 303 645 apply to industrial products or enterprise IoT?
How does ETSI TS 103 701 relate to the CRA conformity assessment process?
What is the current status of harmonized standards for the CRA?
Which products are exempt from the CRA?
Further Reading
Official Sources
Official regulation text of the Cyber Resilience Act on EUR-Lex
Full text of the European standard for cybersecurity in consumer IoT
ETSI overview page on consumer IoT security with all related standards and reports
More on Kunnus
Full regulation text and commentary on the CRA
CRA compliance solution for consumer IoT manufacturers
CRA compliance for smart home device manufacturers
Free initial assessment of your CRA compliance status
How the CRA replaces the cybersecurity requirements of the Radio Equipment Directive
Comparison of CRA and the industrial standard IEC 62443 for industrial cybersecurity
From ETSI EN 303 645 to CRA — Seamlessly
Kunnus transitions your existing ETSI conformity into full CRA compliance: SBOM management, ENISA reporting processes, and CE documentation — all in one platform.