808bits

Secure Generic Sub-System (SGSS), Version 3.5 [1] and 3.6 [2]

FIPS 140-2 certificate #1794 · Thales e-Security Inc. · data as of 2026-10-21

Secure Generic Sub-System (SGSS), Version 3.5 [1] and 3.6 [2], from Thales e-Security Inc., holds FIPS 140-2 certificate #1794 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1794
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorThales e-Security Inc. · website
Software versions3.0.0
Hardware versions1213H130 Issue 6E [1], 1213R130 Issue 1 [1], 1213P130 Issue 2 [1], 1213P130 Issue 2A [1]. 1213P130 Issue 2B [2], 1213R130 Issue 2 [2] and 1213S130 Issue 2 [2]

Module description

Quoted from the NIST CMVP entry for this certificate.

The Secure Generic Sub-System (SGSS) is a multi-chip embedded module used to provide secure cryptographic resources to a number of products in the Thales e-Security portfolio. This includes the Datacryptor® 2000, Datacryptor® Advanced Performance and Small Form Factor family (Link, Frame Relay, E1/T1, E3/T3, and IP models). The SGSS contains a secure bootstrap and authenticates application loading using the Digital Signature Algorithm (ECDSA) and SHA-384 hashing. This is a revalidation of the SGSS certified under FIPS Certificate #836, and does not affect the previous FIPS validation.

Approved algorithms (2)

AlgorithmCAVP certificates
ECDSA283
SHS1717

Validation history

DateTypeLab
2012-08-28InitialCYGNACOM SOLUTIONS INC
2012-09-27Update
2015-12-10UpdateCYGNACOM 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-08-28, 2012-09-27, 2015-12-10

Source documents