← CRA Compliance Checklists
Consumer ElectronicsDeadline: 11 December 2027

CRA Compliance Checklist: Wearable Devices & Fitness Trackers

Important Class I for wearables with a health monitoring purpose outside Regulation (EU) 2017/745 and Regulation (EU) 2017/746, and for wearables intended for use by and for children (Annex III, point 19). Default class for other wearables. Medical devices under those Regulations are outside the CRA

Wearable devices collect sensitive biometric and health data and are in scope for the CRA as products with digital elements. The category covers fitness trackers, smartwatches, and health monitors. Unlike medical devices regulated under MDR, general fitness wearables are not excluded from the CRA. A wearable with a health monitoring purpose, such as heart rate tracking, is Important Class I (Annex III, point 19). A wearable intended for use by and for children is also Important Class I. Every in-scope wearable must comply with all Annex I security requirements, including data minimisation, encrypted transmission, and secure update mechanisms.

16
checklist items
14
high priority
11 December 2027
deadline
Consumer Electronics
sector
CRA Classification:Important Class I for wearables with a health monitoring purpose outside Regulation (EU) 2017/745 and Regulation (EU) 2017/746, and for wearables intended for use by and for children (Annex III, point 19). Default class for other wearables. Medical devices under those Regulations are outside the CRA

Last updated 26 October 2026

1. Scope & Classification

Confirm the wearable connects to a network (Bluetooth, Wi-Fi, LTE) and is not MDR-classified as a medical device

highArticle 3(1)

Wearables with network connectivity are products with digital elements. The CRA does not apply to a device to which Regulation (EU) 2017/745 or Regulation (EU) 2017/746 applies (Article 2(2)). Confirm the medical device status with legal counsel.

Check Annex III, point 19 for wearables with a health monitoring purpose or for use by children

highArticle 7(1), Annex III, point 19

A wearable that senses and processes health-relevant information, such as a fitness tracker or a smartwatch with heart rate tracking, is Important Class I. A wearable for children under 14 is also Important Class I (Commission Implementing Regulation (EU) 2025/2392). Point 19 does not cover a wearable for payment or identity. A payment wristband whose core functionality is its payment secure element is a smartcard and is critical (Annex IV, point 3). Other wearables are default class.

Compile SBOM covering firmware, companion app (iOS/Android), and cloud backend components

high

Wearable ecosystems span device firmware, mobile app, and cloud. All components must be tracked for CVEs.

2. Data Security & Privacy

Encrypt all biometric and health data in transit using TLS 1.2+ (or DTLS for Bluetooth)

high

Biometric data is sensitive personal data under GDPR. End-to-end encryption from device to cloud is mandatory.

Implement data minimisation - only collect data necessary for device function

high

CRA Annex I requires minimising the attack surface including data collected. Collect only what is necessary.

Encrypt health and biometric data at rest on the device and in the cloud

high

Data at rest must be encrypted. Hardware-backed secure storage is preferred for on-device data.

Implement Bluetooth pairing with authentication - reject unauthenticated connections

high

Bluetooth Low Energy pairing must use authenticated bonding. Unauthenticated or 'Just Works' pairing is insufficient for health data.

3. Product Security

Implement signed firmware updates verified before installation

high

OTA firmware updates must be cryptographically signed. Device must verify signature before applying any update.

Require user authentication (PIN, biometric) to access sensitive health data

high

Health data on the wearable must be protected from physical access. Device lock with authentication timeout is required.

Implement factory reset that securely wipes all personal and health data

high

CRA requires the ability to remove personal data. Factory reset must cryptographically erase all user data, not just delete pointers.

Disable unused wireless interfaces when not in use

medium

Minimise radio attack surface. Wi-Fi and Bluetooth should not broadcast when the device is not actively paired or syncing.

4. CVD & Vulnerability Management

Publish a CVD policy covering both device firmware and companion app

highArticle 13(1)

Security researchers investigate wearable firmware and companion apps. A CVD policy covering all components is required.

Define a support lifecycle of at least 5 years for each wearable model

high

Consumers expect wearables to receive security updates throughout their use. Define and publish support end dates per model.

Publish CVEs and security advisories when vulnerabilities are fixed

medium

Issue CVEs for vulnerabilities fixed in firmware or app updates. Release notes alone are not sufficient disclosure.

5. CE Marking & Conformity

Compile technical file with security architecture documentation and risk assessment

highArticle 31, Annex VII

Technical file must cover device firmware, companion app, and cloud backend security architecture.

Issue EU Declaration of Conformity referencing CRA compliance

highArticle 20, Article 28

Wearables typically already have CE marking for radio (RED). CRA adds cybersecurity requirements to the existing DoC. A Class I product can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I wearable needs a notified body.

Track your Wearable Devices & Fitness Trackers compliance progress in CVD Portal.

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

Our wearable tracks heart rate and SpO2 - does this make it a medical device exempt from the CRA?+

Not automatically. Whether a device is a medical device under MDR depends on its intended purpose and medical claims, not just its sensors. A fitness wearable that tracks heart rate for general wellness is typically not an MDR medical device. Only devices with a specific medical intended purpose (diagnosis, monitoring, treatment) qualify. If your device is not MDR-classified, it is in full CRA scope. Its health monitoring purpose then makes it Important Class I (Annex III, point 19).

Do we need to comply with both CRA and GDPR for wearable health data?+

Yes - CRA and GDPR are complementary but separate frameworks. GDPR governs how you process personal data (lawful basis, data subject rights, retention). CRA governs the security of the product itself. Health and biometric data is both personal data under GDPR and sensitive data requiring protection under CRA Annex I. Compliance with one does not substitute for the other.

Our wearable only connects to a smartphone via Bluetooth - is it in scope?+

Yes. Bluetooth connectivity makes the device a product with digital elements under the CRA. Indirect internet connectivity via a smartphone is sufficient to bring the device within scope. The smartphone companion app, which connects to the internet, is also in scope as separate software.

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

Need a CVD policy for Wearable Devices & Fitness Trackers?

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

Browse templates →