808bits

Primus HSM

FIPS 140-2 certificate #3430 · Securosys SA · data as of 2026-09-13

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.

Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode as specified in the Security Policy

Certificate

Certificate number3430
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorSecurosys SA · website
Hardware versionsP/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 versions2.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)

AlgorithmCAVP certificates
AES5485
CKGvendor affirmed
CVL1938, 1939, 1940, 1941
DRBG2160
DSA1412
ECDSA1471
HMAC3643
KAS184
KBKDF226
KTSvendor affirmed
RSA2946
SHA-348
SHS4402
Triple-DES2762

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-04-04InitialUL Verification Services, Inc.
2019-12-23UpdateUL 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

Source documents