Mocana Cryptographic Suite B Module
Mocana Cryptographic Suite B Module, from Mocana Corporation, holds FIPS 140-2 certificate #2045 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.
Certificate
| Certificate number | 2045 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Mocana Corporation · website |
| Software versions | 5.5fs |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Mocana Cryptographic Module is the engine of Mocana's Device Security Framework - a software framework that secures all aspects of a system. The Device Security Framework helps applications and device designers reduce development costs and dramatically enhance cryptographic performance. For details see www.mocana.com.
Approved algorithms (8)
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength)
Tested configurations
- Integrity O/S 5.0 running on Freescale MPC8544ADS Development System
- iOS-5 running on Apple iPad 2
- iOS-6 running on Apple iPad 2
- iOS-9.3 running on iPhone 5s (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-11-18 | Initial | UL Verification Services, Inc. |
| 2014-01-03 | Update | UL Verification Services, Inc. |
| 2016-04-14 | Update | UL Verification Services, Inc. |
| 2017-05-26 | Update | UL Verification Services, Inc. |
| 2018-05-16 | Update | UL 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: 2013-11-18, 2014-01-03, 2016-04-14, 2017-05-26, 2018-05-16