# Ensure /var/log Directory is Mounted on a Separate Partition

- Source: https://support.icompaas.com/support/solutions/articles/62000234980-ensure-var-log-directory-is-mounted-on-a-separate-partition
- 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 2

**Description:**  
 The /var/log directory stores system and application log files. Mounting /var/log on a separate partition isolates log data from other filesystems, enhancing system stability and simplifying log management.

**Rationale:** Having /var/log on a separate partition prevents log files from consuming all available space on the root filesystem, which can cause system failures. It also facilitates applying specific mount options and improves log data security and integrity.

**Impact:** Pros:

-   Prevents disk space exhaustion in the root filesystem due to log file growth.  
    
-   Simplifies backup and restoration of log files.  
    
-   Enables applying secure mount options specific to logs.  
    

Cons:

-   Requires additional partitioning and disk space allocation.  
    
-   Incorrect configuration could disrupt logging services.  
    

**Default Value:** By default, /var/log is usually part of the root filesystem and not a separate partition.

**Pre-requisites:**

-   Root or sudo privileges to modify disk partitions and /etc/fstab.  
    
-   Backup of existing log data before repartitioning.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check current mount points for /var/log:  
    
     mount | grep /var/log
    
2.  Verify if /var/log is mounted on a separate partition:  
    
     findmnt /var/log
    
3.  Check /etc/fstab for /var/log entry:  
    
     grep /var/log /etc/fstab
    
    Expected output: /var/log should be listed as a separate mount point with appropriate options.
    

  

### **Implementation Plan:**

**Using Linux command line:**

1.  Create a separate partition or logical volume for /var/log.  
    
2.  Format the new partition:  
    
     mkfs.ext4 /dev/<partition>
    
3.  Backup current /var/log contents:  
    
     cp -a /var/log /var/log\_backup
    
4.  Mount the new partition temporarily:  
    
     mount /dev/<partition> /mnt
    
5.  Copy backup data back:  
    
     cp -a /var/log\_backup/\* /mnt/
    

---

### **Backout Plan:**

**Using Linux command line:**

1.  Remove or comment out /var/log entry from /etc/fstab.  
    
2.  Unmount /var/log:  
    
     umount /var/log
    
3.  Restore backup if necessary:  
    
     cp -a /var/log\_backup/\* /var/log/
    
4.  Reboot or remount root filesystem.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [NIST SP 800-53 Revision 5 - SC-7  
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#sc-7)

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