Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Windows Firewall with Advanced Security Security Technical Implementation Guide

V1R3 · · · Released 24 Jul 2015 · 30 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Sort by
b
The Windows Firewall with Advanced Security must be enabled when connected to a domain.
Medium - V-17415 - SV-54833r2_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000001
Vuln IDs
  • V-17415
Rule IDs
  • SV-54833r2_rule
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.ECSC-1
Checks: C-58965r1_chk

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)

Fix: 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".

b
The Windows Firewall with Advanced Security must be enabled when connected to a private network.
Medium - V-17416 - SV-54849r2_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000002
Vuln IDs
  • V-17416
Rule IDs
  • SV-54849r2_rule
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.ECSC-1
Checks: C-58991r1_chk

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)

Fix: 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".

b
The Windows Firewall with Advanced Security must be enabled when connected to a public network.
Medium - V-17417 - SV-54855r2_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000003
Vuln IDs
  • V-17417
Rule IDs
  • SV-54855r2_rule
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.ECSC-1
Checks: C-58993r1_chk

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)

Fix: 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".

c
The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.
High - V-17418 - SV-54859r3_rule
RMF Control
Severity
H
CCI
Version
WNFWA-000004
Vuln IDs
  • V-17418
Rule IDs
  • SV-54859r3_rule
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.ECSC-1
Checks: C-61085r1_chk

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)

Fix: 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.

b
The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.
Medium - V-17419 - SV-54863r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000005
Vuln IDs
  • V-17419
Rule IDs
  • SV-54863r3_rule
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.ECSC-1
Checks: C-61087r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a domain.
Low - V-17420 - SV-54866r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000006
Vuln IDs
  • V-17420
Rule IDs
  • SV-54866r3_rule
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.ECSC-1
Checks: C-61089r1_chk

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: DisableNotifications 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: DisableNotifications Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-63489r1_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 -> 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".

b
The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a domain.
Medium - V-17421 - SV-54867r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000007
Vuln IDs
  • V-17421
Rule IDs
  • SV-54867r3_rule
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.ECSC-1
Checks: C-61091r1_chk

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: DisableUnicastResponsesToMulticastBroadcast 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: DisableUnicastResponsesToMulticastBroadcast Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-63491r1_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 -> 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".

a
The Windows Firewall with Advanced Security log file name and location must be configured for domain connections.
Low - V-17424 - SV-54870r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000008
Vuln IDs
  • V-17424
Rule IDs
  • SV-54870r3_rule
A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a domain connection will be defined to ensure the logs are maintained.ECSC-1
Checks: C-61093r1_chk

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: LogFilePath Type: REG_SZ Value: %windir%\system32\logfiles\firewall\domainfirewall.log 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: LogFilePath Type: REG_EXPAND_SZ Value: %windir%\system32\logfiles\firewall\domainfirewall.log Automated tools may search for the file name specified in the check. If the site uses a different name for the log file, the finding will need to be closed manually.

Fix: F-63493r1_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), "Name" to "%windir%\system32\logfiles\firewall\domainfirewall.log". 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 filename %windir%\system32\LogFiles\Firewall\domainfw.log".

a
The Windows Firewall with Advanced Security log size must be configured for domain connections.
Low - V-17425 - SV-54874r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000009
Vuln IDs
  • V-17425
Rule IDs
  • SV-54874r3_rule
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.ECSC-1
Checks: C-61095r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.
Low - V-17426 - SV-54877r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000010
Vuln IDs
  • V-17426
Rule IDs
  • SV-54877r3_rule
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.ECSC-1
Checks: C-61097r1_chk

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)

Fix: 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".

a
The Windows Firewall with Advanced Security must log successful connections when connected to a domain.
Low - V-17427 - SV-54878r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000011
Vuln IDs
  • V-17427
Rule IDs
  • SV-54878r3_rule
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.ECSC-1
Checks: C-61099r1_chk

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)

Fix: 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".

c
The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.
High - V-17428 - SV-54879r3_rule
RMF Control
Severity
H
CCI
Version
WNFWA-000012
Vuln IDs
  • V-17428
Rule IDs
  • SV-54879r3_rule
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.ECSC-1
Checks: C-61101r1_chk

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)

Fix: 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.

b
The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.
Medium - V-17429 - SV-54890r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000013
Vuln IDs
  • V-17429
Rule IDs
  • SV-54890r3_rule
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.ECSC-1
Checks: C-61103r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a private network.
Low - V-17430 - SV-54891r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000014
Vuln IDs
  • V-17430
Rule IDs
  • SV-54891r3_rule
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.ECSC-1
Checks: C-61105r1_chk

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: DisableNotifications 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: DisableNotifications Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-63503r1_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 -> 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".

b
The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a private network.
Medium - V-17431 - SV-54892r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000015
Vuln IDs
  • V-17431
Rule IDs
  • SV-54892r3_rule
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.ECSC-1
Checks: C-61107r1_chk

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: DisableUnicastResponsesToMulticastBroadcast 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: DisableUnicastResponsesToMulticastBroadcast Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-63505r1_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 -> 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".

a
The Windows Firewall with Advanced Security log file name and location must be configured for private network connections.
Low - V-17434 - SV-54902r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000016
Vuln IDs
  • V-17434
Rule IDs
  • SV-54902r3_rule
A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a private connection will be defined to ensure the logs are maintained.ECSC-1
Checks: C-61109r1_chk

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: LogFilePath Type: REG_SZ Value: %windir%\system32\logfiles\firewall\privatefirewall.log 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: LogFilePath Type: REG_EXPAND_SZ Value: %windir%\system32\logfiles\firewall\privatefirewall.log Automated tools may search for the file name specified in the check. If the site uses a different name for the log file, the finding will need to be closed manually.

Fix: F-63507r1_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), "Name" to "%windir%\system32\logfiles\firewall\privatefirewall.log". 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 filename %windir%\system32\LogFiles\Firewall\privatefw.log".

a
The Windows Firewall with Advanced Security log size must be configured for private network connections.
Low - V-17435 - SV-54903r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000017
Vuln IDs
  • V-17435
Rule IDs
  • SV-54903r3_rule
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.ECSC-1
Checks: C-61111r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.
Low - V-17436 - SV-54904r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000018
Vuln IDs
  • V-17436
Rule IDs
  • SV-54904r3_rule
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.ECSC-1
Checks: C-61113r1_chk

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)

Fix: 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".

a
The Windows Firewall with Advanced Security must log successful connections when connected to a private network.
Low - V-17437 - SV-54905r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000019
Vuln IDs
  • V-17437
Rule IDs
  • SV-54905r3_rule
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.ECSC-1
Checks: C-61115r1_chk

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)

Fix: 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".

c
The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.
High - V-17438 - SV-54906r3_rule
RMF Control
Severity
H
CCI
Version
WNFWA-000020
Vuln IDs
  • V-17438
Rule IDs
  • SV-54906r3_rule
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.ECSC-1
Checks: C-61117r1_chk

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)

Fix: 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.

b
The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.
Medium - V-17439 - SV-54908r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000021
Vuln IDs
  • V-17439
Rule IDs
  • SV-54908r3_rule
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.ECSC-1
Checks: C-61121r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a public network.
Low - V-17440 - SV-54910r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000022
Vuln IDs
  • V-17440
Rule IDs
  • SV-54910r3_rule
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 public network must be enabled to alert the user of potential issues.ECSC-1
Checks: C-61123r1_chk

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: DisableNotifications 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: DisableNotifications Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-63519r1_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 -> 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 publicprofile settings inboundusernotification enable". Or "Netsh advfirewall set allprofiles settings inboundusernotification enable".

b
The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a public network.
Medium - V-17441 - SV-54912r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000023
Vuln IDs
  • V-17441
Rule IDs
  • SV-54912r3_rule
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.ECSC-1
Checks: C-61127r1_chk

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: DisableUnicastResponsesToMulticastBroadcast 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: DisableUnicastResponsesToMulticastBroadcast Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-63521r1_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 -> 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".

b
The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.
Medium - V-17442 - SV-54917r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000024
Vuln IDs
  • V-17442
Rule IDs
  • SV-54917r3_rule
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.ECSC-1
Checks: C-61129r1_chk

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)

Fix: 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".

b
The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.
Medium - V-17443 - SV-54918r3_rule
RMF Control
Severity
M
CCI
Version
WNFWA-000025
Vuln IDs
  • V-17443
Rule IDs
  • SV-54918r3_rule
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.ECSC-1
Checks: C-61133r1_chk

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)

Fix: 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".

a
The Windows Firewall with Advanced Security log file name and location must be configured for public network connections.
Low - V-17444 - SV-54919r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000026
Vuln IDs
  • V-17444
Rule IDs
  • SV-54919r3_rule
A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a public network connection will be defined to ensure the logs are maintained.ECSC-1
Checks: C-61135r1_chk

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: LogFilePath Type: REG_SZ Value: %windir%\system32\logfiles\firewall\publicfirewall.log 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: LogFilePath Type: REG_EXPAND_SZ Value: %windir%\system32\logfiles\firewall\publicfirewall.log Automated tools may search for the file name specified in the check. If the site uses a different name for the log file, the finding will need to be closed manually.

Fix: F-63527r1_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), "Name" to "%windir%\system32\logfiles\firewall\publicfirewall.log". 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 filename %windir%\system32\LogFiles\Firewall\publicfw.log".

a
The Windows Firewall with Advanced Security log size must be configured for public network connections.
Low - V-17445 - SV-54921r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000027
Vuln IDs
  • V-17445
Rule IDs
  • SV-54921r3_rule
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.ECSC-1
Checks: C-61137r1_chk

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)

Fix: 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.

a
The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.
Low - V-17446 - SV-54922r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000028
Vuln IDs
  • V-17446
Rule IDs
  • SV-54922r3_rule
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.ECSC-1
Checks: C-61141r1_chk

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)

Fix: 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".

a
The Windows Firewall with Advanced Security must log successful connections when connected to a public network.
Low - V-17447 - SV-54923r3_rule
RMF Control
Severity
L
CCI
Version
WNFWA-000029
Vuln IDs
  • V-17447
Rule IDs
  • SV-54923r3_rule
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.ECSC-1
Checks: C-61143r1_chk

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)

Fix: 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".

b
Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.
CM-6 - Medium - CCI-000366 - V-36440 - SV-55086r1_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
WNFWA-000100
Vuln IDs
  • V-36440
Rule IDs
  • SV-55086r1_rule
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.ECSC-1
Checks: C-48768r1_chk

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.

Fix: 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.