← Industry Guides
Consumer ElectronicsCRA Guide

EU Cyber Resilience Act Guide for Smart Home Device Manufacturers

Default class for smart plugs, bulbs, thermostats and other accessories. Important Class I for smart locks, security cameras, baby monitors, alarm systems and the hubs or apps that centrally control them (Annex III, point 17), for general purpose virtual assistants (Annex III, point 16) and for home routers, modems and wireless access points (Annex III, point 12)

Smart home device manufacturers producing connected doorbells, smart locks, home automation hubs, security cameras, smart plugs, and similar IoT products for the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Smart home products present some of the most common cybersecurity vulnerabilities found in consumer IoT - default credentials, unencrypted cloud communications, and absent update mechanisms - which the CRA directly targets.

Article 13Article 14Annex IArticle 13Annex IVArticle 20
Deadline: 11 December 2027Classification: Default class for smart plugs, bulbs, thermostats and other accessories. Important Class I for smart locks, security cameras, baby monitors, alarm systems and the hubs or apps that centrally control them (Annex III, point 17), for general purpose virtual assistants (Annex III, point 16) and for home routers, modems and wireless access points (Annex III, point 12)

Last updated 26 October 2026

CRA Scope and Classification for Smart Home Products

Smart home products with network connectivity and embedded software - smart plugs, bulbs, thermostats, doorbells, smart locks, home automation hubs, and security camera systems - are products with digital elements within CRA scope. Product classification depends on the core functionality of the device (Article 7(1)).

Smart plugs, bulbs and thermostats are default-class products, because Annex III lists no category for them. Data processing, cloud connectivity and remote control do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. Annex III, point 17 makes smart home products with security functionalities Important Class I. Commission Implementing Regulation (EU) 2025/2392 describes them as products that protect the physical security of consumers in a residential setting and that are remotely controllable or managed. The category includes smart door locks, security cameras, baby monitoring systems and alarm systems, and the hardware and software that centrally control them. A hub or an app whose function is to control these security products is therefore Important Class I. A hub that controls only lights, plugs or thermostats is default class. A video doorbell is Important Class I when it protects the physical security of the home and is remotely controllable or managed. A smart home general purpose virtual assistant, such as a smart speaker, is Important Class I (Annex III, point 16). A home router, a modem for connection to the internet or a wireless access point is Important Class I (Annex III, point 12). Manufacturers must document their classification rationale for each product SKU in the technical file.

CRA reference:Article 7(1), Article 13(2), Annex III

Key Technical Security Requirements for Smart Home Devices

Smart home devices have historically been among the most poorly secured connected products, with default credentials, unencrypted communications, and absent update mechanisms being widespread. CRA Annex I Part I directly targets these systemic weaknesses:

  • Unique or no default credentials: Each device must either use a unique factory-assigned credential or require the user to set credentials at first use. Shared default passwords (e.g., admin/admin) are prohibited.
  • Encrypted communications: All communications between the device, companion app, and cloud backend must be encrypted using current TLS standards. Local network discovery protocols must not expose sensitive device data.
  • Automatic security updates: Smart home devices must support and enable by default automatic security updates. The update mechanism must be authenticated and tamper-resistant.
  • Minimal data collection: Devices must not collect data beyond what is necessary for device function. Camera and audio data must be protected against unauthorised access.
  • End-of-life communication: When a device reaches end of support, the manufacturer must notify users and must not disable security functionality in a way that leaves devices vulnerable.
CRA reference:Annex I

CVD Policy and Article 13 for Smart Home Brands

Most smart home device manufacturers - particularly smaller brands and white-label manufacturers - currently lack a formal CVD policy. Security researchers routinely discover vulnerabilities in smart home products that go unreported or unacknowledged for months because no submission channel exists.

  • Publishing a security.txt file at the brand domain (e.g., https://brand.com/.well-known/security.txt)
  • Providing a submission channel accessible to non-technical users and researchers alike
  • Responding to reports within a defined timeframe (best practice: 5 business days)
  • Committing to security update publication and customer notification for resolved vulnerabilities

Brands operating under private-label or OEM arrangements must clarify which entity bears the Article 13 CVD obligation. If the brand places the product on the EU market under its own brand name, it is the manufacturer for CRA purposes, regardless of the actual hardware manufacturer. CVD Portal's intake and triage tools enable brands without dedicated security teams to manage this obligation operationally.

CRA reference:Article 13(1), and

Article 14 Incident Reporting for Smart Home Products

Smart home vulnerabilities attract significant attention from both security researchers and threat actors due to the privacy implications of compromised home cameras, locks, and microphones. Article 14 requires manufacturers to notify ENISA within 24 hours of becoming aware of active exploitation of a product vulnerability.

  • Unauthorised remote access to device cloud accounts at scale
  • Malware campaigns targeting the device (e.g., Mirai-variant infections)
  • Researcher or law enforcement reports of active exploitation in the wild

The 24-hour ENISA notification must confirm the product and nature of the exploitation. The 72-hour detailed report provides technical content; the final report, due no later than 14 days after a corrective or mitigating measure is available (Article 14(2)(c)) confirms remediation. For consumer-facing smart home products, manufacturer communication must also include direct customer notification through app push notifications and email - passive advisory publication is insufficient given that consumers may not check security advisory pages.

CRA reference:Article 14(1), Article 14(2)

Conformity Assessment and Supply Chain Obligations

Default Class smart home products may use the internal conformity assessment procedure (Module A under Annex VIII). A Class I product, such as a smart lock or a security camera, can use Module A only when it fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so a Class I product needs a notified body for now (Module B plus Module C, or Module H). For brands relying on ODM/OEM manufacturers in Asia, the conformity assessment obligation sits with the EU market placer - the brand.

  1. Obtain security documentation from the ODM/OEM that supports the Annex I technical assessment
  2. Verify that the ODM's software stack meets CRA requirements or commission modifications
  3. Maintain an SBOM for the product that reflects the actual components used
  4. Ensure that post-sale update mechanisms are under the brand's control, not solely the ODM's

This creates a commercial pressure to restructure ODM relationships: brands must have contractual rights to require security patches, SBOM updates, and vulnerability notifications from their hardware suppliers throughout the product's supported lifetime. Sourcing from ODMs who are not CRA-ready will create ongoing compliance liability for EU-market brands.

CRA reference:Article 32, Annex VIII

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Are smart home products from non-EU manufacturers subject to the CRA?+

Yes. The CRA applies to all products with digital elements placed on the EU market, regardless of where the manufacturer is located. Non-EU manufacturers who sell directly to EU customers - through their own websites or through EU-based marketplaces - must comply with the CRA. If a non-EU manufacturer uses an EU-based importer or authorised representative to place products on the market, those entities may take on manufacturer-equivalent CRA obligations. EU-based marketplace operators may also face obligations to remove non-compliant products from their platforms under the CRA's market surveillance provisions.

What happens when we discontinue a smart home product - do CRA obligations end?+

No. CRA obligations persist throughout the product's declared supported lifetime, even if the product is discontinued. If you stop selling a smart home hub but have declared a 3-year support period, you must continue to monitor for vulnerabilities, issue security patches, and maintain the CVD policy for that product for the full 3-year period from the last date of sale. You may not unilaterally shorten the declared supported lifetime after sale. This means manufacturers must carefully consider support cost obligations before declaring supported lifetimes, and must price products accordingly.

Can we use a shared CVD policy that covers all our smart home products?+

Yes. A single CVD policy can cover all products with digital elements placed by a manufacturer, provided the policy clearly states the scope and all products are covered. Article 13 does not require per-product CVD policies - it requires that a policy exists and is publicly accessible. A well-structured policy covering your entire product portfolio is both compliant and more operationally manageable than per-product policies. The policy should list major product categories in scope and should be linked from every product's support page and from the security.txt file.

Guides for related sectors

Wearable Technology BrandsWearable technology brands producing smartwatches, fitness trackers, health monitoring wearables, smart glasses, and connected hearables for the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. A personal wearable with a health monitoring purpose, such as a fitness tracker or a smartwatch, is Important Class I when Regulation (EU) 2017/745 or (EU) 2017/746 does not apply to it. A wearable intended for use by children under 14 is also Important Class I (Annex III, point 19). Smartphone integration and payment functions do not change the class. A wearable that is a medical device is outside the CRA (Article 2(2)). The intimate personal data these devices collect - heart rate, sleep patterns, location - makes security failures particularly consequential for users.Professional Audio-Visual Equipment VendorsProfessional audio-visual equipment vendors manufacturing networked AV processors, digital signage players, conference room systems, streaming encoders, and broadcast infrastructure hardware for the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. AV equipment with IP networking, cloud management, and remote control capabilities is within CRA scope. Most professional AV products are default class, because Annex III lists no AV category and the deployment site does not change the class (Article 7(1)).Consumer Electronics BrandsConsumer electronics brands placing connected products - including smart TVs, streaming devices, Bluetooth speakers, tablets, laptops, and networked peripherals - on the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. The CRA introduces mandatory security standards and vulnerability disclosure requirements that will materially change product development, launch timelines, and post-market support obligations for consumer electronics brands of all sizes.Gaming Hardware ManufacturersGaming hardware manufacturers producing gaming consoles, handheld gaming devices, gaming peripherals with network connectivity, and gaming-specific networking hardware for the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Gaming consoles with online services, account management, and payment processing present a substantial attack surface - and the large, active user base makes vulnerabilities in gaming platforms high-value targets for both financial fraud and account compromise.

This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Start a CRA risk assessment for Smart Home Device Manufacturers

A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.

Open the starter →