STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 4 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide

V-288843

CAT II (Medium)

TOSS must enforce that successful/unsuccessful uses of the "useradd" command generate an audit record.

Rule ID

SV-288843r1262340_rule

STIG

Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide

Version

V2R7

CCIs

CCI-000172

Discussion

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 "useradd" command modifies the system account files to reflect the changes that are specified on the command line.

Check Content

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

$ sudo grep -w useradd /etc/audit/audit.rules

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

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

Fix Text

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

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

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