SV-37661r1: The audit system must be configured to audit all administrative, privileged, and security actions. | Red Hat Enterprise Linux 5 Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

The audit system must be configured to audit all administrative, privileged, and security actions.

Description

Discussion Text

If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000347CCE-14051-7

Additional Details

Responsibility

System Administrator

IA Controls

ECAR-1, ECAR-2, ECAR-3

References

DPMS Target Red Hat 5 DISA DPMS Target Red Hat 5 2154

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.fso.rhel11:def:473
# The audit system must be configured to audit all administrative, privileged, and security actions.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.
#
# MANUAL REVIEW REQUIRED -- the module(s) below could not be reconstructed
# into working code from curated SCC reference data, and are excluded from
# the automated result:
#   - textfilecontent54_object (textfilecontent54_test) -- no arch: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- b32: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- arch: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- b32: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- b64: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- no arch: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- b64: field "subexpression" has an unresolved variable reference
#   - textfilecontent54_object (textfilecontent54_test) -- arch: field "subexpression" has an unresolved variable reference

# check that arch is 32-bit
# uname_object (uname_test)
test_1() {
  (uname -p) | grep -Pq '^i386$|^i686$'
}
# check that arch is 32/64-bit
# uname_object (uname_test)
test_5() {
  (uname -p) | grep -Pq '^x86_64$|^amd64$'
}
# check that arch is 64-bit
# uname_object (uname_test)
test_8() {
  (uname -p) | grep -Pq '^ia64$'
}

if ( test_1 || test_5 || test_8 ); then
  echo "PASS (automated portion only -- MANUAL REVIEW still required, see notes above)"
else
  echo "FAIL (or see MANUAL REVIEW note above)"
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
# DISA STIG / SCAP compliance check for audit system configuration (oval:mil.disa.fso.rhel11:def:473)
ARCH=$(uname -m)
RULES_FILE="/etc/audit/audit.rules"
if [ ! -f "$RULES_FILE" ]; then
  echo "FAIL"
  exit 1
fi
if [ "$ARCH" = "x86_64" ]; then
  grep -q "\-F arch=b32" "$RULES_FILE" || exit 1
  grep -q "\-F arch=b64" "$RULES_FILE" || exit 1
else
  grep -q "\-F arch=$ARCH" "$RULES_FILE" || grep -q "\-F arch=b${ARCH//x86_64/}" "$RULES_FILE" || exit 1
fi
echo "PASS"
exit 0

Remediation

The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules.
On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details.
Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately.
The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding.
Procedure:
Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions:

-a exit,always -F arch=<ARCH> -S clock_settime

Restart the auditd service.
# service auditd restart