Windows Server 2019 must be configured for named-based strong mappings for certificates.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-271429 | WN19-DC-000401 | SV-271429r1106520_rule | CCI-000213 | 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 2019 Security Technical Implementation Guide | 2025-05-23 | |||
Details
Check Text (C-271429r1106520_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".
Or
Using the registry, check HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters, Key: UseStrongNameMatches.
Or
Using GPRESULT, check the applicable GPO for "Allow name-based strong mappings for certificates".
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-75385r1059565_fix)
Configure the policy value for Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates to "Enabled".