Cybersecurity for robot cells, AMR fleets and cobots
RoboSecurity™ finds, contains and closes the cyber paths into your robotic equipment: controllers, fleet managers, ROS middleware and vendor remote access. Built for New Jersey and New York manufacturers, warehouses and integrators who can't afford a cell going down.
Where attacks get in
A robot cell is a computer that can move steel. Most plants secure the office network and assume the cell is isolated. In practice it rarely is.
Controllers
Exposed service ports such as 29999 and 30001-30003, stale firmware, and USB program loads nobody logs.
Middleware
DDS traffic with no authentication by default. Anyone on the segment can publish to /cmd_vel.
Fleets
Web consoles on default logins, Wi-Fi shared with handhelds, and map edits that redirect traffic.
Third parties
Always-on remote desktop tools and shared integrator accounts. The most common way into a cell.
Control
Flat networks between the PLC, the robot and the HMI, with Modbus and EtherNet/IP open to the plant floor.
AI
Pick-and-place models that can be fooled by altered inputs, and model files replaced without anyone noticing.
What we do
When something is wrong
Know your exposure
Stay closed
How an assessment runs
Walk the floor with your maintenance lead. Record every robot, controller, pendant, fleet server and vendor connection.
Passive traffic capture shows what actually talks to each cell, from the office, Wi-Fi and outside vendors.
Active tests only in agreed windows, with the cell in a safe state and your operator at the e-stop.
Ranked fixes, applied with your integrator, then re-tested so you have proof the path is closed.
We never send commands that move a robot during production. Safety of people near the machine comes before any test result.
2-minute self-check
Tick each statement that is true today. Your answers stay in your browser.
Controls in place
High exposure
Most plants start here. An exposure assessment will show which paths to close first.
Talk to an engineerFrameworks we map to
Findings are mapped to the frameworks your customers, insurers and auditors already ask about.
Zones and conduits for industrial control systems, and component requirements (62443-4-2) for robot controllers.
Industrial robot safety. The 2025 revision addresses cybersecurity where it affects safety functions.
US guidance on operational technology security, used as the baseline for most US plant assessments.
For OEMs and exporters: vulnerability reporting from Sept 2026, full product requirements from Dec 2027.
Applies from Jan 2027 and adds protection against corruption of safety-related control software.
We track robot vendor advisories and tell you when one affects equipment on your floor.
Common questions
Yes. Robot controllers, teach pendants, fleet managers and ROS-based robots run networked software. Common entry points are exposed controller service ports, default passwords, always-on vendor remote access and unauthenticated ROS 2 DDS traffic. An attacker can stop a cell, change a program or steal process data.
It is when testing is planned around safety. We start with passive traffic capture, run active tests only in agreed windows with the cell in a safe state and an operator at the e-stop, and never send motion commands during production.
The main ones are IEC 62443 for industrial control systems, ISO 10218-1 and -2 (2025) for industrial robot safety, and NIST SP 800-82 Rev. 3 for OT security in the US. Robot makers selling into the EU also face the Cyber Resilience Act and the EU Machinery Regulation 2023/1230.
Typically one to three weeks per site, depending on the number of robot cells, fleet managers and vendor connections. Testing is scheduled around production shifts.
On-site service across New Jersey and New York, with remote assessments and incident triage available nationwide. RoboSecurity is a service of 2Secure Corp.
Put the cell in a safe state using your normal safety procedures, do not power-cycle the controller or wipe programs, disconnect vendor remote access, and call the 24/7 robot incident line at 646-560-5083.
Get in touch
Tell us what you run. An engineer replies within one business day. For an active incident, call the line below.