Details
Frequently, an attacker that successfully gains access to a system has only gained access to an account with limited privileges, such as a guest account or a service account. The attacker must attempt to change to another user account with normal or elevated privileges in order to proceed. 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).
Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000462-GPOS-00206
Solution
To ensure the appropriate flags are enabled for auditing, run the following command:
/usr/bin/sudo sed -i.bak ‘/^flags/ s/$/,lo/’ /etc/security/audit_control; /usr/bin/sudo /usr/sbin/audit -s
A text editor may also be used to implement the required updates to the ‘/etc/security/audit_control’ file.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Access Control, Audit and Accountability.This control applies to the following type of system Unix.
References
- 800-53|AC-17(1)
- 800-53|AU-12c.
- CAT|II
- CCI|CCI-000067
- CCI|CCI-000172
- Rule-ID|SV-230771r599842_rule
- STIG-ID|APPL-11-001002
- Vuln-ID|V-230771