STIGQter: STIG Summary: Windows Firewall with Advanced Security Security Technical Implementation Guide Version: 1 Release: 7 Benchmark Date: 27 Apr 2018:

The Windows Firewall with Advanced Security must log successful connections when connected to a private network.

DISA Rule

SV-54905r3_rule

Vulnerability Number

V-17437

Group Title

Windows FW Private - Log Successful Connections

Rule Version

WNFWA-000019

Severity

CAT III

CCI(s)

• CCI-001462 - The information system provides the capability for authorized users to capture/record and log content related to a user session.

Weight

10

Fix Recommendation

The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Logging (select Customize), "Logged successful connections" to "Yes".

In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.

The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".

Check Contents

If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.

If the following policy-based registry value exists and is not configured as specified, this is a finding.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging\

Value Name: LogSuccessfulConnections

Type: REG_DWORD
Value: 0x00000001 (1)

If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging\

Value Name: LogSuccessfulConnections

Type: REG_DWORD
Value: 0x00000001 (1)

Vulnerability Number

V-17437

Documentable

False

Rule Version

WNFWA-000019

Severity Override Guidance

If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.

If the following policy-based registry value exists and is not configured as specified, this is a finding.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging\

Value Name: LogSuccessfulConnections

Type: REG_DWORD
Value: 0x00000001 (1)

If the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging\

Value Name: LogSuccessfulConnections

Type: REG_DWORD
Value: 0x00000001 (1)

Check Content Reference

M

Target Key

2565

Comments