Product · Cyber + safety (2027)
Cybersecurity for safety functions, in one assessment
New for 20 January 2027: show that no cyber threat can defeat a safety function, and prove it in the technical file.
- Safety function ↔ zone traced
- Annex III 1.1.9 / 1.2.1 evidence
- Certified engineer sign-off
How you do it in MSA
6 steps
- 1
Start from your safety functions
Use the ISO 13849 / IEC 62061 functions already verified in MSA.
- 2
Map zones and conduits
Link each function to its IEC 62443 zones, conduits and target security level.
- 3
Assess threats to each function
Score corruption, remote access and malicious attempts against the function they could defeat.
- 4
Record measures
Capture protection, intervention evidence and software version logging per Annex III.
- 5
Export the evidence
Generate technical file content against 1.1.9 and 1.2.1, traced to each function.
- 6
Engineer sign-off
A certified safety engineer reviews and signs off before issue.
MSA · Cyber + safety · IEC 62443 ↔ ISO 13849
| Safety function | Zone / conduit | Threat | SL-T | Status |
|---|---|---|---|---|
| SF-01 E-stop · PL d | Z1 Safety PLC | Logic tamper | SL 2 | Covered |
| SF-02 Light curtain · PL e | Z1 Safety PLC | Param. change | SL 2 | Covered |
| SF-03 Door interlock · PL d | C2 Remote access | Bypass via VPN | SL 3 | Gap |
| SF-04 Safe speed · SIL 2 | Z2 Drive network | Firmware swap | SL 2 | Review |
Illustrative screen. Values are example data.
See it on your own machine
Bring a recent project. We’ll walk through it in MSA.