Title

IBM z/OS for PKI-based authentication must use ICSF or the ESM to store keys. (Cat II impact)

Discussion

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.

Check Content

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

Define all Keys/Certificates to ICSF or the security database. Remove all .kdb and .jks key files.

Additional Identifiers

Rule ID: SV-223883r877725_rule

Vulnerability ID: V-223883

Group Title: SRG-OS-000067-GPOS-00035

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.