SV-225475r916422: The Windows SMB server must perform SMB packet signing when possible. | Microsoft Windows Server 2012/2012 R2 Member Server STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

The Windows SMB server must perform SMB packet signing when possible.

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 negotiate SMB packet signing as requested by the client.

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

IA Controls

NIST SP 800-53

Not mappedCCI-002418Not mappedCCI-002421CCE-24354-3SV-52870V-1162

References

DPMS Target Microsoft Windows Server 2012-2012 R2 MS DISA DPMS Target Microsoft Windows Server 2012-2012 R2 MS 4214

Checks

OVAL

oval:mil.disa.fso.windows:var:456200 ← xccdf_mil.disa.stig_value_digitally_sign_communications_server_client_agrees_var

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: EnableSecuritySignature

Value Type: REG_DWORD
Value: 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.fso.windows:def:4562
# The Windows SMB server must perform SMB packet signing when possible.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Verifies 'Microsoft network server: Digitally sign communications (if client agrees)' is set to 'Enabled'
# 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('EnableSecuritySignature').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters' -Name 'EnableSecuritySignature' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'EnableSecuritySignature') -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_2012_and_2012_r2_ms target this check assesses.

# oval:mil.disa.fso.windows:def:4562
$compliant = (Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Services\LanmanServer\Parameters' -Name 'EnableSecuritySignature' -ErrorAction SilentlyContinue).EnableSecuritySignature -eq 1
if ($compliant) { 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 (if client agrees)" to "Enabled".