STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM z/OS TSS Security Technical Implementation Guide

V-223883

CAT II (Medium)

IBM z/OS for PKI-based authentication must use ICSF or the ESM to store keys.

Rule ID

SV-223883r998485_rule

STIG

IBM z/OS TSS Security Technical Implementation Guide

Version

V9R8

CCIs

CCI-000186CCI-004910

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.