This is not the latest version of the STIG. This is provided for archival purposes. See the latest STIG.

The Ubuntu operating system must be configured to preserve log records from failure events.

STIG ID: UBTU-20-010432  |  SRG: SRG-OS-000269-GPOS-00103 |  Severity: medium (CAT II)  |  CCI: CCI-001665 |  Vulnerability Id: V-238353

Vulnerability Discussion

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system.

Preserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes.

Check

Verify the log service is configured to collect system failure events.

Check that the log service is installed properly with the following command:

$ dpkg -l | grep rsyslog

ii rsyslog 8.32.0-1ubuntu4 amd64 reliable system and kernel logging daemon

If the "rsyslog" package is not installed, this is a finding.

Check that the log service is enabled with the following command:

$ systemctl is-enabled rsyslog

enabled

If the command above returns "disabled", this is a finding.

Check that the log service is properly running and active on the system with the following command:

$ systemctl is-active rsyslog

active

If the command above returns "inactive", this is a finding.

Fix

Configure the log service to collect failure events.

Install the log service (if the log service is not already installed) with the following command:

$ sudo apt-get install rsyslog

Enable the log service with the following command:

$ sudo systemctl enable --now rsyslog