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 Mainframe Product Security Requirements Guide

V-205506

CAT II (Medium)

The Mainframe Product, when using PKI-based authentication, must enforce authorized access to the corresponding private key.

Rule ID

SV-205506r961041_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-000186

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

If the Mainframe Product employs an external security manager (ESM) for all account management functions, this is not applicable.

Examine user account management configurations. 

If the Mainframe Product account management configurations do not enforce authorized access to the corresponding private key when using PKI-based authentication, this is a finding.

Fix Text

Configure the Mainframe Product account management settings to enforce authorized access to the corresponding private key when using PKI-based authentication.