Security and compliance for robot software.
Customers' security reviews and new regulations now reach deep into robot software. We make your ROS stack secure and auditable, as an engineering project, not a paperwork exercise.
Selling in Europe?
The EU Cyber Resilience Act applies to robots sold in the EU, wherever the maker is based.
Reporting of actively exploited vulnerabilities within 24 hours began.
Full requirements apply, including an SBOM and security updates for the product's lifetime.
Why robots are harder than most products.
A typical ROS 2 robot ships hundreds of open-source packages, a middleware layer and vendor drivers. You can't fix or report a vulnerability you don't know is in your stack.
Deep dependency trees
ROS packages, DDS middleware, drivers and containers all need to be inventoried.
Known security gaps
Researchers have documented design weaknesses in ROS 2's security framework, SROS2.
Long product lives
Robots stay in service for years and need security updates for that whole period.
What we deliver.
Pick one, or start with a fixed-price sprint that covers the essentials in three to six weeks.
Questions robot makers ask.
Is this the same as certification?
No. We get your software, processes and documentation ready. Where third-party assessment is required, an accredited body performs it; our work gives them what they need.
Do you need access to our source code?
We need access to your build system and dependency manifests. Source access helps for deeper review, under your IP terms.
What happens after the project?
You can run the process yourselves, or we monitor vulnerabilities and prepare advisories as a monthly service.
Is this legal advice?
No. We're engineers. For legal interpretation of your obligations, work with your counsel; we'll coordinate with them.