Cybersecurity in Lab Automation
Lab automation connects instruments, software and people across IT and OT. The SiLA Cybersecurity Working Group makes sure SiLA code meets a high security standard, and helps the community build secure lab automation.
What brings you here?
I use SiLA libraries
Find out which security baseline SiLA defines for its reference implementations.
I build SiLA servers or clients
Learn about the Secure Software Development Life-Cycle and security testing.
I run or integrate lab automation
Guidance for integrators and administrators operating SiLA in an OT/lab environment.
I found a vulnerability
Report it responsibly. Here is how, and what you can expect from us.
Lab automation is software, and software can be attacked
From Excel macros and Python scripts to SiLA servers (devices or services offering SiLA functionalities over the network), middleware and enterprise systems: almost every automated workflow in the lab depends on software. Typical SiLA environments combine office IT with operational technology (OT) on the lab floor. That makes them attractive targets, and the consequences go far beyond lost data.
Cyber risks are growing fast
Healthcare is one of the most attacked sectors, accounting for almost a quarter of all hacks reported by the US government (Nature Biotechnology, 2022).
Real, physical danger
Manipulated data can affect product quality and patient safety. Compromised instruments can cause physical damage and harm the people working with them.
Intellectual property at stake
Research data, methods and results are valuable. Theft or silent manipulation threatens your claims, your products and your shareholder value.
Regulation is catching up
The EU NIS2 directive and the Cyber Resilience Act (CRA) require security controls, testing and vulnerability management for products with digital components.
Questions to ask yourself and your organisation
- Do you know who is responsible for secure lab automation in your organisation? Your IT department may not be aware of the risks.
- If a cyber attack on your organisation originated from your lab automation hardware or scripts, what would your answer be?
- When did you last receive a security update from the vendor of any of your instruments? When did you last ask for one?
- Do you write code (Python scripts, SiLA servers, โฆ)? Do you have security controls in place to protect it?
- Does anybody who understands the operational impact know your lab’s network topology: switches, firewalls, VLANs?
- How do you protect legacy devices and software that no longer receive security updates?
- Which assets do you need to protect: confidential data, data integrity, availability of instruments, operational safety?
Cybersecurity at SiLA
The Working Group
Our objectives, our four-level approach and who is involved.
Secure development & testing
The Secure Software Development Life-Cycle, the security testing pyramid and the security baseline for SiLA code.
Guidelines & resources
Guidelines for developers and integrators, background reading and the disclosure policy.
Only in growth, reform, and change, paradoxically enough, is true security to be found.Anne Morrow Lindbergh
Found a vulnerability? Want to contribute?
Please report security issues in SiLA code or on this website responsibly to vulnerabilities@sila-standard.org. If you would like to join the Cybersecurity Working Group, get in touch with us.
