air-gap-backup · shipping

Air-gapped backup

An air-gapped backup is a recovery copy kept physically disconnected from the production system and its network while isolated.

Related Observatory article: Read on hesela.com

Isolation concerns the access path, not whether the saved state is correct. Offline copies reduce exposure to ransomware that reaches connected backups; encryption and recovery testing address different risks. [1]

An online retention policy is not physical disconnection. Object Lock protects selected object versions under specified retention and bypass rules, while the storage service remains reachable. [2]

Operational assessment: record when media is connected, which machine can write it, who controls transport and reconnection, and how recovery obtains keys and software. A scheduled connection is an exposure period to assess, not permanent isolation. Measure retrieval and restore time for the actual setup instead of assigning every offline copy a fixed speed. [5]

Physical custody differs from application-level isolation. A documented driveless logical library hides cartridges from backup applications and restricts retrieval to administrators with two-factor authentication. Another documented control, localSafeguarded, requires an on-site session to unassign protected cartridges. The management boundary matters: neither a simple firewall rule nor unrestricted remote reassignment describes every implementation. [6] [7]

WORM restricts alteration of recorded data; encryption restricts plaintext access; offline custody restricts electronic reachability while maintained. None guarantees the others. Library-managed encryption can require an available keystore during recovery; losing its keys prevents decryption. Preserve and test those dependencies independently of the production systems being recovered. [9] [8]

Relations

related
Magnetic tape storage, LTO (Linear Tape-Open), Cold archive tier, Storage immutability, WORM storage, Tape library, Tape encryption, Object storage, Storage snapshot, Backup verification, Restore test, Self-securing storage

Advantages

  • A disconnected copy removes the direct production-network write path during that interval. [1]

Limitations

  • Physical isolation does not certify a malware-free recovery point. [4]
  • A retained encrypted object may be unreadable after encryption-key deletion or loss of access. [3]
  • Reconnection and recovery require controlled procedures and separate acceptance checks. [1, 5]

Citations

  1. CISA et al.: #StopRansomware Guide, backup protection and recovery (accessed 2026-10-19)
  2. Amazon S3: Locking objects with Object Lock (accessed 2026-10-19)
  3. Amazon S3: Object Lock considerations, encryption-key dependency (accessed 2026-10-19)
  4. NIST SP 1800-11B: Data Integrity, sections 1.1-1.2 (accessed 2026-10-19)
  5. Hesela: Backup isolation and historical access (accessed 2026-10-19)
  6. IBM TS4300: safeguarded tape and driveless logical libraries (accessed 2026-10-25)
  7. IBM TS4500 1.12.3: logical-library localSafeguarded access restrictions (accessed 2026-10-18)
  8. IBM Security Guide for IBM i V6.1, pages 156-161: encrypted-tape recovery and key-manager dependencies (accessed 2026-10-18)
  9. IBM z/OS 3.1: Write Once Read Many (WORM) (accessed 2026-10-25)
Sources & caveats
  • The library examples describe IBM TS4300 driveless logical libraries and IBM TS4500 1.12.3 localSafeguarded behavior; protections depend on the deployed implementation and configuration. [6] [7]

JSON: /data/terms/air-gap-backup.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Air-gapped backup. Hesela. 2026-10-25. https://hesela.dev/terms/air-gap-backup/