808bits

SUSE Linux Enterprise Server - Kernel Crypto API Cryptographic Module

FIPS 140-2 certificate #3099 · SUSE, LLC · data as of 2026-08-28
Historical. Moved to historical list due to dependency on certificate #3038. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with module SUSE Linux Enterprise Server 12 - OpenSSL Module v2.0 validated to FIPS 140-2 under Cert. #3038 operating in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number3099
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSUSE, LLC · website
Software versions2.0

Module description

SUSE Linux Enterprise Server Kernel Crypto API Module provides cryptographic services to the Linux operating system kernel.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4608, 4609, 4610, 4611, 4612, 4613, 4614, 4615, 4616, 4617, 4618, 4672, 4673, 4674, 4675, 4677, 4678, 4679, 4681, 4682
DRBG1544, 1545, 1546, 1547, 1549, 1550, 1551, 1582, 1584, 1585, 1586
HMAC3042, 3043, 3044, 3045, 3054, 3056, 3057, 3058, 3059, 3060, 3097, 3098
KTS
RSA2513, 2515, 2516, 2517, 2554, 2555
SHS3768, 3769, 3770, 3771, 3782, 3784, 3785, 3786, 3787, 3788, 3789, 3832, 3833
Triple-DES2452, 2453, 2454, 2486, 2487, 2489

Allowed algorithms

NDRNG

Tested configurations

  • SLES12 operating on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure with PAA
  • SLES12 operating on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure without PAA
  • SLES12 operating on IBM z13 with PAI
  • SLES12 operating on IBM z13 without PAI (single-user mode)

Validation history

DateTypeLab
2018-01-02Initialatsec 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: 2018-01-02

Source documents