← Back to VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide

V-241607

CAT II (Medium)

tc Server API must produce log records containing sufficient information to establish where within the web server the events occurred.

Rule ID

SV-241607r879565_rule

STIG

VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000132

Discussion

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 a user accesses the system and the system authenticates 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. Like all web servers, tc Server will log the requested URL and the parameters, if any, sent in the request. This information will enable investigators to determine where in the server an action was requested.

Check Content

At the command prompt, execute the following command:

tail /storage/log/vcops/log/suite-api/localhost_access_log.YYYY-MM-dd.txt

Note: Substitute the actual date in the file name.

If the location of events are not being recorded, this is a finding.

Fix Text

Navigate to and open /usr/lib/vmware-vcops/tomcat-enterprise/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 "%r" %s %b"
                       prefix="localhost_access_log."
                       suffix=".txt"/>