UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Cron logging must be implemented.


Overview

Finding ID Version Rule ID IA Controls Severity
V-215142 UBTU-16-030460 SV-215142r508033_rule Medium
Description
Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.
STIG Date
Canonical Ubuntu 16.04 LTS Security Technical Implementation Guide 2020-09-03

Details

Check Text ( C-16341r285294_chk )
Verify that "rsyslog" is configured to log cron events.

Check the configuration of "/etc/rsyslog.d/50-default.conf" for the cron facility with the following commands:

Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.d/50-default.conf".

# grep cron /etc/rsyslog.d/50-default.conf

cron.* /var/log/cron.log

If the commands do not return a response, check for cron logging all facilities by inspecting the "/etc/rsyslog.d/50-default.con" file:

# more /etc/rsyslog.conf

Look for the following entry:

*.* /var/log/messages

If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.
Fix Text (F-16339r285295_fix)
Configure "rsyslog" to log all cron messages by adding or updating the following line to "/etc/rsyslog.d/50-default.conf":

cron.* /var/log/cron.log

Note: The line must be added before the following entry if it exists in "/etc/rsyslog.d/50-default.conf":

*.* ~ # discards everything