808bits

IBM System Storage LTO Ultrium 4 Tape Drive

FIPS 140-2 certificate #1152 · IBM® Corporation · data as of 2026-09-03

IBM System Storage LTO Ultrium 4 Tape Drive, from IBM® Corporation, holds FIPS 140-2 certificate #1152 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 number1152
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Hardware versions23R9539 (Fibre Channel), 23R9904 (SAS), and 95P4613 (SCSI)
Firmware versionsdf080911bf_89Bb.FC.fips.ro (Fibre Channel), df080911bf_89Bb.SAS.fips.ro (SAS), and df080911bf_89Bb.SCSI.fips.ro (SCSI)

Module description

Quoted from the NIST CMVP entry for this certificate.

The IBM LTO Ultrium 4 Tape Drive provides AES-GCM encryption of customer data recorded to tape. Both encryption and compression are implemented in the hardware for optimum performance. Three different host interface types of the LTO Ultrium 4 "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 (5)

AlgorithmCAVP certificates
AES918, 919
AES GCM918, 919
RNG527
RSA446
SHS906

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Validation history

DateTypeLab
2009-07-01InitialSAIC-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: 2009-07-01

Source documents