Ubuntu 24.04 LTS must generate audit records for all events that affect the systemd journal files.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-270715 | UBTU-24-300029 | SV-270715r1066634_rule | Medium |
| Description |
| Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify system level binaries and their operation. Auditing the systemd journal files provides logging that can be used for forensic purposes. To address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
| STIG | Date |
| Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide | 2025-05-16 |
Details
| Check Text (C-74748r1066632_chk) |
| Verify Ubuntu 24.04 LTS generates audit records for all events that affect "/var/log/journal" with the following command: $ sudo auditctl -l | grep journal -w /var/log/journal -p wa -k systemd_journal If the command does not return a line that matches the example or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above. |
| Fix Text (F-74649r1066633_fix) |
| Configure Ubuntu 24.04 LTS to generate audit records for events that affect "/var/log/journal". Add or update the following rule to "/etc/audit/rules.d/stig.rules": -w /var/log/journal -p wa -k systemd_journal To reload the rules file, issue the following command: $ sudo augenrules --load |