SV-226350r916422: Domain controllers must require LDAP access signing. | Microsoft Windows Server 2012/2012 R2 Domain Controller STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Domain controllers must require LDAP access signing.

Description

Discussion Text

Unsigned network traffic is susceptible to man in the middle attacks where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. You can lower the risk of an attacker pulling this off in a corporate network by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPSec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man in the middle attacks extremely difficult.

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

IA Controls

NIST SP 800-53

Not mappedCCI-002418Not mappedCCI-002421CCE-23587-9SV-51140V-4407

References

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

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\NTDS\Parameters\

Value Name: LDAPServerIntegrity

Value Type: REG_DWORD
Value: 2

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:4702
# Domain controllers must require LDAP access signing.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Verifies 'Domain Controller: LDAP Server signing requirements' is set to 'Require signing'
# 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\NTDS\Parameters').GetValueKind('LDAPServerIntegrity').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters' -Name 'LDAPServerIntegrity' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'LDAPServerIntegrity') -eq 2))
}

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:4702
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\LDAPServerIntegrity"
if (Test-Path $regPath) {
    $regValue = Get-ItemProperty -Path $regPath -Name "System" -ErrorAction SilentlyContinue
    if ($regValue -and $regValue.System -eq 2) {
        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 controller: LDAP server signing requirements" to "Require signing".