# Ensure sshd ClientAliveInterval and ClientAliveCountMax Are Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235421-ensure-sshd-clientaliveinterval-and-clientalivecountmax-are-configured
- 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:  
 The ClientAliveInterval and ClientAliveCountMax settings in the SSH daemon (sshd) configuration help detect and terminate inactive SSH sessions. Properly configuring these parameters improves session management and security by closing idle connections.

Rationale:  
 Closing idle SSH sessions reduces the risk of unauthorized access via abandoned connections and helps free system resources.

Impact:  
 **Pros**:

-   Improves security by limiting idle session duration.  
      
    
-   Helps prevent potential hijacking of inactive sessions.  
      
    

**Cons**:

-   May disconnect users during temporary network issues if values are too aggressive.  
      
    

Default Value:  
 Defaults vary; often, these parameters are unset or configured with long intervals.

Pre-requisites:

-   Root or sudo privileges to modify SSH daemon configuration.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

Check current settings in /etc/ssh/sshd\_config:  

grep -E '^ClientAliveInterval|^ClientAliveCountMax' /etc/ssh/sshd\_config

1.  Verify the values for both parameters.  
      
    

### Implementation Plan:

Using Linux command line:

Edit /etc/ssh/sshd\_config:  
  
vi /etc/ssh/sshd\_config

Add or update the following directives with recommended values, for example:  
  
ClientAliveInterval 300  

ClientAliveCountMax 3

Save the file and restart sshd:

systemctl restart sshd

Verify the configuration:  

grep -E '^ClientAliveInterval|^ClientAliveCountMax' /etc/ssh/sshd\_config

### Backout Plan:

Using Linux command line:

1.  Revert to previous values if needed.  
      
    
2.  Restart sshd and confirm connectivity.  
      
    

References:

-   [NIST SP 800-53 Revision 5 - AC-11  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#ac-11)

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