Robotics & autonomous systems
security roadmap

Industrial and service robots, as well as autonomous systems.

When a robot is hacked, it physically moves. Even without set regulations, checking it from an attacker's perspective before launch reduces the risk of accidents and recalls.

Yes. We have a track record of breaking into real products, including security testing of 6 robot vacuum models, hacking a robot dog (Deep Robotics Lite3), and successful Pwn2Own exploits two years in a row. You can see the cases in TRACK RECORD above.

We look at every path an attacker could take — the app and cloud that control the robot, the robot's firmware and hardware debug ports, and wireless communications such as Wi-Fi and BLE.

Reproduction steps and safety impact for each attack scenario, a remediation guide and retest results.

Yes. Testing at the prototype stage makes design changes easier and less costly. When the firmware is updated after launch, we retest the parts that changed.

We agree on the test scope and safety conditions in advance, and do hands-on work such as hardware analysis on samples we've agreed on with you.

There are no security regulations specific to robots yet, but EU RED 3.3 may apply if the product has wireless functions, the EU CRA if it contains software, and the EU Machinery Regulation if it's industrial machinery.

Results are delivered only to you under a non-disclosure agreement and are never disclosed without your consent.