Cyber Resilience Act checklist for IoT and hardware makers

Hephaestus Technology7 min read

A Cyber Resilience Act checklist for IoT and hardware makers comes down to 15 items: confirm scope and product class, run a risk assessment, meet the Annex I security requirements, set a support period, handle vulnerabilities, report exploited ones, document everything and affix the CE marking. Reporting duties have applied since 11 September 2026 and the main obligations apply from 11 December 2027. Use the list below as a working plan, with each item tied to the article of Regulation (EU) 2024/2847 behind it.

Key takeaways

  • Reporting of actively exploited vulnerabilities already applies; design, documentation and CE marking duties apply from 11 December 2027.
  • Check Annex III and IV first: product class decides whether you can self-assess or need a notified body.
  • The support period must normally be at least five years and must be stated to buyers.
  • An SBOM covering at least top-level dependencies is part of the mandatory vulnerability handling requirements.
  • Keep technical documentation for at least 10 years or the support period, whichever is longer.

Which dates does the checklist work to?

Two dates drive the plan. Under Article 71, Article 14 reporting has applied since 11 September 2026 and the rest of the Regulation applies from 11 December 2027. Products placed on the market before December 2027 only need to meet the full requirements if they are substantially modified afterwards, but the reporting duty already covers them (Article 69).

So the checklist splits in two: items 1 to 3 are live now, and the rest must be in place for products you place on the market from December 2027.

Part 1: what must be in place now?

1. Confirm the product is in scope. The CRA covers "a software or hardware product and its remote data processing solutions" made available on the EU market (Article 3(1)). Medical devices, motor vehicles and certified aviation products are excluded (Article 2). Most connected consumer and industrial devices are in.

2. Set up a reporting route for exploited vulnerabilities and severe incidents. Early warnings are due within 24 hours of becoming aware, notifications within 72 hours, and a final report later (Article 14). Ireland's NCSC confirms that only submissions through ENISA's Single Reporting Platform count. Our explainer on Cyber Resilience Act reporting covers the detail.

3. Know how to tell your users. Article 14(8) requires you to inform affected users of an actively exploited vulnerability or severe incident and, where needed, what they should do. Have a template and a customer contact list ready.

Part 2: what must be ready by December 2027?

4. Classify the product. Check Annex III. Important Class I includes routers, modems and switches, smart home security products such as door locks, cameras and baby monitors, smart home virtual assistants, connected toys with social interaction or location tracking, and certain wearables. Class II includes firewalls, hypervisors and tamper-resistant microcontrollers. Annex IV lists critical products such as smartcards and smart meter gateways. Everything else is a default product.

5. Choose the conformity assessment route. Default products can use internal control (module A) under Article 32(1). Class I products need third-party assessment (module B with C, or module H) where harmonised standards are not applied or only partly applied (Article 32(2)). Class II products must use a third-party route, and critical products may need a European certification scheme. Harmonised standards are still being written: the Commission's request covers a set of 41 standards, so check their status before you plan on self-assessment for a Class I product.

6. Run and document a cybersecurity risk assessment. Article 13(3) requires a risk assessment that is documented and updated during the support period. It decides how each Annex I requirement applies to your product.

7. Meet the Annex I Part I product requirements. These include shipping with no known exploitable vulnerabilities, a secure-by-default configuration with a reset option, security updates (automatic by default where applicable, with an opt-out), protection against unauthorised access, encryption of data, integrity protection, data minimisation, resilience against denial of service, a limited attack surface, security logging and secure deletion of user data (Annex I). For a device, that usually means no universal default passwords, secure boot, signed firmware and encrypted communications. Our guide to secure OTA firmware updates covers the update part in depth.

8. Do due diligence on third-party components. Article 13(5) requires due diligence when integrating third-party components, including open-source ones. If you find a vulnerability in a component, Article 13(6) says you must report it to whoever maintains it.

9. Produce a software bill of materials. Annex I Part II requires you to identify components, including by drawing up an SBOM "in a commonly used and machine-readable format" covering at least the top-level dependencies. You do not have to publish it, but a market surveillance authority can ask for it. See our explainer on what an SBOM is.

10. Put vulnerability handling in place. The rest of Annex I Part II requires you to remediate vulnerabilities without delay, test regularly, publish information on fixed vulnerabilities, keep a coordinated vulnerability disclosure policy, provide a contact address, distribute updates securely and provide security updates free of charge, generally, with advisory messages.

11. Set and publish the support period. Article 13(8) says the support period "shall be at least five years", unless the product is expected to be in use for less time. Annex II requires you to tell users the end date of the support period.

12. Write the user information. Annex II lists what must accompany the product, including a single point of contact for vulnerability reports, where your disclosure policy can be found, and the support end date.

13. Assemble the technical documentation. Annex VII lists the contents: product description, design and vulnerability handling processes, the risk assessment, the support period rationale, standards applied, test reports and the EU declaration of conformity. Microenterprises and small enterprises may use a simplified format under Article 33(5).

14. Sign the EU declaration of conformity and affix the CE marking. Products show CRA compliance with the CE marking. Keep the documentation and declaration for at least 10 years after placing on the market, or the support period if longer (Article 13(13)).

15. Keep series production in conformity. Article 13(14) requires procedures so that units in a production series stay compliant as designs and standards change.

What does the checklist look like at a glance?

# Item Legal basis Applies from
1-3 Scope, reporting route, user notices Art. 3, 14 11 Sept 2026
4-5 Classification and conformity route Art. 32, Annex III, IV 11 Dec 2027
6-8 Risk assessment, Annex I Part I, component due diligence Art. 13, Annex I 11 Dec 2027
9-10 SBOM and vulnerability handling Annex I Part II 11 Dec 2027
11-12 Support period and user information Art. 13(8), Annex II 11 Dec 2027
13-15 Documentation, CE marking, series production Art. 13, Annex VII 11 Dec 2027

Where do small hardware teams usually struggle?

Three places tend to cause trouble. First, classification: a product that looks like a default product can fall into Class I because of one feature, such as a camera or a lock. Second, the support period: committing to five years of security updates affects component choice, cloud costs and pricing, so decide it at design stage, not at launch. Third, retrofitting: secure boot and signed updates are hard to add once hardware is in production, which is why the design stage is the cheapest place to get them right.

The Commission's 27 July 2026 guidance covers scope, support periods, substantial modification and reporting, with examples aimed at SMEs. Read it alongside this list.

Frequently asked questions

When does the Cyber Resilience Act apply to IoT devices?

Reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026. The design, documentation, conformity assessment and CE marking requirements apply to products placed on the market from 11 December 2027.

Do I need a notified body for my connected device?

Only if it falls into Class II or Annex IV, or into Class I without fully applied harmonised standards. Default products can self-assess using internal control. Check Annex III carefully, because cameras, locks, routers and some wearables are listed.

How long must I provide security updates under the CRA?

For the support period, which must be at least five years unless the product is expected to be in use for less time. You must tell users when that period ends.

Does the CRA require me to publish my SBOM?

No. You must draw up an SBOM covering at least top-level dependencies and include it in your technical documentation, but you only have to provide it to a market surveillance authority on reasoned request.

Are products I already sell affected?

Yes, for reporting: Article 14 applies to in-scope products placed on the market before December 2027. The full requirements only apply to those older products if they are substantially modified after 11 December 2027.

Building a connected product and want a second opinion on its security plan? Book a free 30-minute call with our team.

Cover photo by Willquezada on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.