SV-35997r1: The system will be configured to audit "System -> IPSec Driver" successes. | Windows 7 Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

The system will be configured to audit "System -> IPSec Driver" successes.

Description

Discussion Text

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. IPSec Driver records events related to the IPSec Driver such as dropped packets.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000172CCE-9925-9

Additional Details

Responsibility

System Administrator

References

DPMS Target Windows 7 DISA DPMS Target Windows 7 1712

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:3764
# The system will be configured to audit "System -> IPSec Driver" successes.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Audit - IPSec Driver - Success only
# auditeventpolicysubcategories_object (auditeventpolicysubcategories_test)
function test_1 {
  return ((@{'No Auditing'='AUDIT_NONE';'Success'='AUDIT_SUCCESS';'Failure'='AUDIT_FAILURE';'Success and Failure'='AUDIT_SUCCESS_FAILURE'}[(auditpol /get /subcategory:'Ipsec Driver' /r | ConvertFrom-Csv).'Inclusion Setting']) -eq 'AUDIT_SUCCESS')
}
# Audit - IPSec Driver - Success and Failure
# auditeventpolicysubcategories_object (auditeventpolicysubcategories_test)
function test_2 {
  return ((@{'No Auditing'='AUDIT_NONE';'Success'='AUDIT_SUCCESS';'Failure'='AUDIT_FAILURE';'Success and Failure'='AUDIT_SUCCESS_FAILURE'}[(auditpol /get /subcategory:'Ipsec Driver' /r | ConvertFrom-Csv).'Inclusion Setting']) -eq 'AUDIT_SUCCESS_FAILURE')
}

if ((test_1 -or test_2)) {
  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 windows_7 target this check assesses.

# OVAL Definition: oval:mil.disa.fso.windows:def:3764
$auditPolicy = Get-CimInstance -ClassName Win32_LocalSystemAuditPolicy
if ($auditPolicy -eq $null) { exit 1 }
$auditPolicySubCategories = Get-CimInstance -ClassName Win32_AuditEventPolicySubCategories
if ($auditPolicySubCategories -eq $null) { exit 1 }
$ipsecDriverPolicy = $auditPolicySubCategories | Where-Object { $_.Name -eq 'IPSec Driver' }
if ($ipsecDriverPolicy -eq $null) { exit 1 }
if ($ipsecDriverPolicy.AuditSuccess -eq $true) { exit 0 }
exit 1

Remediation

Detailed auditing subcategories are configured in Security Settings -> Advanced Audit Policy Configuration.   The summary level settings under Security Settings -> Local Policies -> Audit Policy will not be enforced (see V-14230).

				Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit IPSec Driver" with “Success” selected.