SV-278173r1268226: Windows Server 2025 must be configured for name-based strong mappings for certificates. | Microsoft Windows Server 2025 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

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

Description

Discussion Text

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.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000213

References

DPMS Target Microsoft Windows Server 2025 DISA DPMS Target Microsoft Windows Server 2025 5719

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

# Windows PowerShell
# Reconstructed from oval:mil.disa.stig.windows2025:def:278173
# Windows Server 2025 must be configured for name-based strong mappings for certificates.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# UseStrongNameMatches == 1
# registry_object (registry_test)
function test_1 {
  return (((@{String='reg_sz';ExpandString='reg_expand_sz';Binary='reg_binary';DWord='reg_dword';MultiString='reg_multi_sz';QWord='reg_qword';None='reg_none'}[(Get-Item -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters').GetValueKind('UseStrongNameMatches').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters' -Name 'UseStrongNameMatches' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'UseStrongNameMatches') -eq 1))
}

if (test_1) {
  Write-Output "PASS"
} else {
  Write-Output "FAIL"
}

Assessment Script Powered by AISyntax-verified

A standalone PowerShell script to assess this control automatically. Review before running it in your environment.

Syntax-checked as valid PowerShell. Not executed here — running it for real needs the actual ms_windows_server_2025 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows2025:def:278173
if ((Test-Path -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters\UseStrongNameMatches" -ErrorAction SilentlyContinue) -and ((Get-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\KDC\Parameters" -ErrorAction SilentlyContinue).UseStrongNameMatches -eq 1)) {Write-Output "PASS"; exit 0} else {Write-Output "FAIL"; exit 1}

Remediation

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

The policy must contain exactly one certificate thumbprint per rule, with each rule represented as a tuple. Thumbprints must be unique and cannot be repeated in multiple rules. The sections of each tuple that are separated by semi-colons must be in the stated order, while the fields separated by commas can be in any order. The rules themselves are separated by new lines.