# Ensure sshd LogLevel Is Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235515-ensure-sshd-loglevel-is-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 Setting an appropriate log level ensures that sufficient information is logged for auditing and troubleshooting while avoiding excessive log noise.

Rationale:  
 Configuring a suitable log level improves the ability to detect and investigate security events without overwhelming the system with unnecessary log data.

Impact:  
 **Pros**:

-   Enhances security monitoring and incident investigation capabilities.  
      
    
-   Balances log detail and system performance.  
      
    

**Cons**:

-   Setting too verbose a level may generate excessive logs.  
      
    

Default Value:  
 The default log level is typically INFO or VERBOSE depending on the SSH server version.

Pre-requisites:

-   Root or sudo privileges to modify SSH daemon configuration.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

 Check current LogLevel setting in /etc/ssh/sshd\_config:

grep ^LogLevel /etc/ssh/sshd\_config

Verify the configured log level.  

### Implementation Plan:

Using Linux command line:

Edit /etc/ssh/sshd\_config:

vi /etc/ssh/sshd\_config

Add or update the LogLevel directive, for example:

  

LogLevel VERBOSE

Save the file and restart sshd:  
  
systemctl restart sshd

  

Confirm the setting:  

grep ^LogLevel /etc/ssh/sshd\_config

### Backout Plan:

Using Linux command line:

1.  Revert to previous LogLevel settings if necessary.  
      
    
2.  Restart sshd and monitor logging behavior.  
    

References:

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

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