FilingCloud Cryptographic Module
FilingCloud Cryptographic Module, from FilingCloud, holds FIPS 140-2 certificate #4122 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. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3273
Certificate
| Certificate number | 4122 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | FilingCloud · website |
| Software versions | 2.2 |
Module description
Quoted from the NIST CMVP entry for this certificate.
FilingCloud Cryptographic Module is a standards-based, drop-in compliant cryptographic engine for servers, PCs, network appliances, mobile devices, and other deployments. The module delivers core cryptographic functions and features robust algorithm support, including Suite B algorithms. FilingCloud Cryptographic Module offloads secure key management, data integrity, data at rest encryption, and secure communications to a trusted implementation.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4750 |
| CKG | vendor affirmed |
| DRBG | 1631 |
| DSA | 1273 |
| ECDSA | 1185 |
| HMAC | 3164 |
| RSA | 2594 |
| SHS | 3893 |
| Triple-DES | 2524 |
Tested configurations
- CentOS 7.3 running on a Dell Optiplex 755 with an Intel Celeron 430 processor (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-01-03 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
| 2022-01-07 | Update | Leidos Accredited Testing & Evaluation (AT&E) Lab |
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: 2022-01-03, 2022-01-07