ISC Cryptographic Development Kit (CDK)
Certificate
| Certificate number | 3105 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Information Security Corporation · website |
| Software versions | 8.0 |
Module description
The CDK is a software module. The physical embodiment of the computer hardware on which it runs is a "multi-chip standalone module" in FIPS 140-2 terminology. The "physical cryptographic boundary" is defined to be the entire computer on which the CDK software runs. As a software module, the "logical boundary" contains the software modules that comprise the CDK shared link library.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 4002 |
| CVL | 831, 832, 853, 854 |
| DRBG | 1192 |
| DSA | 1090 |
| ECDSA | 892 |
| HMAC | 2615 |
| KAS | 85 |
| KTS | |
| RSA | 2065 |
| SHA-3 | 4 |
| SHS | 3307 |
| Triple-DES | 2197 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 or 128 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #853, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- CentOS 6.7 (64-bit) running on Intel Core i7 with PAA
- CentOS 6.7 (64-bit) running on Intel Core i7 without PAA
- Microsoft Windows 10 (64-bit) running on AMD A8-3850 without PAA
- Microsoft Windows 10 (64-bit) running on Intel Core i7 with PAA
- Microsoft Windows 10 (64-bit) running on Intel Core i7 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-01-05 | Initial | COACT INC CAFE LAB |
| 2018-08-15 | Update | COACT INC CAFE LAB |
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: 2018-01-05, 2018-08-15