Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-17391 | 5.403 | SV-18447r1_rule | ECSC-1 | Medium |
Description |
---|
Only Inbound ICMP echo requests will be allowed when connected to the domain. |
STIG | Date |
---|---|
Windows XP Security Technical Implementation Guide | 2012-08-22 |
Check Text ( C-18098r1_chk ) |
---|
If the following registry values don’t exist or are not configured as specified, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile\IcmpSettings\ Type: REG_DWORD (for all) Value Name: AllowInboundEchoRequest Value: 1 Value Name: AllowInboundMaskRequest Value: 0 Value Name: AllowInboundRouterRequest Value: 0 Value Name: AllowInboundTimestampRequest Value: 0 Value Name: AllowOutboundDestinationUnreachable Value: 0 Value Name: AllowOutboundPacketTooBig Value: 0 Value Name: AllowOutboundParameterProblem Value: 0 Value Name: AllowOutboundSourceQuench Value: 0 Value Name: AllowOutboundTimeExceeded Value: 0 Value Name: AllowRedirect Value: 0 Note: If a 3rd party firewall is used, document this with the IAO and mark the Windows Firewall settings as Not Applicable. The Desktop/Secure Remote Computing STIGs contain additional requirements for systems used remotely. The XP Firewall does not meet the requirements for personal firewalls from the Desktop/Secure Remote Computing STIGs. Note: If the system in not a member of a Domain, the Domain Profile requirements can be marked Not Applicable. |
Fix Text (F-17295r1_fix) |
---|
Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile “Windows Firewall: Allow ICMP exceptions” to “Enabled” with the following parameter checked “Allow inbound echo request” |