SV-253006r958412: Successful/unsuccessful uses of setfiles in TOSS must generate an audit record. | Tri-Lab Operating System Stack (TOSS) 4 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Successful/unsuccessful uses of setfiles in TOSS must generate an audit record.

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). The "setfiles" command is primarily used to initialize the security context fields (extended attributes) on one or more filesystems (or parts of them). Usually, it is initially run as part of the SELinux installation process (a step commonly known as labeling). When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1." The AUID representation is an unsigned 32-bit integer, which equals "4294967295." The audit system interprets "-1", "4294967295", and "unset" in the same way. 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-000468-GPOS-00212, SRG-OS-000471-GPOS-00215

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

IA Controls

NIST SP 800-53

Not mappedCCI-000130Not mappedCCI-000135Not mappedCCI-000169Not mappedCCI-000172Not mappedCCI-002884

References

DPMS Target TOSS 4 DISA DPMS Target TOSS 4 5469

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.toss4os:def:253006
# Successful/unsuccessful uses of setfiles in TOSS must generate an audit record.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Audit invocations of /usr/sbin/setfiles
# textfilecontent54_object (textfilecontent54_test)
test_1() {
  grep -Pq '^\s*-a\s+(always,exit|exit,always)(?:\s+-S\s+all)?\s+-F\s+path=/usr/sbin/setfiles\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid>=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$' '/etc/audit/audit.rules' &>/dev/null
}

if test_1; 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
# DISA STIG / SCAP compliance check for audit record generation on setfiles usage
#
# Performs the check described by DISA STIG / SCAP definition oval:mil.disa.stig.toss4os:def:253006

audit_rules_file="/etc/audit/rules.d/audit.rules"
audit_pattern="^\\s*-a\\s+always,exit\\s+-F\\s+path=/usr/sbin/setfiles\\s+-F\\s+perm=x\\s+-F\\s+auid>=1000\\s+-F\\s+auid != unset\\s*$"

if [ ! -f "$audit_rules_file" ]; then
    echo "PASS"
    exit 0
fi

if grep -P "$audit_pattern" "$audit_rules_file" > /dev/null; then
    echo "PASS"
    exit 0
fi

echo "FAIL"
exit 1

Remediation

Configure the audit system to generate an audit event for any successful/unsuccessful use of the "setfiles" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:

-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update

The audit daemon must be restarted for the changes to take effect.