← Industry Guides
Consumer ElectronicsCRA Guide

EU Cyber Resilience Act Guide for Wearable Technology Brands

Important Class I for wearables with a health monitoring purpose outside the MDR and the IVDR, including fitness trackers, and for wearables for children under 14 (Annex III, point 19). Default class for other wearables. Critical for a payment wristband that is a smartcard (Annex IV, point 3). Outside the CRA for wearables that are medical devices (Article 2(2))

Wearable 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.

Article 13Article 14Annex IArticle 13Annex IVArticle 20
Deadline: 11 December 2027Classification: Important Class I for wearables with a health monitoring purpose outside the MDR and the IVDR, including fitness trackers, and for wearables for children under 14 (Annex III, point 19). Default class for other wearables. Critical for a payment wristband that is a smartcard (Annex IV, point 3). Outside the CRA for wearables that are medical devices (Article 2(2))

Last updated 26 October 2026

CRA Scope and Classification for Wearable Products

Smartwatches, fitness trackers, smart rings, health monitoring bands (ECG, SpO2, blood glucose), smart glasses, AR headsets, and connected hearables (smart earbuds) are products with digital elements within CRA scope when they include network connectivity and embedded software. A wearable to which Regulation (EU) 2017/745 or (EU) 2017/746 applies, such as a hearing aid or an ECG monitor that is a medical device, is outside the CRA (Article 2(2)).

Classification follows core functionality (Article 7(1)). Annex III, point 19 makes two groups of wearables Important Class I. The first group is personal wearables with a health monitoring purpose to which Regulation (EU) 2017/745 or (EU) 2017/746 does not apply. Commission Implementing Regulation (EU) 2025/2392 describes them as wearables that sense and process health-relevant information, including body metrics, and names fitness trackers, smartwatches, smart jewellery and smart clothing. A step-counting fitness band and a smart ring that tracks sleep are in this group. The second group is wearables intended for use by children under 14, such as child safety watches. Cellular connectivity, NFC payment, biometric authentication for payment and cloud sync do not change the class. A wearable with no health monitoring purpose that is not intended for children, such as smart glasses or smart earbuds without health tracking, is default class. A payment wristband whose core functionality is a payment secure element is a smartcard, a critical product (Annex IV, point 3). A smartwatch that integrates a secure element for payment keeps the class of its own core functionality. Brands must assess each SKU independently.

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

Technical Security Requirements for Wearables

Wearable security presents unique challenges: devices are small and power-constrained, yet must implement cryptographic security, update mechanisms, and privacy controls:

  • Encrypted health data: Health data stored on the wearable or transmitted to companion apps and cloud platforms must be encrypted. Heart rate, ECG, and sleep data are sensitive personal data under GDPR; their security is both a CRA and GDPR obligation.
  • Bluetooth security: Wearable-to-smartphone Bluetooth connections must use authenticated, encrypted pairing. BLE bonding security and protection against MITM attacks during pairing are required.
  • Authenticated OTA updates: Wearable firmware updates delivered over Bluetooth or WiFi must be cryptographically signed and verified before installation.
  • Unique device pairing: Wearables must not accept pairing requests from unrecognised devices without user confirmation. Promiscuous pairing modes are prohibited.
  • Payment security: Wearables with NFC payment capability must implement the same secure element standards required for contactless payment cards.
CRA reference:Annex I

CVD Policy and Article 13 for Wearable Brands

Wearable technology brands - including both large consumer electronics companies and specialist health technology startups - must establish formal, publicly accessible CVD policies under Article 13. The intimate nature of wearable data makes undisclosed vulnerabilities particularly sensitive; the CVD programme must be functional before it is needed.

  • Cover all connected wearable products and companion mobile applications
  • Be accessible via the brand's security.txt and security/privacy pages
  • Define a submission channel accessible to both security researchers and healthcare professionals who may identify clinical-grade data integrity issues
  • Commit to CSAF advisory publication for resolved vulnerabilities
  • Address the companion app ecosystem: wearable security cannot be considered in isolation from the iOS/Android apps that process the data

Brands distributing health-grade wearables should check whether any product is a medical device under Regulation (EU) 2017/745. A medical device is outside the CRA (Article 2(2)) and follows the post-market surveillance and vigilance requirements of that Regulation instead.

CRA reference:Article 13(1), and

Article 14 Incident Reporting for Wearable Products

  • Mass data breach of cloud-stored health data through backend API vulnerabilities
  • Exploitation of Bluetooth vulnerabilities to intercept health data or impersonate the wearable to the companion app
  • NFC payment fraud through wearable payment credential theft

The 24-hour ENISA notification requirement applies upon confirmation of active exploitation. For wearable brands, GDPR Article 33 (72-hour data breach notification to the supervisory authority) applies concurrently if personal health data is exposed. The two notifications - ENISA (CRA Article 14) and data protection authority (GDPR) - must be coordinated but are filed separately. CVD Portal's Article 14 timeline tool supports multi-track deadline management.

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

Conformity Assessment and Consumer Compliance

Default Class wearables may use the Module A internal conformity assessment. A Class I wearable, such as a fitness tracker or a child safety watch, 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 wearable needs a notified body for now (Module B plus Module C, or Module H). For brands with large consumer product portfolios, managing Class I assessments across multiple SKUs requires careful programme management.

  1. Product classification rationale
  2. Security architecture documentation (Bluetooth security, encryption, update mechanism)
  3. Threat model for the wearable and its companion ecosystem
  4. Security testing records
  5. SBOM for firmware and companion app components

Wearable brands should also ensure that companion mobile applications - iOS and Android apps that sync with wearables - are treated as products with digital elements in their own right where they are placed on the EU market as independent commercial products. App store distribution of a companion app that processes health data from EU users constitutes market placement subject to CRA.

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 health monitoring wearables (ECG, blood glucose) subject to MDR in addition to the CRA?+

One or the other applies, never both. The CRA does not apply to products to which Regulation (EU) 2017/745 (MDR) or Regulation (EU) 2017/746 (IVDR) applies (Article 2(2)). A wearable that makes clinical measurements and displays results intended for medical decision-making can be a medical device under the MDR. It is then outside the CRA. The distinction depends on the intended use and the manufacturer's claims. A smartwatch that measures SpO2 for wellness purposes may not be an MDR device. The same measurement marketed to monitor oxygen saturation in patients with respiratory conditions likely is. A wellness wearable with a health monitoring purpose stays in the CRA and is Important Class I (Annex III, point 19). Manufacturers of health-grade wearables should obtain regulatory guidance on MDR classification for each product.

How do we handle companion app updates - are app store releases subject to CRA?+

Companion mobile applications that a brand distributes through Apple App Store or Google Play to EU users in the course of a commercial activity are products with digital elements in CRA scope, unless Regulation (EU) 2017/745 applies to them. The app and the wearable hardware together constitute the product system. Security vulnerabilities in the companion app that affect the security of the health data or the wearable's functions are within the scope of the manufacturer's CRA vulnerability management and CVD obligations. App store update mechanisms provide one delivery pathway for security updates; the CRA requires that security updates be provided and available within reasonable timeframes.

Does the CRA apply to smart clothing (e-textiles) with embedded sensors?+

Smart clothing and e-textiles with embedded digital elements - sensors, communication modules, and embedded software - are products with digital elements within CRA scope if they are placed on the EU market as commercial products. Classification follows core functionality (Article 7(1)). A sports garment with embedded heart rate sensors and Bluetooth connectivity has a health monitoring purpose. It is Important Class I (Annex III, point 19) when Regulation (EU) 2017/745 does not apply to it. Smart clothing intended for use by children under 14 is also Important Class I. Network exposure and data processing capabilities do not change the class. Manufacturers of smart textiles should conduct a CRA scope and classification assessment for each product line.

Guides for related sectors

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.Smart Appliance ManufacturersSmart appliance manufacturers producing connected washing machines, dishwashers, refrigerators, ovens, and other networked household appliances 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. While individual smart appliances are typically Default Class, manufacturers with large connected appliance portfolios must establish CVD programmes, maintain SBOMs, and declare support lifetimes that reflect the 10–15 year operational life consumers expect from major household appliances.

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

Need a CVD policy template for Wearable Technology Brands?

Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.

Browse templates →