808bits

Mocana Cryptographic Module

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

Mocana Cryptographic Module, from Mocana Corporation, holds FIPS 140-2 certificate #927 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number927
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMocana Corporation · website
Software versions3.06.1, 3.06.1a and 4.2f

Module description

Quoted from the NIST CMVP entry for this certificate.

The Mocana Cryptographic Module is used in conjunction with Mocana's scalable, high performance embedded security solutions. These include: Mocana EAP supplicant/authenticator, Mocana SSL/TLS Client & Server, Mocana SSH Client & Server and Mocana IPsec/IKE.

Approved algorithms (7)

AlgorithmCAVP certificates
AES665
DSA247
HMAC349
RNG384, 443
RSA308
SHS697
Triple-DES611

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Linux Kernel 2.6
  • uCLinux Kernel 2.4
  • VxWorks 5.5 (single-user mode)
  • Windows CE 4.2

Validation history

DateTypeLab
2008-03-14InitialUL Verification Services, Inc.
2008-05-08Update
2009-06-05Update
2009-11-20Update
2009-12-08Update

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: 2008-03-14, 2008-05-08, 2009-06-05, 2009-11-20, 2009-12-08

Source documents