Rule ID
SV-275717r1148201_rule
Version
V1R1
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121
Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow" by using the following command:
$ sudo auditctl -l | grep shadow
-w /etc/shadow -p wa -k usergroup_modification
If the command does not return a line that matches the example or the line is commented out, this is a finding.
Note: The "-k" value is arbitrary and can be different from the example output above.Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow".
Add or modify the following line to "/etc/audit/rules.d/stig.rules":
-w /etc/shadow -p wa -k usergroup_modification
To reload the rules file, issue the following command:
$ sudo augenrules --load
Note: The "-k <keyname>" at the end of the line gives the rule a unique meaning to help during an audit investigation. The <keyname> does not need to match the example above.