Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender Firewall Properties (this link will be in the right pane) >> Public Profile tab >> Settings (select Customize) >> Rule merging, "Apply local firewall rules:" to "No".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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".
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)
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 >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender Firewall with Advanced Security >> Microsoft Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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.
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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)
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 Defender Firewall with Advanced Security >> Windows Defender Firewall with Advanced Security >> Windows Defender 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. Microsoft Defender Firewall Properties will be a link in the center pane after opening Microsoft Defender 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".
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 Microsoft Defender 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.
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.