How the Two Worlds Drifted Together

There are two computing worlds inside any facility that does physical work, and understanding why they were kept apart — and how they stopped being apart — is the spine of this module.

The first world is business information technology, or IT. Email, spreadsheets, the enterprise applications that schedule work and send invoices, the laptops and servers of ordinary office life. Its job is information, and its instinct is connection: IT wants to reach everything, update constantly, and expose services so people can use them from anywhere. Its failure mode is inconvenience. When IT breaks, work stops, money is lost, tempers fray — but the physical world keeps spinning.

The second world is operational technology, or OT: the computers that touch physical reality. The controllers that open valves, run pumps, spin turbines, and hold a cooling loop at temperature. In a data center this is the building-management and industrial-control layer — the systems that keep power flowing and heat moving so the servers don't cook. OT's job is not information; it is control, and its instinct is the opposite of IT's. It wants to be stable, predictable, and left alone. Its equipment lives for decades, runs software that cannot be casually patched, and treats every change as a risk. Its failure mode is not inconvenience. It is fire, flood, and things that spin coming apart.

Because these worlds have opposite instincts and opposite stakes, engineers historically kept them apart — an 'air gap,' the idea that the control network shares no connection with the business network or the internet. Malware on the office side literally could not reach the plant floor because there was no wire to carry it. The gap was a piece of topology doing the work of a wall.

And then the wall drifted away, not through a decision but through a thousand reasonable conveniences. This is the part worth slowing down for, because nobody ever approved 'connect our critical control systems to the internet.' What they approved was a series of individually sensible requests.

Management wanted visibility: let us see plant performance on the same dashboards as the rest of the business, so we can optimize. A wire goes in. Vendors wanted efficiency: let us monitor and update the equipment we sold you remotely, so we don't fly a technician out for every tweak. A remote-access path goes in. Operators wanted convenience during a hard week: let me check the system from home rather than driving in at 2 a.m. Another path. The IT department wanted the OT machines to receive security updates and antivirus signatures — a genuinely good idea — which requires those machines to reach a server, which requires a connection. Each request improves something real. Each one lays a plank across the moat.

Faraday's read: the air gap did not fail. It was never audited. It existed as a diagram and a belief, and the diagram stopped matching the building years before anyone checked. The gap eroded exactly the way a budget erodes or a schedule slips — never in one catastrophic move, always in small, defensible increments, each justified, until the sum is a thing no one would have approved as a whole. If you had proposed the final topology on day one, you'd have been laughed out of the room. Arrived at one exception at a time, it looks like progress.

The result is a class of facility whose security model describes a building that no longer exists. The staff still say 'the control network is isolated' because it was isolated when they learned the phrase. The reality is a control network reachable — through some chain of dashboards, jump boxes, vendor tunnels, and forgotten remote-access tools — from the same internet that carries the spam. The belief in isolation persists precisely because isolation used to be true, and beliefs are patched far less often than software.

The empiricist's response is not nostalgia for a purer past. The connections deliver real value; you are not going back to sneakernet. The response is honesty: know where your wires actually run, not where the old diagram says they run. Assume the gap is gone unless you can prove it is still there today, with a test, not a memory. In the next lesson we follow the consequence — how a compromise that lives entirely in the harmless-looking IT world can force the physical world to stop.