# Ensure journald Log Rotation Is Configured Per Site Policy

- Source: https://support.icompaas.com/support/solutions/articles/62000235506-ensure-journald-log-rotation-is-configured-per-site-policy
- 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 systemd journal (journald) collects and stores log data. Proper configuration of journald log rotation ensures that logs are managed according to site-specific retention policies, preventing disk space exhaustion and maintaining log availability for auditing.

Rationale: Configuring journald log rotation per site policy helps maintain system stability, ensures compliance with data retention requirements, and supports effective log management.

**Impact:** **Pros:**

-   Prevents excessive disk usage by controlling log file size and retention.  
    
-   Supports compliance with organizational and regulatory requirements.  
    

**Cons:**

-   Misconfiguration may lead to loss of important log data or insufficient log retention.  
    

Default Value:  
 Default journald configurations may not align with site-specific policies and often require customization.

Pre-requisites:

-   Root or sudo privileges to modify systemd journal configurations.  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  Review current journald configuration:
    
    cat /etc/systemd/journald.conf
    
2.  Check current runtime settings:
    
    journalctl --disk-usage
    
3.  Verify if log rotation parameters (SystemMaxUse=, SystemKeepFree=, RuntimeMaxUse=, MaxRetentionSec=, etc.) comply with site policy.  
    

### Implementation Plan:

Using Linux command line:

1.  Edit /etc/systemd/journald.conf to configure log rotation parameters according to site policy. For example:
    
    SystemMaxUse=500M  
    SystemKeepFree=50M  
    RuntimeMaxUse=200M  
    MaxRetentionSec=1month 
    
      
    

2.  Restart the journald service to apply changes:
    
    systemctl restart systemd-journald
    
3.  Verify changes:
    
    journalctl --disk-usage
    

### Backout Plan:

Using Linux command line:

1.  Revert changes in /etc/systemd/journald.conf if necessary.
    
2.  Restart journald service and verify logging:
    
    systemctl restart systemd-journald
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   systemd-journald Documentation  
    
-   [NIST SP 800-53 Revision 5 - SI-4  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#si-4)

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