808bits

Athena IDProtect

FIPS 140-2 certificate #925 · Athena Smartcard Inc. · data as of 2026-10-21

Athena IDProtect, from Athena Smartcard Inc., holds FIPS 140-2 certificate #925 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 number925
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorAthena Smartcard Inc. · website
Hardware versionsP/N AT90SC25672RCT Revision D
Firmware versions0106.6340.0101

Module description

Quoted from the NIST CMVP entry for this certificate.

Athena Smartcard Solutions is a global smart card company offering a wide range of smart card products and solutions for Government, Enterprise and Financial institutions. Athena's products include advanced smart card operating systems, cross-platform cryptographic middleware and innovative biometric and card management solutions as well as advanced smart card readers. Athena offers FIPS and VISA certified Java Card solutions for ID and Finance on various smart card silicon and in a variety of form-factors.

Security level exceptions

  • Physical Security: Level 4

Approved algorithms (6)

AlgorithmCAVP certificates
AES577
RNG332
RSA264
SHS633
Triple-DES560
Triple-DES MACvendor affirmed

Other algorithms

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

Validation history

DateTypeLab
2008-03-14InitialUL Verification Services, Inc.
2013-04-12UpdateUL Verification Services, Inc.
2014-05-28UpdateUL 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: 2008-03-14, 2013-04-12, 2014-05-28

Source documents