EU Cyber Resilience Act Guide for Connected Laboratory Instrument Manufacturers
Default class for most instruments, whatever the laboratory setting. Outside the CRA when the instrument is an in vitro diagnostic medical device under Regulation (EU) 2017/746
Manufacturers 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.
Last updated 26 October 2026
CRA Scope for Laboratory Instruments
Connected laboratory instruments placed on the EU market - including mass spectrometers with remote diagnostic capability, automated liquid handling workstations with LIMS integration, scientific imaging systems with cloud synchronisation, chromatography data systems, and laboratory automation platforms - are products with digital elements under Article 3(1). Classification follows core functionality (Article 7(1)). Annex III lists no laboratory instrument category, so research instruments and instruments in GMP pharmaceutical quality control laboratories are default class. The laboratory setting does not change the class. Result data that influences regulated manufacturing release decisions raises the risk that the Article 13(2) cybersecurity risk assessment has to address. An instrument that its manufacturer intends for in vitro diagnostic use, for example in a clinical pathology laboratory, is an in vitro diagnostic medical device under Regulation (EU) 2017/746 and is outside the CRA (Article 2(2)(b)). A version of the same instrument sold for research use only, with no medical purpose, stays in CRA scope.
Technical Security Obligations for Laboratory Instrumentation
Laboratory instruments present specific security challenges: they often run specialised operating systems (frequently Windows-based) with long software lifecycles, are connected to proprietary instrument-control software, and are increasingly networked to LIMS and cloud platforms for data management. Annex I obligations include: ensuring Windows-based instrument computers receive operating system security updates, either through vendor-managed patch packages or through documented customer guidance; implementing access controls on instrument control software and data management interfaces; encrypting data transfers to LIMS, cloud repositories, and remote diagnostic services; eliminating default administrator credentials on instrument management consoles; and providing an authenticated mechanism for remote vendor service access that is auditable and revocable. The SBOM must cover both the vendor-supplied instrument software and any commercial or open-source components embedded in the software stack, including the operating system and instrument control libraries.
CVD Policy Under Article 13
Article 13 requires a published CVD policy with a dedicated security reporting channel. For laboratory instrument manufacturers, the CVD programme must be capable of handling: vulnerability reports from scientific computing security researchers; reports from laboratory IT administrators who discover unexpected network behaviour; and internal findings from the vendor's own security testing programme. Because laboratory instruments are deployed in highly regulated environments - GMP pharmaceutical laboratories, accredited clinical laboratories - security advisories must be communicated in a format compatible with change control and qualification processes. When a security update is released, the vendor should provide customers with a qualification risk assessment summarising the security improvement and confirming that the update does not affect instrument performance or validated method results. This documentation supports customers' change control obligations under applicable quality regulations.
Article 14 Incident Reporting
Article 14 requires notification to the relevant national CSIRT within 24 hours of confirmed active exploitation. For laboratory instrument vendors, exploitation scenarios typically involve remote access to instrument control software enabling data manipulation, exfiltration of proprietary research data, or disruption of automated analytical workflows. Vendors must maintain incident monitoring that covers both cloud-side services and on-premises instrument connectivity. The incident response plan must be capable of generating the 24-hour early warning notification while simultaneously investigating the full scope of exploitation across the installed customer base. For GMP pharmaceutical laboratory customers, a confirmed security incident may trigger their own regulatory notification obligations to the relevant medicines authority - vendor notifications should be designed to give customers sufficient information to fulfil their own regulatory obligations.
Conformity Assessment Pathway
Default-class laboratory instruments can use Module A internal control (Article 32(1)). IEC 62443-4-1 (secure development lifecycle) and IEC 62443-4-2 (component security requirements) are useful references for network-connected scientific instruments. They are not harmonised standards under the CRA and give no presumption of conformity. ISO/IEC 27001 certification of the vendor's information security management system provides supporting evidence for the technical file but does not substitute for product-specific CRA conformity documentation. The technical file must include product security architecture documentation, threat model and risk assessment, SBOM, evidence of security testing, CVD policy, and the declaration of conformity. For vendors with large instrument portfolios, a modular technical file approach - with common security architecture and lifecycle documentation shared across product families - is more efficient than separate files per model.
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 instruments run Windows 7 or Windows 10 because the instrument control software has not been validated on newer OS versions. How do we comply with security update requirements?+
This is a common challenge in laboratory instrumentation. The CRA's Annex I requirement to support security updates does not mandate OS upgrades - but it does require you to take all reasonable steps to provide security protection. Options include: accelerating OS validation timelines to support current Windows versions; working with Microsoft's Extended Security Updates (ESU) programme for Windows 10 end-of-life; implementing compensating controls such as application whitelisting, host-based firewalls, and network segmentation for instruments that cannot be updated; and providing customers with documented hardening guidance for end-of-life OS environments. The approach must be documented in the technical file with a risk assessment justifying the compensating controls.
Our remote service access system allows vendor engineers to connect to instruments at customer sites. How must this be secured?+
Remote service access must be secured to meet Annex I requirements. Minimum standards include: requiring multi-factor authentication for all vendor engineer connections; using encrypted channels (VPN or similar) with no unencrypted fallback; implementing session logging that records all actions taken during a service session; requiring explicit customer authorisation before each service session is initiated; and providing customers with a mechanism to review and revoke vendor access. Service access credentials must be individual - shared service account passwords are not acceptable under Annex I. Access for legacy instruments should be reviewed against these requirements, with remediation plans for products that cannot meet them within the current architecture.
Our LIMS integration uses standard HL7 or ASTM interfaces. Are these covered by CRA security requirements?+
Yes. All network interfaces including HL7 and ASTM messaging interfaces are in scope for Annex I security requirements. The CRA requires that interfaces are secured proportionate to their risk - HL7 interfaces transmitting diagnostic results should use authenticated and encrypted transport (e.g. HL7 over TLS, MLLP Secure). Where existing LIMS middleware does not support encrypted transport natively, compensating controls at the network layer should be implemented and documented. Your technical file should enumerate all external interfaces, their security mechanisms, and any known limitations. Customer documentation should include network configuration guidance specifying the security controls required for LIMS integration.
Compliance checklists for your products
Key CRA articles for Connected Laboratory Instrument Manufacturers
Guides for related sectors
Free CRA tools
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 Connected Laboratory Instrument Manufacturers?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.