{
"stig": {
"date": "2015-06-03",
"description": "The Windows Firewall with Advanced Security Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.\n",
"findings": {
"V-17415": {
"checkid": "C-58965r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63429r3_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile state on\".\nOr\n\"Netsh advfirewall set allprofiles state on\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17415",
"ruleID": "SV-54833r2_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must be enabled when connected to a domain.",
"version": "WNFWA-000001"
},
"V-17416": {
"checkid": "C-58991r1_chk",
"checktext": "If the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63481r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile state on\".\nOr\n\"Netsh advfirewall set allprofiles state on\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17416",
"ruleID": "SV-54849r2_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must be enabled when connected to a private network.",
"version": "WNFWA-000002"
},
"V-17417": {
"checkid": "C-58993r1_chk",
"checktext": "If the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\\n\nValue Name: EnableFirewall\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63483r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile state on\".\nOr\n\"Netsh advfirewall set allprofiles state on\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17417",
"ruleID": "SV-54855r2_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must be enabled when connected to a public network.",
"version": "WNFWA-000003"
},
"V-17418": {
"checkid": "C-61085r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63485r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17418",
"ruleID": "SV-54859r3_rule",
"severity": "high",
"title": "The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a domain.",
"version": "WNFWA-000004"
},
"V-17419": {
"checkid": "C-61087r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63487r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17419",
"ruleID": "SV-54863r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a domain.",
"version": "WNFWA-000005"
},
"V-17420": {
"checkid": "C-61089r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD\nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63489r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile settings inboundusernotification enable\".\nOr\n\"Netsh advfirewall set allprofiles settings inboundusernotification enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17420",
"ruleID": "SV-54866r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a domain.",
"version": "WNFWA-000006"
},
"V-17421": {
"checkid": "C-61091r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63491r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile settings unicastresponsetomulticast disable\".\nOr\n\"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17421",
"ruleID": "SV-54867r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a domain.",
"version": "WNFWA-000007"
},
"V-17424": {
"checkid": "C-61093r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\domainfirewall.log\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_EXPAND_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\domainfirewall.log\n\nAutomated 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.",
"description": "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.",
"fixid": "F-63493r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile logging filename %windir%\\system32\\LogFiles\\Firewall\\domainfw.log\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17424",
"ruleID": "SV-54870r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log file name and location must be configured for domain connections.",
"version": "WNFWA-000008"
},
"V-17425": {
"checkid": "C-61095r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)",
"description": "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.",
"fixid": "F-63495r3_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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.\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile logging maxfilesize 16384\" or greater.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17425",
"ruleID": "SV-54874r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log size must be configured for domain connections.",
"version": "WNFWA-000009"
},
"V-17426": {
"checkid": "C-61097r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63497r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile logging droppedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging droppedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17426",
"ruleID": "SV-54877r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log dropped packets when connected to a domain.",
"version": "WNFWA-000010"
},
"V-17427": {
"checkid": "C-61099r1_chk",
"checktext": "If the system is not a member of a domain, the Domain Profile requirements can be marked NA.\n\nIf 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.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\DomainProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63917r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set domainprofile logging allowedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging allowedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17427",
"ruleID": "SV-54878r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log successful connections when connected to a domain.",
"version": "WNFWA-000011"
},
"V-17428": {
"checkid": "C-61101r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63499r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17428",
"ruleID": "SV-54879r3_rule",
"severity": "high",
"title": "The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a private network.",
"version": "WNFWA-000012"
},
"V-17429": {
"checkid": "C-61103r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63501r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17429",
"ruleID": "SV-54890r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a private network.",
"version": "WNFWA-000013"
},
"V-17430": {
"checkid": "C-61105r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD \nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63503r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile settings inboundusernotification enable\".\nOr\n\"Netsh advfirewall set allprofiles settings inboundusernotification enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17430",
"ruleID": "SV-54891r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a private network.",
"version": "WNFWA-000014"
},
"V-17431": {
"checkid": "C-61107r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63505r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile settings unicastresponsetomulticast disable\".\nOr\n\"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17431",
"ruleID": "SV-54892r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a private network.",
"version": "WNFWA-000015"
},
"V-17434": {
"checkid": "C-61109r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\privatefirewall.log\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_EXPAND_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\privatefirewall.log\n\nAutomated 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.",
"description": "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.",
"fixid": "F-63507r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile logging filename %windir%\\system32\\LogFiles\\Firewall\\privatefw.log\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17434",
"ruleID": "SV-54902r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log file name and location must be configured for private network connections.",
"version": "WNFWA-000016"
},
"V-17435": {
"checkid": "C-61111r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)",
"description": "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.",
"fixid": "F-63509r3_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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.\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile logging maxfilesize 16384\" or greater.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17435",
"ruleID": "SV-54903r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log size must be configured for private network connections.",
"version": "WNFWA-000017"
},
"V-17436": {
"checkid": "C-61113r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63511r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile logging droppedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging droppedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17436",
"ruleID": "SV-54904r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log dropped packets when connected to a private network.",
"version": "WNFWA-000018"
},
"V-17437": {
"checkid": "C-61115r1_chk",
"checktext": "If the firewall's Private Profile is not enabled (see V-17416), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PrivateProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63513r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set privateprofile logging allowedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging allowedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17437",
"ruleID": "SV-54905r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log successful connections when connected to a private network.",
"version": "WNFWA-000019"
},
"V-17438": {
"checkid": "C-61117r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\\n\nValue Name: DefaultInboundAction\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63515r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17438",
"ruleID": "SV-54906r3_rule",
"severity": "high",
"title": "The Windows Firewall with Advanced Security must block unsolicited inbound connections when connected to a public network.",
"version": "WNFWA-000020"
},
"V-17439": {
"checkid": "C-61121r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\\n\nValue Name: DefaultOutboundAction\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63517r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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)\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound\".\nOr\n\"Netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound\".\nBoth inbound and outbound parameters must be specified to execute this command.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17439",
"ruleID": "SV-54908r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must allow outbound connections, unless a rule explicitly blocks the connection when connected to a public network.",
"version": "WNFWA-000021"
},
"V-17440": {
"checkid": "C-61123r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD\nValue: 0x00000000 (0)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\\n\nValue Name: DisableNotifications\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63519r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile settings inboundusernotification enable\".\nOr\n\"Netsh advfirewall set allprofiles settings inboundusernotification enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17440",
"ruleID": "SV-54910r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must display notifications when a program is blocked from receiving an inbound connection when connected to a public network.",
"version": "WNFWA-000022"
},
"V-17441": {
"checkid": "C-61127r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\\n\nValue Name: DisableUnicastResponsesToMulticastBroadcast\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63521r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile settings unicastresponsetomulticast disable\".\nOr\n\"Netsh advfirewall set allprofiles settings unicastresponsetomulticast disable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17441",
"ruleID": "SV-54912r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security must block unicast responses to multicast or broadcast messages when connected to a public network.",
"version": "WNFWA-000023"
},
"V-17442": {
"checkid": "C-61129r1_chk",
"checktext": "If the system is not a member of a domain, this is NA.\n\nIf the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nVerify the registry value below.\n\nIf this registry value does not exist or is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: AllowLocalPolicyMerge\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63523r1_fix",
"fixtext": "If the system is not a member of a domain, this is NA.\n\nConfigure 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\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17442",
"ruleID": "SV-54917r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security local firewall rules must not be merged with Group Policy settings when connected to a public network.",
"version": "WNFWA-000024"
},
"V-17443": {
"checkid": "C-61133r1_chk",
"checktext": "If the system is not a member of a domain, this is NA.\n\nIf the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nVerify the registry value below.\n\nIf this registry value does not exist or is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\\n\nValue Name: AllowLocalIPsecPolicyMerge\n\nType: REG_DWORD\nValue: 0x00000000 (0)",
"description": "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.",
"fixid": "F-63525r1_fix",
"fixtext": "If the system is not a member of a domain, this is NA.\n\nConfigure 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\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17443",
"ruleID": "SV-54918r3_rule",
"severity": "medium",
"title": "The Windows Firewall with Advanced Security local connection rules must not be merged with Group Policy settings when connected to a public network.",
"version": "WNFWA-000025"
},
"V-17444": {
"checkid": "C-61135r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\publicfirewall.log\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\Logging\\\n\nValue Name: LogFilePath\n\nType: REG_EXPAND_SZ\nValue: %windir%\\system32\\logfiles\\firewall\\publicfirewall.log\n\nAutomated 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.",
"description": "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.",
"fixid": "F-63527r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile logging filename %windir%\\system32\\LogFiles\\Firewall\\publicfw.log\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17444",
"ruleID": "SV-54919r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log file name and location must be configured for public network connections.",
"version": "WNFWA-000026"
},
"V-17445": {
"checkid": "C-61137r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\Logging\\\n\nValue Name: LogFileSize\n\nType: REG_DWORD\nValue: 0x00004000 (16384) (or greater)",
"description": "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.",
"fixid": "F-63529r2_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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.\n\nIn 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.\nThe 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.\n\nThe following Netsh command may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile logging maxfilesize 16384\" or greater.",
"iacontrols": [
"ECSC-1"
],
"id": "V-17445",
"ruleID": "SV-54921r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security log size must be configured for public network connections.",
"version": "WNFWA-000027"
},
"V-17446": {
"checkid": "C-61141r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\Logging\\\n\nValue Name: LogDroppedPackets\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63531r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile logging droppedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging droppedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17446",
"ruleID": "SV-54922r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log dropped packets when connected to a public network.",
"version": "WNFWA-000028"
},
"V-17447": {
"checkid": "C-61143r1_chk",
"checktext": "If the firewall's Public Profile is not enabled (see V-17417), this requirement is also a finding.\n\nIf the following policy-based registry value exists and is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\PublicProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)\n\nIf the policy-based registry value does not exist, verify the following registry value. If it is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile\\Logging\\\n\nValue Name: LogSuccessfulConnections\n\nType: REG_DWORD\nValue: 0x00000001 (1)",
"description": "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.",
"fixid": "F-63533r1_fix",
"fixtext": "The preferred method of configuring the firewall settings is with a policy, particularly in a domain environment.\n\nConfigure 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\".\n\nIn 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.\nThe 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.\n\nThe following Netsh commands may also be used to configure this setting:\n\"Netsh advfirewall set publicprofile logging allowedconnections enable\".\nOr\n\"Netsh advfirewall set allprofiles logging allowedconnections enable\".",
"iacontrols": [
"ECSC-1"
],
"id": "V-17447",
"ruleID": "SV-54923r3_rule",
"severity": "low",
"title": "The Windows Firewall with Advanced Security must log successful connections when connected to a public network.",
"version": "WNFWA-000029"
},
"V-36440": {
"checkid": "C-48768r1_chk",
"checktext": "This requirement is NA for servers and non domain workstations.\n\nVerify firewall exceptions for inbound connections on domain workstations only allow authorized management systems and remote management hosts.\n\nReview inbound firewall exception rules in Windows Firewall with Advanced Security. Firewall rules can be complex and should be reviewed with the firewall administrator.\n\nOne method for restricting inbound connections is to only allow exceptions for a specific scope of remote IP addresses.\n\nIf allowed inbound exceptions are not limited to authorized management systems and remote management hosts, this is a finding.",
"description": "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.",
"fixid": "F-47957r2_fix",
"fixtext": "Ensure firewall exceptions to inbound connections on domain workstations only allow authorized management systems and remote management hosts.\n\nFirewall rules can be complex and should be thoroughly tested before applying in a production environment.\n\nOne 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.",
"iacontrols": [
"ECSC-1"
],
"id": "V-36440",
"ruleID": "SV-55086r1_rule",
"severity": "medium",
"title": "Inbound exceptions to the firewall on domain workstations must only allow authorized remote management hosts.",
"version": "WNFWA-000100"
}
},
"profiles": {
"MAC-1_Classified": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-1_Classified",
"title": "I - Mission Critical Classified"
},
"MAC-1_Public": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-1_Public",
"title": "I - Mission Critical Public"
},
"MAC-1_Sensitive": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-1_Sensitive",
"title": "I - Mission Critical Sensitive"
},
"MAC-2_Classified": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-2_Classified",
"title": "II - Mission Support Classified"
},
"MAC-2_Public": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-2_Public",
"title": "II - Mission Support Public"
},
"MAC-2_Sensitive": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-2_Sensitive",
"title": "II - Mission Support Sensitive"
},
"MAC-3_Classified": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-3_Classified",
"title": "III - Administrative Classified"
},
"MAC-3_Public": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-3_Public",
"title": "III - Administrative Public"
},
"MAC-3_Sensitive": {
"description": "",
"findings": {
"V-17415": "true",
"V-17416": "true",
"V-17417": "true",
"V-17418": "true",
"V-17419": "true",
"V-17420": "true",
"V-17421": "true",
"V-17424": "true",
"V-17425": "true",
"V-17426": "true",
"V-17427": "true",
"V-17428": "true",
"V-17429": "true",
"V-17430": "true",
"V-17431": "true",
"V-17434": "true",
"V-17435": "true",
"V-17436": "true",
"V-17437": "true",
"V-17438": "true",
"V-17439": "true",
"V-17440": "true",
"V-17441": "true",
"V-17442": "true",
"V-17443": "true",
"V-17444": "true",
"V-17445": "true",
"V-17446": "true",
"V-17447": "true",
"V-36440": "true"
},
"id": "MAC-3_Sensitive",
"title": "III - Administrative Sensitive"
}
},
"slug": "windows_firewall_with_advanced_security",
"title": "Windows Firewall with Advanced Security Security Technical Implementation Guide",
"version": "1"
}
}