IBM® z/OS® Version 2 Release 2 ICSF PKCS #11 Cryptographic Module
Certificate
| Certificate number | 3019 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software-Hybrid |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | IBM Corporation · website |
| Software versions | OA52336 |
| Hardware versions | COP chips integrated within processor unit [1] and P/N 00LV487 [2] |
| Firmware versions | Feature 3863 (aka FC3863) with System Driver Level 27I [1] and CCA 5.2.27z RC30 [2] |
Module description
ICSF is a software element of z/OS that works with hardware cryptographic features and the Security Server (RACF) to provide secure, high-speed cryptographic services in the z/OS environment. ICSF, which runs as a started task, provides the application programming interfaces by which applications request the cryptographic services.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 4579, 4586 |
| CKG | vendor affirmed |
| CVL | 1259, 1322 |
| DRBG | 1526, 1530 |
| DSA | 1216 |
| ECDSA | 1123 |
| HMAC | 3035 |
| KTS | |
| RSA | 2501, 2548 |
| SHS | 3661, 3761 |
| Triple-DES | 2432 |
Allowed algorithms
Diffie-Hellman (CVL Cert. #1259, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1259, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); HMAC-MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)
Tested configurations
- IBM z/OS Version 2 Release 2 running on an IBM z13 with CP Assist for Cryptographic Functions (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2017-09-21 | Initial | atsec information security corporation |
| 2018-02-20 | Update | atsec information security corporation |
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-09-21, 2018-02-20