How do AI agents and robots change a construction site's threat model?

AI agents and robots turn a construction site into a place where software decisions move heavy equipment. The threat model grows in three ways: more networked devices on temporary networks, more data worth stealing, and software faults that can cause physical harm. Start by mapping assets, segmenting networks and fixing human stop points.

What is new compared with a conventional site?

A conventional site relies on people, paper and some connected tools. Add robots, drones, autonomous or remote-operated machines, and AI tools that schedule, order and plan, and four changes follow.

1. More connected devices. Each machine, tablet and sensor is a computer. CISA's drone guidance makes the point for unmanned aircraft: they are ICT devices that receive and transmit data, and every connection is a possible route for compromise.
2. Temporary, shared networks. Sites change weekly and host many contractors. Network boundaries are usually informal.
3. Valuable data. Site layouts, schedules, imagery and bids are information others want.
4. Software that can hurt people. NIST describes operational technology as systems that monitor or control physical processes, and notes that securing it must account for safety and reliability.

How do AI agents add risk on top of that?

An AI agent that can place orders, change schedules or call an equipment API holds permissions. OWASP's guidance on LLM applications recommends enforcing authorization outside the model and giving each agent only the privileges it needs. It also says a system prompt should not be treated as a secret or a security control. For a site, that means a scheduling agent should not hold the same credentials as the person who approves payments or machine commands.

NIST's AI Risk Management Framework, released January 2023, gives a common structure of Govern, Map, Measure and Manage. For a site, "Map" starts with an honest list of every AI tool and what it can touch.

Which standards are worth reading?

• NIST SP 800-82 Revision 3 covers OT security, including threats and countermeasures.
• ISA/IEC 62443 divides responsibility among asset owners, integrators and product suppliers, and part 4-1 covers a secure product development lifecycle.
• ISO 10218, the industrial robot safety standard, was revised in 2025 in two parts, one for manufacturers and one for integrators, and adds cybersecurity measures to the extent they bear on robot safety. It addresses industrial robots, so check whether a given site machine falls in its scope before citing it.

What does a sensible first threat model look like?

Draw four lists and one line.

• Assets: machines, controllers, drones, tablets, gateways, cloud accounts.
• Connections: who can reach each asset, and from where.
• Permissions: what each person and each AI agent can do.
• Failure effects: what happens physically if each fails or is manipulated.
• The line: which actions always need a human to confirm before they happen.

Then ask, for each asset, who supplies the software, how updates arrive, and whether the supplier gives you an SBOM.

What to do

1. Inventory every connected machine and AI tool on the site, including contractor equipment.
2. Put control and machine networks on a separate segment from office and guest access.
3. Give each AI agent its own limited credentials, and log what it does.
4. Define actions that require human approval, such as moving a machine near people.
5. Ask suppliers for an SBOM, update policy and vulnerability contact.
6. Rehearse a stop: how to halt every autonomous machine quickly.

Quick check

Sources

• CISA and FBI: Cybersecurity Guidance, Chinese-Manufactured UAS (PDF)
• NIST SP 800-82 Rev. 3, Guide to Operational Technology Security
• ISA: ISA/IEC 62443 series of standards
• Modern Materials Handling: ISO 10218 updates for 2025
• NIST: AI Risk Management Framework
• OWASP: LLM07:2025 System Prompt Leakage

Last reviewed: 18 October 2026.