- Service
- Custom software development
- Regulation
- EU Cyber Resilience Act
- Status
- In progress
A global life science instrument company added EU Cyber Resilience Act compliance to a planned update of its imaging software. TotalLab is building it into the same release.
The customer
A global life science instrument company. TotalLab develops the imaging analysis software that ships with its instruments, white-label, under the customer’s brand.
The challenge
The customer commissioned a version update of that software. Part way through, a new requirement arrived: the release must comply with the EU Cyber Resilience Act. The CRA was not the reason for the update, but every unit placed on the EU market from 11 December 2027 must meet it, so the next release had to.
Our approach
Rather than treat CRA compliance as a separate program, we are building it into the release already under way. The software is being assessed against the CRA’s essential requirements, and the work needed to meet them is being delivered alongside the planned features, by the team that already knows the codebase.
Why it matters for other instrument makers
A planned update is the easiest time to add CRA compliance. The code is already open, the release is already being tested and documented, and the customer gets one release instead of two. If you have a software update planned before December 2027, that is where CRA compliance belongs.
Related links
EU Cyber Resilience Act compliance for OEMs →
Cyber Resilience Act FAQ →
All case studies →