SV-205827r958908: Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. | Microsoft Windows Server 2019 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.

Description

Discussion Text

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing. 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-002421SV-103645V-93559

References

DPMS Target Microsoft Windows Server 2019 DISA DPMS Target Microsoft Windows Server 2019 2907

Checks

DISA STIG (Manual Reference)

If the following registry value does not exist or is not configured as specified, this is a finding:

Registry Hive: HKEY_LOCAL_MACHINE 
Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\

Value Name: RequireSecuritySignature

Value Type: REG_DWORD
Value: 0x00000001 (1)

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.windows2019:def:205827
# Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.
# 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\LanManServer\Parameters').GetValueKind('RequireSecuritySignature').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters' -Name 'RequireSecuritySignature' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'RequireSecuritySignature') -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_2019 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows2019:def:205827
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters"
if (Test-Path $regPath) { $regValue = (Get-ItemProperty -Path $regPath -Name "RequireSecuritySignature").RequireSecuritySignature } else { $regValue = $null }
if ($regValue -eq 1) { Write-Output "PASS"; exit 0 } else { Write-Output "FAIL"; exit 1 }

Remediation

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" to "Enabled".