Inspect a warehouse robot fleet in this order: what exists, how it connects, who can reach it remotely, and what software it runs. Safety behavior comes with the machine, so your first job is the cyber side: inventory, network separation, vendor access and update paths. Public OT guidance supports each step.
What are you actually defending?
A robot fleet is more than robots. It usually includes the machines, a fleet manager or control server, a warehouse management system that sends tasks, wireless networks, charging stations, sensors, cameras and vendor support tools. NIST SP 800-82 Revision 3 frames operational technology as programmable systems and devices that interact with the physical environment, and covers typical system layouts, common threats and vulnerabilities, and recommended countermeasures. Treat your fleet as one of those systems.
We are not describing any specific incident. This is an inspection order, not a story of attacks.
Which standards give you a vocabulary?
The ISA/IEC 62443 series addresses cybersecurity for industrial automation and control systems. ISA describes parts for general concepts, policies and procedures, system requirements and component requirements, and names stakeholder groups: asset owners, integrators, product suppliers and service providers. That map is useful for a warehouse. As the owner you hold some duties. The robot maker and the integrator who installed it hold others. Part 2-4 covers security program requirements for service providers, part 3-2 security risk assessment for system design, and part 4-1 secure product development lifecycle requirements for suppliers.
CISA's industrial control systems pages add advisories, role-specific pages for asset owners, integrators and vendors, and guidance such as zero trust approaches for OT.
The inspection order
1. Inventory. Every robot, controller, server, access point and vendor tool, with model, firmware version, owner and location.
2. Network paths. Which networks do robots and the fleet server sit on? Can they reach the corporate network, the internet or each other? The aim is separation, so a compromised office laptop does not reach a robot controller.
3. Remote access. Vendors often connect for support. Find every remote path, who holds credentials, whether multi-factor authentication is on, and whether access is time limited and logged.
4. Software and firmware. What runs on each device, and can the vendor give you a list of components? An SBOM from the supplier lets you check new advisories against what you actually run.
5. Updates. How does firmware get updated, who approves it, and is the update signed? Can you test before rolling out to the floor?
6. Credentials. Change default passwords, remove shared accounts and store service credentials properly.
7. Monitoring. Do you log fleet server and remote access events, and does anyone look?
8. Recovery. If the fleet manager fails, what do operators do? Practice the manual fallback, with safety staff involved.
What to ask suppliers
Ask whether they follow a secure development lifecycle, how they handle vulnerability reports, how long they support a model with patches, and whether they provide a component list. IEC 62443 part 4-1 is a reasonable reference for the first question.
What to do
- Build the inventory and assign an owner to each item.
- Draw the network map and mark every path between robots, the fleet server, office networks and the internet.
- List all vendor remote access and require multi-factor authentication and logging.
- Request component lists and patch policies from each supplier.
- Define a tested process for firmware updates.
- Replace default and shared credentials.
- Turn on logging for the fleet server and remote access, and review it weekly.
- Run a tabletop with operations and safety staff on the manual fallback.
- Involve safety engineers before any change touching robot behavior.
Quick check
Should I patch robots as soon as an advisory appears?
Not blindly. Test first and coordinate with safety staff and the vendor, since updates can affect machine behavior. Reduce exposure meanwhile through network separation and tighter remote access.
Whose job is robot security, mine or the manufacturer's?
Both, and the integrator's too. IEC 62443 splits duties across asset owners, integrators and product suppliers, so write down who owns each task.
Sources
- NIST SP 800-82 Rev. 3, Guide to Operational Technology Security, fetched 18 October 2026.
- ISA: ISA/IEC 62443 series of standards, fetched 18 October 2026.
- CISA: Industrial control systems, fetched 18 October 2026.
Last reviewed: 18 October 2026.
