SV-217252r958412: The SUSE operating system must generate audit records for all uses of the crontab command. | SUSE Linux Enterprise Server 12 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

The SUSE operating system must generate audit records for all uses of the crontab command.

Description

Discussion Text

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-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000172Not mappedCCI-000169Not mappedCCI-000130Not mappedCCI-002884V-77417SV-92113

References

DPMS Target SUSE Linux Enterprise Server 12 DISA DPMS Target SUSE Linux Enterprise Server 12 4033

Checks

DISA STIG (Manual Reference)

Verify an audit record is generated for all uses of the "crontab" command.

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

# sudo grep -i '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 any output or the returned line is commented out, this is a finding.

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.sles12:def:214
# The SUSE operating system must generate audit records for all uses of the crontab command.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# package audit is installed
# rpminfo_object (rpminfo_test)
test_1() {
  rpm -q --quiet 'audit' &>/dev/null
}
# check for running auditd
# process58_object (process58_test)
test_2() {
  ps -eo args | grep -P '^/sbin/auditd\b' &>/dev/null
}
# Audit invocations of /usr/bin/crontab
# textfilecontent54_object (textfilecontent54_test)
test_3() {
  grep -Pq '^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/crontab\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid>=1000\s+-F\s+auid!=4294967295(\s+(-k\s+|-F\s+key=)\S+)?\s*$' '/etc/audit/audit.rules' &>/dev/null
}

if ( test_1 && test_2 && test_3 ); then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# OVAL Definition: oval:mil.disa.stig.sles12:def:214
if ! rpm -q audit >/dev/null 2>&1; then echo "FAIL"; exit 1; fi
if ! pgrep -f '^/sbin/auditd' >/dev/null 2>&1; then echo "FAIL"; exit 1; fi
if ! grep -q '^\\s*-a\\s+always,exit\\s+-F\\s+path=/usr/bin/crontab\\s+-F\\s+perm=x\\s+-F\\s+auid>=1000\\s+-F\\s+auid != 4294967295\\s*$' /etc/audit/rules.d/audit.rules; then echo "FAIL"; exit 1; fi
echo "PASS"; exit 0

Remediation

Configure the SUSE operating system to generate an audit record for all uses of the "crontab" command.

Add or update the following rules in the "/etc/audit/rules.d/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.

# sudo systemctl restart auditd.service