A vulnerable dependency in an autonomous vehicle on a factory or warehouse floor matters in two ways: whether an attacker can reach it, and what the vehicle does if it fails or is patched. The answer decides whether you patch today, schedule a window or isolate the vehicle. Start with inventory and network reach.
Why is the shop floor different from a web app?
On a web server you patch, restart and watch dashboards. On a floor with automated guided vehicles or mobile robots, a restart can stop a line, a bad update can change motion behavior, and a failure can put people at risk. NIST SP 800-82 Rev. 3, the guide to OT security, says OT security has to account for performance, reliability and safety requirements. That is the constraint that makes patching a planned activity.
These vehicles also have layered software: a real time controller, a navigation stack, a fleet management client, an operating system and open source libraries. Most of that code is made by someone other than your vendor.
What does the supplier owe you?
ISA/IEC 62443 splits responsibility. Part 4-1 covers secure product development lifecycle requirements and Part 4-2 covers technical security requirements for components, aimed at product suppliers. Part 2-1 covers security program requirements for asset owners, and a technical report in the series covers patch management in these environments. In short, the supplier should build and disclose well, and you should run a program that accepts updates and tracks exposure.
Ask the supplier for a software bill of materials per software version, a vulnerability disclosure contact and a stated patch process. A list of components lets you match new advisories yourself instead of waiting for a letter.
How do you rank a finding on a moving machine?
Ask four questions in order.
- Is the vulnerable component actually present and used? Many listed components are linked but never called. Reachability analysis, or the supplier's statement, narrows the list.
- Can an attacker reach it? A flaw in a wireless interface or fleet API is different from one in a local diagnostic tool. Network segmentation changes the answer.
- Is it being exploited? Check CISA's Known Exploited Vulnerabilities catalog and EPSS. CISA describes the catalog as vulnerabilities exploited in the wild, and notes stakeholders must evaluate each asset's exposure.
- What is the safety effect of patching or not patching? Involve the safety engineer. A patch may require revalidation.
What about regulation?
Rules differ by use. Road vehicles fall under vehicle cybersecurity regulation, while automated guided vehicles inside a plant usually sit under machinery, workplace safety and OT security practice. We did not confirm the text of any vehicle regulation for this post, so ask your supplier and counsel which rules apply to your equipment instead of assuming.
What can go wrong with the SBOM approach?
Component lists go stale, and firmware images sometimes bundle code the vendor cannot fully enumerate. If the SBOM is incomplete, ask what is missing instead of treating the list as final.
What to do
- List every autonomous vehicle, its software version, owner and network connections.
- Collect an SBOM and a patch policy from each supplier.
- Put vehicle control networks behind segmentation and restrict who can reach fleet management.
- Match new advisories to your inventory weekly; use exploit data to rank.
- Agree a change process with safety engineering for patches, including test in a spare unit.
- Keep a rollback plan and a manual operating mode for each vehicle class.
- Run a drill: pick a library and time how long it takes to list affected vehicles.
Safeguard can ingest SBOMs and help you match advisories with reachability signals, but patch approval on a safety system remains a decision for your safety team.
Quick check
Should I patch every vehicle immediately?
Not automatically. Rank by exposure and exploit data, then patch inside a safety approved process.
Is an SBOM from the supplier enough?
It is a start. You still need matching, ranking and a patch process.
Sources
Last reviewed: 18 October 2026.
