Why it matters
Automation adds networked controllers, fleet managers, and vendor connections to the operation. Each one is a system to secure, update, and recover.
Most automation also needs ongoing remote support from its supplier. How that access is granted, limited, and recorded is a design decision, and it is easier to make before deployment than after.
What can go wrong
- Automation equipment sits on the same network segment as office systems, so a problem in one reaches the other.
- Vendor remote access uses a shared account or an always-on connection that nobody monitors.
- Software updates are applied by the vendor without notice, or are never applied at all.
- Controller programs and fleet configurations have no tested backup, so recovery depends on the vendor’s schedule.
- Operational or product data flows to a vendor cloud under terms nobody reviewed.
What evidence to examine
| Evidence | What it can establish |
|---|---|
| Network architecture diagram showing zones and connections | Whether IT and OT are separated, and where they connect |
| Asset inventory for automation and control systems | What must be secured and maintained |
| Vendor remote-access method, sign-off records, and session logs | Whether external access is controlled and traceable |
| Account and identity records, including shared and service accounts | Who can do what, and whether access is individual |
| Patch and update policy with named owners | How changes reach production equipment |
| Logging and monitoring coverage | Whether abnormal activity would be noticed |
| Backup records and restore test results | Whether recovery has been demonstrated |
| Data-flow records and contract terms for vendor-hosted services | Where proprietary data goes, and under what conditions |
Warning signs
- IT learns about the automation project after the vendor is selected.
- The vendor’s support model assumes a permanent connection into the facility.
- Nobody can produce a current list of who has remote access.
- Recovery plans cover business systems but not controllers or fleet managers.
What to do next
- Define the remote-access architecture and include it in the vendor requirements.
- Decide where automation sits in the network, and what it is allowed to reach.
- Agree who signs off updates, who holds backups, and how a restore is tested.
NIST SP 800-82 Rev. 3 is a freely available reference for securing operational technology. Safety standards are also moving in this direction. According to ANSI’s summary, the 2025 edition of ISO 10218-1 added cybersecurity requirements where they bear on industrial robot safety.