RoboDR · Robot security

Stop a hijacked robot safely. Prove what happened.

RoboDR sees an attack on your robot as it begins, stops the dangerous command before it reaches the motors and keeps a tamper-proof record. People approve the steps that matter.

January 2027

Machines sold in the EU must be protected against malicious tampering, with a record of any tampering.EU Machinery Regulation (EU) 2023/1230, Annex III 1.1.9. Not legal advice.

The same hours, twice

A “run” command nobody sent

Night shift in a warehouse. A humanoid robot stands at its post. At 02:47 a device nobody recognizes starts sending it commands over the network.

TimeWithout RoboDRWith RoboDR
02:47The stranger tells the robot to run. The robot obeys, because nothing checks who sent it.RoboDR sees a sender that does not belong. It drops the command and the robot stays standing.
02:48The robot strides across the floor toward the racks. No alert reaches the security team.A case opens in AutoSecOps. The AI agent summarizes it and recommends quarantining the sender.
02:52A worker hits the emergency stop. The motors let go and the robot falls.The on-call analyst approves. RoboDR quarantines the rogue sender.
03:05Managers ask who sent the command. There is no record to show them.The black box record is verified and attached to the case, ready for the auditor.
How it endsA damaged robot, a stopped fleet and no answers.The robot never took a single step.

Why RoboDR

Six reasons to choose RoboDR

01 · Who commands it

Know who is giving your robot orders

On most robots, motion commands cross the network without any check, so anyone on that network can tell the robot to walk or raise an arm. RoboDR reads every command sent to the motors, knows which senders belong and flags a stranger at once.

  • Reads Unitree and ROS 2 motion, arm and hand commands
  • Flags unknown senders, even when they change identity
  • Catches spoofed, replayed or out-of-limit speed and joint commands
  • Compares what the robot was told with what it did
  • Spots faked or frozen telemetry and disagreeing navigation sensors

02 · Break-ins

Catch a break-in before it reaches the motors

In 2025 a published vulnerability let attackers take over widely used robots over Bluetooth alone. From there they install software, change the robot’s apps or switch off defenses. RoboDR watches the robot’s onboard computer and raises an alert at every step of known robot attacks.

  • New processes, outbound connections and remote tunnels
  • Package installs and changes to ROS 2 and robot apps
  • Bluetooth and Wi-Fi setup tools and wireless setting changes
  • Reads of the robot’s private keys
  • Any attempt to change or stop RoboDR itself

03 · Safe stop

Stop the attack without dropping the robot

For a humanoid or four-legged robot, cutting the motors means a fall. RoboDR blocks dangerous commands before they arrive and keeps humanoid and four-legged robots on their feet. The response escalates in stages, so a moving robot is never stopped blindly.

  • Every command passed, limited or rejected
  • Escalates in stages: alert, restrict, slow down, pause, safe state
  • Slows the robot without changing its direction
  • Stop commands are never delayed
  • Isolates the robot or quarantines a rogue sender

04 · People decide

Your people make the calls that matter

An automatic action on a moving robot is a risk of its own. RoboDR’s rules limit dangerous commands on their own, but pausing the robot, a safe state or a rollback needs two people. Every action is time-limited and can be undone.

  • Starts monitor-only; protection goes on when you are ready
  • Learns each robot’s normal, then locks it with human sign-off
  • The approver is always someone other than the requester
  • Emergency off at any time
  • Asks a person whenever the robot’s state is unknown

05 · Your SOC

Robot incidents land where your team already works

A robot alert in a separate tool gets missed. Each RoboDR finding opens a tracked case in AutoSecOps, Singularity’s AI security operations product, next to your other alerts. An AI agent triages it and recommends a response. A person decides.

  • A case opens for every finding, before an analyst looks
  • The AI cannot delete cases, run scripts or go online
  • Attacker text from the robot never becomes AI instructions
  • Forged, stale or unsigned findings rejected and logged
  • Whole fleet on one screen, with each robot’s cases

06 · Proof

Answer the auditor with proof, not memory

After an incident someone will ask what happened and who intervened. RoboDR writes every incident to a tamper-proof black box, like a flight recorder. Auditors can check the records but cannot forge them, which supports your evidence for the Machinery Regulation and the Cyber Resilience Act.

  • Records survive power loss; any deletion shows
  • Every finding mapped to MITRE ATT&CK and tied to evidence
  • Pull evidence by finding or time range into the case
  • Findings in the open OCSF format, for any compatible SIEM
  • Signed releases with a software bill of materials (SBOM)

Before and after

Your robots, before and after RoboDR

WhatBeforeWith RoboDR
Motion commandsAnyone on the network can send themEvery command passed, limited or rejected
Robot’s computerNew software and connections go unseenEach change raises an alert in your SOC
During an attackCutting the motors can drop the robotDangerous commands blocked; the robot stays standing
Who decidesUnclear who can cut a robot offNamed approvers; every action can be undone
After an incidentNo proof of what happenedOne signed record an auditor can verify

Straight talk

What RoboDR will not do

Replace your safety system

RoboDR is not a safety-rated component. It complements the robot’s own safety system and never stands in for it.

Cut power or reset e-stops

It never cuts motor power, resets the emergency stop or kills a program on a moving robot. With the e-stop active, it only records.

Pause a robot on its own

Rules limit dangerous commands automatically. Pausing the robot, a safe state or a rollback always needs two people’s approval.

Certify you

Its documents for IEC 62443 and the Cyber Resilience Act are an engineering self-assessment, not a certification.

How you start

One robot, one test area, three steps

  1. 1

    Choose together

    Which robot, which site, which threat. Together we write the criteria for false alerts, resource use and response time.

  2. 2

    Watch first

    RoboDR learns the robot’s normal behavior and connects to AutoSecOps. Nothing is blocked at this stage.

  3. 3

    Protect, attack, report

    We switch on protection and approval rules, attack the robot with our own red team and deliver a management report.

Questions buyers ask

Questions about RoboDR

What is RoboDR, and which robots does it work with?

RoboDR is a security layer for robots from Singularity. It sees an attack as it begins, stops dangerous commands before they reach the motors and keeps a tamper-proof record. It supports Unitree quadruped and humanoid robots, and robots running ROS 2, the open-source robot software.

Can RoboDR run on our own servers, at a site with no internet?

Yes. RoboDR’s security center runs on your own servers or in your cloud, and RoboDR works at air-gapped sites, meaning sites with no internet connection. No component calls out, and your data stays on your infrastructure.

Will RoboDR take action on our robots without asking us?

RoboDR starts in monitor-only mode, and protection goes on only when you are ready. Its rules limit dangerous commands automatically. Pausing a robot, a safe state or a rollback needs approval from two people, the approver is never the requester, and every action can be undone.

Does RoboDR replace or interfere with our robot’s safety system?

No. RoboDR is not a safety-rated component; it complements the robot’s own safety system. It never cuts motor power, resets the emergency stop or kills a program on a moving robot, and it keeps humanoid and four-legged robots from falling during a stop.

Our IT security already covers the network. Why do we need RoboDR?

Traditional security software protects the computer. RoboDR protects the robot. It reads the commands sent to the motors, can tell “walk” from “run”, and stops a hijacked robot without a fall. Its findings land in your existing SOC, beside your other alerts.

Every feature of RoboDRThe full list for your evaluation team: 47 capabilities in 8 groups.

Motion and network

  • Decodes Unitree and ROS 2 motion, arm and hand commands
  • Flags unknown senders on the robot’s network, even under new identities
  • Spoofed, replayed or out-of-limit speed, joint and torque commands
  • Compares what the robot was told with what it did
  • Faked or frozen telemetry and disagreeing navigation sensors
  • Links events into attacks such as key theft or motion hijacking
  • Never reports “all clear” when its own inputs go silent

On the robot’s computer

  • New processes and outbound connections on the robot
  • Package installs and changes to ROS 2 and robot apps
  • Bluetooth and Wi-Fi setup tools and wireless setting changes
  • Reverse tunnels, VPNs, code injection and fileless execution
  • Reads of the robot’s private keys and unexpected kernel modules
  • Attempts to change or stop RoboDR itself
  • Published robot attacks, including UniPwn (CVE-2025-35027)

Safe response

  • Escalates in stages: alert, restrict, slow down, pause, safe state
  • Isolates the robot from the network or quarantines a rogue sender
  • Every motion command passed, limited or rejected
  • Slows the robot without changing its direction; stops never delayed
  • Never cuts motor power or resets the emergency stop

Your SOC, with AI

  • Each finding opens a case in AutoSecOps automatically
  • AI agent triages each finding and recommends a response
  • The AI can never delete cases, run scripts or go online
  • Attacker text from the robot flagged, never taken as instructions
  • Forged, stale or unsigned findings rejected and logged
  • Findings in open OCSF format for any compatible SIEM

Signed evidence

  • Black box records survive power loss; any deletion shows
  • Auditors can verify records but cannot forge them
  • Every finding signed, mapped to MITRE ATT&CK and tied to evidence
  • Pull evidence by finding or time range into the case
  • Whole fleet on one screen, with each robot’s cases and evidence

Robots and add-ons

  • Unitree quadrupeds: Go2 (all editions), Go2-W, B2, B2-W, A2, AS2, Go1
  • Unitree humanoids: G1, H1, H1-2, H2, R1
  • ROS 2 mobile robots and collaborative arms, like MiR or Universal Robots
  • Add-on: signed, staged rollout of your robot apps, AI models and settings
  • Add-on: encrypted storage, boot integrity checks, erasure if compromised
  • Add-on: safe pause for Nav2, ros2_control and PX4 robots

Fleet and updates

  • Learns each robot’s normal, then locks it with human sign-off
  • Ready-made Unitree profiles; profiles pushed from the SOC need two approvers
  • Keys created on the robot; rotate or revoke them from the SOC
  • RoboDR’s own updates: signed, staged, never below your security baseline
  • Signed, reproducible releases with a software bill of materials (SBOM)

People decide

  • Starts monitor-only; protection switched on when you are ready
  • Two people approve safe pause, safe state and rollback
  • The approver is always someone other than the requester
  • Approval cannot be switched off and can cover every block
  • Every action time-limited and reversible; emergency off any time
  • Asks a person whenever the robot’s state is unknown
Robots
Unitree quadrupeds and humanoids, ROS 2 mobile robots and collaborative arms
Platforms
Ubuntu 20.04, 22.04 and 24.04; JetPack 5 and 6; amd64 and arm64
Deployment
On the robot, beside it, or both; security center on your servers or cloud
Works with
AutoSecOps and any OCSF-compatible SIEM, over HTTPS or Kafka
Evidence for
EU Machinery Regulation, Cyber Resilience Act, IEC 62443-4-1 and 4-2 (self-assessed)
Data
Stays on your infrastructure; works air-gapped; no component calls out

Built for

  • Defense
  • Energy and critical infrastructure
  • Manufacturing
  • Logistics
  • Public safety
  • Robot manufacturers

Works with

  • ROS 2
  • Unitree quadruped robots
  • Unitree humanoid robots
  • AutoSecOps

Book a demo

See RoboDR on one of your robots

Bring one robot, a test area and a schedule. We handle the setup, attack it ourselves and report to management.

Architecture, deployment and integration details are shared under NDA.