The Windows Firewall must allow outbound connections, unless a rule explicitly blocks the connection for the Private Profile.

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The Windows Firewall must allow outbound connections, unless a rule explicitly blocks the connection for the Private Profile.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
WN12-FW-000012	WN12-FW-000012	WN12-FW-000012_rule		Medium

Description
A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a private network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.

STIG	Date
Microsoft Windows Server 2012 Domain Controller Security Technical Implementation Guide	2013-07-25

Details

Check Text ( C-WN12-FW-000012_chk )
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: \Software\Policies\Microsoft\WindowsFirewall\PrivateProfile\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0 If a third-party firewall is used, verify a comparable setting has been implemented.

Fix Text (F-WN12-FW-000012_fix)
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 -> State, "Outbound connections" to "Allow (default)". Configure a comparable setting if a third-party firewall is used.