# RoboSecurity™

> RoboSecurity (robosecurity.io) is a robot and OT cybersecurity service run by 2Secure Corp. It finds, contains and closes cyber attack paths into industrial robots, collaborative robots (cobots), autonomous mobile robot (AMR) fleets and the plant networks around them. On-site service across New Jersey and New York; remote assessments and incident triage nationwide.

- Robot incident line (24/7): +1 646-560-5083
- Email: robotics@2securecorp.com
- Parent company: 2Secure Corp, https://2securecorp.com/
- Service area: New Jersey and New York on-site; United States remote
- Who it is for: manufacturers, warehouses and distribution centers running robots; robot integrators and OEMs

## Services

- [Robot incident response](https://robosecurity.io/#services): 24/7. Remote triage within 60 minutes, on-site containment in NJ/NY without unsafe stops, forensics on controller logs and programs, recovery to production. Billed hourly or on retainer.
- [Robot exposure assessment](https://robosecurity.io/#services): fixed scope, typically 1–3 weeks per site. Inventory of every robot, controller, pendant and fleet manager; mapping of network paths from IT, Wi-Fi and vendors; passive-first testing scheduled around production; ranked findings mapped to IEC 62443 and NIST SP 800-82; executive summary for insurers and auditors.
- [Hardening and monitoring](https://robosecurity.io/#services): monthly per-site subscription. Cell segmentation and firewall rules, brokered time-limited recorded vendor remote access, patch tracking against robot vendor advisories, alerts on new devices and program changes, quarterly review and tabletop exercise.

## Robot attack surface covered

- Robot controllers and teach pendants: exposed service ports (for example cobot dashboard server tcp/29999 and real-time interfaces tcp/30001–30003), outdated firmware, unlogged USB program loads
- ROS and ROS 2: DDS traffic without authentication by default (no SROS2), discovery on udp/7400–7500, writable topics such as /cmd_vel
- AMR fleet managers: default web logins, shared Wi-Fi, mission and map tampering
- Vendor and integrator remote access: always-on remote desktop tools, shared accounts, no MFA
- PLCs, HMIs and safety interlocks: flat networks, Modbus and EtherNet/IP exposed to the plant floor
- Vision and AI models in pick-and-place: adversarial inputs, model file tampering

## How testing stays safe

1. Inventory with the site maintenance lead
2. Passive traffic capture to map real network paths
3. Active tests only in agreed windows, cell in a safe state, operator at the e-stop
4. Fixes applied with the integrator, then re-tested
RoboSecurity never sends motion commands to a robot during production.

## Standards and regulations mapped

- IEC 62443 (including 62443-4-2 component requirements)
- ISO 10218-1 and ISO 10218-2 (2025 revision)
- NIST SP 800-82 Rev. 3
- EU Cyber Resilience Act: vulnerability reporting from 11 Sept 2026; full requirements from 11 Dec 2027
- EU Machinery Regulation 2023/1230: applies from 20 Jan 2027
- CISA ICS advisories for robot vendors

## FAQ

- Can industrial robots be hacked? Yes. Entry points include exposed controller 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.
- Is it safe to test robots in a working plant? Yes, when planned around safety: passive first, active tests in agreed windows with the cell safe and an operator at the e-stop.
- How long is an assessment? Typically 1–3 weeks per site.
- What to do in a suspected compromise? Put the cell in a safe state, do not power-cycle the controller or wipe programs, disconnect vendor remote access, call 646-560-5083.

## Optional

- [Home page](https://robosecurity.io/)
- [2Secure Corp](https://2securecorp.com/)
- [Sitemap](https://robosecurity.io/sitemap.xml)

## Legal

- © 2026 2Secure Corp. All rights reserved.
- RoboSecurity™ is a trademark of 2Secure Corp.
- [Privacy policy](https://robosecurity.io/privacy/)
- [Terms of use](https://robosecurity.io/terms/)