BaselineWatch
Desk

RHEL-09-611190 RHEL 9, for PKI-based authentication, must enforce authorized access to the corresponding private key.

DISA STIG library V2R10
All changes in this version
first version loaded CAT II

Maps to IA-5(2) via CCI-000186

Title

RHEL 9, for PKI-based authentication, must enforce authorized access to the corresponding private key.

Control

Note: If the system administrator demonstrates the use of an approved alternate multifactor authentication method, this requirement is not applicable. Verify the SSH private key files have a passcode. For each private key stored on the system, use the following command: $ sudo ssh-keygen -y -f /path/to/file The expected output is a password prompt: "Enter passphrase:" If the password prompt is not displayed, and the contents of the key are displayed, this is a finding.

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 nonrepudiation 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.

Related controls

CCI-000186

Fix

Create a new private and public key pair that utilizes a passcode with the following command: $ sudo ssh-keygen -N [passphrase]