AI and network security

What is an air gap, and is a local network the same thing?

An air gap is a boundary between two systems with no physical connection and no automated logical one, so data crosses only by hand, under human control. A local network is not an air gap, because devices on it can still exchange data automatically and may reach the internet through a gateway. A local network with one narrow gateway works like an airlock instead, keeping most of an air gap's protection while data still moves on its own.

TL;DR

An air gap means no physical or automated connection, so every transfer is a person carrying data. A local network is not an air gap, but one whose devices reach the internet only through one narrow gateway gets close. Air-gap the few systems that can live with manual transfer, and use the gateway airlock where data must move.

Learning objectives

After reading this article you will be able to:

  • Define an air gap using the CNSSI and RFC 4949 wording
  • Distinguish an air gap from a local network and from a local network with one gateway
  • Choose between an air gap and a narrow-gateway design for a given system

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:

DesignAutomatic exchange insidePath to the internetWhat crosses the boundary
Air gapPossibly, inside each sideNoneOnly what a person carries
Local network with one narrow gatewayYesOne gatewayA defined set of messages through one controlled point
Ordinary connected networkYesEvery device, or a router open to allAnything 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.

Frequently asked questions

Is a network with no internet connection air-gapped?

Not by the strict definition. If devices on it exchange data automatically with each other, or if any of them also has a cellular or Wi-Fi link to the outside, there is an automated connection. It is an isolated network, which is useful, but the air gap is the boundary where only manual transfer crosses.

Can an air gap be crossed?

Yes, through the manual transfer it allows. By definition data crosses only by hand, so the removable media, laptops and people who carry it are the path in, and they need their own controls.

Why not air-gap everything?

Because every transfer then needs a person. Updates, reports and coordination with other sites all become manual work, which is slow and often leads people to add an unofficial connection that undoes the gap.

Is a gateway a weaker boundary than an air gap?

Yes, because data crosses it automatically. It is a far stronger boundary than an internet connection on every device, though, since nothing behind it is reachable from outside and everything that crosses passes one point that can be filtered and watched.

Does a phone on a local mesh count as isolated?

Only for the workflow that runs on the mesh. The phone itself may still have cellular data, so the boundary you can rely on is the application's: which paths its traffic is allowed to take.

Sources

Build it with Offline Protocol

The transport and routing docs list the local paths Offline Protocol devices use, explain how a gateway is provisioned, and say how to test that a workflow really runs with the internet switched off.

Read the transport and routing docs