acceptedWindows Firewall with Advanced Security Security Technical Implementation GuideThe Windows Firewall with Advanced Security Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.Developed_by_DISA_for_the_DoDDISASTIG.DOD.MILRelease: 5 Benchmark Date: 28 Oct 20161DISADISADISASTIG.DOD.MILI - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>CAT I OnlyThis profile only includes rules that are Severity Category I.public_profile_size_limit_varFirewall log file size for a public network connection1638416384Outbound ConnectionsThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.001public_profile_logged_successful_connections_varEnables logging of successful connections for a public network connection101public_profile_log_dropped_packets_varEnable logging of dropped packets for a public network connection101Inbound ConnectionsThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.101Firewall stateThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.101Apply Local Firewall RulesThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.001Apply Local Connection Security RulesThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.001private_profile_size_limit_varFirewall log file size for a private network connection1638416384Outbound ConnectionsThe Private Profile is used only if a local administrator changes the profile for a computer connected previously to a public network (using a Public Profile).001private_profile_logged_successful_connections_varEnable logging of successful connections for a private network connection101private_profile_log_dropped_packets_varEnable logging of dropped packets for a private network connection101Inbound ConnectionsThe Private Profile is used only if a local administrator changes the profile for a computer connected previously to a public network (using a Public Profile).101Firewall stateEnable the firewall when connected to a private network101Display a NotificationThe Private Profile is used only if a local administrator changes the profile for a computer connected previously to a public network (using a Public Profile).001Allow Unicast ResponseThe Private Profile is used only if a local administrator changes the profile for a computer connected previously to a public network (using a Public Profile).101domain_profile_size_limit_varFirewall log file size for a domain connection.1638416384Outbound ConnectionsThe Domain Profile is used when the computer is connected to a network and is authenticated to a domain controller.001domain_profile_logged_successful_connections_varEnables logging of successful connections for a domain connection.101domain_profile_log_dropped_packets_varEnables logging of dropped packets for a domain connection.101Inbound ConnectionsThe Domain Profile is used when the computer is connected to a network and is authenticated to a domain controller.101Firewall stateThe Domain Profile is used when the computer is connected to a network and is authenticated to a domain controller.101Display a NotificationThe Domain Profile is used when the computer is connected to a network and is authenticated to a domain controller.001Allow Unicast ResponseThe Domain Profile is used when the computer is connected to a network and is authenticated to a domain controller.101Allow Unicast ResponseThe Public Profile is the default profile for a computer connected to a public network but not connected to a domain controller. This should be the most restricted profile.101Windows Firewall Domain - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000001The Windows Firewall with Advanced Security must be enabled when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> State, "Firewall state" to "On (recommended)".
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 domainprofile state on".
Or
"Netsh advfirewall set allprofiles state on".Windows Firewall Private - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000002The Windows Firewall with Advanced Security must be enabled when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a private network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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 -> State, "Firewall state" to "On (recommended)".
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 state on".
Or
"Netsh advfirewall set allprofiles state on".Windows Firewall Public - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000003The Windows Firewall with Advanced Security must be enabled when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a public network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> State, "Firewall state" to "On (recommended)".
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 publicprofile state on".
Or
"Netsh advfirewall set allprofiles state on".Windows Firewall Domain - Inbound<GroupDescription></GroupDescription>WNFWA-000004The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked in the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> State, "Inbound connections" to "Block (default)".
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 domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Domain - Outbound<GroupDescription></GroupDescription>WNFWA-000005The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed in the domain, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> State, "Outbound connections" to "Allow (default)".
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 domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Domain - Display Notifications<GroupDescription></GroupDescription>WNFWA-000006The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection in the domain must be enabled to alert the user of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> Settings (select Customize) -> Firewall settings, "Display a notification" 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 domainprofile settings inboundusernotification enable".
Or
"Netsh advfirewall set allprofiles settings inboundusernotification enable".Windows Firewall Domain - Unicast Response<GroupDescription></GroupDescription>WNFWA-000007The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages in the domain will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
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 domainprofile settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".Windows Firewall Domain - Log Size<GroupDescription></GroupDescription>WNFWA-000009The Windows Firewall with Advanced Security log size must be configured for domain connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a domain connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> Logging (select Customize), "Size limit (KB):" to "16,384" or greater.
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 command may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging maxfilesize 16384" or greater.Windows Firewall Domain - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000010The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a domain connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> Logging (select Customize), "Log dropped packets" 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 domainprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".Windows FW Domain - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000011The Windows Firewall with Advanced Security must log successful connections when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a domain connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Domain Profile Tab -> Logging (select Customize), "Log 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 domainprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".Windows Firewall Private – Inbound<GroupDescription></GroupDescription>WNFWA-000012The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a private network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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 -> State, "Inbound connections" to "Block (default)".
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 firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Private - Outbound<GroupDescription></GroupDescription>WNFWA-000013The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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 -> State, "Outbound connections" to "Allow (default)".
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 firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Private - Display Notifications<GroupDescription></GroupDescription>WNFWA-000014The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection on a private network must be enabled to alert the user of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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 -> Settings (select Customize) -> Firewall settings, "Display a notification" 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 settings inboundusernotification enable".
Or
"Netsh advfirewall set allprofiles settings inboundusernotification enable".Windows Firewall Private - Unicast Response<GroupDescription></GroupDescription>WNFWA-000015The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a private connection will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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 -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
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 settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".Windows Firewall Private - Log Size<GroupDescription></GroupDescription>WNFWA-000017The Windows Firewall with Advanced Security log size must be configured for private network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a private connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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), "Size limit (KB)" to "16,384" or greater.
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 command may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging maxfilesize 16384" or greater.Windows Firewall Private - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000018The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a private network connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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), "Log dropped packets" 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 droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".Windows FW Private - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000019The Windows Firewall with Advanced Security must log successful connections when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a private network connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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".Windows Firewall Public – Inbound<GroupDescription></GroupDescription>WNFWA-000020The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a public network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> State, "Inbound connections" to "Block (default)".
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 publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Public - Outbound<GroupDescription></GroupDescription>WNFWA-000021The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.<VulnDiscussion>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 public network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> State, "Outbound connections" to "Allow (default)".
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 publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.Windows Firewall Public - Unicast Response<GroupDescription></GroupDescription>WNFWA-000023The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a public network will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
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 publicprofile settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".Windows Firewall Public - Local Firewall Rules<GroupDescription></GroupDescription>WNFWA-000024The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local firewall rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565If the system is not a member of a domain, this is NA.
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) -> Public Profile Tab -> Settings (select Customize) -> Rule merging, "Apply local firewall rules:" to "No".Windows Firewall Public - Local Connection Rules<GroupDescription></GroupDescription>WNFWA-000025The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local connection rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565If the system is not a member of a domain, this is NA.
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) -> Public Profile Tab -> Settings (select Customize) -> Rule merging, "Apply local connection security rules:" to "No".Windows Firewall Public - Log Size<GroupDescription></GroupDescription>WNFWA-000027The Windows Firewall with Advanced Security log size must be configured for public network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a public network connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> Logging (select Customize), "Size limit (KB)" to "16,384" or greater.
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 command may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging maxfilesize 16384" or greater.Windows Firewall Public - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000028The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a public network connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public Profile Tab -> Logging (select Customize), "Log dropped packets" 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 publicprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".Windows FW Public - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000029The Windows Firewall with Advanced Security must log successful connections when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a public network connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows Firewall with Advanced SecurityDISADPMS TargetWindows Firewall with Advanced Security2565The 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) -> Public 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 publicprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".