StigData/Archive/Windows.Firewall/U_Windows_Firewall_STIG_V1R6_Manual-xccdf.xml
|
<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dc="http://purl.org/dc/elements/1.1/" id="Windows_Firewall" xml:lang="en" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2017-01-30">accepted</status><title>Windows Firewall with Advanced Security Security Technical Implementation Guide</title><description>The 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.
</description><notice id="terms-of-use" xml:lang="en">Developed_by_DISA_for_the_DoD</notice><reference href="http://iase.disa.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 6 Benchmark Date: 28 Apr 2017</plain-text><version>1</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-1_Public"><title>I - Mission Critical Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-1_Sensitive"><title>I - Mission Critical Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Classified"><title>II - Mission Support Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Public"><title>II - Mission Support Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-2_Sensitive"><title>II - Mission Support Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Classified"><title>III - Administrative Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Public"><title>III - Administrative Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Profile id="MAC-3_Sensitive"><title>III - Administrative Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-17415" selected="true" /><select idref="V-17416" selected="true" /><select idref="V-17417" selected="true" /><select idref="V-17418" selected="true" /><select idref="V-17419" selected="true" /><select idref="V-17425" selected="true" /><select idref="V-17426" selected="true" /><select idref="V-17427" selected="true" /><select idref="V-17428" selected="true" /><select idref="V-17429" selected="true" /><select idref="V-17435" selected="true" /><select idref="V-17436" selected="true" /><select idref="V-17437" selected="true" /><select idref="V-17438" selected="true" /><select idref="V-17439" selected="true" /><select idref="V-17442" selected="true" /><select idref="V-17443" selected="true" /><select idref="V-17445" selected="true" /><select idref="V-17446" selected="true" /><select idref="V-17447" selected="true" /><select idref="V-36440" selected="true" /></Profile><Group id="V-17415"><title>Windows Firewall Domain - Enable Firewall</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54833r2_rule" severity="medium" weight="10.0"><version>WNFWA-000001</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a domain.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63429r3_fix">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) -> 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".</fixtext><fix id="F-63429r3_fix" /><check system="C-58965r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. 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\DomainProfile\ Value Name: EnableFirewall 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\DomainProfile\ Value Name: EnableFirewall Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17416"><title>Windows Firewall Private - Enable Firewall</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54849r2_rule" severity="medium" weight="10.0"><version>WNFWA-000002</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a private network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63481r1_fix">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 -> 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".</fixtext><fix id="F-63481r1_fix" /><check system="C-58991r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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\ Value Name: EnableFirewall 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\ Value Name: EnableFirewall Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17417"><title>Windows Firewall Public - Enable Firewall</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54855r2_rule" severity="medium" weight="10.0"><version>WNFWA-000003</version><title>The Windows Firewall with Advanced Security must be enabled when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63483r1_fix">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) -> 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".</fixtext><fix id="F-63483r1_fix" /><check system="C-58993r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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\PublicProfile\ Value Name: EnableFirewall 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\PublicProfile\ Value Name: EnableFirewall Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17418"><title>Windows Firewall Domain - Inbound</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54859r3_rule" severity="high" weight="10.0"><version>WNFWA-000004</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63485r1_fix">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) -> 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.</fixtext><fix id="F-63485r1_fix" /><check system="C-61085r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), 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\DomainProfile\ Value Name: DefaultInboundAction 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\DomainProfile\ Value Name: DefaultInboundAction Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17419"><title>Windows Firewall Domain - Outbound</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54863r3_rule" severity="medium" weight="10.0"><version>WNFWA-000005</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63487r1_fix">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) -> 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.</fixtext><fix id="F-63487r1_fix" /><check system="C-61087r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), 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\DomainProfile\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0) 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\DomainProfile\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17425"><title>Windows Firewall Domain - Log Size</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54874r3_rule" severity="low" weight="10.0"><version>WNFWA-000009</version><title>The Windows Firewall with Advanced Security log size must be configured for domain connections.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63495r3_fix">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) -> 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.</fixtext><fix id="F-63495r3_fix" /><check system="C-61095r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), 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\DomainProfile\Logging\ Value Name: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater) 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\DomainProfile\Logging\ Value Name: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17426"><title>Windows Firewall Domain - Log Dropped Packets</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54877r3_rule" severity="low" weight="10.0"><version>WNFWA-000010</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63497r1_fix">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) -> 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".</fixtext><fix id="F-63497r1_fix" /><check system="C-61097r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), 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\DomainProfile\Logging\ Value Name: LogDroppedPackets 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\DomainProfile\Logging\ Value Name: LogDroppedPackets Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17427"><title>Windows FW Domain - Log Successful Connections</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54878r3_rule" severity="low" weight="10.0"><version>WNFWA-000011</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a domain.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63917r1_fix">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) -> 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".</fixtext><fix id="F-63917r1_fix" /><check system="C-61099r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, the Domain Profile requirements can be marked NA. If the system is a member of a domain and the firewall's Domain Profile is not enabled (see V-17415), 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\DomainProfile\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\DomainProfile\Logging\ Value Name: LogSuccessfulConnections Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17428"><title>Windows Firewall Private – Inbound</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54879r3_rule" severity="high" weight="10.0"><version>WNFWA-000012</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63499r1_fix">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 -> 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.</fixtext><fix id="F-63499r1_fix" /><check system="C-61101r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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\ Value Name: DefaultInboundAction 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\ Value Name: DefaultInboundAction Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17429"><title>Windows Firewall Private - Outbound</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54890r3_rule" severity="medium" weight="10.0"><version>WNFWA-000013</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63501r1_fix">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 -> 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.</fixtext><fix id="F-63501r1_fix" /><check system="C-61103r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0) 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\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17435"><title>Windows Firewall Private - Log Size</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54903r3_rule" severity="low" weight="10.0"><version>WNFWA-000017</version><title>The Windows Firewall with Advanced Security log size must be configured for private network connections.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63509r3_fix">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), "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.</fixtext><fix id="F-63509r3_fix" /><check system="C-61111r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater) 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: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17436"><title>Windows Firewall Private - Log Dropped Packets</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54904r3_rule" severity="low" weight="10.0"><version>WNFWA-000018</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63511r1_fix">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), "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".</fixtext><fix id="F-63511r1_fix" /><check system="C-61113r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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: LogDroppedPackets 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: LogDroppedPackets Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17437"><title>Windows FW Private - Log Successful Connections</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54905r3_rule" severity="low" weight="10.0"><version>WNFWA-000019</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a private network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63513r1_fix">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".</fixtext><fix id="F-63513r1_fix" /><check system="C-61115r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>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></check></Rule></Group><Group id="V-17438"><title>Windows Firewall Public – Inbound </title><description><GroupDescription></GroupDescription></description><Rule id="SV-54906r3_rule" severity="high" weight="10.0"><version>WNFWA-000020</version><title>The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63515r1_fix">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) -> 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.</fixtext><fix id="F-63515r1_fix" /><check system="C-61117r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), 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\PublicProfile\ Value Name: DefaultInboundAction 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\PublicProfile\ Value Name: DefaultInboundAction Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17439"><title>Windows Firewall Public - Outbound </title><description><GroupDescription></GroupDescription></description><Rule id="SV-54908r3_rule" severity="medium" weight="10.0"><version>WNFWA-000021</version><title>The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63517r1_fix">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) -> 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.</fixtext><fix id="F-63517r1_fix" /><check system="C-61121r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), 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\PublicProfile\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0) 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\PublicProfile\ Value Name: DefaultOutboundAction Type: REG_DWORD Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17442"><title>Windows Firewall Public - Local Firewall Rules</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54917r3_rule" severity="medium" weight="10.0"><version>WNFWA-000024</version><title>The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63523r1_fix">If 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".</fixtext><fix id="F-63523r1_fix" /><check system="C-61129r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, this is NA. If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding. Verify the registry value below. If this 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\PublicProfile\ Value Name: AllowLocalPolicyMerge Type: REG_DWORD Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17443"><title>Windows Firewall Public - Local Connection Rules</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54918r3_rule" severity="medium" weight="10.0"><version>WNFWA-000025</version><title>The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63525r1_fix">If 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".</fixtext><fix id="F-63525r1_fix" /><check system="C-61133r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the system is not a member of a domain, this is NA. If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding. Verify the registry value below. If this 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\PublicProfile\ Value Name: AllowLocalIPsecPolicyMerge Type: REG_DWORD Value: 0x00000000 (0)</check-content></check></Rule></Group><Group id="V-17445"><title>Windows Firewall Public - Log Size</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54921r3_rule" severity="low" weight="10.0"><version>WNFWA-000027</version><title>The Windows Firewall with Advanced Security log size must be configured for public network connections.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63529r2_fix">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) -> 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.</fixtext><fix id="F-63529r2_fix" /><check system="C-61137r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), 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\PublicProfile\Logging\ Value Name: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater) 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\PublicProfile\Logging\ Value Name: LogFileSize Type: REG_DWORD Value: 0x00004000 (16384) (or greater)</check-content></check></Rule></Group><Group id="V-17446"><title>Windows Firewall Public - Log Dropped Packets</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54922r3_rule" severity="low" weight="10.0"><version>WNFWA-000028</version><title>The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63531r1_fix">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) -> 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".</fixtext><fix id="F-63531r1_fix" /><check system="C-61141r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), 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\PublicProfile\Logging\ Value Name: LogDroppedPackets 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\PublicProfile\Logging\ Value Name: LogDroppedPackets Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-17447"><title>Windows FW Public - Log Successful Connections</title><description><GroupDescription></GroupDescription></description><Rule id="SV-54923r3_rule" severity="low" weight="10.0"><version>WNFWA-000029</version><title>The Windows Firewall with Advanced Security must log successful connections when connected to a public network.</title><description><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></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><fixtext fixref="F-63533r1_fix">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) -> 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".</fixtext><fix id="F-63533r1_fix" /><check system="C-61143r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>If the firewall's Public Profile is not enabled (see V-17417), 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\PublicProfile\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\PublicProfile\Logging\ Value Name: LogSuccessfulConnections Type: REG_DWORD Value: 0x00000001 (1)</check-content></check></Rule></Group><Group id="V-36440"><title>Inbound Firewall Exception for Administration</title><description><GroupDescription></GroupDescription></description><Rule id="SV-55086r1_rule" severity="medium" weight="10.0"><version>WNFWA-000100</version><title>Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.</title><description><VulnDiscussion>Allowing inbound access to domain workstations from other systems may allow lateral movement across systems if credentials are compromised. Limiting inbound connections only from authorized remote management systems will help limit this exposure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls></description><reference><dc:title>DPMS Target Windows Firewall with Advanced Security</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Windows Firewall with Advanced Security</dc:subject><dc:identifier>2565</dc:identifier></reference><ident system="http://iase.disa.mil/cci">CCI-000366</ident><fixtext fixref="F-47957r2_fix">Ensure firewall exceptions to inbound connections on domain workstations only allow authorized management systems and remote management hosts. Firewall rules can be complex and should be thoroughly tested before applying in a production environment. One method for restricting inbound connections is to only allow exceptions for a specific scope of remote IP addresses. For any inbound rules that allow connections from other systems, configure the Scope for Remote IP addresses to those of authorized management systems and remote management hosts. This may be defined as an IP address, subnet, or range. Apply the rule to all firewall profiles.</fixtext><fix id="F-47957r2_fix" /><check system="C-48768r1_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_Windows_Firewall.xml" /><check-content>This requirement is NA for servers and non domain workstations. Verify firewall exceptions for inbound connections on domain workstations only allow authorized management systems and remote management hosts. Review inbound firewall exception rules in Windows Firewall with Advanced Security. Firewall rules can be complex and should be reviewed with the firewall administrator. One method for restricting inbound connections is to only allow exceptions for a specific scope of remote IP addresses. If allowed inbound exceptions are not limited to authorized management systems and remote management hosts, this is a finding.</check-content></check></Rule></Group></Benchmark> |