808bits

Model 330G2 Smart Card

FIPS 140-2 certificate #444 · SafeNet, Inc. · data as of 2026-10-21

Model 330G2 Smart Card, from SafeNet, Inc., holds FIPS 140-2 certificate #444 at overall level 2. 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

Certificate

Certificate number444
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle-chip
VendorSafeNet, Inc. · website
Hardware versions1.0
Firmware versions2.0, EXFs: GSC-IS application executable (G2 EXF) Version 22

Module description

Quoted from the NIST CMVP entry for this certificate.

The 330G2 is an ISO 7816 and GSC-IS compliant cryptographic smart card designed for identification and access control applications. The card provides a secure, mobile platform for creating, storing and using keys, certificates, passwords and other digital credentials. Security services include: Multiapplication secure storage and retrieval of data and digital credentials. Authentication of the cardholder and the security officer. Cryptographic services including SHA-1, DES, 3DES, RSA Sign/Verify, RSA Encrypt/Decrypt and DSA Sign/Verify with on board key generation including RSA 2048-bit key generation.

Security level exceptions

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

Approved algorithms (3)

AlgorithmCAVP certificates
DSA/SHA-1
RSAvendor affirmed
Triple-DES236

Other algorithms

DES (Cert. #88); Diffie-Hellman (key agreement)

Validation history

DateTypeLab
2004-06-30InitialSAIC-VA
2005-02-22Update

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: 2004-06-30, 2005-02-22

Source documents