Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
IBM z/OS for PKI-based authentication must use ICSF or the ESM to store keys.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-223883 | TSS0-ES-000100 | SV-223883r877725_rule | Medium |
| Description |
|---|
| If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys. |
| STIG | Date |
|---|---|
| IBM z/OS TSS Security Technical Implementation Guide | 2022-12-14 |
Details
| Check Text ( C-25556r877724_chk ) |
|---|
| Any keys or Certificates must be managed in ICSF or the external security manager and not in UNIX files. From the ISPF Command Shell enter: OMVS enter find / -name *.kdb and Find / -name *.jks If any files are present, this is a finding. OMVS enter find / -name *.kdb and Find / -name *.jks If any files are present, this is a finding. |
| Fix Text (F-25544r811041_fix) |
|---|
| Define all Keys/Certificates to ICSF or the security database. Remove all .kdb and .jks key files. |