UCF STIG Viewer Logo

Successful/unsuccessful uses of the crontab command must generate an audit record.


Overview

Finding ID Version Rule ID IA Controls Severity
V-215103 UBTU-16-020810 SV-215103r610931_rule Medium
Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215
STIG Date
Canonical Ubuntu 16.04 LTS Security Technical Implementation Guide 2020-12-09

Details

Check Text ( C-16302r285177_chk )
Verify that an audit event is generated for any successful/unsuccessful use of the "crontab" command.

Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":

# sudo grep -w crontab /etc/audit/audit.rules

-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab

If the command does not return a line, or the line is commented out, this is a finding.
Fix Text (F-16300r285178_fix)
Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command.

Add or update the following rule in the "/etc/audit/audit.rules" file:

-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab

The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:

# sudo systemctl restart auditd.service