SV-225337r569185: Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown. | Microsoft Windows Server 2012/2012 R2 Member Server STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown.

Description

Discussion Text

Compromised boot drivers can introduce malware prior to some protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000366CCE-25320-3SV-51608V-36679

References

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

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\Policies\EarlyLaunch\

Value Name: DriverLoadPolicy

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:4453
# Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Verifies 'Boot-Start Driver Initialization Policy' is set to 'Enabled' with 'Good and Unknown' selected
# 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\Policies\EarlyLaunch').GetValueKind('DriverLoadPolicy').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies\EarlyLaunch' -Name 'DriverLoadPolicy' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'DriverLoadPolicy') -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:4453
if (Test-Path -Path "HKLM:\System\CurrentControlSet\Policies\EarlyLaunch\DriverLoadPolicy" -ErrorAction SilentlyContinue) { $regValue = Get-ItemProperty -Path "HKLM:\System\CurrentControlSet\Policies\EarlyLaunch\DriverLoadPolicy" -Name "DriverLoadPolicy" -ErrorAction SilentlyContinue; if ($regValue -ne $null -and $regValue.DriverLoadPolicy -eq 1) { Write-Output "PASS"; exit 0 } } Write-Output "FAIL"; exit 1

Remediation

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Early Launch Antimalware -> "Boot-Start Driver Initialization Policy" to "Enabled" with "Good and Unknown" selected.