← CRA Compliance Checklists
EmergingDeadline: 11 December 2027

CRA Compliance Checklist: Laboratory Instruments & Scientific Equipment

Default class for most laboratory instruments and laboratory software, because Annex III lists no laboratory category. Outside the CRA when Regulation (EU) 2017/746 applies, as for an IVD instrument (Article 2(2)(b))

Laboratory instruments and scientific equipment - including networked analysers, chromatography systems, mass spectrometers, laboratory information management systems (LIMS), and laboratory automation platforms - are products with digital elements subject to the CRA. In Vitro Diagnostic (IVD) instruments regulated under IVDR are excluded from CRA scope. General-purpose laboratory instruments with network connectivity and data management capabilities are fully in CRA scope.

15
checklist items
12
high priority
11 December 2027
deadline
Emerging
sector
CRA Classification:Default class for most laboratory instruments and laboratory software, because Annex III lists no laboratory category. Outside the CRA when Regulation (EU) 2017/746 applies, as for an IVD instrument (Article 2(2)(b))

Last updated 26 October 2026

1. Scope & Classification

Verify whether each instrument is an IVD under Regulation (EU) 2017/746. If it is, the CRA does not apply to it

highArticle 2(2)(b), CRA / IVDR 2017/746

The CRA does not apply to instruments to which the IVDR applies (Article 2(2)(b)). General-purpose laboratory instruments (HPLC, GC-MS, spectrophotometers) without an IVD intended purpose are fully in CRA scope.

Confirm the class of each instrument from its core functionality (Article 7(1))

mediumArticle 7(1), Annex III

Annex III lists no laboratory instrument category, so most instruments are default class. Use for pharmaceutical batch release, forensic evidence or environmental regulatory reporting does not change the class. Address it in the Article 13(2) risk assessment.

Assess LIMS and laboratory automation software as standalone software products with digital elements - fully in CRA scope regardless of hardware classification

highArticle 3(1)

LIMS software, laboratory automation platforms, and electronic lab notebooks (ELNs) are standalone software products in CRA scope. Each requires its own CVD policy, SBOM, and DoC.

Compile SBOM for instrument firmware, control software, data acquisition software, and laboratory integration middleware

high

Laboratory instruments include embedded firmware, Windows-based control software, and laboratory data system (LDS) software. Compile SBOMs for each software layer.

2. Product Security (Annex I Part I)

Implement role-based access control for laboratory instruments - separate operator, scientist, administrator, and service roles

highAnnex I, Part I(2)

Laboratory instruments processing regulated data require strict access controls. In GMP environments, audit trails and access controls are also regulatory requirements (21 CFR Part 11 / EU Annex 11).

Implement tamper-evident audit trails for all instrument data - align with FDA 21 CFR Part 11 and EU Annex 11 requirements for electronic records

high

21 CFR Part 11 and EU Annex 11 require audit trails for electronic records in regulated environments. CRA Part I(8) logging requirements align with these. Implement compliant audit trails that satisfy both.

Encrypt all instrument data transmissions - chromatography data, analytical results, and calibration records must be protected in transit

high

Laboratory data transmitted over lab networks should be encrypted. Use TLS for all data transfers between instruments, LIMS, and data repositories.

Implement cryptographically signed software updates - laboratory instrument software updates must be verified before installation in regulated environments

high

Software updates to instruments in regulated laboratories require validation. Signed updates support change control processes by allowing integrity verification before and after update.

3. CVD Policy & Vulnerability Handling

Publish a CVD policy and security contact for laboratory instrument software vulnerabilities

highArticle 13(1)

Laboratory instrument software, particularly Windows-based data systems, faces the same vulnerability landscape as general Windows applications. A CVD policy enables responsible disclosure.

Align security patch delivery with laboratory change control processes - provide validated patches with qualification documentation

high

In GMP laboratories, software changes require validation. Provide security patches with IQ/OQ/PQ documentation to support customers' change control processes and reduce the validation burden.

Define security support lifecycle appropriate to laboratory equipment investment cycles - minimum 7 years

high

Laboratory instruments are capital investments with 7–15 year lifespans. Publish per-product security support end dates and provide migration guidance before end of support.

4. Article 14 Incident Reporting

Define Article 14 triggers - focus on data integrity compromise in regulated quality systems, exfiltration of proprietary research data, and ransomware disrupting laboratory operations

mediumArticle 14(1)

Exploitation compromising the integrity of GMP quality data or research data supporting regulatory submissions is a significant Article 14 trigger.

Coordinate Article 14 reporting with GDPR breach notifications if laboratory instruments process personal data (e.g. patient samples in clinical labs)

mediumArticle 14(2), CRA / GDPR Article 33

Clinical laboratory instruments processing patient samples handle personal data. A breach may trigger both CRA Article 14 and GDPR Article 33.

5. CE Marking & Technical Documentation

For IVD instruments, maintain IVDR technical documentation as primary compliance evidence and confirm the IVDR applies

highArticle 2(2)(b), CRA / IVDR Article 13

The CRA exclusion follows from the IVDR applying to the instrument (Article 2(2)(b)). The IVDR then governs the instrument. Keep your IVDR technical file and notified body assessment current.

For non-IVDR laboratory instruments, prepare CRA technical file and issue EU Declaration of Conformity

highArticle 31, Annex VII, Article 28, Annex V / Article 20

Non-IVD laboratory instruments require full CRA DoC and technical file. Leverage 21 CFR Part 11 / EU Annex 11 validation documentation as supplementary evidence.

Track your Laboratory Instruments & Scientific Equipment 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 analytical instruments run Windows 10 with vendor-specific data acquisition software - does the Windows support lifecycle affect our CRA obligations?+

Yes. CRA requires you to deliver security updates for the duration of your stated support period. Windows 10 reaches end of mainstream support in October 2025. If your instruments run Windows 10, you must obtain Extended Security Updates (ESU) from Microsoft, upgrade the OS, or implement compensating controls. You cannot meet your CRA security update obligations for OS-level vulnerabilities on an unsupported OS. Plan your OS migration strategy now.

We manufacture laboratory equipment that is used in both research and clinical settings - does the clinical use change the CRA classification?+

No. The CRA class follows the core functionality of the product (Article 7(1)), and Annex III lists no laboratory instrument category. Clinical use does not raise the class. It raises the risk that the Article 13(2) risk assessment must address. If the instrument has an IVD intended purpose, Regulation (EU) 2017/746 applies and the CRA does not (Article 2(2)(b)). Check the IVDR qualification of the instrument for its clinical use.

Our LIMS is deployed in a pharmaceutical GMP environment - do 21 CFR Part 11 / EU Annex 11 compliance and CRA have significant overlap?+

Yes, there is significant overlap. Both frameworks require audit trails (CRA Part I(8) / 21 CFR 11.10(e)) and access controls (CRA Part I(2) / 21 CFR 11.10(d)). Both also require system validation documentation (CRA technical file / 21 CFR 11.10(a)) and software change control (CRA update requirements / 21 CFR 11.10(k)). Design your compliance programme to satisfy both simultaneously. Your LIMS validation documentation can provide substantial CRA technical file evidence.

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 Laboratory Instruments & Scientific Equipment?

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

Browse templates →