808bits

MiniHSM

FIPS 140-2 certificate #671 · nCipher Corporation Ltd. · data as of 2026-08-28
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 and initialized to Overall Level 3 per Security Policy

Certificate

Certificate number671
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendornCipher Corporation Ltd. · website
Hardware versionsnC4033z-10 Build Standards A, B & N
Firmware versions2.22.17-3 and 2.22.34-3

Module description

The nCipher MiniHSM is a fully featured HSM supplied in a single chip package. The MiniHSM offers all the security and key management features of other nCipher modules - but with reduced processing speed. The MiniHSM is an OEM part and will be included within other appliances or products, for example switches or routers. The MiniHSM's real time clock, also makes it suitable for use as a time-stamping engine.

Approved algorithms

AlgorithmCAVP certificate
AES258
DSA136
ECDSA2
HMAC68
RNG91
RSA68
SHS333
Triple-DES339
Triple-DES MACvendor affirmed

Other algorithms

ARC FOUR; CAST5; CAST 6; DES (non compliant); DES MAC (non compliant); MD2; MD5; SEED; HMAC (MD2, MD5, and RIPEMD160); RIPEMD 160; El-Gamal; Blowfish; Twofish; Serpent; KCDSA; HSA 160; Diffie-Hellman (key agreement, key establishment methodology provides 112 bits to 256 bits of encryption strength; non-compliant less that 112 bits of encryption strength); EC Diffie-Hellman (key agreement, key establishment methodology provides 192 bits of encryption strength); RSA (Cert.#68, key wrapping, key establishment methodology provides 112 bits to 256 bits of encryption strength; non-compliant less that 112 bits of encryption strength)

Validation history

DateTypeLab
2006-05-11InitialDOMUS
2006-08-29Update
2008-06-24Update

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: 2006-05-11, 2006-08-29, 2008-06-24

Source documents