Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:a:air_gap [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:a:air_gap [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Air Gap ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Air Gap separates systems, networks, or operating environments by preventing direct electronic communication across a defined boundary. | ||
| + | |||
| + | The separation protects a [[public: | ||
| + | |||
| + | An Air Gap represents a controlled communication boundary rather than an absence of all information transfer. Organizations transfer information across the boundary through approved physical media, transfer devices, gateways, review processes, or other controlled mechanisms. | ||
| + | |||
| + | The effectiveness of an Air Gap depends on the technical controls, physical controls, operating procedures, personnel responsibilities, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalised from cybersecurity, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Air Gap identifies the separation between environments. An [[private: | ||
| + | |||
| + | A controlled transfer across an Air Gap does not remove the Air Gap when the transfer process preserves the defined separation and governance controls. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A connected build environment exports an approved transfer bundle to controlled media. Personnel inspect and transfer the media across an Air Gap before importing the bundle into a disconnected enclave. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||