FIPS Crypto Module
FIPS Crypto Module, from Ionic Security Inc., holds FIPS 140-2 certificate #2761 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.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Section 3 of the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy
Certificate
| Certificate number | 2761 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Ionic Security Inc. · website |
| Software versions | 1.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Ionic Security’s Fusion Platform implements the FIPS Crypto Module for all cryptographic functions such as key pair generation, digital signature generation/ and verification, encryption and decryption, hashing functions, and message authentication.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (6)
Other algorithms
RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength)
Tested configurations
- CentOS 7.1 running on an Intel Server System R1304GZ4GC (single-user mode)
- Windows 7 SP1 running on a Hewlett-Packard (HP) Z230 desktop
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-09-27 | Initial | CGI Information Systems & Management Consultants 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: 2016-09-27