# Ensure Source Routed Packets Are Not Accepted

- Source: https://support.icompaas.com/support/solutions/articles/62000235322-ensure-source-routed-packets-are-not-accepted
- 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:** Source routed packets allow the sender to specify the route a packet should take through the network. Accepting these packets can be exploited by attackers to bypass security controls and intercept or manipulate traffic. Disabling acceptance enhances network security.

**Rationale:** Rejecting source routed packets prevents attackers from influencing network routing paths and reduces the risk of man-in-the-middle and traffic interception attacks.

**Impact:** Pros:

-   Protects against routing-based network attacks.  
    
-   Enhances integrity and security of network traffic.  
    

Cons:

-   May affect legitimate network traffic in some complex routing scenarios.  
    

**Default Value:** Many systems accept source routed packets by default unless configured otherwise.

**Pre-requisites:**

-   Root or sudo privileges to modify system network settings.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1\. Check current settings for source routed packet acceptance:  

sysctl net.ipv4.conf.all.accept\_source\_route  
sysctl net.ipv4.conf.default.accept\_source\_route

2\. Confirm both values are set to 0 (disabled).

### **Implementation Plan:**

**Using Linux command line:**

1\. Disable acceptance of source routed packets temporarily:  

sysctl -w net.ipv4.conf.all.accept\_source\_route=0  
sysctl -w net.ipv4.conf.default.accept\_source\_route=0

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

net.ipv4.conf.all.accept\_source\_route = 0  
net.ipv4.conf.default.accept\_source\_route = 0

### **Backout Plan:**

**Using Linux command line:**

1\. Re-enable acceptance of source routed packets if necessary:  

sysctl -w net.ipv4.conf.all.accept\_source\_route=1  
sysctl -w net.ipv4.conf.default.accept\_source\_route=1

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.
