Windows Server 2022 must be configured for name-based strong mappings for certificates.

Quick Actions

We are continuing to improve Stigviewer and we are planning on rolling out new services in the near future. Would you like to be part of the conversation on what those features should be? If so, click here.

Featured Partners

Web page built by Cyber Protection Services

Check out our new AI-powered GRC tool here .
Compliance Dictionary

Standardizes and unifies compliance terms.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-271427	WN22-DC-000406	SV-271427r1059560_rule		Medium

Description

Weak mappings give rise to security vulnerabilities and demand hardening measures. Certificate names must be correctly mapped to the intended user account in Active Directory. A lack of strong name-based mappings allows certain weak certificate mappings, such as Issuer/Subject AltSecID and User Principal Names (UPN) mappings, to be treated as strong mappings.

STIG	Date
Microsoft Windows Server 2022 Security Technical Implementation Guide	2025-01-14

Details

Check Text (C-75476r1059558_chk)

This applies to domain controllers. This is not applicable for member servers.

Verify the effective setting in Local Group Policy Editor.

Run "gpedit.msc".

Navigate to Local Computer Policy >> Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates.

If "Allow name-based strong mappings for certificates" is not "Enabled", this is a finding.

Fix Text (F-75383r1059559_fix)

Configure the policy value for Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates to "Enabled".

STIG VIEWER