808bits

ID-One Cosmo 32 v5

FIPS 140-2 certificate #597 · Oberthur Card Systems · data as of 2026-10-21

ID-One Cosmo 32 v5, from Oberthur Card Systems, holds FIPS 140-2 certificate #597 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 number597
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorOberthur Card Systems · website
Hardware versionsP/N 90
Firmware versionsE311-063842

Module description

Quoted from the NIST CMVP entry for this certificate.

The ID-One Cosmo 32 v5 is a JavaCard cryptographic module specifically designed for identity and government market needs. It offers a full 32K Byte of EEPROM space available for customer discretionary use, together with on-card cryptographic services such as TDES (using double and triple length DES keys), and 2048-bit RSA with on-card key generation. The cryptographic module loads and runs applets written in Java programming language. It includes a native implementation of the latest Java Card TM (Version 2.2) and Open Platform (Version 2.1.1A) specifications, with full support for Delegated Management and DAP / Mandated DAP, that define a secure infrastructure for post-issuance programmable platforms. Additional features include On-Card fingerprint matching and Logical Channels.

Approved algorithms (5)

AlgorithmCAVP certificates
RNG99
RSA42
SHS290
Triple-DES303
Triple-DES MACvendor affirmed

Other algorithms

DES (Cert. #286); DES MAC (Cert. #286, vendor affirmed); MD5

Validation history

DateTypeLab
2005-12-01InitialUL 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: 2005-12-01

Source documents