808bits

ID-One Cosmo 64 v5

FIPS 140-2 certificate #449 · Oberthur Card Systems · data as of 2026-09-15

ID-One Cosmo 64 v5, from Oberthur Card Systems, holds FIPS 140-2 certificate #449 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 number449
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorOberthur Card Systems · website
Hardware versionsP/N: 77
Firmware versionsE302

Module description

Quoted from the NIST CMVP entry for this certificate.

The ID-One Cosmo 64 v5 is a JavaCard cryptographic module with dual interface (ISO 7816 & ISO 14443) specifically designed for identity and government needs. It offers a full 64K Byte of EEPROM space available for customer discretionary use, together with on card cryptographic services such as TDES, AES, and 2048-bit RSA algorithms with on-card key generation. It is compliant to Java Card v2.2 and Open Platform v2.1.1A. To protect against skimming, a built-in firewall allows application developers to disable contactless access for sensitive operations. Additional features include On-Card fingerprint matching and Logical Channels. The ID-One Cosmo 64 v5 is available in contact only, dual interface, or contactless only formats.

Approved algorithms (5)

AlgorithmCAVP certificates
AES123
RSAvendor affirmed
SHA-1209
Triple-DES232
Triple-DES MACvendor affirmed

Other algorithms

DES (Cert. #246); DES MAC (Cert. #246, vendor affirmed);

Validation history

DateTypeLab
2004-07-28InitialUL Verification Services, Inc.
2005-02-25Update
2005-03-01Update
2005-06-29Update
2005-09-23Update

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-07-28, 2005-02-25, 2005-03-01, 2005-06-29, 2005-09-23

Source documents