The SLES for vRealize must protect audit information from unauthorized modification.

From VMware vRealize Operations Manager 6.x SLES Security Technical Implementation Guide

Part of SRG-OS-000058-GPOS-00028

Associated with: CCI-000163

SV-99037r1_rule The SLES for vRealize must protect audit information from unauthorized modification.

Vulnerability discussion

If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.To ensure the veracity of audit information, the SLES for vRealize must protect audit information from unauthorized modification.Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.

Check content

Check that the SLES for vRealize audit logs with the following command: # (audit_log_file=$(grep "^log_file" /etc/audit/auditd.conf|sed s/^[^\/]*//) && if [ -f "${audit_log_file}" ] ; then printf "Log(s) found in "${audit_log_file%/*}":\n"; ls -l ${audit_log_file%/*}; else printf "audit log file(s) not found\n"; fi) If any audit log file has a mode more permissive than "0640", this is a finding.

Fix text

Change the mode of the audit log file(s): # chmod 0640

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer