AI Glossary / Data governance and quality / Advanced
Air gap (networking)
Definition
An air gap is a separation between systems without a direct physical connection or an automated logical data-transfer path across the boundary. The NIST glossary, drawing on RFC 4949, describes transfer across such an interface as manual and under human control. In networking discussions, the term indicates deliberate isolation. It should not be treated as a general guarantee that the isolated system is immune to every security problem.
What it means
A computer can run software and process local data without being connected to an external network. That arrangement changes how information, updates and results enter or leave. In an original AI evaluation example, a local model might analyze an approved dataset inside an isolated environment, with inputs and outputs moved through a separately controlled manual process. The isolation boundary must be defined explicitly. A firewall rule, a private network or a disabled internet browser is not automatically equivalent to an air gap, because other automated connections may still exist.
How it works
The design removes direct and automated communication paths across the specified boundary and defines how necessary transfers are handled. NIST and RFC 4949 provide the terminology rather than a complete operational design. In an original isolated AI workspace, the team would account for model files, software updates, input datasets and exported results. Each crossing needs an appropriate process. Local network connections within the isolated environment may exist, provided they do not create a path across the boundary being claimed. Manual transfer changes the route of information; it does not establish that the transferred content is trustworthy or appropriate.
Three practical examples
- A local AI evaluation environment processes approved files without a direct connection to external services.
- A research team plans controlled manual import of model updates into an isolated computing environment.
- An organization keeps a recovery copy disconnected during a defined interval and documents when any transfer occurs.
Think of it this way
Imagine a workshop with no conveyor belt connecting it to the neighboring building. Materials can still be carried through a controlled handover, but they do not move automatically between the two places. Removing the conveyor changes the connection; it does not inspect the contents of every delivered box. The analogy highlights why isolation and transfer quality are separate considerations, and why an undocumented temporary conveyor would change the claimed boundary.
Worked example
Consider an original fictional AI evaluation workspace that is separated from an external preparation system. In one week, staff manually import two approved input packages and one model-update package. They manually export one report package. There are four transfer events across the boundary: three inward and one outward. There are no automated network transfers between the systems under the example's assumptions. The four events are not evidence that zero information crossed; they document a controlled manual exchange. Now suppose a maintenance laptop connects to both environments and automatically synchronizes files between them. That creates an automated path inconsistent with the stated air-gap arrangement, even if the main evaluation server still lacks its own internet connection. The example counts events rather than files or bytes: one package may contain many files. It illustrates boundary accounting, not a quantitative estimate of security risk or proof that the four transfers were safe.
Illustrative case study
In a fictional AI testing project, the team describes its evaluation server as air-gapped because it cannot browse the web. A review of the full workflow finds an automated transfer through a maintenance device. The team removes that connection from the intended isolated workflow and documents a manual procedure for approved packages. It checks both inputs and exported reports according to the project's requirements and records model versions so results remain interpretable. The scenario illustrates verifying the actual boundary rather than relying on a label attached to one machine. It does not claim that removing the automated path eliminates every threat from software, removable media or authorized users.
Common misconceptions and mistakes
Air-gapped does not mean that no information can ever enter or leave. Manual transfers may be part of the arrangement. Another mistake is equating a firewall or network segmentation with the absence of an automated connection. The scope of isolation also matters: a server may be disconnected from one network while reachable through another path. Physical separation does not establish the correctness of local software or data. Finally, temporary maintenance connections and later reconnection can change the conditions under which an isolation claim was made. The claim needs to match the actual configuration and time period.
Business use
For an AI project considering isolation, identify the boundary and the workflow requirements in concrete terms. In the fictional evaluation workspace, model updates, inputs and outputs all need handling even without a live external connection. Plan how authorized staff obtain updates, track versions, verify transfers and recover from failures. Assess whether the required operational process is practical for the task. Document any changes to connectivity rather than assuming the original label remains accurate indefinitely. This supports a realistic understanding of what isolation achieves and what responsibilities remain within the environment and its transfer process.
People also ask
Is a computer behind a firewall necessarily air-gapped?
No. A firewall can regulate an existing connection rather than remove it.
Can an isolated environment contain its own local network?
Yes, if that network remains within the defined boundary and does not create an external automated path.
Does manual transfer guarantee safe content?
No. The transfer method and the trustworthiness of its content are separate questions.
Check your understanding
How many transfer events occur in the toy week?
Answer: Four.
How many are inward?
Answer: Three.
Does the absence of automated transfers mean no information crossed the boundary?
Answer: No.
Why does the synchronizing maintenance laptop change the claim?
Answer: It introduces an automated path between the environments.
Does the main server's inability to browse the internet prove isolation by itself?
Answer: No; other connections must be considered.
Related terms
- Firewall (computing)
- Network isolation
- network segmentation
- firewall
- removable media
- offline processing
- controlled transfer
Learn next
Draw an isolated AI workflow with its input preparation, local processing and report export. Mark every path that crosses the claimed boundary, including maintenance devices and updates. Distinguish manual from automated transfers and explain how a temporary connection would change the description of the environment.
More in Data governance and quality
- Access Control - Access control is the process of permitting or denying access to resources according to defined rules.
- Adaptive redaction - Adaptive redaction is the policy-directed removal or replacement of selected sensitive content according to the circumstances of a communication or data use.
- Application firewall - An application firewall examines application-level communication and applies rules to permit or block traffic.
- Application security - Application security is the work of designing, building, testing, operating and maintaining applications to protect them against security failures and misuse.
- Backup validation - Backup validation is the process of checking whether a backup meets defined requirements for integrity, completeness and intended recovery use.
- Biometric tokenization - Biometric tokenization is a term used for authentication arrangements that combine biometric verification with a substitute digital credential or...
Sources
NIST Computer Security Resource Center, Air gap glossary: https://csrc.nist.gov/glossary/term/air_gap IETF, RFC 4949, Internet Security Glossary, Version 2, air gap entry: https://www.rfc-editor.org/rfc/rfc4949 The transfer counts, workshop analogy and AI evaluation scenario are original educational illustrations. The glossary definition is not a complete security architecture or evidence that an isolated system is invulnerable.