SV-254455r958908: Windows Server 2022 must be configured to require a strong session key. | Microsoft Windows Server 2022 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Windows Server 2022 must be configured to require a strong session key.

Description

Discussion Text

A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

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

IA Controls

NIST SP 800-53

Not mappedCCI-002418Not mappedCCI-002421

References

DPMS Target Microsoft Windows Server 2022 DISA DPMS Target Microsoft Windows Server 2022 5485

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.windows2022:def:254455
# Windows Server 2022 must be configured to require a strong session key.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# 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\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters').GetValueKind('RequireStrongKey').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters' -Name 'RequireStrongKey' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'RequireStrongKey') -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_2022 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows2022:def:254455
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters"
if (Test-Path $regPath) {
    $regValue = Get-ItemProperty -Path $regPath -Name RequireStrongKey -ErrorAction SilentlyContinue
    if ($regValue -and $regValue.RequireStrongKey -eq 1) {
        Write-Output "PASS"; exit 0
    }
}
Write-Output "FAIL"; exit 1

Remediation

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Require strong (Windows 2000 or Later) session key to "Enabled".