ID-One PIV on Cosmo V8.1 - SPE Configurations
Caveat: When operated in FIPS mode and initialized to Overall Level 3 per the Security Policy
Certificate
| Certificate number | 3039 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Single Chip |
| Vendor | Oberthur Technologies · website |
| Hardware versions | P/Ns ‘30-5F01’ [1], ‘30-5F02’ [2], '40-6001' [3] and '40-6002' [4] |
| Firmware versions | Firmware Extension: ‘086294’+’086683’ (ID-One PIV Applet Suite 2.4.0 on Cosmo V8.1 LARGE) [1], Firmware Extension: ‘090191’ (ID-One PIV 2.4.1 on Cosmo V8.1 LARGE) [2], Firmware Extension: ‘086294’+’086693’ (ID-One PIV Applet Suite 2.4.0 on Cosmo V8.1 STD) [3] and Firmware Extension: ‘090211’ (ID-One PIV 2.4.1 on Cosmo V8.1 STD) [4] |
Module description
ID-One PIV on Cosmo V8.1 is the next generation of Personal Identification and Verification cards, avalaible in multiple FIPS 140-2 validated configurations. The SPE configurations are extensions to the PIV/CIV configurations where the module enforces the encryption of the PIN when submitted to the module for card holder verification, regardless of the communication interface being used (contact & contactless). The EP (Enhanced Privacy) option added to the default SPE configuration prevents the leaking from the card of any traceable or PII over the contactless interface.
Security level exceptions
- Physical Security: Level 4
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 4107, 4108, 4109 |
| CVL | 921, 953, 954 |
| DRBG | 1234 |
| ECDSA | 933 |
| HMAC | 2683 |
| KAS | 48 |
| KBKDF | 106 |
| KTS | |
| KTS | |
| RSA | 2252, 2253 |
| SHA-3 | 6 |
| SHS | 3379, 3380 |
| Triple-DES | 2245 |
Allowed algorithms
NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2017-10-06 | Initial | UL Verification Services, Inc. |
| 2017-11-09 | Update | UL 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: 2017-10-06, 2017-11-09