Information
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds, or identifying an improperly configured operating system.
Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000365-GPOS-00152, SRG-OS-000255-GPOS-00096
Solution
Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred.
Enable the auditd service with the following command:
# systemctl start auditd.service
Item Details
Category: AUDIT AND ACCOUNTABILITY, CONFIGURATION MANAGEMENT
References: 800-53|AU-3, 800-53|AU-3(1), 800-53|AU-14(1), 800-53|CM-5(1), CAT|II, CCI|CCI-000131, CCI|CCI-000132, CCI|CCI-000135, CCI|CCI-001464, CCI|CCI-001487, CCI|CCI-001814, CCI|CCI-003938, Rule-ID|SV-221764r1015189_rule, STIG-ID|OL07-00-030000, STIG-Legacy|SV-108371, STIG-Legacy|V-99267, Vuln-ID|V-221764
Control ID: 1ee1f76621a95fb82cd529656510e8c65c7234141cdca17ac947696f7323c72d