808bits

Ultralock Symmetric Module

FIPS 140-2 certificate #741 · nCipher Corporation Ltd. · data as of 2026-10-21

Ultralock Symmetric Module, from nCipher Corporation Ltd., holds FIPS 140-2 certificate #741 at overall level 1. 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and using the nForce Ultra Asymmetric Module validated to FIPS 140-2 under Cert. #740 and nCipher MiniHSM validated to FIPS 140-2 under Cert. #672 when operated in FIPS mode and initialized to Overall Level 2 per Security Policy

Certificate

Certificate number741
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip embedded
VendornCipher Corporation Ltd. · website
Hardware versions010-00007 a.00

Module description

Quoted from the NIST CMVP entry for this certificate.

The Ultralock Symmetric Module performs all the cryptography required for SSL/TLS applications. This module is a common element of the Britestream BN2010 SSL Security ASIC, the industry's first single-chip solution for completely off-loading SSL/TLS processing from host systems. The innovative in-line architecture combines TCP.

Security level exceptions

  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES263
HMAC75
SHS342
Triple-DES345

Other algorithms

DES; RC4; MD5; HMAC-MD5; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2007-03-01InitialDOMUS

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: 2007-03-01

Source documents