← Industry Guides
HealthcareCRA Guide

EU Cyber Resilience Act Guide for Home Health Monitoring Device Manufacturers

Outside the CRA for medical devices under Regulation (EU) 2017/745 and in vitro diagnostic medical devices under Regulation (EU) 2017/746. Important Class I for a wellness wearable with a health monitoring purpose (Annex III, point 19). Default class for other wellness devices, such as smart scales

Manufacturers of connected home health devices, such as blood pressure monitors, pulse oximeters, blood glucose meters and smart scales, must first check whether each device is a medical device. A medical device under Regulation (EU) 2017/745 and an in vitro diagnostic medical device under Regulation (EU) 2017/746 are outside the CRA (Article 2(2)). Connected wellness devices with no medical purpose are in CRA scope. A wellness wearable with a health monitoring purpose is Important Class I (Annex III, point 19), and other wellness devices are default class. These devices collect sensitive physiological data in consumer home environments and must meet stringent security-by-design standards. The consumer deployment context means that usability and security must be engineered together, with automatic update mechanisms and clear end-of-support policies particularly important.

Article 13Article 14Annex IArticle 13Article 17Article 3
Deadline: 11 December 2027Classification: Outside the CRA for medical devices under Regulation (EU) 2017/745 and in vitro diagnostic medical devices under Regulation (EU) 2017/746. Important Class I for a wellness wearable with a health monitoring purpose (Annex III, point 19). Default class for other wellness devices, such as smart scales

Last updated 26 October 2026

CRA Scope: Medical Devices vs. Wellness Products

The CRA does not apply to medical devices under Regulation (EU) 2017/745 or to in vitro diagnostic medical devices under Regulation (EU) 2017/746 (Article 2(2)). The intended purpose that the manufacturer gives the product decides whether it is a device. Connected blood pressure monitors and pulse oximeters with a medical purpose are medical devices, and blood glucose meters are in vitro diagnostic medical devices. Their cybersecurity follows those Regulations. Consumer wellness devices that make no medical claims, such as smart scales, step counters and general-purpose heart rate monitors, are in CRA scope. Their class follows core functionality (Article 7(1)). A personal wearable with a health monitoring purpose that is not a medical device, such as a step counter or a heart rate monitor worn on the body, is Important Class I (Annex III, point 19). Commission Implementing Regulation (EU) 2025/2392 describes these wearables as worn on the body directly or through clothing or accessories. A wearable intended for use by and for children under 14 is also Important Class I. A wellness device that is not worn, such as a smart scale, is default class. The intersection of consumer distribution channels and medical-grade function creates classification complexity that must be resolved product by product.

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

Consumer Security Requirements Under Annex I

Home health devices deployed in consumer environments must meet Annex I security requirements in a context where users are not IT professionals and may include elderly or chronically ill individuals. Core obligations include: shipping devices without default shared credentials - each device must have a unique credential or require account creation before activation; implementing automatic software and firmware update mechanisms that operate without user intervention; encrypting all health data transmitted to cloud services; supporting account deletion and full data erasure when requested; and minimising data collection to what is clinically or functionally necessary. The SBOM requirement applies to both device firmware and companion smartphone applications. User-facing privacy notices must accurately describe what data is collected and how it is secured. Manufacturers must clearly state the security support period at point of sale, and it should reflect how long the device is expected to be in use rather than defaulting to the five-year floor.

CRA reference:Annex I Parts I and II

CVD Policy Requirements Under Article 13

Article 13 requires manufacturers to publish a CVD policy with a dedicated security reporting channel. For consumer health device manufacturers, the CVD policy must be accessible to security researchers who discover vulnerabilities but also legible to patients and healthcare providers who may encounter unusual device behaviour. The policy should specify: a dedicated security email address and ideally a web-based reporting form; a commitment to acknowledge reports within 5 working days; and a process for notifying the manufacturer's medical device competent authority contact where a vulnerability has potential patient safety implications. Manufacturers should also maintain a public security advisory page documenting resolved vulnerabilities, firmware versions affected, and update availability. This transparency is both a regulatory expectation under the CRA and increasingly a consumer trust requirement in the health technology market.

CRA reference: and , Article 13(7)

Article 14 Incident Reporting for Consumer Health Devices

Article 14 requires notification to the relevant national CSIRT within 24 hours of confirmed active exploitation. For consumer health device vendors, active exploitation typically manifests through cloud platform compromise - affecting account credentials, health data access, or device firmware delivery - rather than direct field device exploitation. Vendors must have monitoring in place at the cloud platform level to detect anomalous access patterns indicating potential exploitation. The 24-hour notification window requires a pre-established incident response team with clear authority to file regulatory notifications. Because health data is special category data under GDPR, a cloud platform breach affecting patient health records simultaneously triggers GDPR data breach notification obligations to the relevant data protection authority within 72 hours. Incident response plans must coordinate both notification obligations.

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

CE Marking and Conformity Assessment

Default-class wellness devices, such as smart scales, can use Module A internal control (Article 32(1)). A wellness wearable with a health monitoring purpose is Important Class I. It 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 (Module B plus Module C, or Module H). ETSI EN 303 645 (IoT device security) is a useful reference for consumer home health devices. It covers default credential elimination, update mechanisms and vulnerability disclosure. It is not a harmonised standard under the CRA and gives no presumption of conformity. The technical file must include: product architecture documentation; threat model; SBOM; evidence of security testing (penetration testing or structured security review); CVD policy documentation; and the declaration of conformity. A medical device follows the conformity assessment of Regulation (EU) 2017/745 or Regulation (EU) 2017/746 only, and the CRA adds no assessment for it. A manufacturer that makes both devices and in-scope wellness products can ask whether its notified body under those Regulations is also notified under the CRA.

CRA reference:Article 2(2), Article 28, 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

Our connected blood pressure monitor is sold as a consumer product, not a medical device. Does the CRA apply?+

It depends on the intended purpose. If the monitor has a medical purpose, it is a medical device under Regulation (EU) 2017/745 and the CRA does not apply (Article 2(2)(a)), also when it is sold at retail. If it is a consumer product with no medical purpose and it connects to a smartphone app or cloud service, even for data logging or trend visualisation, it is a product with digital elements in CRA scope. Its class follows core functionality (Article 7(1)). A monitor that is worn on the body, such as a wrist unit, can match the category of wearables with a health monitoring purpose (Annex III, point 19). It is then Important Class I. Check the design against the technical description in Commission Implementing Regulation (EU) 2025/2392. A default-class device can use Module A internal control (Article 32(1)). ETSI EN 303 645 is a useful reference, but it is not a harmonised standard under the CRA. For an in-scope product you must also establish a CVD policy, maintain an SBOM, and implement Annex I security controls.

We are a small manufacturer with limited engineering resources. Which CRA obligations are most urgent to address?+

Prioritise in this order: first, eliminate default shared credentials in your current product line - this is both the highest-risk vulnerability and the CRA's most fundamental requirement; second, implement automatic firmware update capability if your devices do not already support it; third, establish a CVD policy and security.txt file, which can be done quickly using hosted platforms like CVD Portal; fourth, begin SBOM generation using software composition analysis tooling on your firmware and app codebases. Threat modelling, penetration testing, and technical file compilation can follow once these foundations are in place. Article 14 reporting applies from 11 September 2026, and the other CRA obligations apply from 11 December 2027. Start the most impactful changes now.

How long must we support home health devices with security updates under the CRA?+

The CRA requires security update support for the lesser of the expected product lifetime or five years from last placement on the market. For consumer health devices sold at retail, 'expected product lifetime' is typically 3–5 years for entry-level products and up to 7–10 years for premium devices. You must clearly state the security support period at point of sale and notify customers in advance of end-of-support. If a device's hardware cannot support continued security updates, you must provide customers with clear information about the end-of-support date and any available data migration options when the device is replaced.

Guides for related sectors

Connected Laboratory Instrument ManufacturersManufacturers of connected laboratory instruments - including mass spectrometers, chromatography systems, automated liquid handlers, and scientific imaging systems with network interfaces - must comply with the CRA for their EU-market products. Laboratory instruments increasingly integrate with LIMS platforms, cloud data repositories, and remote diagnostic services, creating network exposure that the CRA directly addresses. Manufacturers must establish vulnerability disclosure programmes, maintain SBOMs for complex instrument software stacks, and implement Article 14 notification procedures. An instrument that is an in vitro diagnostic medical device under Regulation (EU) 2017/746 is outside the CRA (Article 2(2)(b)). Other instruments are default class, because Annex III lists no laboratory instrument category.Medical Device ManufacturersThe Cyber Resilience Act does not apply to medical devices under Regulation (EU) 2017/745, the MDR, or to in vitro diagnostic medical devices under Regulation (EU) 2017/746, the IVDR (Article 2(2)). Software as a Medical Device (SaMD) that is a device under those Regulations is also outside the CRA. The cybersecurity of those devices follows the MDR and IVDR general safety and performance requirements and the guidance MDCG 2019-16. A medical device manufacturer still has CRA obligations for its other products with digital elements, such as wellness wearables and software that is not a device. Those products are default class unless their core functionality matches an Annex III category.Pharmaceutical Manufacturing Automation VendorsPharmaceutical manufacturing automation vendors - supplying SCADA systems, batch management software, process analytical technology (PAT) platforms, and manufacturing execution systems (MES) to EU pharmaceutical manufacturers - must comply with the CRA for their products. The intersection of CRA cybersecurity requirements and EU GMP computerised systems validation (CSV) obligations creates a dual compliance framework that demands careful coordination between security and validation activities. CRA non-compliance by automation vendors directly threatens their customers' GMP compliance status and product supply security.Point-of-Care Diagnostics & IVD ManufacturersThe Cyber Resilience Act does not apply to in vitro diagnostic medical devices under Regulation (EU) 2017/746, the IVDR (Article 2(2)(b)). Connected blood analysers, point-of-care PCR systems and IVD software that are devices under that Regulation are therefore outside the CRA. Their cybersecurity follows the general safety and performance requirements of the IVDR. Products that are not devices stay in CRA scope, for example research use only instruments and laboratory data software with no medical purpose. Those products are default class unless their core functionality matches an Annex III category. A manufacturer with products under both regimes must decide the regulatory qualification of each product first.

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 Home Health Monitoring Device Manufacturers?

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

Browse templates →