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

V-241616

CAT II (Medium)

tc Server API must produce log records that contain sufficient information to establish the outcome (success or failure) of events.

Rule ID

SV-241616r879567_rule

STIG

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

Version

V1R2

CCIs

CCI-000134

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 generates HTTP status codes. The status code is a three-digit indicator of the outcome of the server's response to the request.

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 HTTP status codes are not being recorded, this is a finding.

Note: HTTP status codes are three-digit codes, which are recorded immediately after "HTTP/1.1"

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"/>