# Ensure sshd MACs Are Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235516-ensure-sshd-macs-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 MACs option in the SSH daemon (sshd) configuration specifies the Message Authentication Codes used to verify the integrity of SSH communications. Configuring strong MAC algorithms protects against tampering and ensures data authenticity.

Rationale:  
 Using robust MAC algorithms strengthens session security by preventing unauthorized modifications and replay attacks during SSH sessions.

Impact:  
 Pros:

-   Enhances data integrity and session security.  
      
    
-   Supports compliance with security best practices.  
      
    

Cons:

-   May reduce compatibility with older SSH clients.  
      
    

Default Value:  
 Default MAC settings vary; older defaults may include weaker algorithms.

Pre-requisites:

-   Root or sudo privileges to modify SSH daemon configuration.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

Check current MACs configuration in /etc/ssh/sshd\_config:

grep ^MACs /etc/ssh/sshd\_config

Review the list of enabled MAC algorithms.  
  
Implementation Plan:

Using Linux command line:

Edit /etc/ssh/sshd\_config:

vi /etc/ssh/sshd\_config

Add or update the MACs directive with strong algorithms, for example:

MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com

Save the file and restart sshd:

systemctl restart sshd

Verify the configuration:  

grep ^MACs /etc/ssh/sshd\_config

### Backout Plan:

Using Linux command line:

1.  Revert to previous MAC settings if necessary.  
      
    
2.  Restart sshd and verify client 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.
