SUSE Linux Enterprise Server Libica Cryptographic Module
SUSE Linux Enterprise Server Libica Cryptographic Module, from SUSE, LLC, holds FIPS 140-2 certificate #4055 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
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 number | 4055 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software-Hybrid |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | SUSE, LLC · website |
| Software versions | 1.0 |
| Hardware versions | IBM z15 |
| Firmware versions | Feature 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)
| Algorithm | CAVP certificates |
|---|---|
| AES | A389, A806 |
| DRBG | A491 |
| ECDSA | A360 |
| HMAC | A360 |
| KAS-SSC | A684 |
| RSA | A360 |
| SHA-3 | A389 |
| SHS | A389, A491 |
| Triple-DES | A389 |
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
| Date | Type | Lab |
|---|---|---|
| 2021-10-27 | Initial | atsec information security corporation |
| 2021-11-28 | Update | atsec 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2021-10-27, 2021-11-28