Air gap definition
An air gap is a boundary where two systems are not connected physically and no logical connection between them is automated. The definition used by the US Committee on National Security Systems, taken from the internet security glossary RFC 4949, says data crosses the interface only manually, under human control.
Both halves matter. Unplugging a cable is not enough if a wireless link, a cellular modem or a remote-management chip still connects the system to something else. And a system with no cable but an automatic sync job is not air-gapped either. The test is whether any data can cross without a person deciding to carry it.
Air gaps are used where the cost of compromise is very high, such as some industrial control networks and offline backups that ransomware must not reach.
Local network vs air gap
A local network is not an air gap. It is a set of devices that talk to each other automatically over a shared link such as Wi-Fi, Ethernet or Bluetooth LE. That automatic exchange is exactly what an air gap rules out. And many local networks also have a route to the internet, through a router or through devices that carry their own cellular connection.
There are three different things people mean:
| Design | Automatic exchange inside | Path to the internet | What crosses the boundary |
|---|---|---|---|
| Air gap | Possibly, inside each side | None | Only what a person carries |
| Local network with one narrow gateway | Yes | One gateway | A defined set of messages through one controlled point |
| Ordinary connected network | Yes | Every device, or a router open to all | Anything any device chooses to send |
The middle row is the one most organisations can actually run, and it keeps most of what makes an air gap valuable.
Single-gateway local network as an airlock
A local network with one gateway works like an airlock because nothing inside is reachable from the internet, and everything that does cross passes one point you control. An airlock does not seal a space off; it lets things through in a narrow, deliberate way. A local network with one gateway does the same for data.
- Nothing to scan from outside. Devices on the local network have no public address, so internet-wide scanning, the method the Mirai botnet used, finds nothing.
- One controlled crossing. NIST’s control SC-7(3) asks for fewer external connections so traffic is easier to monitor. With one gateway there is one to watch.
- Data still moves. Devices coordinate among themselves automatically, and the gateway carries reports, updates and messages out on its own, without a person walking a USB stick across a room.
- The site keeps working when the link is cut. If devices coordinate locally, losing the gateway pauses only what has to leave.
CISA’s guidance for operational technology describes the same structure: remove OT connections to the public internet, and segment IT from OT with a demilitarised zone for passing control data out.
True air gap use cases
Use a true air gap when a system can live with manual transfer and the damage from compromise would be severe. Offline backups are the clearest case: a copy that no automated process can reach is a copy ransomware cannot encrypt. Some safety systems and signing keys belong behind one too.
Use the narrow-gateway design when devices need to coordinate continuously and data needs to leave without someone carrying it. Field fleets, warehouses, vehicles, clinics and factories usually fall here. The rule of thumb is to air-gap the few things that can tolerate it, and put everything else behind one narrow door rather than leaving each device on the internet.
Offline Protocol airlock design
Offline Protocol builds the inside of the airlock. Devices discover, verify and message each other over Bluetooth LE, Wi-Fi Direct, the local Wi-Fi network and local IP, with Ed25519 keys generated on each device and MLS end-to-end encryption for every session. A local mesh needs no portal account, no API key and no internet. Shared state syncs between devices as replicated documents that merge when peers reconnect, so a site keeps one picture of its work without a server.
The door is a gateway you provision against a defined contract covering identity, delivery verdicts and recovery. The docs also give the test for whether a design really is local: switching off the internet proves cloud independence only if the path that remains actually carries the workflow, so you check the observed path, not just the setting.