| name | cis-ubuntu2004-v300-6-2-2-4 |
| description | Ensure journald Storage is configured |
| category | cis-logging |
| version | 3.0.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu","linux","ubuntu-20.04","journald"] |
| cis_id | 6.2.2.4 |
| cis_benchmark | CIS Ubuntu Linux 20.04 LTS Benchmark v3.0.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
6.2.2.4 Ensure journald Storage is configured (Automated)
Profile
- Level 1 - Server
- Level 1 - Workstation
Description
Data from journald may be stored in volatile memory or persisted locally on the server. Logs in memory will be lost upon a system reboot. By persisting logs to local disk on the server they are protected from loss due to a reboot.
Rationale
Writing log data to disk will provide the ability to forensically reconstruct events which may have impacted the operations or security of a system even after a system crash or reboot.
Note: This recommendation only applies if journald is the chosen method for client side logging. Do not apply this recommendation if rsyslog is used.
Audit Procedure
Command Line
- IF -
journald is the method for capturing logs
Run the following script to verify Storage is set to persistent:
Expected Result
Storage=persistent
Remediation
Command Line
- IF -
rsyslog is the preferred method for capturing logs, this section and Recommendation should be skipped and the "Configure rsyslog" section followed.
- IF -
journald is the preferred method for capturing logs:
Set the following parameter in the [Journal] section in /etc/systemd/journald.conf or a file in /etc/systemd/journald.conf.d/ ending in .conf:
Storage=persistent
Note: If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten.
Run to following command to update the parameters in the service:
Default Value
Storage=persistent
References
- NIST SP 800-53 Rev. 5: AU-3, AU-12
CIS Controls