808bits

SUSE Linux Enterprise Server Kernel Crypto API Cryptographic Module

FIPS 140-2 certificate #4508 · SUSE, LLC · data as of 2026-10-21

SUSE Linux Enterprise Server Kernel Crypto API Cryptographic Module, from SUSE, LLC, holds FIPS 140-2 certificate #4508 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in section 10.1 of the Security Policy

Certificate

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

Module description

Quoted from the NIST CMVP entry for this certificate.

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 (8)

AlgorithmCAVP certificates
AESA53, A54, A55, A57, A58, A59, A60, A61, A63, A66, A68, A69, A70, A71, A72
DRBGA53, A57, A58, A60, A62, A66, A73, A74
HMACA56, A62, A66, A73, A74
KTS
RSAA62, A66, A73, A74
SHA-3A56
SHSA62, A65, A66, A73, A74
Triple-DESA57, A66, A67

Allowed algorithms

NDRNG

Tested configurations

  • SUSE Linux Enterprise Server 15 SP0 running on Dell EMC PowerEdge 640 with Intel Cascade Lake Xeon Gold 6234 with PAA
  • SUSE Linux Enterprise Server 15 SP0 running on Dell EMC PowerEdge 640 with Intel Cascade Lake Xeon Gold 6234 without PAA (single-user mode)

Validation history

DateTypeLab
2023-05-05Initialatsec 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: 2023-05-05

Source documents