808bits

SUSE Linux Enterprise Server Libica Cryptographic Module

FIPS 140-2 certificate #4055 · SUSE, LLC · data as of 2026-09-12

SUSE Linux Enterprise Server Libica Cryptographic Module, from SUSE, LLC, holds FIPS 140-2 certificate #4055 at overall level 1. The validation is active, with a sunset date of 2026-09-21. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Active. Sunset date 2026-09-21, 8 days away. This is the FIPS 140-2 sunset: after it, agencies may keep the module only in existing systems.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Section 9.1 of the Security Policy with module SUSE Linux Enterprise Server OpenSSL Cryptographic Module validated to FIPS 140-2 under Cert. #3991 operating in FIPS mode

Certificate

Certificate number4055
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorSUSE, LLC · website
Software versions1.0
Hardware versionsIBM z15
Firmware versionsFeature Code 3863 (FC3863)

Module description

Quoted from the NIST CMVP entry for this certificate.

The SUSE Linux Enterprise Server Libica Cryptographic Module contains the interface library routines used by IBM modules to interface with OpenSSL and the IBM Central Processor Assist for Cryptographic Functions (CPACF).

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AESA389, A806
DRBGA491
ECDSAA360
HMACA360
KAS-SSCA684
RSAA360
SHA-3A389
SHSA389, A491
Triple-DESA389

Allowed algorithms

NDRNG

Tested configurations

  • SUSE Linux Enterprise Server 15 SP2 running on IBM System Z/15 with IBM z15 (single-user mode)

Validation history

DateTypeLab
2021-10-27Initialatsec information security corporation
2021-11-28Updateatsec 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 active
  • Validation dates on record: 2021-10-27, 2021-11-28

Source documents