UCF STIG Viewer Logo

vIDM must be configured to log activity to the horizon.log file.


Finding ID Version Rule ID IA Controls Severity
V-90291 VRAU-VI-000340 SV-100941r1_rule Medium
The structure and content of error messages need to be carefully considered by the organization and development team. Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The extent to which the application server is able to identify and handle error conditions is guided by organizational policy and operational requirements. Adequate logging levels and system performance capabilities need to be balanced with data protection requirements. The structure and content of error messages needs to be carefully considered by the organization and development team. Application servers must have the capability to log at various levels, which can provide log entries for potential security-related error events. An example is the capability for the application server to assign a criticality level to a failed logon attempt error message, a security-related error message being of a higher criticality.
VMW vRealize Automation 7.x vIDM Security Technical Implementation Guide 2018-10-12


Check Text ( C-89983r1_chk )
At the command prompt, execute the following command:

grep log4j.appender.rollingFile.file /usr/local/horizon/conf/saas-log4j.properties

If the "log4j.appender.rollingFile.file" is not set to "/opt/vmware/horizon/workspace/logs/horizon.log" or is commented out or is missing, this is a finding.
Fix Text (F-97033r1_fix)
Navigate to and open /usr/local/horizon/conf/saas-log4j.properties.

Configure the vIDM policy log file with the following lines:

log4j.appender.rollingFile.layout.ConversionPattern=%d{ISO8601} %-5p (%t) [%X{orgId};%X{userId};%X{ip}] %c - %m%n