STIGQter: STIG Summary: Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 26 Mar 2026:

TOSS 5, for public key infrastructure (PKI)-based authentication, must enforce authorized access to the corresponding private key.

DISA Rule

SV-282443r1200309_rule

Vulnerability Number

V-282443

Group Title

SRG-OS-000067-GPOS-00035

Rule Version

TOSS-05-000074

Severity

CAT II

CCI(s)

• CCI-000186 - For public key-based authentication, enforce authorized access to the corresponding private key.

Weight

10

Fix Recommendation

Create a new private and public key pair that uses a passcode using the following command:

$ sudo ssh-keygen -n [passphrase]

Check Contents

If the system does not allow PKI authentication, this requirement is not applicable.

Verify the operating system, for PKI-based authentication, enforces authorized access to the corresponding private key.

Verify the SSH private key files have a passphrase.

For each private key stored on the system, use the following command:

$ sudo ssh-keygen -y -f /path/to/file

If the contents of the key are displayed, and use of un-passphrased Secure Shell (SSH) keys is not documented with the information system security officer, this is a finding.

Vulnerability Number

V-282443

Documentable

False

Rule Version

TOSS-05-000074

Severity Override Guidance

If the system does not allow PKI authentication, this requirement is not applicable.

Verify the operating system, for PKI-based authentication, enforces authorized access to the corresponding private key.

Verify the SSH private key files have a passphrase.

For each private key stored on the system, use the following command:

$ sudo ssh-keygen -y -f /path/to/file

If the contents of the key are displayed, and use of un-passphrased Secure Shell (SSH) keys is not documented with the information system security officer, this is a finding.

Check Content Reference

M

Target Key

5738