Verify SSH ClientAliveInterval and ClientAliveCountMax are configured for idle session timeout
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-ubuntu1404-v210-5-2-12 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Ubuntu1404 V210 5 2 12?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-ubuntu1404-v210-5-2-12)More formats (shields.io, HTML) on the badges page.
---
name: "CIS Ubuntu 14.04 LTS - 5.2.12 Ensure SSH Idle Timeout Interval is configured"
description: "Verify SSH ClientAliveInterval and ClientAliveCountMax are configured for idle session timeout"
category: "cis-os-hardening"
version: "2.1.0"
author: "cyberstrike-official"
tags:
- cis
- ubuntu
- ubuntu-14.04
- level-1
- scored
- ssh
cis_id: "5.2.12"
cis_benchmark: "CIS Ubuntu Linux 14.04 LTS Benchmark v2.1.0"
tech_stack:
- ubuntu
- linux
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: "medium"
---
# 5.2.12 Ensure SSH Idle Timeout Interval is configured (Scored)
## Profile Applicability
- Level 1 - Server
- Level 1 - Workstation
## Description
The two options `ClientAliveInterval` and `ClientAliveCountMax` control the timeout of ssh sessions. When the `ClientAliveInterval` variable is set, ssh sessions that have no activity for the specified length of time are terminated. When the `ClientAliveCountMax` variable is set, `sshd` will send client alive messages at every `ClientAliveInterval` interval. When the number of consecutive client alive messages are sent with no response from the client, the `ssh` session is terminated. For example, if the `ClientAliveInterval` is set to 15 seconds and the `ClientAliveCountMax` is set to 3, the client `ssh` session will be terminated after 45 seconds of idle time.
## Rationale
Having no timeout value associated with a connection could allow an unauthorized user access to another user's `ssh` session (e.g. user walks away from their computer and doesn't lock the screen). Setting a timeout value at least reduces the risk of this happening.
While the recommended setting is 300 seconds (5 minutes), set this timeout value based on site policy. The recommended setting for `ClientAliveCountMax` is 0. In this case, the client session will be terminated after 5 minutes of idle time and no keepalive messages will be sent.
## Audit Procedure
Run the following commands and verify `ClientAliveInterval` is between 1 and 300 and `ClientAliveCountMax` is 3 or less:
```bash
grep "^ClientAliveInterval" /etc/ssh/sshd_config
grep "^ClientAliveCountMax" /etc/ssh/sshd_config
```
## Expected Result
```
ClientAliveInterval 300
ClientAliveCountMax 0
```
## Remediation
Edit the `/etc/ssh/sshd_config` file to set the parameters according to site policy:
```
ClientAliveInterval 300
ClientAliveCountMax 0
```
## Default Value
ClientAliveInterval 0, ClientAliveCountMax 3
## References
- CIS Controls: 16.4 - Automatically Log Off Users After Standard Period Of Inactivity
## Profile
- Level 1 - Server
- Level 1 - Workstation
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!