808bits

IDCore 30

FIPS 140-2 certificate #1966 · Gemalto · data as of 2026-10-21

IDCore 30, from Gemalto, holds FIPS 140-2 certificate #1966 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: When operated in FIPS mode

Certificate

Certificate number1966
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorGemalto · website
Hardware versionsSLE78CFX3009P
Firmware versionsIDCore 30 Build 1.17, Demonstration Applet version V1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The IDCore 30 is a part of Gemalto's IDCore family of Java Cards and offers a comprehensive array of features and options for logical and physical access control applications. IDCore 30 is a highly secure platform for private and public sector smart card deployments implementing Java Card 2.2.2 and Global Platform 2.1.1 / 2.2 Amdt D specifications. IDCore 30 is ideally suited for markets such as Identity or Security/Access, including one-time password authentication, Public Key Infrastructure (PKI) services, digital transactions and physical access control.

Approved algorithms (7)

AlgorithmCAVP certificates
AES2261
CVL41
ECDSA363
RSA1158, 1163
SHS1946
Triple-DES1413
Triple-DES MACvendor affirmed

Other algorithms

EC Diffie-Hellman (SP 800-56A; non-compliant); PRNG

Validation history

DateTypeLab
2013-06-21InitialUL Verification Services, Inc.
2013-07-05UpdateUL Verification Services, Inc.
2016-08-08UpdateUL Verification Services, 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: 2013-06-21, 2013-07-05, 2016-08-08

Source documents