UCF STIG Viewer Logo

The SLES for vRealize must generate audit records when concurrent logons to the same account occur from different sources.


Finding ID Version Rule ID IA Controls Severity
V-240532 VRAU-SL-001425 SV-240532r671337_rule Medium
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).
VMware vRealize Automation 7.x SLES Security Technical Implementation Guide 2023-09-22


Check Text ( C-43765r671335_chk )
The message types that are always recorded to /var/log/audit/audit.log include "LOGIN", "USER_LOGIN", "USER_START", "USER_END" among others and do not need to be added to audit.rules.

The log files /var/log/faillog, /var/log/lastlog, and /var/log/tallylog must be protected from tampering of the logon records:

# egrep "faillog|lastlog|tallylog" /etc/audit/audit.rules

If /var/log/faillog, /var/log/lastlog, and /var/log/tallylog entries do not exist, this is a finding.
Fix Text (F-43724r671336_fix)
Ensure the auditing of logons by modifying /etc/audit/audit.rules to contain:

-w /var/log/faillog -p wa
-w /var/log/lastlog -p wa
-w /var/log/tallylog -p wa


# /etc/dodscript.sh