808bits

IBM® z/VM® Version 6 Release 4 System SSL Cryptographic Module

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

IBM® z/VM® Version 6 Release 4 System SSL Cryptographic Module, from IBM Corporation, holds FIPS 140-2 certificate #3374 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number3374
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorIBM Corporation · website
Software versions5735FAL00: z/VM Version 6 Release 4 with 1701RSU and APAR PI99134
Hardware versionsz13 CP Assist for Cryptographic Functions DES/TDES Enablement Feature 3863

Module description

Quoted from the NIST CMVP entry for this certificate.

z/VM System SSL provides cryptographic functions which allows z/VM to protect data using the SSL/TLS protocols. z/VM System SSL also enables administrators to create and manage X.509 V3 certificates and keys within key database files.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES4579, 5553
CVL1989, 1990
DRBG2208
DSA1427
HMAC3701
RSA2983
SHS3661, 4456
Triple-DES2432, 2794

Allowed algorithms

HMAC-MD5; MD5; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)

Tested configurations

  • IBM z/VM Version 6 Release 4 running on an IBM z13 with CP Assist for Cryptographic Functions (single-user mode)

Validation history

DateTypeLab
2019-02-19Initialatsec information security corporation

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: 2019-02-19

Source documents