808bits

Gemalto .NET Smart Card

FIPS 140-2 certificate #1099 · Gemalto · data as of 2026-09-13

Gemalto .NET Smart Card, from Gemalto, holds FIPS 140-2 certificate #1099 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1099
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorGemalto · website
Hardware versionsInfineon SLE 88CFX4000P
Firmware versions.Net Platform and Content Manager v2.2; FIPS Assembly v1.1; FIPS Access Manager v1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Gemalto .NET v2.2 Smart Card Platform implements a subset of the .NET Framework with high end cryptographic capabilities, including Random Number Generation, on Board Key Generation, and encryption and hashing algorithms such as 3DES, AES, SHA, and 2048 bit RSA. The combination of advanced programmability provided by the .NET Framework and the high end security features make .NET v2.2 a perfect support for Enterprise and Government security solutions.

Approved algorithms (6)

AlgorithmCAVP certificates
AES877
HMAC491
RNG503
RSA424
SHS869
Triple-DES719

Other algorithms

AES (key wrapping; key establishment methodology provides 192 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2009-03-10InitialUL Verification Services, Inc.
2009-03-19Update

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: 2009-03-10, 2009-03-19

Source documents