# Ensure Proper Access Permissions are Set on /etc/motd

- Source: https://support.icompaas.com/support/solutions/articles/62000235146-ensure-proper-access-permissions-are-set-on-etc-motd
- 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 /etc/motd (Message of the Day) file displays system messages to users upon login. Properly configuring access to this file prevents unauthorized modification or viewing of sensitive information, which could be exploited for social engineering or system reconnaissance.

**Rationale:** Restricting access to /etc/motd ensures that only authorized users can read or modify the message, maintaining message integrity and reducing information disclosure risks.

**Impact:** Pros:

-   Protects the integrity and confidentiality of login messages.  
    
-   Prevents unauthorized users from modifying system messages.  
    

Cons:

-   Overly restrictive permissions might prevent legitimate users from viewing the message.  
    

**Default Value:** By default, /etc/motd is typically world-readable but owned by root.

**Pre-requisites:**

-   Root or sudo privileges to modify file permissions.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check current permissions and ownership of /etc/motd:  
    
    ls -l /etc/motd
    
      
    
2.  Verify that the file is owned by root and permissions are appropriately restrictive (e.g., 644).  
    

### **Implementation Plan:**

**Using Linux command line:**

1\. Set ownership to root:  

chown root:root /etc/motd

2\. Set permissions to restrict access:  

chmod 644 /etc/motd

### **Backout Plan:**

**Using Linux command line:**

1.  Restore previous ownership and permissions if necessary (backup recommended).  
    
2.  Inform users if access changes impact usability.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   Linux man page: motd

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