808bits

IBM LTO Generation 5 Encrypting Tape Drive

FIPS 140-2 certificate #1522 · IBM® Corporation · data as of 2026-10-21

IBM LTO Generation 5 Encrypting Tape Drive, from IBM® Corporation, holds FIPS 140-2 certificate #1522 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1522
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Hardware versions45E8192 EC Level M11221 (Fibre Channel) and 45E8193 EC Level M11221 (SAS)
Firmware versionspf100923e.A9Q5.FC.fips.ro (Fibre Channel) and pf100923e.A9Q5.SAS.fips.ro (SAS)

Module description

Quoted from the NIST CMVP entry for this certificate.

The IBM LTO Generation 5 Encrypting Tape Drive provides AES-GCM encryption of customer data recorded to tape. Both encryption and compression are implemented in the hardware for optimum performance. Two different host interface types of the LTO Generation 5 "brick" unit are FIPS certified as a multi-chip, standalone cryptographic module. In customer operation the "brick" unit may be embedded in bridge box or in a canister package for operation in a library.

Approved algorithms (4)

AlgorithmCAVP certificates
AES1530, 1531, 1532
RNG825
RSA744
SHS1361

Other algorithms

AES (Cert. #1530, key wrapping; key establishment methodology provides 256-bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Validation history

DateTypeLab
2011-03-23InitialSAIC-VA

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2011-03-23

Source documents