Join our Newsletter — 33% off our NHI Course

Why do routine SCADA maintenance paths break air gaps?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Routine SCADA isolation is often undone by USB media, vendor laptops, hidden bridges, contaminated devices and side-channel paths, according to Asimily. Industrial operators need visibility into every device and crossing so maintenance does not reopen access.

Editorial analysis by NHI Mgmt Group, based on content published by Asimily: “Mind the Gap: Why Your “Air-Gapped” SCADA System Is a Myth”.

Key questions

Q: Why do removable media and vendor devices create such a high-risk OT exposure?

A: They create high risk because they bring outside trust into a control environment that was designed to assume very limited change.

Q: What are the signs that an air gap is failing in practice?

A: Look for dual-homed workstations, unexplained modem links, ad hoc vendor access, inconsistent device baselines and traffic that does not match the approved protocol profile.

Q: What breaks when an air-gapped SCADA environment relies on normal maintenance workflows?

A: The isolation claim breaks when routine maintenance depends on removable media, vendor laptops or bridged connections that are not governed as privileged access paths.

Practitioner guidance

  • Inventory every crossing point into the OT boundary Map USB handling, vendor laptops, remote maintenance links, dual-homed workstations and cellular modems as explicit ingress paths, then assign an owner to each one.
  • Restrict removable media to approved transfer workflows Require scanning, validation and documented approval before any firmware, logic file or log export is introduced into a control environment.
  • Baseline every device before trusting it on the segment Capture known-good device behavior, protocol use and configuration state so deviations from expected OT activity surface quickly during operations.

Bottom line: Air-gapped SCADA fails most often through routine operational exceptions, not through headline remote exploits.

Glossary terms: Air-Gap Drift, Shadow Connection, Configuration Control, Behavioural Baselining

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Air-gap theory fails when operational convenience becomes a control path. The article is right to frame isolation as something that erodes through routine business and engineering decisions, not only through exotic exploits. In OT environments, the practical question is who can move data, devices or configuration changes across the boundary and under what approval model. That makes the problem a governance failure as much as a network design issue. Practitioners should treat every exception as part of the control surface, not as an operational footnote.

A question worth separating out:

Q: How should industrial teams govern remote maintenance without weakening segmentation?

A: They should confine maintenance access to the exact devices, protocols and destinations required for the job, then verify that the access path ends when the task ends. That means device profiling, least-privilege network rules and explicit approval for every crossing point. The goal is not to ban maintenance, but to ensure it cannot silently become general-purpose connectivity.

👉 Read our full editorial: Air gaps fail when operational reality creates hidden OT paths


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.