STIGQter: STIG Summary: Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide Version: 2 Release: 6 Benchmark Date: 01 Jul 2026:

TOSS must map the authenticated identity to the user or group account for PKI-based authentication.

DISA Rule

SV-252950r958452_rule

Vulnerability Number

V-252950

Group Title

SRG-OS-000068-GPOS-00036

Rule Version

TOSS-04-020050

Severity

CAT II

CCI(s)

CCI-000187 - For public key-based authentication, map the authenticated identity to the account of the individual or group.

Weight

Fix Recommendation

Configure TOSS to map the authenticated identity to the user or group account by adding or modifying the certmap section of the "/etc/sssd/sssd.conf" file based on the following example:

[certmap/testing.test/rule_name]
matchrule =<SAN>.*EDIPI@mil
maprule = (userCertificate;binary={cert!bin})
dmains = testing.test

The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command:

$ sudo systemctl restart sssd.service

Check Contents

Verify the certificate of the user or group is mapped to the corresponding user or group in the "sssd.conf" file with the following command:

Note: If the system does not support PKI authentication, this requirement is Not Applicable.

$ sudo cat /etc/sssd/sssd.conf

[sssd]
config_file_version = 2
services = pam, sudo, ssh
domains = testing.test

[pam]
pam_cert_auth = True

[domain/testing.test]
id_provider = ldap

[certmap/testing.test/rule_name]
matchrule =<SAN>.*EDIPI@mil
maprule = (userCertificate;binary={cert!bin})
domains = testing.test

If the certmap section does not exist, ask the System Administrator to indicate how certificates are mapped to accounts. If there is no evidence of certificate mapping, this is a finding.

Vulnerability Number

V-252950

Documentable

False

Rule Version

TOSS-04-020050

Severity Override Guidance

Check Content Reference

Target Key

5469