BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

RHEL-10-200648 RHEL 10 must use cron logging.

DISA STIG library V1R3
All changes in this version
first version loaded CAT II

Maps to AU-3 via CCI-000133

Title

RHEL 10 must use cron logging.

Control

Verify RHEL 10 rsyslog is configured to log cron events with the following command: Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files. $ grep -s "cron.\*" /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.d/99-cron-stig.conf:cron.* action(type="omfile" file="/var/log/cron") If the command does not return a line demonstrating logging to /var/log/cron, perform a functional cron test. Inject a message into the cron logging facility with the following command: $ logger -p cron.info "STIG-TEST-CRON-LOGGING" Check if it successfully wrote to the dedicated log file with the following command: $ sudo grep "STIG-TEST-CRON-LOGGING" /var/log/cron Jul 16 11:33:00 RHEL10Sim pdosadmin[33692]: STIG-TEST-CRON-LOGGING If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.

Discussion

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.

Related controls

CCI-000133

Fix

Configure RHEL 10 rsyslog to log all cron messages by adding or updating the following line to "/etc/rsyslog.conf" or a configuration file in the /etc/rsyslog.d/ directory: cron.* /var/log/cron The rsyslog daemon must be restarted for the changes to take effect: $ sudo systemctl restart rsyslog.service