Rule ID
SV-268248r1038777_rule
Version
V1R2
CCIs
It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done to compile an accurate risk assessment. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource usage or capacity thresholds; or identifying an improperly configured network device. Without this capability, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.
Log in to the VM console and run the following command: chkconfig auditd If the Audit Service is not in a running state, this is a finding. Check the contents of the "/var/log/audit/audit.log" file. If the audit log does not have the required contents, this is a finding.
Audit logging is enabled by default within the HYCU VM console. If an administrator disabled it, reenable it by logging in to the HYCU VM console and running the following command: chkconfig auditd on Use the following command to review the logs: cat /var/log/secure | less Use the "/" character to search the log or timeframe for any undesired/unapproved changes. Log in to the HYCU VM console and load the STIG audit rules by using the following commands: 1. sudo cp /usr/share/audit/sample-rules/10-base-config.rules /usr/share/audit/sample-rules/30-stig.rules /usr/share/audit/sample-rules/31-privileged.rules /usr/share/audit/sample-rules/99-finalize.rules /etc/audit/rules.d/ 2. sudo augenrules --load