808bits

Unisys Linux Kernel Cryptographic API Module

FIPS 140-2 certificate #4068 · Unisys Corporation · data as of 2026-10-09

Unisys Linux Kernel Cryptographic API Module, from Unisys Corporation, holds FIPS 140-2 certificate #4068 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 dependency on certificate #3971. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with module Unisys Linux strongSwan Cryptographic Module validated to FIPS 140-2 under Cert. #3971 operating in FIPS mode

Certificate

Certificate number4068
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorUnisys Corporation · website
Software versions2.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The module is a software-only cryptographic module that comprises a set of Linux kernel modules; this set defines the module's cryptographic boundary. It provides cryptographic functionality for any application that calls into it.

Security level exceptions

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

Approved algorithms (6)

AlgorithmCAVP certificates
AESC873
CVLC1012
HMACC873
RSAC873
SHA-3C873
SHSC873

Tested configurations

  • Ubuntu 18.04 LTS server edition running on a Dell PowerEdge R640 Server with an Intel Xeon Gold 5115 with PAA
  • Ubuntu 18.04 LTS server edition running on a Dell PowerEdge R640 Server with an Intel Xeon Gold 5115 without PAA (single-user mode)

Validation history

DateTypeLab
2021-11-09InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2021-11-09

Source documents