808bits

PrivateServer

FIPS 140-2 certificate #1790 · ARX (Algorithmic Research) · data as of 2026-09-15

PrivateServer, from ARX (Algorithmic Research), holds FIPS 140-2 certificate #1790 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1790
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorARX (Algorithmic Research) · website
Hardware versions4.7
Firmware versions4.8.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The PrivateServer is a high-performance cryptographic service provider. PrivateServer performs high-speed cryptographic operations while protecting sensitive data. Its features include Triple-DES, AES, Triple-DES MAC, CCM, HMAC, RSA, ECDSA, SHA-1, SHA-256, SHA-384, SHA-512, authenticated and encrypted communication with the module, secure storage of secret/private keys, software key medium and smartcard support, tamper-responsive enclosure, high level API requiring no cryptographic expertise, in-depth logging and auditing, and secure backup capability.

Approved algorithms (8)

AlgorithmCAVP certificates
AES1983
ECDSA288
HMAC1196
RNG1042
RSA1029
SHS1738
Triple-DES1286
Triple-DES MACvendor affirmed

Other algorithms

DES Stream; MD5; RSA cipher only with ISO9796 padding; ARDFP; RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); DES; DES MAC

Validation history

DateTypeLab
2012-11-05InitialCYGNACOM SOLUTIONS 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: 2012-11-05

Source documents