808bits

Athena IDProtect Duo PIV

FIPS 140-2 certificate #991 · Athena Smartcard Inc. · data as of 2026-08-28
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 number991
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle-chip
VendorAthena Smartcard Inc. · website
Software versionsP/N Athena PIV Applet Version 1.0
Hardware versionsP/N AT90SC12872RCFT Revision M
Firmware versionsP/N Athena IDProtect Duo Version 0107.7099.0105

Module description

The Athena IDProtect Duo PIV cryptographic module is compliant with FIPS 201 as an end point compliant card. The PIV application is hosted by the Athena IDProtect dual interface smart card operating system compliant with the Java Card 2.2.2 and GlobalPlatform 2.1.1 specifications and FIPS 140-2 Level 2 (Level 4 for Physical Security). IDProtect supports FIPS Approved Random Number Generator, TDES, AES, SHA-1, SHA-256, and RSA up to 2048 bits including on board key generation.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Roles, Services, and Authentication: Level 3
  • Physical Security: Level 4
  • Cryptographic Key Management: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES646
CVL210
RNG368
RSA296
SHS680
Triple-DES598
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-08-15InitialUL Verification Services, Inc.
2013-04-12UpdateUL Verification Services, Inc.
2014-02-06Update
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-08-15, 2013-04-12, 2014-02-06, 2014-05-28

Source documents