Compliance
Cybersecurity under the CRA
The Cyber Resilience Act turns vulnerability watching into a duty with a clock. The colleague keeps both the list and the deadlines.
How you work it in Colleag
- 1
Component lists per firmware version are kept current.
- 2
Published vulnerabilities are matched against them.
- 3
Affected products, versions and customers are listed.
- 4
Reporting duty and deadline are shown per event.
A worked example
“Does the new vulnerability in the Bluetooth stack affect our products?”
Affected products and firmware versions, installed base per customer from the business system, and what the CRA requires with its deadline, ready as reporting material.
Screenshot from Colleag. The example uses invented figures.
The material
- Component lists per version
- The release documentation
- Serial numbers and customers in the business system
You approve
Everything the colleague produces is a proposal with sources. Nothing is published, sent or saved to the archive without a human approving it, and every figure traces to its material.
Curious what it feels like?
We run pilot programs with a few manufacturing companies at a time. Tell us about your business and we will show what the colleagues can do with your documents and your data.