STIGQter: STIG Summary: VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 28 Sep 2018:

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

DISA Rule

SV-99517r1_rule

Vulnerability Number

V-88867

Group Title

SRG-APP-000099-WSR-000061

Rule Version

VROM-TC-000240

Severity

CAT II

CCI(s)

• CCI-000134 - The information system generates audit records containing information that establishes the outcome of the event.

Weight

10

Fix Recommendation

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 &quot;%r&quot; %s %b"
prefix="localhost_access_log."
suffix=".txt"/>

Check Contents

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"

Vulnerability Number

V-88867

Documentable

False

Rule Version

VROM-TC-000240

Severity Override Guidance

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"

Check Content Reference

M

Target Key

3441

Comments