Cron logging must be implemented in TOSS.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-253101 | TOSS-04-040590 | SV-253101r991589_rule | CCI-000366 | 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 | |||
| Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide | 2025-05-08 | |||
Related Frameworks
4 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-6
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
- DISA · 2 · disa_xccdf · related
Details
Check Text (C-253101r991589_chk)
Verify that "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.
$ sudo grep -r cron /etc/rsyslog.conf /etc/rsyslog.d
/etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages
/etc/rsyslog.conf:# Log cron stuff
/etc/rsyslog.conf:cron.* /var/log/cron
If the command does not return a response, check for cron logging all facilities with the following command.
$ sudo grep -r /var/log/messages /etc/rsyslog.conf /etc/rsyslog.d
/etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages
If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.
Fix Text (F-56504r824974_fix)
Configure "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