VMware vRealize Automation 7.x tc Server STIG Version Comparison

VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide


There are 6 differences between versions v1 r1 (Sept. 28, 2018) (the "left" version) and v2 r1 (July 23, 2021) (the "right" version).

Check VRAU-TC-000130 was removed from the benchmark in the "right" version. The text below reflects the old wording.

This check's original form is available here.

Text Differences


tc Server HORIZON must capture, record, and log all content related to a user session.

Check Content

At the command prompt, execute the following command: tail /storage/log/vmware/horizon/localhost_access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If all content related to a user session is not being recorded, this is a finding.


After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when users access the system, and the system authenticates the users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. As a Tomcat derivative, tc Server can be configured with an AccessLogValve. A Valve element represents a component that can be inserted into the request processing pipeline. The pattern attribute of the AccessLogValve controls which data gets logged.


Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to and locate <Host>. Configure the <Host> node with the <AccessLogValve> below. Note: The "AccessLogValve" should be configured as follows: <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="localhost_access_log." suffix=".txt"/>