tape-encryption · shipping · also drive-based tape encryption, LTO encryption

Tape encryption

Tape encryption records selected data as ciphertext whose plaintext recovery requires the corresponding cryptographic key.

Related Observatory article: Read on hesela.com

Drive-based LTO encryption uses AES-256-GCM after compression. Encryption-capable LTO-4 drives already implemented it; LTO-5 is not the starting generation. The documented LTO-4 drive obtains its data key externally rather than storing that key on the cartridge. [5]

Encryption coverage is per recorded block, not a promise that every block on a cartridge is confidential. A 2011 LTO-5 interface supports mixed encrypted and unencrypted blocks. Its VCELB status flag indicates at least one encrypted logical block, not that all blocks are encrypted. Its RAW decryption mode can return ciphertext without decryption only when the block permits RAW reads; RAW reading is disabled by default. Reading ciphertext does not recover its plaintext. [7]

Key provision depends on the configured method. Application-managed encryption can obtain keys from the backup application without a separate encryption key server; system-managed and library-managed arrangements can rely on one. Recovery must preserve the applicable key source and the means to supply the correct key. [8]

Published performance claims include under 1% drive overhead and a 2007 library white paper's 5-10% degradation. The latter separately warns of capacity loss with small blocks or frequent key changes. These claims are not cross-system measurements. [4] [6]

Relations

related
Magnetic tape storage, LTO (Linear Tape-Open), Self-encrypting drive (SED), Air-gapped backup, XTS-AES, Authenticated encryption

Limitations

  • Loss of the only usable key can make intact encrypted records unrecoverable. [4]

Citations

  1. LTO Program. What is data encryption? (accessed 2026-11-21)
  2. NIST CMVP. FIPS 140-2 Security Policy 140sp1152, LTO Generation 4 encrypting tape drive. (accessed 2026-11-21)
  3. Dell. Library-Managed Encryption for Tape, LTO-4 white paper. (accessed 2026-11-21)
  4. HP LTO-5 Host Interface Guide, fifth edition (April 2011), pp. 202, 204, 206-207: encryption modes and RAW-read control (accessed 2026-11-21)
  5. IBM 3592 Tape Drives Operator Guide, GA32-0556-09 (November 2018), p. 4: application-managed encryption (accessed 2026-11-21)

Further reading

  1. Tape encryption (accessed 2026-03-26)
  2. IEEE 1619.1-2018. Standard for Authenticated Encryption with Length Expansion for Storage Devices. (accessed 2026-10-16)
  3. NIST SP 800-38D. Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC. November 2007. (accessed 2026-10-16)
Sources & caveats
  • The mixed-block and RAW-read behavior describes HP's LTO-5 interface, fifth edition (2011), not every tape drive or backup application's policy. [7]
  • IBM's 3592 guide supplies the application-managed counterexample to a mandatory separate key server. It is not an LTO drive specification. [8]
  • Historical LTO-4 encryption support is documented in the NIST-hosted IBM module security policy, version 3 revision 5. [5]
  • Performance figures are industry and product-document claims, not independent measurements. No tape hardware experiment was performed. [4] [6]
  • The IEEE standard was read only through its public page and scope.

JSON: /data/terms/tape-encryption.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Tape encryption. Hesela. 2026-11-21. https://hesela.dev/terms/tape-encryption/