# Ensure Broadcast ICMP Requests Are Ignored

- Source: https://support.icompaas.com/support/solutions/articles/62000235313-ensure-broadcast-icmp-requests-are-ignored
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Amazon Linux 2 Benchmark v3.0.0](https://support.icompaas.com/support/solutions/62000112696) › [CIS Amazon Linux 2 Benchmarks](https://support.icompaas.com/support/solutions/folders/62000169265)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:** • Level 1

**Description:**  
 Broadcast ICMP requests can be exploited in denial-of-service (DoS) attacks by amplifying network traffic. Configuring the system to ignore these requests helps prevent such attacks and enhances network security.

**Rationale:** Ignoring broadcast ICMP requests mitigates the risk of amplification attacks and reduces unnecessary network traffic processing.

**Impact:** Pros:

-   Protects against DoS attacks leveraging broadcast ICMP.  
    
-   Improves overall network resilience.  
    

Cons:

-   May affect legitimate network diagnostics if broadcast ICMP is required.  
    

**Default Value:** Broadcast ICMP requests are often accepted by default unless explicitly disabled.

**Pre-requisites:**

-   Root or sudo privileges to modify system network parameters.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1\. Check current setting for ignoring broadcast ICMP requests:  

sysctl net.ipv4.icmp\_echo\_ignore\_broadcasts

2\. Confirm the value is set to 1 (enabled).

### **Implementation Plan:**

**Using Linux command line:**

1\. Enable ignoring of broadcast ICMP requests temporarily:  

sysctl -w net.ipv4.icmp\_echo\_ignore\_broadcasts=1

2\. Persist the setting by adding the following to /etc/sysctl.conf or a file in /etc/sysctl.d/:  

net.ipv4.icmp\_echo\_ignore\_broadcasts = 1

3\. Reload sysctl settings:  

sysctl -p

### **Backout Plan:**

**Using Linux command line:**

1\. Disable ignoring broadcast ICMP requests if necessary:  

sysctl -w net.ipv4.icmp\_echo\_ignore\_broadcasts=0

2\. Update configuration files accordingly and reload sysctl.  
  
**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   Linux sysctl Documentation  
    
-   [NIST SP 800-53 Revision 5 - SC-7  
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#sc-7)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
