STIGQter STIGQter: STIG Summary: Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide Version: 2 Release: 6 Benchmark Date: 01 Jul 2026:

Successful/unsuccessful uses of the "unlink" command in TOSS must generate an audit record.

DISA Rule

SV-253000r958412_rule

Vulnerability Number

V-253000

Group Title

SRG-OS-000037-GPOS-00015

Rule Version

TOSS-04-030460

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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

-a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=unset -k delete
-a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=unset -k delete

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

Check Contents

Verify that an audit event is generated for any successful/unsuccessful use of the "unlink" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":

$ sudo grep -w "unlink" /etc/audit/audit.rules

-a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=unset -k delete
-a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=unset -k delete

If the command does not return a line, or the line is commented out, this is a finding.

Vulnerability Number

V-253000

Documentable

False

Rule Version

TOSS-04-030460

Severity Override Guidance

Verify that an audit event is generated for any successful/unsuccessful use of the "unlink" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":

$ sudo grep -w "unlink" /etc/audit/audit.rules

-a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=unset -k delete
-a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=unset -k delete

If the command does not return a line, or the line is commented out, this is a finding.

Check Content Reference

M

Target Key

5469