How to centralise remote access: securing all access to your OT systems
What happened
The piece recommends centralising remote access to operational technology to reduce tool sprawl and the third‑party attack surface. It shows many organisations use multiple remote tools and links that tool sprawl to increased cyber incidents and slower governance. Watch whether procurement can mandate a single approved gateway or must manage supplier exceptions
Buyer takeaway
Require a central approved remote‑access method in RFx/LTSA or capture exceptions explicitly; otherwise suppliers will introduce tool and support costs
Cost / money
Undefined remote access can create recurring licence or support pass‑throughs; lock cost treatment in contract templates
Supplier / commercial
Suppliers with compatible gateway solutions will win on fit‑to‑scope; mandate proof of compatibility to avoid late change orders
Safety / operations
Controlled access improves incident traceability and response; include session logging and escalation paths in acceptance criteria
What to watch
Suppliers may resist single‑tool rules and propose their own appliances; require documented exceptions and sunset clauses
Key facts
- Most organisations have multiple remote access tools
- High proportion of cyber incidents involve third‑party access
- Maturity model spans do‑nothing to full centralised control
Source excerpts
Level 1: First-party access — Internal engineers use a centralised remote access tool
” Binding Agreements: “Remote Access is built into our contract
Tool sprawl like this translates to an expanded attack surface, so it’s no coincidence that 82% of organisations have experienced at least one cyber attack related to third-party access. And that’s only breaches from third-party remote access — not including internal engineers remotely accessing critical devices
