808bits

Mocana Cryptographic Loadable Kernel Module

FIPS 140-2 certificate #3191 · Mocana Corporation · data as of 2026-10-21

Mocana Cryptographic Loadable Kernel Module, from Mocana Corporation, holds FIPS 140-2 certificate #3191 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. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys

Certificate

Certificate number3191
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorMocana Corporation · website
Software versions6.5.1f

Module description

Quoted from the NIST CMVP entry for this certificate.

The Mocana Cryptographic Loadable Kernel Module (Software Version 6.5.1f) 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
AES5252, 5253, 5254
DRBG2009
HMAC3478
SHS4229
Triple-DES2658

Tested configurations

  • Wind River Linux 6.0 running on a Xerox Explorer 6.0 with an Intel Atom E3800 CPU
  • Wind River Linux 9.0 (64-bit) on a Xerox Explorer 6.5 with an Intel Atom E3900 CPU (single-user mode)

Validation history

DateTypeLab
2018-06-06InitialUL Verification Services, Inc.
2019-07-26UpdateUL 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
  • Validation dates on record: 2018-06-06, 2019-07-26

Source documents