808bits

Mocana Cryptographic Loadable Kernel Module

FIPS 140-2 certificate #4298 · DigiCert, Inc. · data as of 2026-10-09

Mocana Cryptographic Loadable Kernel Module, from DigiCert, Inc., holds FIPS 140-2 certificate #4298 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.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys

Certificate

Certificate number4298
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDigiCert, Inc. · website
Software versions6.5.2f

Module description

Quoted from the NIST CMVP entry for this certificate.

The Mocana Cryptographic Loadable Kernel Module (Software Version 6.5.2f) is a software only, multi-chip standalone cryptographic module that runs on a general purpose computer. The primary purpose of this module is to provide FIPS Approved cryptographic routines to consuming applications via an Application Programming Interface.

Security level exceptions

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

Approved algorithms (5)

AlgorithmCAVP certificates
AESA661, A662, A663, C1810, C1811, C1812
DRBGA661, C1810
HMACA661, C1810
SHSA661, C1810
Triple-DESA661, C1810

Tested configurations

  • Wind River Linux 9.0 (64-bit) running on Xerox Explorer 6.5 with Intel Atom E3950 (single-user mode)

Validation history

DateTypeLab
2022-09-12InitialUL Verification Services, Inc.

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: 2022-09-12

Source documents