SecureParser®
SecureParser®, from Security First Corp., holds FIPS 140-2 certificate #1180 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
Certificate
| Certificate number | 1180 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software-Hybrid |
| Embodiment | Multi-chip standalone |
| Vendor | Security First Corp. · website |
| Software versions | 4.7.0 |
| Hardware versions | P/N AC2020-S, Version 1.0 |
| Firmware versions | 1.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The SecureParser® is a security and high data availability architecture delivered in the form of a software toolkit that provides cryptographic data splitting (data encryption, random or deterministic distribution to multiple shares including additional fault tolerant bits, key splitting, authentication, integrity, share reassembly, key restoration and decryption) of arbitrary data. During the split process, additional redundant data may be optionally written to each share enabling the capability of restoring the original data when all shares are not available.
Security level exceptions
- Cryptographic Module Specification: Level 3
- Cryptographic Key Management: Level 3
- EMI/EMC: Level 3
- Design Assurance: Level 3
Approved algorithms (7)
Other algorithms
RSA (key wrapping; key establishment methodology provides 128 bits of encryption strength); AES (Cert. #1027, key wrapping; key establishment methodology provides 128, 192, or 256 bits of encryption strength)
Tested configurations
- Ubuntu 8
- Windows 2003 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2009-08-31 | Initial | 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: 2009-08-31