# Ensure sshd Ciphers Are Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235415-ensure-sshd-ciphers-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:  
Configuring strong cryptographic ciphers for the SSH daemon (sshd) ensures secure encrypted communication between clients and the server, protecting against cryptographic attacks and data interception.

Rationale:  
 Using strong and modern ciphers mitigates vulnerabilities associated with weak or deprecated algorithms, enhancing the confidentiality and integrity of SSH sessions.

Impact:  
 Pros:

-   Strengthens encryption protecting SSH sessions.  
      
    
-   Helps comply with security standards and best practices.  
      
    

Cons:

-   May reduce compatibility with very old SSH clients.  
      
    

Default Value:  
 Default cipher settings vary by SSH server version and distribution; older defaults may include weak ciphers.

Pre-requisites:

-   Root or sudo privileges to modify SSH daemon configuration.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

Check current ciphers configured in /etc/ssh/sshd\_config:  

grep ^Ciphers /etc/ssh/sshd\_config

1.  Review the list of enabled ciphers.  
      
    

### Implementation Plan:

Using Linux command line:

Edit /etc/ssh/sshd\_config:  

vi /etc/ssh/sshd\_config

Add or update the Ciphers directive with strong ciphers, for example:  
  
Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com

Save the file and restart sshd:  

systemctl restart sshd

Verify the configuration:  

grep ^Ciphers /etc/ssh/sshd\_config

  

### Backout Plan:

Using Linux command line:

1.  Revert to previous Ciphers settings if necessary.
    
2.  Restart sshd and verify compatibility.  
      
    

References:

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

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