- Duration
- Typically 1–3 weeks per site
- Testing
- Passive first. Active tests only in agreed windows, with the cell in a safe state.
- Covers
- Robot controllers and pendants, cobots, AMR fleet managers, ROS-based robots, cell PLCs and HMIs, vendor access
- Mapped to
- IEC 62443, NIST SP 800-82 Rev. 3, ISO 10218-1:2025 (cybersecurity as it affects safety)
- Price
- Fixed quote after a scoping call
What we check
| Area | What we look for |
|---|---|
| Robot controllers and pendants | Exposed service interfaces such as a cobot Dashboard Server, outdated software with published advisories, default or shared passwords, unlogged USB program loads |
| Cobots | Remote interfaces reachable from the office network, an unprotected safety configuration, third-party plugins such as URCaps |
| AMR and AGV fleets | Fleet manager web consoles, API tokens, Wi-Fi security, map and mission permissions, integrations with WMS and doors |
| ROS and ROS 2 | Open DDS discovery, SROS2 not enabled, exposed rosbridge or web dashboards, unmanaged packages |
| Network paths | Flat networks between office, Wi-Fi and cells, firewall rules, remote-access tools, cloud telemetry |
| Vendor access | Always-on remote desktop, shared integrator accounts, missing MFA, no session recording |
| Recovery | Whether robot programs and configurations are backed up, versioned and restorable |
How it runs
- Scoping call. We agree on sites, cells and safe testing windows, and name who on your team can stop a test at any time.
- Walk-down and inventory. With your maintenance lead we record every robot, controller, pendant, fleet server and vendor connection, with software versions.
- Passive capture. We mirror switch traffic to see what actually talks to each cell. Nothing is sent to the robots.
- Targeted active tests. These run only in agreed windows, with the cell in a safe state and an operator at the e-stop. We never send motion commands during production.
- Report and walkthrough. You get ranked findings with fixes your integrator can apply, an executive summary for management and insurers, and a walkthrough call.
- Re-test. After fixes, we re-test the critical findings so you have proof the paths are closed.
What you get
- An inventory of robots and connected systems, with software versions
- A network path map showing how each cell can be reached
- Findings ranked Critical, High, Medium and Low, each with a concrete fix
- A one-page executive summary for leadership and insurers
- Mapping to IEC 62443 and NIST SP 800-82 for customer and auditor questions
- A re-test of critical findings
Who it's for
Manufacturers and warehouses running robots in New Jersey and New York. Robot integrators who want a security review before handover. Robot makers preparing for customer security questionnaires or the EU Cyber Resilience Act.
Common questions
Will a robot security assessment stop production?
No. Most of the work is passive observation. Active tests run only in windows you approve, with the cell in a safe state and your operator present.
How long does a robot exposure assessment take?
Typically one to three weeks per site, depending on the number of robot cells, fleet managers and vendor connections. Smaller sites can be quicker.
Do you need copies of our robot programs?
No. Configuration and version information covers most checks. We don't take proprietary programs off site without your agreement.
Can the assessment be done remotely?
The inventory and walk-down are done on site in New Jersey and New York. For sites elsewhere in the US, parts of the work can be remote with help from your team.
Robot cell acting up?
24/7 robot incident line: 646-560-5083. Not urgent? Book an exposure assessment and an engineer replies within one business day.