SV-226294r916422: The Windows SMB client must be enabled to perform SMB packet signing when possible. | Microsoft Windows Server 2012/2012 R2 Domain Controller STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

The Windows SMB client must be enabled to perform SMB packet signing when possible.

Description

Discussion Text

The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing.

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

IA Controls

NIST SP 800-53

Not mappedCCI-002418Not mappedCCI-002421CCE-24740-3SV-52874V-1166

References

DPMS Target Microsoft Windows Server 2012-2012 R2 DC DISA DPMS Target Microsoft Windows Server 2012-2012 R2 DC 4217

Checks

OVAL

oval:mil.disa.fso.windows:var:455800 ← xccdf_mil.disa.stig_value_digitally_sign_communications_client_server_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\LanmanWorkstation\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:4558
# The Windows SMB client must be enabled to 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 client: Digitally sign communications (if server 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\LanmanWorkstation\Parameters').GetValueKind('EnableSecuritySignature').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\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_dc target this check assesses.

# OVAL Definition: oval:mil.disa.fso.windows:def:4558
$regPath = "HKLM:\System\CurrentControlSet\Services\LanmanWorkstation\Parameters"
$regKey = "EnableSecuritySignature"
if (Test-Path $regPath) {
    $regValue = Get-ItemProperty -Path $regPath -Name $regKey -ErrorAction SilentlyContinue
    if ($regValue -and $regValue.$regKey -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 -> "Microsoft network client: Digitally sign communications (if server agrees)" to "Enabled".