| name | cis-ubuntu1804-v220-5-1-1-6 |
| description | Ensure journald log rotation is configured per site policy |
| category | cis-logging |
| version | 2.2.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu","linux","ubuntu-18.04","journald","logging"] |
| cis_id | 5.1.1.6 |
| cis_benchmark | CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
5.1.1.6 Ensure journald log rotation is configured per site policy (Manual)
Profile
- Level: 1 - Server
- Level: 1 - Workstation
- Assessment Status: Manual
Description
Journald includes the capability of rotating log files regularly to avoid filling up the system with logs or making the logs unmanageably large. The file /etc/systemd/journald.conf is the configuration file used to specify how logs generated by Journald should be rotated.
Rationale
By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files.
Audit Procedure
Command Line
Review /etc/systemd/journald.conf, and files in /etc/systemd/journald.conf.d/, and verify logs are rotated according to site policy. The specific parameters for log rotation are:
SystemMaxUse=
SystemKeepFree=
RuntimeMaxUse=
RuntimeKeepFree=
MaxFileSec=
Expected Result
Log rotation parameters should be configured according to site policy.
Remediation
Command Line
Review /etc/systemd/journald.conf and verify logs are rotated according to site policy. The settings should be carefully understood as there are specific edge cases and prioritisation of parameters. The specific parameters for log rotation are:
SystemMaxUse=
SystemKeepFree=
RuntimeMaxUse=
RuntimeKeepFree=
MaxFileSec=
Default Value
See man 5 journald.conf for default values.
References
- NIST SP 800-53 Rev. 5: AU-2, AU-7, AU-12
CIS Controls
| Controls Version | Control |
|---|
| v8 | 8.2 Collect Audit Logs - Collect audit logs. Ensure that logging, per the enterprise's audit log management process, has been enabled across enterprise assets. |
| v7 | 6.2 Activate audit logging - Ensure that local logging has been enabled on all systems and networking devices. |
| v7 | 6.3 Enable Detailed Logging - Enable system logging to include detailed information such as an event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |