808bits

nToken

FIPS 140-2 certificate #683 · 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

Certificate

Certificate number683
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
VendornCipher Corporation Ltd. · website
Hardware versionsnC2033P-000; Build Standards C & N
Firmware versions2.22.6

Module description

The nCipher nToken Hardware Security Module improves the security of cryptographic keys, security sensitive software applications and increases server throughput of secure transactions in Public Key Infrastructure and other high integrity applications such as: Certificate Authorities, Registration Authorities, Government and Financial Institutions.

Security level exceptions

  • Physical Security: Level 3
  • EMI/EMC: Level 3

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; HAS 160; Diffie-Hellman (key agreement, key establishment methodology provides 112 bits to 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement, key establishment methodology provides 192-bits of encryption strength); RSA (key wrapping, key establishment methodology provides 112 bits to 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2006-06-26InitialDOMUS
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-06-26, 2008-06-24

Source documents