For PKI-based authentication, AlmaLinux OS 9 must enforce authorized access to the corresponding private key.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-269410	SRG-OS-000067-GPOS-00035	ALMA-09-038850	SV-269410r1050293_rule	2025-02-20	1

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

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

ℹ️ Check
Verify the SSH private key files have a passcode. For each private key stored on the system, use the following command: $ ssh-keygen -y -f /path/to/file If the contents of the key are displayed, instead of a passphrase prompt, this is a finding.

✔️ Fix
Create a new private and public key pair that uses a passcode, as the correct user, with the following command: $ ssh-keygen -n [passphrase]