acceptedWindows Firewall with Advanced Security Security Technical Implementation GuideThe Windows Firewall with Advanced Security Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
Developed_by_DISA_for_the_DoDDISA, Field Security OperationsSTIG.DOD.MILRelease: 2 Benchmark Date: 24 Apr 20151I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>Windows Firewall Domain - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000001The Windows Firewall with Advanced Security must be enabled when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> State, "Firewall state" to "On (recommended)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile state on".
Or
"Netsh advfirewall set allprofiles state on".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)Windows Firewall Private - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000002The Windows Firewall with Advanced Security must be enabled when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a private network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> State, "Firewall state" to "On (recommended)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile state on".
Or
"Netsh advfirewall set allprofiles state on".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)Windows Firewall Public - Enable Firewall<GroupDescription></GroupDescription>WNFWA-000003The Windows Firewall with Advanced Security must be enabled when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a public network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> State, "Firewall state" to "On (recommended)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile state on".
Or
"Netsh advfirewall set allprofiles state on".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)Windows Firewall Domain - Inbound<GroupDescription></GroupDescription>WNFWA-000004The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked in the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> State, "Inbound connections" to "Block (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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: 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)Windows Firewall Domain - Outbound<GroupDescription></GroupDescription>WNFWA-000005The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed in the domain, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> State, "Outbound connections" to "Allow (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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: 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)Windows Firewall Domain - Display Notifications<GroupDescription></GroupDescription>WNFWA-000006The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection in the domain must be enabled to alert the user of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Settings (select Customize) -> Firewall settings, "Display a notification" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile settings inboundusernotification enable".
Or
"Netsh advfirewall set allprofiles settings inboundusernotification enable".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: 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)Windows Firewall Domain - Unicast Response<GroupDescription></GroupDescription>WNFWA-000007The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages in the domain will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".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: 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)Windows Firewall Domain - Log File<GroupDescription></GroupDescription>WNFWA-000008The Windows Firewall with Advanced Security log file name and location must be configured for domain connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a domain connection will be defined to ensure the logs are maintained.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Logging (select Customize), "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".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\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.Windows Firewall Domain - Log Size<GroupDescription></GroupDescription>WNFWA-000009The Windows Firewall with Advanced Security log size must be configured for domain connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a domain connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Logging (select Customize), "Size limit (KB):" to "16,384" or greater.
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging maxfilesize 16384" or greater.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\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)Windows Firewall Domain - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000010The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a domain connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Logging (select Customize), "Log dropped packets" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".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\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)Windows FW Domain - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000011The Windows Firewall with Advanced Security must log successful connections when connected to a domain.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a domain connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Domain Profile Tab -> Logging (select Customize), "Log successful connections" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set domainprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".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\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)Windows Firewall Private – Inbound<GroupDescription></GroupDescription>WNFWA-000012The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a private network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> State, "Inbound connections" to "Block (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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)Windows Firewall Private - Outbound<GroupDescription></GroupDescription>WNFWA-000013The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a private network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> State, "Outbound connections" to "Allow (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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)Windows Firewall Private - Display Notifications<GroupDescription></GroupDescription>WNFWA-000014The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection on a private network must be enabled to alert the user of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Settings (select Customize) -> Firewall settings, "Display a notification" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile settings inboundusernotification enable".
Or
"Netsh advfirewall set allprofiles settings inboundusernotification enable".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)Windows Firewall Private - Unicast Response<GroupDescription></GroupDescription>WNFWA-000015The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a private connection will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".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)Windows Firewall Private - Log File<GroupDescription></GroupDescription>WNFWA-000016The Windows Firewall with Advanced Security log file name and location must be configured for private network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a private connection will be defined to ensure the logs are maintained.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Logging (select Customize), "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".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.Windows Firewall Private - Log Size<GroupDescription></GroupDescription>WNFWA-000017The Windows Firewall with Advanced Security log size must be configured for private network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a private connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Logging (select Customize), "Size limit (KB)" to "16,384" or greater.
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging maxfilesize 16384" or greater.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)Windows Firewall Private - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000018The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a private network connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Logging (select Customize), "Log dropped packets" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".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)Windows FW Private - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000019The Windows Firewall with Advanced Security must log successful connections when connected to a private network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a private network connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Private Profile Tab -> Logging (select Customize), "Logged successful connections" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set privateprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".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)Windows Firewall Public – Inbound <GroupDescription></GroupDescription>WNFWA-000020The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections, for which there is no rule allowing the connection, will be blocked on a public network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> State, "Inbound connections" to "Block (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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)Windows Firewall Public - Outbound <GroupDescription></GroupDescription>WNFWA-000021The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a public network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> State, "Outbound connections" to "Allow (default)".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound".
Or
"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound".
Both inbound and outbound parameters must be specified to execute this command.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)Windows Firewall Public - Display Notifications<GroupDescription></GroupDescription>WNFWA-000022The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Settings (select Customize) -> 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".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)Windows Firewall Public - Unicast Response<GroupDescription></GroupDescription>WNFWA-000023The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a public network will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Settings (select Customize) -> Unicast response, "Allow unicast response" to "No".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile settings unicastresponsetomulticast disable".
Or
"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable".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)Windows Firewall Public - Local Firewall Rules<GroupDescription></GroupDescription>WNFWA-000024The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local firewall rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565If the system is not a member of a domain, this is NA.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Settings (select Customize) -> Rule merging, "Apply local firewall rules:" to "No".If the system is not a member of a domain, this is NA.
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)Windows Firewall Public - Local Connection Rules<GroupDescription></GroupDescription>WNFWA-000025The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local connection rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565If the system is not a member of a domain, this is NA.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Settings (select Customize) -> Rule merging, "Apply local connection security rules:" to "No".If the system is not a member of a domain, this is NA.
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)Windows Firewall Public - Log File <GroupDescription></GroupDescription>WNFWA-000026The Windows Firewall with Advanced Security log file name and location must be configured for public network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a public network connection will be defined to ensure the logs are maintained.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Logging (select Customize), "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".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.Windows Firewall Public - Log Size<GroupDescription></GroupDescription>WNFWA-000027The Windows Firewall with Advanced Security log size must be configured for public network connections.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a public network connection will be set to ensure enough capacity is allocated for audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Logging (select Customize), "Size limit (KB)" to "16,384" or greater.
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh command may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging maxfilesize 16384" or greater.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)Windows Firewall Public - Log Dropped Packets<GroupDescription></GroupDescription>WNFWA-000028The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a public network connection will be enabled to maintain an audit trail of potential issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Logging (select Customize), "Log dropped packets" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging droppedconnections enable".
Or
"Netsh advfirewall set allprofiles logging droppedconnections enable".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)Windows FW Public - Log Successful Connections<GroupDescription></GroupDescription>WNFWA-000029The Windows Firewall with Advanced Security must log successful connections when connected to a public network.<VulnDiscussion>A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a public network connection will be enabled to maintain an audit trail if issues are discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.
Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Windows Firewall with Advanced Security -> Windows Firewall with Advanced Security -> Windows Firewall Properties (this link will be in the right pane) -> Public Profile Tab -> Logging (select Customize), "Logged successful connections" to "Yes".
In addition to using policies, systems may also be configured using the firewall GUI or Netsh commands. These methods may be more appropriate for standalone systems.
The configuration settings in the GUI are the same as those specified in the policy above. Windows Firewall Properties will be a link in the center pane after opening Windows Firewall with Advanced Security.
The following Netsh commands may also be used to configure this setting:
"Netsh advfirewall set publicprofile logging allowedconnections enable".
Or
"Netsh advfirewall set allprofiles logging allowedconnections enable".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)Inbound Firewall Exception for Administration<GroupDescription></GroupDescription>WNFWA-000100Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.<VulnDiscussion>Allowing inbound access to domain workstations from other systems may allow lateral movement across systems if credentials are compromised. Limiting inbound connections only from authorized remote management systems will help limit this exposure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Windows Firewall with Advanced SecurityDISA FSODPMS TargetWindows Firewall with Advanced Security2565CCI-000366Ensure 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.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.