# Ensure Only Approved Services Are Listening on Network Interfaces

- Source: https://support.icompaas.com/support/solutions/articles/62000235296-ensure-only-approved-services-are-listening-on-network-interfaces
- 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:**  
Only authorized and approved services should be allowed to listen on network interfaces to minimize the attack surface and prevent unauthorized access. Regular manual reviews of listening services help maintain system security and compliance.

**Rationale:** Unapproved services listening on network interfaces can provide attackers with entry points into the system. Ensuring only approved services listen reduces exposure to vulnerabilities and unauthorized access.

**Impact:** Pros:

-   Reduces risk of unauthorized network access.  
    
-   Supports compliance with security policies.  
    

Cons:

-   Manual review requires administrative effort and expertise.  
    
-   Risk of disrupting necessary services if incorrectly disabled.  
    

**Default Value:** Systems may have various services listening depending on configuration and role.

**Pre-requisites:**

-   Root or sudo privileges to audit network services.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  List all services listening on network interfaces  
    
    ss -tuln  
    netstat -tuln
    
      
    
2.  Compare the list against the approved services inventory.  
    
3.  Identify unapproved or unexpected listening services.  
    

### **Implementation Plan:**

**Using Linux command line:**

1.  Investigate unapproved services to determine necessity.  
    

2.  Disable or reconfigure unnecessary services to stop listening:  
    
    systemctl stop <service\_name>  
    systemctl disable <service\_name>
    
      
    
3.  Verify changes by re-listing listening services.  
    

### **Backout Plan:**

**Using Linux command line:**

1.  Re-enable services if required for business or operational needs:  
    
    systemctl enable <service\_name>  
    systemctl start <service\_name>
    
      
    
2.  Confirm services are functioning correctly.  
    

**References:**

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

## 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.
