Primus HSM
Primus HSM, from Securosys SA, holds FIPS 140-2 certificate #3430 at overall level 3. 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 as specified in the Security Policy
Certificate
| Certificate number | 3430 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Securosys SA · website |
| Hardware versions | P/Ns E20 / 60-1004 Rev0, E60 / 60-1004 Rev0, E150 / 60-1004 Rev0, EP700 / 60-1008 Rev0, X200 / 60-1002 Rev1, X400 / 60-1002 Rev1, X700 / 60-1002 Rev1 and X1000 / 60-1010 Rev1 |
| Firmware versions | 2.5.3 and 2.5.13 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Securosys' Primus series of hardware security modules (HSM) provide high performance cryptographic operations, creation, storage, and controlled access to encryption keys and certificates in an always active tamper protected appliance. Applications include digital signatures for financial transactions, secure messaging and email, blockchain, crypto currency and crypto asset storage, PKI, elDAS, database and cloud encryption, GDPR, SSL / TLS, and e-government.
Approved algorithms (14)
| Algorithm | CAVP certificates |
|---|---|
| AES | 5485 |
| CKG | vendor affirmed |
| CVL | 1938, 1939, 1940, 1941 |
| DRBG | 2160 |
| DSA | 1412 |
| ECDSA | 1471 |
| HMAC | 3643 |
| KAS | 184 |
| KBKDF | 226 |
| KTS | vendor affirmed |
| RSA | 2946 |
| SHA-3 | 48 |
| SHS | 4402 |
| Triple-DES | 2762 |
Allowed algorithms
NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2019-04-04 | Initial | UL Verification Services, Inc. |
| 2019-12-23 | 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: 2019-04-04, 2019-12-23