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

- Source: https://support.icompaas.com/support/solutions/articles/62000235147-ensure-proper-access-permissions-are-set-on-etc-issue
- 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/issue file contains a pre-login message displayed before the login prompt. Properly configuring access to this file prevents unauthorized modification or disclosure of sensitive information, which could aid attackers in reconnaissance.

**Rationale:** Restricting access to /etc/issue ensures that only authorized users can read or modify the file, maintaining the confidentiality and integrity of the pre-login message.

**Impact:** Pros:

-   Protects the system’s pre-login banner from unauthorized changes.  
    
-   Prevents disclosure of system information to unauthorized users.  
    

Cons:

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

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

**Pre-requisites:**

-   Root or sudo privileges to modify file ownership and permissions.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check current ownership and permissions of /etc/issue:  
    
    ls -l /etc/issue
    
2.  Verify file is owned by root and permissions are typically 644.  
    

### **Implementation Plan:**

**Using Linux command line:**

1\. Set ownership to root:  

chown root:root /etc/issue

2\. Set permissions to restrict access:  

chmod 644 /etc/issue

### **Backout Plan:**

**Using Linux command line:**

1.  Restore previous ownership and permissions if needed.  
    
2.  Notify users if permission changes affect usage.  
    

**References:**

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

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