Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

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

V1R1 · · · Released 28 Sep 2018 · 161 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Sort by
b
tc Server VCO must limit the number of maximum concurrent connections permitted.
AC-10 - Medium - CCI-000054 - V-89883 - SV-100533r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000010
Vuln IDs
  • V-89883
Rule IDs
  • SV-100533r1_rule
Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a web site, facilitating a denial-of-service attack. Unless the number of requests is controlled, the web server can consume enough system resources to cause a system crash. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests. Each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the value of the maxThreads attribute.
Checks: C-89575r1_chk

At the command prompt, execute the following command: grep maxThreads /etc/vco/app-server/server.xml If the value of "maxThreads" is not "300" or is missing, this is a finding.

Fix: F-96625r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to and locate the <Connector> node. Configure the <Connector> with the value 'maxThreads="300"'.

b
tc Server VCAC must limit the number of maximum concurrent connections permitted.
AC-10 - Medium - CCI-000054 - V-89885 - SV-100535r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000015
Vuln IDs
  • V-89885
Rule IDs
  • SV-100535r1_rule
Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a web site, facilitating a denial-of-service attack. Unless the number of requests is controlled, the web server can consume enough system resources to cause a system crash. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests. Each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the value of the maxThreads attribute.
Checks: C-89577r1_chk

At the command prompt, execute the following command: grep maxThreads /etc/vcac/server.xml If the value of "maxThreads" is not "1000" or is missing, this is a finding.

Fix: F-96627r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to and locate <Executor>. Configure the <Executor> with the value 'maxThreads="1000"'. Note: The <Executor> node should be configured per the following: <Executor maxThreads="1000" minSpareThreads="50" name="tomcatThreadPool" namePrefix="tomcat-http--"/>

b
tc Server HORIZON must limit the amount of time that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89887 - SV-100537r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000020
Vuln IDs
  • V-89887
Rule IDs
  • SV-100537r1_rule
Denial of Service is one threat against web servers. Many DoS attacks attempt to consume web server resources in such a way that no more resources are available to satisfy legitimate requests. Mitigation against these threats is to take steps to limit the number of resources that can be consumed in certain ways. tc Server provides the connectionTimeout attribute. This sets the number of milliseconds tc Server will wait, after accepting a connection, for the request URI line to be presented. This timeout will also be used when reading the request body (if any).
Checks: C-89579r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "connectionTimeout" is not set to "20000" or is missing, this is a finding.

Fix: F-96629r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'connectionTimeout="20000"'.

b
tc Server VCO must limit the amount of time that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89889 - SV-100539r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000025
Vuln IDs
  • V-89889
Rule IDs
  • SV-100539r1_rule
Denial of Service is one threat against web servers. Many DoS attacks attempt to consume web server resources in such a way that no more resources are available to satisfy legitimate requests. Mitigation against these threats is to take steps to limit the number of resources that can be consumed in certain ways. tc Server provides the connectionTimeout attribute. This sets the number of milliseconds tc Server will wait, after accepting a connection, for the request URI line to be presented. This timeout will also be used when reading the request body (if any).
Checks: C-89581r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "connectionTimeout" is not set to "20000" or is missing, this is a finding.

Fix: F-96631r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'connectionTimeout="10000"'.

b
tc Server VCAC must limit the amount of time that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89891 - SV-100541r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000030
Vuln IDs
  • V-89891
Rule IDs
  • SV-100541r1_rule
Denial of Service is one threat against web servers. Many DoS attacks attempt to consume web server resources in such a way that no more resources are available to satisfy legitimate requests. Mitigation against these threats is to take steps to limit the number of resources that can be consumed in certain ways. tc Server provides the connectionTimeout attribute. This sets the number of milliseconds tc Server will wait, after accepting a connection, for the request URI line to be presented. This timeout will also be used when reading the request body (if any).
Checks: C-89583r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "connectionTimeout" is not set to "10000" or is missing, this is a finding.

Fix: F-96633r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'connectionTimeout="10000"'.

b
tc Server HORIZON must limit the number of times that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89893 - SV-100543r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000035
Vuln IDs
  • V-89893
Rule IDs
  • SV-100543r1_rule
KeepAlive provides long lived HTTP sessions that allow multiple requests to be sent over the same connection. Enabling KeepAlive mitigates the effects of several types of denial-of-service attacks. An advantage of KeepAlive is the reduced latency in subsequent requests (no handshaking). However, a disadvantage is that server resources are not available to handle other requests while a connection is maintained between the server and the client. tc Server can be configured to limit the number of subsequent requests that one client can submit to the server over an established connection. This limit helps provide a balance between the advantages of KeepAlive, while not allowing any one connection being held too long by any one client. maxKeepAliveRequests is the tc Server attribute that sets this limit.
Checks: C-89585r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "maxKeepAliveRequests" is not set to "15" or is missing, this is a finding.

Fix: F-96635r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'maxKeepAliveRequests="15"'.

b
tc Server VCO must limit the number of times that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89895 - SV-100545r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000040
Vuln IDs
  • V-89895
Rule IDs
  • SV-100545r1_rule
KeepAlive provides long-lived HTTP sessions that allow multiple requests to be sent over the same connection. Enabling KeepAlive mitigates the effects of several types of denial-of-service attacks. An advantage of KeepAlive is the reduced latency in subsequent requests (no handshaking). However, a disadvantage is that server resources are not available to handle other requests while a connection is maintained between the server and the client. tc Server can be configured to limit the number of subsequent requests that one client can submit to the server over an established connection. This limit helps provide a balance between the advantages of KeepAlive, while not allowing any one connection being held too long by any one client. maxKeepAliveRequests is the tc Server attribute that sets this limit.
Checks: C-89587r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "maxKeepAliveRequests" is not set to "15" or is missing, this is a finding.

Fix: F-96637r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'maxKeepAliveRequests="15"'.

b
tc Server VCAC must limit the number of times that each TCP connection is kept alive.
AC-10 - Medium - CCI-000054 - V-89897 - SV-100547r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000045
Vuln IDs
  • V-89897
Rule IDs
  • SV-100547r1_rule
KeepAlive provides long-lived HTTP sessions that allow multiple requests to be sent over the same connection. Enabling KeepAlive mitigates the effects of several types of denial-of-service attacks. An advantage of KeepAlive is the reduced latency in subsequent requests (no handshaking). However, a disadvantage is that server resources are not available to handle other requests while a connection is maintained between the server and the client. tc Server can be configured to limit the number of subsequent requests that one client can submit to the server over an established connection. This limit helps provide a balance between the advantages of KeepAlive, while not allowing any one connection being held too long by any one client. maxKeepAliveRequests is the tc Server attribute that sets this limit.
Checks: C-89589r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "maxKeepAliveRequests" is not set to "15" or is missing, this is a finding.

Fix: F-96639r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'maxKeepAliveRequests="15"'.

b
tc Server HORIZON must perform server-side session management.
AC-10 - Medium - CCI-000054 - V-89899 - SV-100549r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000050
Vuln IDs
  • V-89899
Rule IDs
  • SV-100549r1_rule
Cookies are a common way to save session state over the HTTP(S) protocol. If an attacker can compromise session data stored in a cookie, they are better able to launch an attack against the server and its applications. Session cookies stored on the server are more secure than cookies stored on the client. Therefore, tc Server must be configured correctly in order to generate and manage session cookies on the server. Managing cookies on the server provides a layer of defense to vRealize Automation. By default, tc Server is designed to manage cookies on the server. However, incorrect configuration can turn off the default feature.
Checks: C-89591r1_chk

At the command prompt, execute the following command: grep -E 'cookies=.false' /opt/vmware/horizon/workspace/conf/context.xml If the command produces any output, this is a finding.

Fix: F-96641r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/context.xml. Navigate to and locate the <Context> node. Remove the value 'cookies="false"' from the <Context> node.

b
tc Server VCO must perform server-side session management.
AC-10 - Medium - CCI-000054 - V-89901 - SV-100551r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000055
Vuln IDs
  • V-89901
Rule IDs
  • SV-100551r1_rule
Cookies are a common way to save session state over the HTTP(S) protocol. If an attacker can compromise session data stored in a cookie, they are better able to launch an attack against the server and its applications. Session cookies stored on the server are more secure than cookies stored on the client. Therefore, tc Server must be configured correctly in order to generate and manage session cookies on the server. Managing cookies on the server provides a layer of defense to vRealize Automation. By default, tc Server is designed to manage cookies on the server. However, incorrect configuration can turn off the default feature.
Checks: C-89593r1_chk

At the command prompt, execute the following command: grep -E 'cookies=.false' /etc/vco/app-server/context.xml If the command produces any output, this is a finding.

Fix: F-96643r1_fix

Navigate to and open /etc/vco/app-server/context.xml. Navigate to and locate the <Context> node. Remove the value 'cookies="false"' from the <Context> node.

b
tc Server VCAC must perform server-side session management.
AC-10 - Medium - CCI-000054 - V-89903 - SV-100553r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000060
Vuln IDs
  • V-89903
Rule IDs
  • SV-100553r1_rule
Cookies are a common way to save session state over the HTTP(S) protocol. If an attacker can compromise session data stored in a cookie, they are better able to launch an attack against the server and its applications. Session cookies stored on the server are more secure than cookies stored on the client. Therefore, tc Server must be configured correctly in order to generate and manage session cookies on the server. Managing cookies on the server provides a layer of defense to vRealize Automation. By default, tc Server is designed to manage cookies on the server. However, incorrect configuration can turn off the default feature.
Checks: C-89595r1_chk

At the command prompt, execute the following command: grep -E 'cookies=.false' /etc/vcac/context.xml If the command produces any output, this is a finding.

Fix: F-96645r1_fix

Navigate to and open /etc/vcac/context.xml. Navigate to and locate the <Context> node. Remove the value 'cookies="false"' from the <Context> node.

b
tc Server HORIZON must be configured with FIPS 140-2 compliant ciphers for HTTPS connections.
AC-17 - Medium - CCI-000068 - V-89905 - SV-100555r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000068
Version
VRAU-TC-000065
Vuln IDs
  • V-89905
Rule IDs
  • SV-100555r1_rule
Encryption of data-in-flight is an essential element of protecting information confidentiality. If a web server uses weak or outdated encryption algorithms, then the server's communications can potentially be compromised. The US Federal Information Processing Standards (FIPS) publication 140-2, Security Requirements for Cryptographic Modules (FIPS 140-2) identifies eleven areas for a cryptographic module used inside a security system that protects information. FIPS 140-2 approved ciphers provide the maximum level of encryption possible for a private web server. Configuration of ciphers used by tc Server are set in the catalina.properties file. Only those ciphers specified in the configuration file, and which are available in the installed OpenSSL library, will be used by tc Server while encrypting data for transmission.
Checks: C-89597r1_chk

At the command prompt, execute the following command: grep bio-ssl.cipher.list /opt/vmware/horizon/workspace/conf/catalina.properties If the value of "bio-ssl.cipher.list" does not match the list of FIPS 140-2 ciphers or is missing, this is a finding. Note: To view a list of FIPS 140-2 ciphers, at the command prompt execute the following command: openssl ciphers 'FIPS'

Fix: F-96647r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to and locate "bio-ssl.cipher.list". Configure the "bio-ssl.cipher.list" with FIPS 140-2 compliant ciphers.

b
tc Server VCAC must be configured with FIPS 140-2 compliant ciphers for HTTPS connections.
AC-17 - Medium - CCI-000068 - V-89907 - SV-100557r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000068
Version
VRAU-TC-000070
Vuln IDs
  • V-89907
Rule IDs
  • SV-100557r1_rule
Encryption of data-in-flight is an essential element of protecting information confidentiality. If a web server uses weak or outdated encryption algorithms, then the server's communications can potentially be compromised. The US Federal Information Processing Standards (FIPS) publication 140-2, Security Requirements for Cryptographic Modules (FIPS 140-2) identifies eleven areas for a cryptographic module used inside a security system that protects information. FIPS 140-2 approved ciphers provide the maximum level of encryption possible for a private web server. Configuration of ciphers used by tc Server are set in the catalina.properties file. Only those ciphers specified in the configuration file, and which are available in the installed OpenSSL library, will be used by tc Server while encrypting data for transmission.
Checks: C-89599r1_chk

At the command prompt, execute the following command: grep cipher /etc/vcac/catalina.properties If the value of "cipher" does not match the list of FIPS 140-2 ciphers or is missing, this is a finding. Note: To view a list of FIPS 140-2 ciphers, at the command prompt execute the following command: openssl ciphers 'FIPS'

Fix: F-96649r1_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to and locate "cipher". Configure the "cipher" with FIPS 140-2 compliant ciphers.

b
tc Server HORIZON must use cryptography to protect the integrity of remote sessions.
AC-17 - Medium - CCI-001453 - V-89909 - SV-100559r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-001453
Version
VRAU-TC-000075
Vuln IDs
  • V-89909
Rule IDs
  • SV-100559r1_rule
Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even when data appears to be static, the non-displayed logic in a web page may expose business logic or trusted system relationships. The integrity of all the data being exchanged between the user and web server must always be trusted. To protect the integrity and trust, encryption methods should be used to protect the complete communication session. HTTP connections in tc Server are managed through the Connector object. Setting the Connector's SSLEnabled flag, SSL handshake/encryption/decryption is enabled.
Checks: C-89601r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "SSLEnabled" is not set to "true" or is missing, this is a finding.

Fix: F-96651r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'SSLEnabled="true"'.

b
tc Server HORIZON must record user access in a format that enables monitoring of remote access.
AC-17 - Medium - CCI-000067 - V-89911 - SV-100561r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000067
Version
VRAU-TC-000085
Vuln IDs
  • V-89911
Rule IDs
  • SV-100561r1_rule
Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of success. 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 Access Log Valve creates log files in the same format as those created by standard web servers.
Checks: C-89603r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The AccessLogValve should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" prefix="access_log" suffix=".txt" rotatable="false" requestAttributesEnabled="true" checkExists="true"/&gt;

Fix: F-96653r1_fix

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

b
tc Server VCO must record user access in a format that enables monitoring of remote access.
AC-17 - Medium - CCI-000067 - V-89913 - SV-100563r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000067
Version
VRAU-TC-000090
Vuln IDs
  • V-89913
Rule IDs
  • SV-100563r1_rule
Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of success. 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 Access Log Valve creates log files in the same format as those created by standard web servers.
Checks: C-89605r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The AccessLogValve should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" rotatable="false" checkExists="true"/&gt;

Fix: F-96655r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must record user access in a format that enables monitoring of remote access.
AC-17 - Medium - CCI-000067 - V-89915 - SV-100565r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000067
Version
VRAU-TC-000095
Vuln IDs
  • V-89915
Rule IDs
  • SV-100565r1_rule
Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of success. 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 Access Log Valve creates log files in the same format as those created by standard web servers.
Checks: C-89607r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The AccessLogValve should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" checkExists="true" directory="logs" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/&gt;

Fix: F-96657r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server ALL must generate log records for system startup and shutdown.
AU-12 - Medium - CCI-000169 - V-89917 - SV-100567r1_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
VRAU-TC-000105
Vuln IDs
  • V-89917
Rule IDs
  • SV-100567r1_rule
Logging must be started as soon as possible when a service starts and when a service is stopped. Many forms of suspicious actions can be detected by analyzing logs for unexpected service starts and stops. Also, by starting to log immediately after a service starts, it becomes more difficult for suspicious activity to go unlogged. During start, tc Server reports system messages onto STDOUT and STDERR. These messages will be logged if the initialization script is configured correctly. For historical reasons, the standard log file for this is called catalina.out.
Checks: C-89609r1_chk

At the command prompt, execute the following command: more /storage/log/vmware/vco/app-server/catalina.out Verify that tc Server start and stop events are being logged. If the tc Server start and stop events are not being recorded, this is a finding. Note: The tc Server service is referred to as Catalina in the log.

Fix: F-96659r1_fix

Navigate to and open /usr/share/tomcat/bin/catalina.sh. Navigate to and locate the start block : "elif [ "$1" = "start" ] ; then" Navigate to and locate both "eval" statements : "org.apache.catalina.startup.Bootstrap "$@" start \" Add this statement immediately below both of the "eval" statements : '>> "$CATALINA_OUT" 2>&1 "&"'

b
tc Server HORIZON must generate log records for user access and authentication events.
AU-12 - Medium - CCI-000169 - V-89919 - SV-100569r1_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
VRAU-TC-000110
Vuln IDs
  • V-89919
Rule IDs
  • SV-100569r1_rule
Log records can be generated from various components within the web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific web server functionalities may be logged as well. The web server must allow the definition of what events are to be logged. As conditions change, the number and types of events to be logged may change, and the web server must be able to facilitate these changes. 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.
Checks: C-89611r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The "AccessLogValve" should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" prefix="access_log" suffix=".txt" rotatable="false" requestAttributesEnabled="true" checkExists="true"/&gt;

Fix: F-96661r1_fix

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

b
tc Server VCO must generate log records for user access and authentication events.
AU-12 - Medium - CCI-000169 - V-89921 - SV-100571r1_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
VRAU-TC-000115
Vuln IDs
  • V-89921
Rule IDs
  • SV-100571r1_rule
Log records can be generated from various components within the web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific web server functionalities may be logged as well. The web server must allow the definition of what events are to be logged. As conditions change, the number and types of events to be logged may change, and the web server must be able to facilitate these changes. 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.
Checks: C-89613r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The AccessLogValve should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" rotatable="false" checkExists="true"/&gt;

Fix: F-96663r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must generate log records for user access and authentication events.
AU-12 - Medium - CCI-000169 - V-89923 - SV-100573r1_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
VRAU-TC-000120
Vuln IDs
  • V-89923
Rule IDs
  • SV-100573r1_rule
Log records can be generated from various components within the web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific web server functionalities may be logged as well. The web server must allow the definition of what events are to be logged. As conditions change, the number and types of events to be logged may change, and the web server must be able to facilitate these changes. 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.
Checks: C-89615r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Host&gt; node. Verify that the node contains a &lt;Valve className="org.apache.catalina.valves.AccessLogValve"&gt; node. If an "AccessLogValve" is not configured correctly or is missing, this is a finding. Note: The "AccessLogValve" should be configured as follows: &lt;Valve className="org.apache.catalina.valves.AccessLogValve" checkExists="true" directory="logs" pattern="%h %l %u %t &amp;quot;%r&amp;quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/&gt;

Fix: F-96665r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server ALL must initiate logging during service start-up.
AU-14 - Medium - CCI-001464 - V-89925 - SV-100575r1_rule
RMF Control
AU-14
Severity
M
CCI
CCI-001464
Version
VRAU-TC-000125
Vuln IDs
  • V-89925
Rule IDs
  • SV-100575r1_rule
An attacker can compromise a web server during the startup process. If logging is not initiated until all the web server processes are started, key information may be missed and not available during a forensic investigation. To assure all logable events are captured, the web server must begin logging once the first web server process is initiated. During start, tc Server reports system messages onto STDOUT and STDERR. These messages will be logged if the initialization script is configured correctly. For historical reasons, the standard log file for this is called catalina.out.
Checks: C-89617r1_chk

At the command prompt, execute the following command: more /usr/share/tomcat/bin/catalina.sh Type /touch "$CATALINA_OUT" Verify that the start command contains the command "&gt;&gt; "$CATALINA_OUT" 2&gt;&amp;1 "&amp;"" If the command is not correct or is missing, this is a finding. Note: Use the "Enter" key to scroll down after typing /touch "$CATALINA_OUT"

Fix: F-96667r1_fix

Navigate to and open Navigate to and open /usr/share/tomcat/bin/catalina.sh. Navigate to and locate the start block : "elif [ "$1" = "start" ] ; then" Navigate to and locate both "eval" statements : "org.apache.catalina.startup.Bootstrap "$@" start \" Add this statement immediately below both of the "eval" statements : '>> "$CATALINA_OUT" 2>&1 "&"'

b
tc Server HORIZON must capture, record, and log all content related to a user session.
AU-14 - Medium - CCI-001462 - V-89927 - SV-100577r1_rule
RMF Control
AU-14
Severity
M
CCI
CCI-001462
Version
VRAU-TC-000130
Vuln IDs
  • V-89927
Rule IDs
  • SV-100577r1_rule
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.
Checks: C-89619r1_chk

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.

Fix: F-96669r1_fix

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

b
tc Server VCO must capture, record, and log all content related to a user session.
AU-14 - Medium - CCI-001462 - V-89929 - SV-100579r1_rule
RMF Control
AU-14
Severity
M
CCI
CCI-001462
Version
VRAU-TC-000135
Vuln IDs
  • V-89929
Rule IDs
  • SV-100579r1_rule
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.
Checks: C-89621r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If all content related to a user session is not being recorded, this is a finding.

Fix: F-96671r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must capture, record, and log all content related to a user session.
AU-14 - Medium - CCI-001462 - V-89931 - SV-100581r1_rule
RMF Control
AU-14
Severity
M
CCI
CCI-001462
Version
VRAU-TC-000140
Vuln IDs
  • V-89931
Rule IDs
  • SV-100581r1_rule
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server VCAC 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.
Checks: C-89623r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/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.

Fix: F-96673r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must produce log records containing sufficient information to establish what type of events occurred.
AU-3 - Medium - CCI-000130 - V-89933 - SV-100583r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000130
Version
VRAU-TC-000145
Vuln IDs
  • V-89933
Rule IDs
  • SV-100583r1_rule
After a security incident has occurred, investigators will often review log files to determine what happened. Understanding what type of event occurred is critical for investigation of a suspicious event. Like all servers, tc Server will typically process GET and POST requests clients. These will help investigators understand what happened.
Checks: C-89625r1_chk

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 HTTP "GET" and/or "POST" events are not being recorded, this is a finding.

Fix: F-96675r1_fix

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

b
tc Server VCO must produce log records containing sufficient information to establish what type of events occurred.
AU-3 - Medium - CCI-000130 - V-89935 - SV-100585r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000130
Version
VRAU-TC-000150
Vuln IDs
  • V-89935
Rule IDs
  • SV-100585r1_rule
After a security incident has occurred, investigators will often review log files to determine what happened. Understanding what type of event occurred is critical for investigation of a suspicious event. Like all servers, tc Server will typically process GET and POST requests clients. These will help investigators understand what happened.
Checks: C-89627r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If HTTP "GET" and/or "POST" events are not being recorded, this is a finding.

Fix: F-96677r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records containing sufficient information to establish what type of events occurred.
AU-3 - Medium - CCI-000130 - V-89937 - SV-100587r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000130
Version
VRAU-TC-000155
Vuln IDs
  • V-89937
Rule IDs
  • SV-100587r1_rule
After a security incident has occurred, investigators will often review log files to determine what happened. Understanding what type of event occurred is critical for investigation of a suspicious event. Like all servers, tc Server will typically process GET and POST requests clients. These will help investigators understand what happened.
Checks: C-89629r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If HTTP "GET" and/or "POST" events are not being recorded, this is a finding.

Fix: F-96679r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must produce log records containing sufficient information to establish when (date and time) events occurred.
AU-3 - Medium - CCI-000131 - V-89939 - SV-100589r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000131
Version
VRAU-TC-000160
Vuln IDs
  • V-89939
Rule IDs
  • SV-100589r1_rule
After a security incident has occurred, investigators will often review log files to determine when events occurred. Understanding the precise sequence of events is critical for investigation of a suspicious 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. The %t parameter specifies that the system time should be recorded.
Checks: C-89631r1_chk

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 the time and date of events are not being recorded, this is a finding.

Fix: F-96681r1_fix

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

b
tc Server VCO must produce log records containing sufficient information to establish when (date and time) events occurred.
AU-3 - Medium - CCI-000131 - V-89941 - SV-100591r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000131
Version
VRAU-TC-000165
Vuln IDs
  • V-89941
Rule IDs
  • SV-100591r1_rule
After a security incident has occurred, investigators will often review log files to determine when events occurred. Understanding the precise sequence of events is critical for investigation of a suspicious 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. The %t parameter specifies that the system time should be recorded.
Checks: C-89633r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the time and date of events are not being recorded, this is a finding.

Fix: F-96683r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records containing sufficient information to establish when (date and time) events occurred.
AU-3 - Medium - CCI-000131 - V-89943 - SV-100593r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000131
Version
VRAU-TC-000170
Vuln IDs
  • V-89943
Rule IDs
  • SV-100593r1_rule
After a security incident has occurred, investigators will often review log files to determine when events occurred. Understanding the precise sequence of events is critical for investigation of a suspicious 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. The %t parameter specifies that the system time should be recorded.
Checks: C-89635r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If the time and date of events are not being recorded, this is a finding.

Fix: F-96685r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must produce log records containing sufficient information to establish where within the web server the events occurred.
AU-3 - Medium - CCI-000132 - V-89945 - SV-100595r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000132
Version
VRAU-TC-000175
Vuln IDs
  • V-89945
Rule IDs
  • SV-100595r1_rule
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. 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.
Checks: C-89637r1_chk

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 the location of events are not being recorded, this is a finding.

Fix: F-96687r1_fix

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

b
tc Server VCO must produce log records containing sufficient information to establish where within the web server the events occurred.
AU-3 - Medium - CCI-000132 - V-89947 - SV-100597r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000132
Version
VRAU-TC-000180
Vuln IDs
  • V-89947
Rule IDs
  • SV-100597r1_rule
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. 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.
Checks: C-89639r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the location of events are not being recorded, this is a finding.

Fix: F-96689r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records containing sufficient information to establish where within the web server the events occurred.
AU-3 - Medium - CCI-000132 - V-89949 - SV-100599r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000132
Version
VRAU-TC-000185
Vuln IDs
  • V-89949
Rule IDs
  • SV-100599r1_rule
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. 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.
Checks: C-89641r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/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: F-96691r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must produce log records containing sufficient information to establish the source of events.
AU-3 - Medium - CCI-000133 - V-89951 - SV-100601r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000190
Vuln IDs
  • V-89951
Rule IDs
  • SV-100601r1_rule
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. The %h parameter will record the remote hostname or IP address that sent the request; i.e. the source of the event.
Checks: C-89643r1_chk

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 the source IP of events are not being recorded, this is a finding.

Fix: F-96693r1_fix

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

b
tc Server VCO must produce log records containing sufficient information to establish the source of events.
AU-3 - Medium - CCI-000133 - V-89953 - SV-100603r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000195
Vuln IDs
  • V-89953
Rule IDs
  • SV-100603r1_rule
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. The %h parameter will record the remote hostname or IP address that sent the request; i.e. the source of the event.
Checks: C-89645r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the source IP of events are not being recorded, this is a finding.

Fix: F-96695r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records containing sufficient information to establish the source of events.
AU-3 - Medium - CCI-000133 - V-89955 - SV-100605r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000200
Vuln IDs
  • V-89955
Rule IDs
  • SV-100605r1_rule
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. The %h parameter will record the remote hostname or IP address that sent the request; i.e. the source of the event.
Checks: C-89647r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If the source IP of events are not being recorded, this is a finding.

Fix: F-96697r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must be configured with the RemoteIpValve in order to produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event.
AU-3 - Medium - CCI-000133 - V-89957 - SV-100607r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000205
Vuln IDs
  • V-89957
Rule IDs
  • SV-100607r1_rule
tc Server HORIZON logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. tc Server HORIZON must be configured with the RemoteIpValve element in order to record the Client source vice the load balancer or proxy server as the source of every logable event. The RemoteIpValve enables the x-forward-* HTTP properties, which are used by the load balance to provide the client source.
Checks: C-89649r1_chk

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 actual client IP information, not load balancer or proxy server, is not being recorded, this is a finding.

Fix: F-96699r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to and locate <Host>. Configure the <Host> node with the <RemoteIpValve> below. Note: The "RemoteIpValve" should be configured as follows: <Valve className="org.apache.catalina.valves.RemoteIpValve" httpServerPort="80" httpsServerPort="443" protocolHeader="x-forwarded-proto" proxiesHeader="x-forwarded-by" remoteIpHeader="x-forwarded-for" internalProxies="127\.0\.0\.1"/>

b
tc Server VCO must be configured with the RemoteIpValve in order to produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event.
AU-3 - Medium - CCI-000133 - V-89959 - SV-100609r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000210
Vuln IDs
  • V-89959
Rule IDs
  • SV-100609r1_rule
tc Server HORIZON logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. tc Server HORIZON must be configured with the RemoteIpValve element in order to record the Client source vice the load balancer or proxy server as the source of every logable event. The RemoteIpValve enables the x-forward-* HTTP properties, which are used by the load balance to provide the client source.
Checks: C-89651r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If actual client IP information, not load balancer or proxy server, is not being recorded, this is a finding.

Fix: F-96701r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to and locate <Host>. Configure the <Host> node with the <RemoteIpValve> below. Note: The "RemoteIpValve" should be configured as follows: <Valve className="org.apache.catalina.valves.RemoteIpValve" remoteIpHeader="x-forwarded-for" remoteIpProxiesHeader="x-forwarded-by" internalProxies=".*" protocolHeader="x-forwarded-proto" />

b
tc Server VCAC must be configured with the RemoteIpValve in order to produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event.
AU-3 - Medium - CCI-000133 - V-89961 - SV-100611r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
VRAU-TC-000215
Vuln IDs
  • V-89961
Rule IDs
  • SV-100611r1_rule
tc Server VCAC logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct source, e.g. source IP, of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the logable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. tc Server VCAC must be configured with the RemoteIpValve element in order to record the Client source vice the load balancer or proxy server as the source of every logable event. The RemoteIpValve enables the x-forward-* HTTP properties, which are used by the load balance to provide the client source.
Checks: C-89653r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If actual client IP information, not load balancer or proxy server, is not being recorded, this is a finding.

Fix: F-96703r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to and locate <Host>. Configure the <Host> node with the <RemoteIpValve> below. Note: The "RemoteIpValve" should be configured as follows: <Valve className="org.apache.catalina.valves.RemoteIpValve" httpServerPort="80" httpsServerPort="443" internalProxies="127\.0\.0\.1" protocolHeader="x-forwarded-proto" proxiesHeader="x-forwarded-by" remoteIpHeader="x-forwarded-for"/>

b
tc Server HORIZON must produce log records that contain sufficient information to establish the outcome (success or failure) of events.
AU-3 - Medium - CCI-000134 - V-89963 - SV-100613r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000134
Version
VRAU-TC-000220
Vuln IDs
  • V-89963
Rule IDs
  • SV-100613r1_rule
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. Like all web servers, tc Server generates HTTP status codes. The status code is a 3-digit indicator of the outcome of the server's response to the request.
Checks: C-89655r1_chk

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 the HTTP status codes are not being recorded, this is a finding. Note: HTTP status codes are 3-digit codes, which are recorded immediately after "HTTP/1.1"

Fix: F-96705r1_fix

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

b
tc Server VCO must produce log records that contain sufficient information to establish the outcome (success or failure) of events.
AU-3 - Medium - CCI-000134 - V-89965 - SV-100615r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000134
Version
VRAU-TC-000225
Vuln IDs
  • V-89965
Rule IDs
  • SV-100615r1_rule
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. Like all web servers, tc Server generates HTTP status codes. The status code is a 3-digit indicator of the outcome of the server's response to the request.
Checks: C-89657r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the HTTP status codes are not being recorded, this is a finding. Note: HTTP status codes are 3-digit codes, which are recorded immediately after "HTTP/1.1"

Fix: F-96707r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records that contain sufficient information to establish the outcome (success or failure) of events.
AU-3 - Medium - CCI-000134 - V-89967 - SV-100617r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000134
Version
VRAU-TC-000230
Vuln IDs
  • V-89967
Rule IDs
  • SV-100617r1_rule
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. Like all web servers, tc Server generates HTTP status codes. The status code is a 3-digit indicator of the outcome of the server's response to the request.
Checks: C-89659r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/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 3-digit codes, which are recorded immediately after "HTTP/1.1"

Fix: F-96709r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.
AU-3 - Medium - CCI-001487 - V-89969 - SV-100619r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-001487
Version
VRAU-TC-000235
Vuln IDs
  • V-89969
Rule IDs
  • SV-100619r1_rule
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. The %u parameter will record the remote user that was authenticated. Knowing the authenticated user could be crucial to know in an investigation.
Checks: C-89661r1_chk

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 the identity of the user is not being recorded, this is a finding.

Fix: F-96711r1_fix

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

b
tc Server VCO must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.
AU-3 - Medium - CCI-001487 - V-89971 - SV-100621r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-001487
Version
VRAU-TC-000240
Vuln IDs
  • V-89971
Rule IDs
  • SV-100621r1_rule
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. The %u parameter will record the remote user that was authenticated. Knowing the authenticated user could be crucial to know in an investigation.
Checks: C-89663r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the identity of the user is not being recorded, this is a finding.

Fix: F-96713r1_fix

Navigate to and open /etc/vco/app-server/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"/>

b
tc Server VCAC must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.
AU-3 - Medium - CCI-001487 - V-89973 - SV-100623r1_rule
RMF Control
AU-3
Severity
M
CCI
CCI-001487
Version
VRAU-TC-000245
Vuln IDs
  • V-89973
Rule IDs
  • SV-100623r1_rule
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. The %u parameter will record the remote user that was authenticated. Knowing the authenticated user could be crucial to know in an investigation.
Checks: C-89665r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If the identity of the user is not being recorded, this is a finding.

Fix: F-96715r1_fix

Navigate to and open /etc/vcac/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" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server ALL must use a logging mechanism that is configured to alert the ISSO and SA in the event of a processing failure.
AU-5 - Medium - CCI-000139 - V-89975 - SV-100625r1_rule
RMF Control
AU-5
Severity
M
CCI
CCI-000139
Version
VRAU-TC-000250
Vuln IDs
  • V-89975
Rule IDs
  • SV-100625r1_rule
Reviewing log data allows an investigator to recreate the path of an attacker and to capture forensic data for later use. Log data is also essential to system administrators in their daily administrative duties on the hosted system or within the hosted applications. If the logging system begins to fail, events will not be recorded. Organizations must define logging failure events, at which time the application or the logging mechanism the application utilizes will provide a warning to the ISSO and SA at a minimum.
Checks: C-89667r1_chk

Interview the ISSO. Determine if log data and records are configured to alert the ISSO and SA in the event of processing failure. If log data and records are not configured to alert the ISSO and SA in the event of processing failure, this is a finding.

Fix: F-96717r1_fix

Configure the web server to provide an alert to the ISSO and SA when log processing failures occur. If the web server cannot generate alerts, utilize an external logging system that meets this criterion.

b
tc Server HORIZON log files must only be accessible by privileged users.
AU-9 - Medium - CCI-000162 - V-89977 - SV-100627r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000162
Version
VRAU-TC-000260
Vuln IDs
  • V-89977
Rule IDs
  • SV-100627r1_rule
Log data is essential in the investigation of events. If log data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve. In addition, access to log records provides information an attacker could potentially use to their advantage since each event record might contain communication ports, protocols, services, trust relationships, user names, etc. The web server must protect the log data from unauthorized read, write, copy, etc. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from access by non-privileged users.
Checks: C-89669r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/horizon If any log files have permissions less restrictive than "640", this is a finding.

Fix: F-96719r1_fix

At the command prompt, execute the following commands: chmod 640 /storage/log/vmware/horizon/<file> sed -i "/^[^#]*UMASK/ c\UMASK 077" /etc/login.defs Note: Substitute <file> with the listed file.

b
tc Server VCO log files must only be accessible by privileged users.
AU-9 - Medium - CCI-000162 - V-89979 - SV-100629r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000162
Version
VRAU-TC-000265
Vuln IDs
  • V-89979
Rule IDs
  • SV-100629r1_rule
Log data is essential in the investigation of events. If log data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve. In addition, access to log records provides information an attacker could potentially use to their advantage since each event record might contain communication ports, protocols, services, trust relationships, user names, etc. The web server must protect the log data from unauthorized read, write, copy, etc. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from access by non-privileged users.
Checks: C-89671r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vco/app-server If any log files have permissions less restrictive than "640", this is a finding.

Fix: F-96721r1_fix

At the command prompt, execute the following commands: chmod 640 /storage/log/vmware/vco/app-server/<file> sed -i "/^[^#]*UMASK/ c\UMASK 077" /etc/login.defs Note: Substitute <file> with the listed file.

b
tc Server VCAC log files must only be accessible by privileged users.
AU-9 - Medium - CCI-000162 - V-89981 - SV-100631r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000162
Version
VRAU-TC-000270
Vuln IDs
  • V-89981
Rule IDs
  • SV-100631r1_rule
Log data is essential in the investigation of events. If log data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve. In addition, access to log records provides information an attacker could potentially use to their advantage since each event record might contain communication ports, protocols, services, trust relationships, user names, etc. The web server must protect the log data from unauthorized read, write, copy, etc. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from access by non-privileged users.
Checks: C-89673r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vcac If any log files have permissions less restrictive than "640", this is a finding.

Fix: F-96723r1_fix

At the command prompt, execute the following commands: chmod 640 /storage/log/vmware/vcac/<file> sed -i "/^[^#]*UMASK/ c\UMASK 077" /etc/login.defs Note: Substitute <file> with the listed file.

b
tc Server HORIZON log files must be protected from unauthorized modification.
AU-9 - Medium - CCI-000163 - V-89983 - SV-100633r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000163
Version
VRAU-TC-000275
Vuln IDs
  • V-89983
Rule IDs
  • SV-100633r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of log records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized modification. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from modification by non-privileged users.
Checks: C-89675r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vcac If any log files are not owned by "root" or "vcac", this is a finding. The following files should be owned by "vcac": access_log catalina.out gc_logs host-manager localhost manager tc Server.pid The following files should be owned by "root": system-config-history telemetry toolsgc vcac-config

Fix: F-96725r1_fix

At the command prompt, execute the following command: chown <owner>:<owner> /storage/log/vmware/vcac/<file> Note: Substitute <file> with the listed file. Note: Substitute <owner> with the correct value below. The following files should be owned by "vcac": access_log catalina.out gc_logs host-manager localhost manager tc Server.pid The following files should be owned by "root": system-config-history telemetry toolsgc vcac-config

b
tc Server VCO log files must be protected from unauthorized modification.
AU-9 - Medium - CCI-000163 - V-89985 - SV-100635r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000163
Version
VRAU-TC-000280
Vuln IDs
  • V-89985
Rule IDs
  • SV-100635r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of log records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized modification. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from modification by non-privileged users.
Checks: C-89677r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vco/app-server If any log files are not owned by "vco", this is a finding.

Fix: F-96727r1_fix

At the command prompt, execute the following command: chown vco:vco /storage/log/vmware/vco/app-server/<file> Note: Substitute <file> with the listed file.

b
tc Server VCAC log files must be protected from unauthorized modification.
AU-9 - Medium - CCI-000163 - V-89987 - SV-100637r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000163
Version
VRAU-TC-000285
Vuln IDs
  • V-89987
Rule IDs
  • SV-100637r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of log records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized modification. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from modification by non-privileged users.
Checks: C-89679r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vcac If any log files are not owned by "root" or "vcac", this is a finding.

Fix: F-96729r1_fix

At the command prompt, execute the following command: Set the owner & group of these files: access_log.txt, audit.log, catalina.log, catalina.out, gc_logs.log.0.current, host-manager.log, localhost.log, manager.log, and tomcat.pid to vcac, with the following command: chown vcac:vcac /storage/log/vmware/vcac/<file> Set all other files not listed above to the owner and group of root, with the following command: chown root:root /storage/log/vmware/vcac/<file> Note: Substitute <file> with the listed file.

b
tc Server HORIZON log files must be protected from unauthorized deletion.
AU-9 - Medium - CCI-000164 - V-89989 - SV-100639r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000164
Version
VRAU-TC-000290
Vuln IDs
  • V-89989
Rule IDs
  • SV-100639r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of audit records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized deletion. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from deletion by non-privileged users.
Checks: C-89681r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/horizon If any log files are not group-owned by "www", this is a finding.

Fix: F-96731r1_fix

At the command prompt, execute the following command: chown horizon:www /storage/log/vmware/horizon/<file> Note: Substitute <file> with the listed file.

b
tc Server VCO log files must be protected from unauthorized deletion.
AU-9 - Medium - CCI-000164 - V-89991 - SV-100641r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000164
Version
VRAU-TC-000295
Vuln IDs
  • V-89991
Rule IDs
  • SV-100641r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of audit records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized deletion. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from deletion by non-privileged users.
Checks: C-89683r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vco/app-server If any log files are not group-owned by "vco", this is a finding.

Fix: F-96733r1_fix

At the command prompt, execute the following command: chown vco:vco /storage/log/vmware/vco/app-server/<file> Note: Substitute <file> with the listed file.

b
tc Server VCAC log files must be protected from unauthorized deletion.
AU-9 - Medium - CCI-000164 - V-89993 - SV-100643r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000164
Version
VRAU-TC-000300
Vuln IDs
  • V-89993
Rule IDs
  • SV-100643r1_rule
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will undertake is the modification or deletion of audit records to cover his tracks and prolong discovery. The web server must protect the log data from unauthorized deletion. This can be done by the web server if the web server is also doing the logging function. The web server may also use an external log system. In either case, the logs must be protected from deletion by non-privileged users.
Checks: C-89685r1_chk

At the command prompt, execute the following command: ls -lL /storage/log/vmware/vcac If any log files are not group-owned by "root", this is a finding.

Fix: F-96735r1_fix

At the command prompt, execute the following command: chown root:root /storage/log/vmware/vcac/<file> Note: Substitute <file> with the listed file.

b
tc Server ALL log data and records must be backed up onto a different system or media.
AU-9 - Medium - CCI-001348 - V-89995 - SV-100645r1_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001348
Version
VRAU-TC-000305
Vuln IDs
  • V-89995
Rule IDs
  • SV-100645r1_rule
Protection of tc Server ALL log data includes assuring log data is not accidentally lost or deleted. Backing up tc Server ALL log records to an unrelated system or onto separate media than the system the web server is actually running on helps to assure that, in the event of a catastrophic system failure, the log records will be retained.
Checks: C-89687r1_chk

Interview the ISSO. Determine if log data and records are not being backed up onto a different system or media. If log data and records are not being backed up onto a different system or media, this is a finding.

Fix: F-96737r1_fix

Ensure log data and records are being backed up to a different system or separate media.

b
tc Server ALL server files must be verified for their integrity (e.g., checksums and hashes) before becoming part of the production web server.
CM-5 - Medium - CCI-001749 - V-89997 - SV-100647r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
VRAU-TC-000310
Vuln IDs
  • V-89997
Rule IDs
  • SV-100647r1_rule
Being able to verify that a patch, upgrade, certificate, etc., being added to the web server is unchanged from the producer of the file is essential for file validation and non-repudiation of the information. VMware delivers product updates and patches regularly. It is crucial that system administrators coordinate installation of product updates with the site ISSO to ensure that only valid files are uploaded onto the system.
Checks: C-89689r1_chk

Interview the ISSO. Determine whether web server files are being fully reviewed, tested, and signed before being implemented into the production environment. If the web server files are not being fully reviewed, tested, and signed before being implemented into the production environment, this is a finding.

Fix: F-96739r1_fix

Configure the web server to verify object integrity before becoming part of the production web server or utilize an external tool designed to meet this requirement.

b
tc Server ALL expansion modules must be fully reviewed, tested, and signed before they can exist on a production web server.
CM-5 - Medium - CCI-001749 - V-89999 - SV-100649r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
VRAU-TC-000315
Vuln IDs
  • V-89999
Rule IDs
  • SV-100649r1_rule
In the case of a production web server, areas for content development and testing will not exist, as this type of content is only permissible on a development website. The process of developing on a functional production website entails a degree of trial and error and repeated testing. This process is often accomplished in an environment where debugging, sequencing, and formatting of content are the main goals. The opportunity for a malicious user to obtain files that reveal business logic and logon schemes is high in this situation. The existence of such immature content on a web server represents a significant security risk that is totally avoidable. VMware delivers product updates and patches regularly. It is crucial that system administrators coordinate installation of product updates with the site ISSO to ensure that only valid files are uploaded onto the system.
Checks: C-89691r1_chk

Interview the ISSO. Determine whether expansion modules are being fully reviewed, tested, and signed before being implemented into the production environment. If the expansion modules are not being fully reviewed, tested, and signed before being implemented into the production environment, this is a finding.

Fix: F-96741r1_fix

Configure the web server to enforce, internally or through an external utility, the review, testing and signing of modules before implementation into the production environment.

b
tc Server HORIZON must not use the tomcat-users XML database for user management.
CM-7 - Medium - CCI-000381 - V-90001 - SV-100651r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000320
Vuln IDs
  • V-90001
Rule IDs
  • SV-100651r1_rule
User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks like password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts; and all of this must be done enterprise-wide. For historical reasons, tc Server contains a tomcat-users.xml file in the configuration directory. This file was originally used by standalone applications that did not authenticate against an LDAP or other enterprise mechanism. vRA does not use this file.
Checks: C-89693r1_chk

At the command prompt, execute the following command: cat /opt/vmware/horizon/workspace/conf/tomcat-users.xml If "tomcat-users.xml" file contains any user information, this is a finding.

Fix: F-96743r1_fix

Contact the ISSO and/or SA. Determine why user data is being stored in "tomcat-users.xml". If the user data is not required then it should be removed. The vRA appliance does not maintain user data in this file by default.

b
tc Server VCO must not use the tomcat-users XML database for user management.
CM-7 - Medium - CCI-000381 - V-90003 - SV-100653r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000325
Vuln IDs
  • V-90003
Rule IDs
  • SV-100653r1_rule
User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks like password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts; and all of this must be done enterprise-wide. For historical reasons, tc Server contains a tomcat-users.xml file in the configuration directory. This file was originally used by standalone applications that did not authenticate against an LDAP or other enterprise mechanism. vRA does not use this file.
Checks: C-89695r1_chk

At the command prompt, execute the following command: cat /etc/vco/app-server/tomcat-users.xml If "tomcat-users.xml" file contains any user information, this is a finding.

Fix: F-96745r1_fix

Contact the ISSO and/or SA. Determine why user data is being stored in "tomcat-users.xml". If the user data is not required then it should be removed. The vRA appliance does not maintain user data in this file by default.

b
tc Server VCAC must not use the tomcat-users XML database for user management.
CM-7 - Medium - CCI-000381 - V-90005 - SV-100655r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000330
Vuln IDs
  • V-90005
Rule IDs
  • SV-100655r1_rule
User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks like password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts; and all of this must be done enterprise-wide. For historical reasons, tc Server contains a tomcat-users.xml file in the configuration directory. This file was originally used by standalone applications that did not authenticate against an LDAP or other enterprise mechanism. vRA does not use this file.
Checks: C-89697r1_chk

At the command prompt, execute the following command: cat /etc/vcac/tomcat-users.xml If "tomcat-users.xml" file contains any user information, this is a finding.

Fix: F-96747r1_fix

Contact the ISSO and/or SA. Determine why user data is being stored in "tomcat-users.xml". If the user data is not required then it should be removed. The vRA appliance does not maintain user data in this file by default.

b
tc Server ALL must only contain services and functions necessary for operation.
CM-7 - Medium - CCI-000381 - V-90007 - SV-100657r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000335
Vuln IDs
  • V-90007
Rule IDs
  • SV-100657r1_rule
A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DoD system. The web server must provide the capability to disable, uninstall, or deactivate functionality and services that are deemed to be non-essential to the web server mission or can adversely impact server performance.
Checks: C-89699r1_chk

Interview the ISSO. Review the web server documentation and deployed configuration to determine if web server features, services, and processes are installed that are not needed for hosted application deployment. If excessive features, services, and processes are installed, this is a finding.

Fix: F-96749r1_fix

Uninstall or deactivate features, services, and processes not needed by the web server for operation.

c
tc Server ALL must exclude documentation, sample code, example applications, and tutorials.
CM-7 - High - CCI-000381 - V-90009 - SV-100659r1_rule
RMF Control
CM-7
Severity
H
CCI
CCI-000381
Version
VRAU-TC-000345
Vuln IDs
  • V-90009
Rule IDs
  • SV-100659r1_rule
Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server because this type of code has not been evaluated and approved. A production web server must only contain components that are operationally necessary (e.g., compiled code, scripts, web-content, etc.). Any documentation, sample code, example applications, and tutorials must be removed from a production web server. Because tc Server is installed as part of the entire vRA application, and not installed separately, VMware has ensured that all documentation, sample code, example applications, and tutorials have been removed from tc Server as part of the build process.
Checks: C-89701r1_chk

Interview the ISSO. Review the web server documentation and deployed configuration to determine if documentation, sample code, example applications, and tutorials have been removed. If documentation, sample code, example applications, and tutorials have not been removed, this is a finding.

Fix: F-96751r1_fix

Remove all documentation, sample code, example applications, and tutorials.

b
tc Server ALL must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.
CM-7 - Medium - CCI-000381 - V-90011 - SV-100661r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000360
Vuln IDs
  • V-90011
Rule IDs
  • SV-100661r1_rule
Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. tc Server configures MIME types in the web.xml file. By ensuring that sh, csh, and shar MIME types are not included in web.xml, the server is protected against malicious users tricking the server into executing shell command files.
Checks: C-89703r1_chk

At the command prompt, execute the following command: find / -name 'web.xml' -print0 | xargs -0r grep -HEn '(x-csh&lt;)|(x-sh&lt;)|(x-shar&lt;)|(x-ksh&lt;)' If the command produces any output, this is a finding.

Fix: F-96753r1_fix

Navigate to a file that was listed. Open the file in a text editor. Delete any of the following types: application/x-sh application/x-shar application/x-csh application/x-ksh

b
tc Server ALL must have all mappings to unused and vulnerable scripts to be removed.
CM-7 - Medium - CCI-000381 - V-90013 - SV-100663r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000365
Vuln IDs
  • V-90013
Rule IDs
  • SV-100663r1_rule
Scripts allow server side processing on behalf of the hosted application user or as processes needed in the implementation of hosted applications. Removing scripts not needed for application operation or deemed vulnerable helps to secure the web server. To assure scripts are not added to the web server and run maliciously, those script mappings that are not needed or used by the web server for hosted application operation must be removed. Because tc Server is installed as part of the entire vRA application, and not installed separately, VMware has ensured that scripts not needed for application operation or deemed vulnerable have been removed from tc Server.
Checks: C-89705r1_chk

Interview the ISSO. Review the web server documentation and deployed configuration to determine if all mappings to unused and vulnerable scripts to be removed. If all mappings to unused and vulnerable scripts have not been removed, this is a finding.

Fix: F-96755r1_fix

Remove script mappings that are not needed for web server and hosted application operation.

b
tc Server HORIZON must have mappings set for Java Servlet Pages.
CM-7 - Medium - CCI-000381 - V-90015 - SV-100665r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000370
Vuln IDs
  • V-90015
Rule IDs
  • SV-100665r1_rule
Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to be delivered to a client. By not specifying which files can and which files cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. As a derivative of the Apache Tomcat project, tc Server is a java-based web server. As a result, the main file extension used by tc Server is *.jsp. This check ensures that the *.jsp file type has been properly mapped to servlets.
Checks: C-89707r1_chk

At the command prompt, execute the following command: grep -E '&lt;url-pattern&gt;\*\.jsp&lt;/url-pattern&gt;' -B 2 -A 2 /opt/vmware/horizon/workspace/conf/web.xml If the jsp and jspx file extensions have not been mapped to the JSP servlet, this is a finding.

Fix: F-96757r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Navigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>jsp</servlet-name>. Configure the <servlet-mapping> node to look like the code snippet below: <!-- The mappings for the JSP servlet --> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>*.jsp</url-pattern> <url-pattern>*.jspx</url-pattern> </servlet-mapping>

b
tc Server VCO must have mappings set for Java Servlet Pages.
CM-7 - Medium - CCI-000381 - V-90017 - SV-100667r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000375
Vuln IDs
  • V-90017
Rule IDs
  • SV-100667r1_rule
Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to be delivered to a client. By not specifying which files can and which files cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. As a derivative of the Apache Tomcat project, tc Server is a java-based web server. As a result, the main file extension used by tc Server is *.jsp. This check ensures that the *.jsp file type has been properly mapped to servlets.
Checks: C-89709r1_chk

At the command prompt, execute the following command: grep -E '&lt;url-pattern&gt;\*\.jsp&lt;/url-pattern&gt;' -B 2 -A 2 /etc/vco/app-server/web.xml If the jsp and jspx file extensions have not been mapped to the JSP servlet, this is a finding.

Fix: F-96759r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Navigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>jsp</servlet-name>. Configure the <servlet-mapping> node to look like the code snippet below: <!-- The mappings for the JSP servlet --> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>*.jsp</url-pattern> <url-pattern>*.jspx</url-pattern> </servlet-mapping>

b
tc Server VCAC must have mappings set for Java Servlet Pages.
CM-7 - Medium - CCI-000381 - V-90019 - SV-100669r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000380
Vuln IDs
  • V-90019
Rule IDs
  • SV-100669r1_rule
Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to be delivered to a client. By not specifying which files can and which files cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. As a derivative of the Apache Tomcat project, tc Server is a java-based web server. As a result, the main file extension used by tc Server is *.jsp. This check ensures that the *.jsp file type has been properly mapped to servlets.
Checks: C-89711r1_chk

At the command prompt, execute the following command: grep -E '&lt;url-pattern&gt;\*\.jsp&lt;/url-pattern&gt;' -B 2 -A 2 /etc/vcac/web.xml If the jsp and jspx file extensions have not been mapped to the JSP servlet, this is a finding.

Fix: F-96761r1_fix

Navigate to and open /etc/vcac/web.xml. Navigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>jsp</servlet-name>. Configure the <servlet-mapping> node to look like the code snippet below: <!-- The mappings for the JSP servlet --> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>*.jsp</url-pattern> <url-pattern>*.jspx</url-pattern> </servlet-mapping>

b
tc Server ALL must not have the Web Distributed Authoring (WebDAV) servlet installed.
CM-7 - Medium - CCI-000381 - V-90021 - SV-100671r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000385
Vuln IDs
  • V-90021
Rule IDs
  • SV-100671r1_rule
A web server can be installed with functionality that, just by its nature, is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server. As an extension to Tomcat, tc Server VCO-CFG uses the org.apache.catalina.servlets.WebdavServlet servlet to provide WebDAV services. Because the WebDAV service has been found to have an excessive number of vulnerabilities, this servlet must not be installed.
Checks: C-89713r1_chk

At the command prompt, execute the following command: find / -name 'web.xml' -print0 | xargs -0r grep -HEn 'webdav' If the command produces any output, this is a finding.

Fix: F-96763r1_fix

Navigate to and open all listed files. Navigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>webdav</servlet-name>. Remove the WebDAV servlet and any mapping associated with it.

b
tc Server HORIZON must be configured with memory leak protection.
CM-7 - Medium - CCI-000381 - V-90023 - SV-100673r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000390
Vuln IDs
  • V-90023
Rule IDs
  • SV-100673r1_rule
The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, tc Server HORIZON can continue to consume system resources that will lead to OutOfMemoryErrors when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton as this will cause a memory leak if a web application class loader happens to be the context class loader at the time. The JreMemoryLeakPreventionListener class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure that the hosted application does not consume system resources and cause an unstable environment.
Checks: C-89715r1_chk

At the command prompt, execute the following command: grep JreMemoryLeakPreventionListener /opt/vmware/horizon/workspace/conf/server.xml If the JreMemoryLeakPreventionListener &lt;Listener&gt; node is not listed, this is a finding.

Fix: F-96765r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to the <Server> node. Add '<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>' to the <Server> node.

b
tc Server VCO must be configured with memory leak protection.
CM-7 - Medium - CCI-000381 - V-90025 - SV-100675r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000395
Vuln IDs
  • V-90025
Rule IDs
  • SV-100675r1_rule
The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, tc Server HORIZON can continue to consume system resources that will lead to OutOfMemoryErrors when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton as this will cause a memory leak if a web application class loader happens to be the context class loader at the time. The JreMemoryLeakPreventionListener class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure that the hosted application does not consume system resources and cause an unstable environment.
Checks: C-89717r1_chk

At the command prompt, execute the following command: grep JreMemoryLeakPreventionListener /etc/vco/app-server/server.xml If the JreMemoryLeakPreventionListener &lt;Listener&gt; node is not listed, this is a finding.

Fix: F-96767r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Server> node. Add '<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>' to the <Server> node.

b
tc Server VCAC must be configured with memory leak protection.
CM-7 - Medium - CCI-000381 - V-90027 - SV-100677r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000400
Vuln IDs
  • V-90027
Rule IDs
  • SV-100677r1_rule
The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, tc Server VCAC can continue to consume system resources that will lead to OutOfMemoryErrors when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton as this will cause a memory leak if a web application class loader happens to be the context class loader at the time. The JreMemoryLeakPreventionListener class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure that the hosted application does not consume system resources and cause an unstable environment.
Checks: C-89719r1_chk

At the command prompt, execute the following command: grep JreMemoryLeakPreventionListener /etc/vcac/server.xml If the JreMemoryLeakPreventionListener &lt;Listener&gt; node is not listed, this is a finding.

Fix: F-96769r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Server> node. Add '<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>' to the <Server> node.

b
tc Server VCO must not have any symbolic links in the web content directory tree.
CM-7 - Medium - CCI-000381 - V-90029 - SV-100679r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000410
Vuln IDs
  • V-90029
Rule IDs
  • SV-100679r1_rule
A web server is designed to deliver content and execute scripts or applications on the request of a client or user. Containing user requests to files in the directory tree of the hosted web application and limiting the execution of scripts and applications guarantees that the user is not accessing information protected outside the application's realm. By checking that no symblic links exist in the document root, the web server is protected from users jumping outside the hosted application directory tree and gaining access to the other directories, including the system root.
Checks: C-89721r1_chk

At the command prompt, execute the following command: ls -lR /usr/lib/vco/configuration/webapps | grep '^l' If the command produces any output, this is a finding.

Fix: F-96771r1_fix

At the command prompt, execute the following commands: Note: Replace <file_name> for the name of any files that were returned. unlink <file_name> Repeat the commands for each file that was returned.

b
tc Server HORIZON must be configured to use a specified IP address and port.
CM-7 - Medium - CCI-000382 - V-90031 - SV-100681r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000382
Version
VRAU-TC-000420
Vuln IDs
  • V-90031
Rule IDs
  • SV-100681r1_rule
The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utilize, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.
Checks: C-89723r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If either the IP address or the port is not specified for each &lt;Connector&gt;, this is a finding.

Fix: F-96773r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'address="XXXXX"'. Note: Replace XXXXX with the appropriate address for that node.

b
tc Server VCO must be configured to use a specified IP address and port.
CM-7 - Medium - CCI-000382 - V-90033 - SV-100683r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000382
Version
VRAU-TC-000425
Vuln IDs
  • V-90033
Rule IDs
  • SV-100683r1_rule
The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utilize, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.
Checks: C-89725r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Connector&gt; node. If either the IP address or the port is not specified for the &lt;Connector&gt;, this is a finding.

Fix: F-96775r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'address="XXXXX"'. Note: Replace XXXXX with the appropriate address for that node.

b
tc Server VCAC must be configured to use a specified IP address and port.
CM-7 - Medium - CCI-000382 - V-90035 - SV-100685r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000382
Version
VRAU-TC-000430
Vuln IDs
  • V-90035
Rule IDs
  • SV-100685r1_rule
The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to utilize, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.
Checks: C-89727r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If either the IP address or the port is not specified for the &lt;Connector&gt;, this is a finding.

Fix: F-96777r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'address="XXXXX"'. Note: Replace XXXXX with the appropriate address for that node.

b
tc Server HORIZON must encrypt passwords during transmission.
IA-5 - Medium - CCI-000197 - V-90037 - SV-100687r1_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000197
Version
VRAU-TC-000435
Vuln IDs
  • V-90037
Rule IDs
  • SV-100687r1_rule
Data used to authenticate, especially passwords, needs to be protected at all times, and encryption is the standard method for protecting authentication data during transmission. Data used to authenticate can be passed to and from the web server for many reasons. Examples include data passed from a user to the web server through an HTTPS connection for authentication, the web server authenticating to a backend database for data retrieval and posting, and the web server authenticating to a clustered web server manager for an update. HTTP connections in tc Server are managed through the Connector object. Setting the Connector's SSLEnabled flag, SSL handshake/encryption/decryption is enabled.
Checks: C-89729r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "SSLEnabled" is not set to "true" or is missing, this is a finding.

Fix: F-96779r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'SSLEnabled="true"'.

b
tc Server VCAC must encrypt passwords during transmission.
IA-5 - Medium - CCI-000197 - V-90039 - SV-100689r1_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000197
Version
VRAU-TC-000440
Vuln IDs
  • V-90039
Rule IDs
  • SV-100689r1_rule
Data used to authenticate, especially passwords, needs to be protected at all times, and encryption is the standard method for protecting authentication data during transmission. Data used to authenticate can be passed to and from the web server for many reasons. Examples include data passed from a user to the web server through an HTTPS connection for authentication, the web server authenticating to a backend database for data retrieval and posting, and the web server authenticating to a clustered web server manager for an update. HTTP connections in tc Server are managed through the Connector object. Setting the Connector's SSLEnabled flag, SSL handshake/encryption/decryption is enabled.
Checks: C-89731r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "SSLEnabled" is not set to "true" or is missing, this is a finding.

Fix: F-96781r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure each <Connector> node with the value 'SSLEnabled="true"'.

b
tc Server ALL must validate client certificates, to include all intermediary CAs, to ensure the client-presented certificates are valid and that the entire trust chain is valid.
IA-5 - Medium - CCI-000185 - V-90041 - SV-100691r1_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000185
Version
VRAU-TC-000445
Vuln IDs
  • V-90041
Rule IDs
  • SV-100691r1_rule
The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.
Checks: C-89733r1_chk

If PKI is not being used, this check is Not Applicable. Interview the ISSO. Review tc Server ALL configuration to verify that certificates being provided by the client are being validated in accordance with RFC 5280. If certificates are not being validated in accordance with RFC 5280, this is a finding.

Fix: F-96783r1_fix

If PKI is not being used, this check is Not Applicable. Validate client certificates in accordance with RFC 5280.

b
tc Server HORIZON must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when authenticating users and processes.
IA-7 - Medium - CCI-000803 - V-90043 - SV-100693r1_rule
RMF Control
IA-7
Severity
M
CCI
CCI-000803
Version
VRAU-TC-000460
Vuln IDs
  • V-90043
Rule IDs
  • SV-100693r1_rule
Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised due to weak algorithms. FIPS 140-2 is the current standard for validating cryptographic modules and NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules. vRA relies upon the OpenSSL suite of encryption libraries. A special carefully defined software component called the OpenSSL FIPS Object Module has been created from the OpenSSL libraries to provide FIPS 140-2 validated encryption. This Module was designed for compatibility with OpenSSL so that products using the OpenSSL API can be converted to use validated cryptography with minimal effort.
Checks: C-89735r1_chk

At the command prompt, execute the following command: grep bio-ssl.cipher.list /opt/vmware/horizon/workspace/conf/catalina.properties If the value of "bio-ssl.cipher.list" does not match the list of FIPS 140-2 ciphers or is missing, this is a finding. Note: To view a list of FIPS 140-2 ciphers, at the command prompt execute the following command: openssl ciphers 'FIPS'

Fix: F-96785r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to and locate "bio-ssl.cipher.list". Configure the "bio-ssl.cipher.list" with FIPS 140-2 compliant ciphers.

b
tc Server VCAC must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when authenticating users and processes.
IA-7 - Medium - CCI-000803 - V-90045 - SV-100695r1_rule
RMF Control
IA-7
Severity
M
CCI
CCI-000803
Version
VRAU-TC-000465
Vuln IDs
  • V-90045
Rule IDs
  • SV-100695r1_rule
Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised due to weak algorithms. FIPS 140-2 is the current standard for validating cryptographic modules and NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules. vRA relies upon the OpenSSL suite of encryption libraries. A special carefully defined software component called the OpenSSL FIPS Object Module has been created from the OpenSSL libraries to provide FIPS 140-2 validated encryption. This Module was designed for compatibility with OpenSSL so that products using the OpenSSL API can be converted to use validated cryptography with minimal effort.
Checks: C-89737r1_chk

At the command prompt, execute the following command: grep cipher /etc/vcac/catalina.properties If the value of "cipher" does not match the list of FIPS 140-2 ciphers or is missing, this is a finding. Note: To view a list of FIPS 140-2 ciphers, at the command prompt execute the following command: openssl ciphers 'FIPS'

Fix: F-96787r1_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to and locate "cipher". Configure the "cipher" with FIPS 140-2 compliant ciphers.

c
tc Server HORIZON accounts accessing the directory tree, the shell, or other operating system functions and utilities must be administrative accounts.
SC-2 - High - CCI-001082 - V-90047 - SV-100697r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000475
Vuln IDs
  • V-90047
Rule IDs
  • SV-100697r1_rule
As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. The resources to which these accounts have access must also be closely monitored and controlled. Only the system administrator needs access to all the system's capabilities, while the web administrator and associated staff require access and control of the web content and web server configuration files. As with all secure web server installations, tc Server files and directories must be adequately protected with correct permissions.
Checks: C-89739r1_chk

At the command prompt, execute the following command: ls -alR /opt/vmware/horizon/workspace/webapps | grep -E '^-' | awk '$3 !~ /horizon|root/ {print}' If the command produces any output, this is a finding.

Fix: F-96789r1_fix

At the command prompt, execute the following command: chown horizon:www <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned.

c
tc Server VCO accounts accessing the directory tree, the shell, or other operating system functions and utilities must be administrative accounts.
SC-2 - High - CCI-001082 - V-90049 - SV-100699r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000480
Vuln IDs
  • V-90049
Rule IDs
  • SV-100699r1_rule
As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. The resources to which these accounts have access must also be closely monitored and controlled. Only the system administrator needs access to all the system's capabilities, while the web administrator and associated staff require access and control of the web content and web server configuration files. As with all secure web server installations, tc Server files and directories must be adequately protected with correct permissions.
Checks: C-89741r1_chk

At the command prompt, execute the following command: ls -lL /usr/lib/vco/configuration/webapps If the listed files are not owned by "vco", this is a finding.

Fix: F-96791r1_fix

At the command prompt, execute the following command: chown vco:vco <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned.

c
tc Server VCAC accounts accessing the directory tree, the shell, or other operating system functions and utilities must be administrative accounts.
SC-2 - High - CCI-001082 - V-90051 - SV-100701r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000485
Vuln IDs
  • V-90051
Rule IDs
  • SV-100701r1_rule
As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. The resources to which these accounts have access must also be closely monitored and controlled. Only the system administrator needs access to all the system's capabilities, while the web administrator and associated staff require access and control of the web content and web server configuration files. As with all secure web server installations, tc Server files and directories must be adequately protected with correct permissions.
Checks: C-89743r1_chk

At the command prompt, execute the following command: ls -alR /etc/vcac /usr/lib/vcac/server/webapps | grep -E '^-' | awk '$3 !~ /vcac|root/ {print}' If the command produces any output, this is a finding.

Fix: F-96793r1_fix

At the command prompt, execute the following command: If the file was found in /etc/vcac or /usr/lib/vcac/server/webapps, execute the following command: chown vcac:vcac <file_name> Note: Replace <file_name> for the name of the file that was returned.

c
tc Server HORIZON web server application directories must not be accessible to anonymous user.
SC-2 - High - CCI-001082 - V-90053 - SV-100703r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000490
Vuln IDs
  • V-90053
Rule IDs
  • SV-100703r1_rule
In order to properly monitor the changes to the web server and the hosted applications, logging must be enabled. Along with logging being enabled, each record must properly contain the changes made and the names of those who made the changes. Allowing anonymous users the capability to change the web server or the hosted application will not generate proper log information that can then be used for forensic reporting in the case of a security issue. Allowing anonymous users to make changes will also grant change capabilities to anybody without forcing a user to authenticate before the changes can be made.
Checks: C-89745r1_chk

At the command prompt, execute the following command: ls -alR /opt/vmware/horizon/workspace | grep -E '^-' | awk '$1 !~ /---$/ {print}' If the command produces any output, this is a finding.

Fix: F-96795r1_fix

At the command prompt, execute the following command: chmod 750 <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned.

c
tc Server VCO web server application directories must not be accessible to anonymous user.
SC-2 - High - CCI-001082 - V-90055 - SV-100705r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000495
Vuln IDs
  • V-90055
Rule IDs
  • SV-100705r1_rule
In order to properly monitor the changes to the web server and the hosted applications, logging must be enabled. Along with logging being enabled, each record must properly contain the changes made and the names of those who made the changes. Allowing anonymous users the capability to change the web server or the hosted application will not generate proper log information that can then be used for forensic reporting in the case of a security issue. Allowing anonymous users to make changes will also grant change capabilities to anybody without forcing a user to authenticate before the changes can be made.
Checks: C-89747r1_chk

At the command prompt, execute the following command: ls -alR /etc/vco /usr/lib/vco/app-server | grep -E '^-' | awk '$1 !~ /---$/ {print}' If anything is returned, this is a finding.

Fix: F-96797r1_fix

At the command prompt, execute the following command: chmod 750 <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned.

c
tc Server VCAC web server application directories must not be accessible to anonymous user.
SC-2 - High - CCI-001082 - V-90057 - SV-100707r1_rule
RMF Control
SC-2
Severity
H
CCI
CCI-001082
Version
VRAU-TC-000500
Vuln IDs
  • V-90057
Rule IDs
  • SV-100707r1_rule
In order to properly monitor the changes to the web server and the hosted applications, logging must be enabled. Along with logging being enabled, each record must properly contain the changes made and the names of those who made the changes. Allowing anonymous users the capability to change the web server or the hosted application will not generate proper log information that can then be used for forensic reporting in the case of a security issue. Allowing anonymous users to make changes will also grant change capabilities to anybody without forcing a user to authenticate before the changes can be made.
Checks: C-89749r1_chk

At the command prompt, execute the following command: ls -alR /etc/vcac /usr/lib/vcac/server/webapps | grep -E '^-' | awk '$1 !~ /---$/ {print}' If the command produces any output, this is a finding.

Fix: F-96799r1_fix

At the command prompt, execute the following command: chmod 750 <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned.

b
tc Server ALL baseline must be documented and maintained.
SC-24 - Medium - CCI-001190 - V-90059 - SV-100709r1_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001190
Version
VRAU-TC-000550
Vuln IDs
  • V-90059
Rule IDs
  • SV-100709r1_rule
Making certain that the web server has not been updated by an unauthorized user is always a concern. Adding patches, functions, and modules that are untested and not part of the baseline opens the possibility for security risks. The web server must offer, and not hinder, a method that allows for the quick and easy reinstallation of a verified and patched baseline to guarantee the production web server is up-to-date and has not been modified to add functionality or expose security risks. Because tc Server is installed as part of the entire vRA application, and not installed separately, VMware has ensured that all updates, upgrades, and patches have been thoroughly tested before becoming part of the production build process.
Checks: C-89751r1_chk

Interview the ISSO. Review the web server documentation and deployed configuration to determine if the tc Server code baseline is documented and maintained. If the tc Server code baseline is not documented and maintained, this is a finding.

Fix: F-96801r1_fix

Develop baseline documentation of the tc Server codebase.

b
tc Server HORIZON must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
SC-24 - Medium - CCI-001190 - V-90061 - SV-100711r1_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001190
Version
VRAU-TC-000555
Vuln IDs
  • V-90061
Rule IDs
  • SV-100711r1_rule
Determining a safe state for failure and weighing that against a potential DoS for users depends on what type of application the web server is hosting. For an application presenting publicly available information that is not critical, a safe state for failure might be to shut down for any type of failure; but for an application that presents critical and timely information, a shutdown might not be the best state for all failures. Performing a proper risk analysis of the hosted applications and configuring the web server according to what actions to take for each failure condition will provide a known fail safe state for the web server. The VMware engineering process includes regression testing of new and modified components before they become part of the production build process.
Checks: C-89753r1_chk

At the command line, execute the following command: grep EXIT_ON_INIT_FAILURE /opt/vmware/horizon/workspace/conf/catalina.properties If the "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" setting is not set to "true" or is missing, this is a finding.

Fix: F-96803r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Configure the setting "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" with the value "true". Note: The word "true" should not be surrounded with any quote characters.

b
tc Server VCO must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
SC-24 - Medium - CCI-001190 - V-90063 - SV-100713r1_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001190
Version
VRAU-TC-000560
Vuln IDs
  • V-90063
Rule IDs
  • SV-100713r1_rule
Determining a safe state for failure and weighing that against a potential DoS for users depends on what type of application the web server is hosting. For an application presenting publicly available information that is not critical, a safe state for failure might be to shut down for any type of failure; but for an application that presents critical and timely information, a shutdown might not be the best state for all failures. Performing a proper risk analysis of the hosted applications and configuring the web server according to what actions to take for each failure condition will provide a known fail safe state for the web server. The VMware engineering process includes regression testing of new and modified components before they become part of the production build process.
Checks: C-89755r1_chk

At the command line, execute the following command: grep EXIT_ON_INIT_FAILURE /etc/vco/app-server/catalina.properties If the "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" setting is not set to "true" or is missing, this is a finding.

Fix: F-96805r1_fix

Navigate to and open /etc/vco/app-server/catalina.properties. Configure the setting "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" with the value "true". Note: The word "true" should not be surrounded with any quote characters.

b
tc Server VCAC must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.
SC-24 - Medium - CCI-001190 - V-90065 - SV-100715r1_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001190
Version
VRAU-TC-000565
Vuln IDs
  • V-90065
Rule IDs
  • SV-100715r1_rule
Determining a safe state for failure and weighing that against a potential DoS for users depends on what type of application the web server is hosting. For an application presenting publicly available information that is not critical, a safe state for failure might be to shut down for any type of failure; but for an application that presents critical and timely information, a shutdown might not be the best state for all failures. Performing a proper risk analysis of the hosted applications and configuring the web server according to what actions to take for each failure condition will provide a known fail safe state for the web server. The VMware engineering process includes regression testing of new and modified components before they become part of the production build process.
Checks: C-89757r1_chk

At the command line, execute the following command: grep EXIT_ON_INIT_FAILURE /etc/vcac/catalina.properties If the "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" setting is not set to "true" or is missing, this is a finding.

Fix: F-96807r1_fix

Navigate to and open /etc/vcac/catalina.properties. Configure the setting "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE" with the value "true". Note: The word "true" should not be surrounded with any quote characters.

b
tc Server HORIZON document directory must be in a separate partition from the web servers system files.
SC-3 - Medium - CCI-001084 - V-90067 - SV-100717r1_rule
RMF Control
SC-3
Severity
M
CCI
CCI-001084
Version
VRAU-TC-000580
Vuln IDs
  • V-90067
Rule IDs
  • SV-100717r1_rule
A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted application files to be accessed and delivered. To allow a client access to system files of any type is a major security risk that is entirely avoidable. Obtaining such access is the goal of directory traversal and URL manipulation vulnerabilities. To facilitate such access by misconfiguring the web document (home) directory is a serious error. In addition, having the path on the same drive as the system folder compounds potential attacks such as drive space exhaustion. As a Tomcat derivative, tc Server stores the web applications in a special 'webapps' folder. The Java engine, however, is stored in a separate are of the OS directory structure. For greatest security It is important to verify that the webapps and the Java directories remain separated.
Checks: C-89759r1_chk

At the command prompt, execute the following commands: df -k /usr/java/jre-vmware df -k /opt/vmware/horizon/workspace/webapps If the two directories above are on the same partition, this is a finding.

Fix: F-96809r1_fix

Consult with the ISSO. Move the tc Server HORIZON /opt/vmware/horizon/workspace/webapps folder to a separate partition.

b
tc Server VCO document directory must be in a separate partition from the web servers system files.
SC-3 - Medium - CCI-001084 - V-90069 - SV-100719r1_rule
RMF Control
SC-3
Severity
M
CCI
CCI-001084
Version
VRAU-TC-000585
Vuln IDs
  • V-90069
Rule IDs
  • SV-100719r1_rule
A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted application files to be accessed and delivered. To allow a client access to system files of any type is a major security risk that is entirely avoidable. Obtaining such access is the goal of directory traversal and URL manipulation vulnerabilities. To facilitate such access by misconfiguring the web document (home) directory is a serious error. In addition, having the path on the same drive as the system folder compounds potential attacks such as drive space exhaustion. As a Tomcat derivative, tc Server stores the web applications in a special 'webapps' folder. The Java engine, however, is stored in a separate are of the OS directory structure. For greatest security It is important to verify that the webapps and the Java directories remain separated.
Checks: C-89761r1_chk

At the command prompt, execute the following commands: df -k /usr/java/jre-vmware df -k /usr/lib/vco/configuration/webapps If the two directories above are on the same partition, this is a finding.

Fix: F-96811r1_fix

Consult with the ISSO. Move the tc Server VCO /usr/lib/vco/configuration/webapps folder to a separate partition.

b
tc Server VCAC document directory must be in a separate partition from the web servers system files.
SC-3 - Medium - CCI-001084 - V-90071 - SV-100721r1_rule
RMF Control
SC-3
Severity
M
CCI
CCI-001084
Version
VRAU-TC-000590
Vuln IDs
  • V-90071
Rule IDs
  • SV-100721r1_rule
A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted application files to be accessed and delivered. To allow a client access to system files of any type is a major security risk that is entirely avoidable. Obtaining such access is the goal of directory traversal and URL manipulation vulnerabilities. To facilitate such access by misconfiguring the web document (home) directory is a serious error. In addition, having the path on the same drive as the system folder compounds potential attacks such as drive space exhaustion. As a Tomcat derivative, tc Server stores the web applications in a special 'webapps' folder. The Java engine, however, is stored in a separate are of the OS directory structure. For greatest security It is important to verify that the webapps and the Java directories remain separated.
Checks: C-89763r1_chk

At the command prompt, execute the following commands: df -k /usr/java/jre-vmware df -k /usr/lib/vcac/server/webapps If the two directories above are on the same partition, this is a finding.

Fix: F-96813r1_fix

Consult with the ISSO. Move the tc Server VCAC /usr/lib/vcac/server/webapps folder to a separate partition.

b
tc Server HORIZON must be configured with a cross-site scripting (XSS) filter.
SC-5 - Medium - CCI-001094 - V-90073 - SV-100723r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-001094
Version
VRAU-TC-000595
Vuln IDs
  • V-90073
Rule IDs
  • SV-100723r1_rule
Cross-site scripting (XSS) is a type of computer security vulnerability typically found in web applications. XSS enables attackers to inject client-side scripts into web pages viewed by other users. A cross-site scripting vulnerability may be used by attackers to bypass access controls such as the same-origin policy. As a web server, tc Server can be vulnerable to XSS if steps are not taken to mitigate the threat. VMware provides the XssFilter component to provide a layer of defense against XSS. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89765r1_chk

At the command prompt, execute the following command: grep -B 2 -A 7 XssFilter /opt/vmware/horizon/workspace/conf/web.xml If the XSS filter is not present, this is a finding.

Fix: F-96815r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Configure a <filter> node with the below configuration: <filter> <filter-name>xssfilter</filter-name> <filter-class>com.vmware.vcops.ui.util.XssFilter</filter-class> <init-param> <!-- Comma separated list of URLs that will be sanitized by this filter --> <param-name>fileIncludes</param-name> <param-value>/vcops/services/api.js,/vcops/services/api-debug.js,/vcops/services/api-debug-doc.js</param-value> </init-param> </filter> <filter-mapping> <filter-name>xssfilter</filter-name> <url-pattern>/vcops/services/*</url-pattern> </filter-mapping>

b
tc Server VCO must be configured with a cross-site scripting (XSS) filter.
SC-5 - Medium - CCI-001094 - V-90075 - SV-100725r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-001094
Version
VRAU-TC-000600
Vuln IDs
  • V-90075
Rule IDs
  • SV-100725r1_rule
Cross-site scripting (XSS) is a type of computer security vulnerability typically found in web applications. XSS enables attackers to inject client-side scripts into web pages viewed by other users. A cross-site scripting vulnerability may be used by attackers to bypass access controls such as the same-origin policy. As a web server, tc Server can be vulnerable to XSS if steps are not taken to mitigate the threat. VMware provides the XssFilter component to provide a layer of defense against XSS. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89767r1_chk

At the command prompt, execute the following command: grep -B 2 -A 7 XssFilter /etc/vco/app-server/web.xml If the XSS filter is not present, this is a finding.

Fix: F-96817r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Configure a <filter> node with the below configuration: <filter> <filter-name>xssfilter</filter-name> <filter-class>com.vmware.vcops.ui.util.XssFilter</filter-class> <init-param> <!-- Comma separated list of URLs that will be sanitized by this filter --> <param-name>fileIncludes</param-name> <param-value>/vcops/services/api.js,/vcops/services/api-debug.js,/vcops/services/api-debug-doc.js</param-value> </init-param> </filter> <filter-mapping> <filter-name>xssfilter</filter-name> <url-pattern>/vcops/services/*</url-pattern> </filter-mapping>

b
tc Server VCAC must be configured with a cross-site scripting (XSS) filter.
SC-5 - Medium - CCI-001094 - V-90077 - SV-100727r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-001094
Version
VRAU-TC-000605
Vuln IDs
  • V-90077
Rule IDs
  • SV-100727r1_rule
Cross-site scripting (XSS) is a type of computer security vulnerability typically found in web applications. XSS enables attackers to inject client-side scripts into web pages viewed by other users. A cross-site scripting vulnerability may be used by attackers to bypass access controls such as the same-origin policy. As a web server, tc Server can be vulnerable to XSS if steps are not taken to mitigate the threat. VMware provides the XssFilter component to provide a layer of defense against XSS. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89769r1_chk

At the command prompt, execute the following command: grep -B 2 -A 7 XssFilter /etc/vcac/web.xml If the XSS filter is not present, this is a finding.

Fix: F-96819r1_fix

Navigate to and open /etc/vcac/server.xml. Configure a <filter> node with the below configuration: <filter> <filter-name>xssfilter</filter-name> <filter-class>com.vmware.vcops.ui.util.XssFilter</filter-class> <init-param> <!-- Comma separated list of URLs that will be sanitized by this filter --> <param-name>fileIncludes</param-name> <param-value>/vcops/services/api.js,/vcops/services/api-debug.js,/vcops/services/api-debug-doc.js</param-value> </init-param> </filter> <filter-mapping> <filter-name>xssfilter</filter-name> <url-pattern>/vcops/services/*</url-pattern> </filter-mapping>

b
tc Server HORIZON must set URIEncoding to UTF-8.
SI-10 - Medium - CCI-001310 - V-90079 - SV-100729r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000610
Vuln IDs
  • V-90079
Rule IDs
  • SV-100729r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. To mitigate against many types of character-based vulnerabilities, tc Server should be configured to use a consistent character set. The URIEncoding attribute on the Connector nodes provides the means for tc Server to enforce a consistent character set encoding.
Checks: C-89771r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "URIEncoding" is not set to "UTF-8" or is missing, this is a finding.

Fix: F-96821r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'URIEncoding="UTF-8"'.

b
tc Server VCO must set URIEncoding to UTF-8.
SI-10 - Medium - CCI-001310 - V-90081 - SV-100731r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000615
Vuln IDs
  • V-90081
Rule IDs
  • SV-100731r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. To mitigate against many types of character-based vulnerabilities, tc Server should be configured to use a consistent character set. The URIEncoding attribute on the Connector nodes provides the means for tc Server to enforce a consistent character set encoding.
Checks: C-89773r1_chk

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "URIEncoding" is not set to "UTF-8" or is missing, this is a finding.

Fix: F-96823r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Connector> node. Configure each <Connector> node with the value 'URIEncoding="UTF-8"'.

b
tc Server HORIZON must use the setCharacterEncodingFilter filter.
SI-10 - Medium - CCI-001310 - V-90083 - SV-100733r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000620
Vuln IDs
  • V-90083
Rule IDs
  • SV-100733r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. As a web server, tc Server can be vulnerable to character encoding attacks if steps are not taken to mitigate the threat. VMware utilizes the standard Tomcat SetCharacterEncodingFilter to provide a layer of defense against character encoding attacks. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89775r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Verify that the 'setCharacterEncodingFilter' &lt;filter&gt; has been specified. If the "setCharacterEncodingFilter" filter has not been specified or is commented out, this is a finding.

Fix: F-96825r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Configure the <web-app> node with the <filter> node listed below. <filter> <filter-name>setCharacterEncodingFilter</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> <param-name>ignore</param-name> <param-value>false</param-value> </init-param> <async-supported>true</async-supported> </filter>

b
tc Server VCO must use the setCharacterEncodingFilter filter.
SI-10 - Medium - CCI-001310 - V-90085 - SV-100735r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000625
Vuln IDs
  • V-90085
Rule IDs
  • SV-100735r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. As a web server, tc Server can be vulnerable to character encoding attacks if steps are not taken to mitigate the threat. VMware utilizes the standard Tomcat SetCharacterEncodingFilter to provide a layer of defense against character encoding attacks. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89777r1_chk

Navigate to and open /etc/vco/app-server/web.xml. Verify that the 'setCharacterEncodingFilter' &lt;filter&gt; has been specified. If the "setCharacterEncodingFilter" filter has not been specified or is commented out, this is a finding.

Fix: F-96827r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Configure the <web-app> node with the <filter> node listed below. <filter> <filter-name>setCharacterEncodingFilter</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> <param-name>ignore</param-name> <param-value>false</param-value> </init-param> <async-supported>true</async-supported> </filter>

b
tc Server VCAC must set URIEncoding to UTF-8.
SI-10 - Medium - CCI-001310 - V-90087 - SV-100737r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000630
Vuln IDs
  • V-90087
Rule IDs
  • SV-100737r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. To mitigate against many types of character-based vulnerabilities, tc Server should be configured to use a consistent character set. The URIEncoding attribute on the Connector nodes provides the means for tc Server to enforce a consistent character set encoding.
Checks: C-89779r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "URIEncoding" is not set to "UTF-8" or is missing, this is a finding.

Fix: F-96829r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'URIEncoding="UTF-8"'.

b
tc Server VCAC must use the setCharacterEncodingFilter filter.
SI-10 - Medium - CCI-001310 - V-90089 - SV-100739r1_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
VRAU-TC-000635
Vuln IDs
  • V-90089
Rule IDs
  • SV-100739r1_rule
Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. As a web server, tc Server can be vulnerable to character encoding attacks if steps are not taken to mitigate the threat. VMware utilizes the standard Tomcat SetCharacterEncodingFilter to provide a layer of defense against character encoding attacks. Filters are Java objects that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both.
Checks: C-89781r1_chk

Navigate to and open /etc/vcac/web.xml. Verify that the 'setCharacterEncodingFilter' &lt;filter&gt; has been specified. If the "setCharacterEncodingFilter" filter has not been specified or is commented out, this is a finding.

Fix: F-96831r1_fix

Navigate to and open /etc/vcac/web.xml. Configure the <web-app> node with the <filter> node listed below. <filter> <filter-name>setCharacterEncodingFilter</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> <param-name>ignore</param-name> <param-value>false</param-value> </init-param> <async-supported>true</async-supported> </filter>

b
tc Server HORIZON must set the welcome-file node to a default web page.
SI-11 - Medium - CCI-001312 - V-90091 - SV-100741r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000640
Vuln IDs
  • V-90091
Rule IDs
  • SV-100741r1_rule
The goal is to completely control the web user's experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an index.html file is a significant factor to accomplish this end. Enumeration techniques, such as URL parameter manipulation, rely upon being able to obtain information about the web server's directory structure by locating directories without default pages. In the scenario, the web server will display to the user a listing of the files in the directory being accessed. By having a default hosted application web page, the anonymous web user will not obtain directory browsing information or an error message that reveals the server type and version. As a web server, tc Server can be vulnerable to enumeration techniques if steps are not taken to mitigate the vulnerability. Ensuring that every document directory has an index.jsp (or equivalent) file is one common sense approach to mitigating the vulnerability.
Checks: C-89783r1_chk

At the command prompt, execute the following command: grep -E -A 4 '&lt;welcome-file-list' /opt/vmware/horizon/workspace/conf/web.xml If a &lt;welcome-file&gt; node is not set to a default web page, this is a finding.

Fix: F-96833r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Inspect the file and ensure that it contains the below section: <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> </welcome-file-list>

b
tc Server VCO must set the welcome-file node to a default web page.
SI-11 - Medium - CCI-001312 - V-90093 - SV-100743r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000645
Vuln IDs
  • V-90093
Rule IDs
  • SV-100743r1_rule
The goal is to completely control the web user's experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an index.html file is a significant factor to accomplish this end. Enumeration techniques, such as URL parameter manipulation, rely upon being able to obtain information about the web server's directory structure by locating directories without default pages. In the scenario, the web server will display to the user a listing of the files in the directory being accessed. By having a default hosted application web page, the anonymous web user will not obtain directory browsing information or an error message that reveals the server type and version. As a web server, tc Server can be vulnerable to enumeration techniques if steps are not taken to mitigate the vulnerability. Ensuring that every document directory has an index.jsp (or equivalent) file is one common sense approach to mitigating the vulnerability.
Checks: C-89785r1_chk

At the command prompt, execute the following command: grep -E -A 4 '&lt;welcome-file-list' /etc/vco/app-server/web.xml If a &lt;welcome-file&gt; node is not set to a default web page, this is a finding.

Fix: F-96835r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Inspect the file and ensure that it contains the below section: <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> </welcome-file-list>

b
tc Server VCAC must set the welcome-file node to a default web page.
SI-11 - Medium - CCI-001312 - V-90095 - SV-100745r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000650
Vuln IDs
  • V-90095
Rule IDs
  • SV-100745r1_rule
The goal is to completely control the web user's experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an index.html file is a significant factor to accomplish this end. Enumeration techniques, such as URL parameter manipulation, rely upon being able to obtain information about the web server's directory structure by locating directories without default pages. In the scenario, the web server will display to the user a listing of the files in the directory being accessed. By having a default hosted application web page, the anonymous web user will not obtain directory browsing information or an error message that reveals the server type and version. As a web server, tc Server can be vulnerable to enumeration techniques if steps are not taken to mitigate the vulnerability. Ensuring that every document directory has an index.jsp (or equivalent) file is one common sense approach to mitigating the vulnerability.
Checks: C-89787r1_chk

At the command prompt, execute the following command: grep -E -A 4 '&lt;welcome-file-list' /etc/vcac/web.xml If a &lt;welcome-file&gt; node is not set to a default web page, this is a finding.

Fix: F-96837r1_fix

Navigate to and open /etc/vcac/web.xml. Inspect the file and ensure that it contains the below section: <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> </welcome-file-list>

b
tc Server HORIZON must have the allowTrace parameter set to false.
SI-11 - Medium - CCI-001312 - V-90097 - SV-100747r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000660
Vuln IDs
  • V-90097
Rule IDs
  • SV-100747r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. "Trace" is a technique for a user to request internal information about tc Server. This is useful during product development, but should not be enabled in production. Allowing an attacker to conduct a Trace operation against tc Server will expose information that would be useful to perform a more targeted attack. tc Server provides the allowTrace parameter as means to disable responding to Trace requests.
Checks: C-89789r1_chk

At the command prompt, execute the following command: grep allowTrace /opt/vmware/horizon/workspace/conf/server.xml If "allowTrace" is set to "true", this is a finding. Note: If no line is returned this is NOT a finding.

Fix: F-96839r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to and locate 'allowTrace="true"'. Remove the 'allowTrace="true"' setting.

b
tc Server VCO must have the allowTrace parameter set to false.
SI-11 - Medium - CCI-001312 - V-90099 - SV-100749r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000665
Vuln IDs
  • V-90099
Rule IDs
  • SV-100749r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. "Trace" is a technique for a user to request internal information about tc Server. This is useful during product development, but should not be enabled in production. Allowing an attacker to conduct a Trace operation against tc Server will expose information that would be useful to perform a more targeted attack. tc Server provides the allowTrace parameter as means to disable responding to Trace requests.
Checks: C-89791r1_chk

At the command prompt, execute the following command: grep allowTrace /etc/vco/app-server/server.xml If "allowTrace" is set to "true", this is a finding. Note: If no line is returned this is NOT a finding.

Fix: F-96841r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to and locate 'allowTrace="true"'. Remove the 'allowTrace="true"' setting.

b
tc Server VCAC must have the allowTrace parameter set to false.
SI-11 - Medium - CCI-001312 - V-90101 - SV-100751r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000670
Vuln IDs
  • V-90101
Rule IDs
  • SV-100751r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. "Trace" is a technique for a user to request internal information about tc Server. This is useful during product development, but should not be enabled in production. Allowing an attacker to conduct a Trace operation against tc Server will expose information that would be useful to perform a more targeted attack. tc Server provides the allowTrace parameter as means to disable responding to Trace requests.
Checks: C-89793r1_chk

At the command prompt, execute the following command: grep allowTrace /etc/vcac/server.xml If "allowTrace" is set to "true", this is a finding. Note: If no line is returned this is NOT a finding.

Fix: F-96843r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to and locate 'allowTrace="true"'. Remove the 'allowTrace="true"' setting.

b
tc Server HORIZON must have the debug option turned off.
SI-11 - Medium - CCI-001312 - V-90103 - SV-100753r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000675
Vuln IDs
  • V-90103
Rule IDs
  • SV-100753r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. As a Tomcat derivative, tc Server can be configured to set the debugging level. By setting the debugging level to zero (0), no debugging information will be provided to a malicious user. This provides a layer of defense to vRA.
Checks: C-89795r1_chk

At the command prompt, execute the following command: grep -En -A 2 -B 1 '&lt;param-name&gt;debug&lt;/param-name&gt;' /opt/vmware/horizon/workspace/conf/web.xml If all instances of the debug parameter are not set to "0", this is a finding.

Fix: F-96845r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Navigate to all <debug> nodes that are not set to "0". Set the <param-value> to "0" in all <param-name>debug</param-name> nodes. Note: The debug setting should look like the below: <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param>

b
tc Server VCO must have the debug option turned off.
SI-11 - Medium - CCI-001312 - V-90105 - SV-100755r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000680
Vuln IDs
  • V-90105
Rule IDs
  • SV-100755r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. As a Tomcat derivative, tc Server can be configured to set the debugging level. By setting the debugging level to zero (0), no debugging information will be provided to a malicious user. This provides a layer of defense to vRA.
Checks: C-89797r1_chk

At the command prompt, execute the following command: grep -En -A 2 -B 1 '&lt;param-name&gt;debug&lt;/param-name&gt;' /etc/vco/app-server/web.xml If all instances of the debug parameter are not set to "0", this is a finding.

Fix: F-96847r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Navigate to all <debug> nodes that are not set to "0". Set the <param-value> to "0" in all <param-name>debug</param-name> nodes. Note: The debug setting should look like the below: <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param>

b
tc Server VCAC must have the debug option turned off.
SI-11 - Medium - CCI-001312 - V-90107 - SV-100757r1_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
VRAU-TC-000685
Vuln IDs
  • V-90107
Rule IDs
  • SV-100757r1_rule
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Since this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. As a Tomcat derivative, tc Server can be configured to set the debugging level. By setting the debugging level to zero (0), no debugging information will be provided to a malicious user. This provides a layer of defense to vRA.
Checks: C-89799r1_chk

At the command prompt, execute the following command: grep -En -A 2 -B 1 '&lt;param-name&gt;debug&lt;/param-name&gt;' /etc/vcac/web.xml If all instances of the debug parameter are not set to "0", this is a finding.

Fix: F-96849r1_fix

Navigate to and open /etc/vcac/web.xml. Navigate to all <debug> nodes that are not set to "0". Set the <param-value> to "0" in all <param-name>debug</param-name> nodes. Note: The debug setting should look like the below: <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param>

b
tc Server HORIZON must set an inactive timeout for sessions.
AC-12 - Medium - CCI-002361 - V-90109 - SV-100759r1_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
VRAU-TC-000695
Vuln IDs
  • V-90109
Rule IDs
  • SV-100759r1_rule
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. tc Server provides a session timeout parameter in the web.xml configuration file.
Checks: C-89801r1_chk

At the command prompt, execute the following command: grep session-timeout /opt/vmware/horizon/workspace/conf/web.xml If the value of &lt;session-timeout&gt; is not "30" or is missing, this is a finding.

Fix: F-96851r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Navigate to the <session-config> node. Add the <session-timeout>30</session-timeout> node setting to the <session-config> node.

b
tc Server VCO must set an inactive timeout for sessions.
AC-12 - Medium - CCI-002361 - V-90111 - SV-100761r1_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
VRAU-TC-000700
Vuln IDs
  • V-90111
Rule IDs
  • SV-100761r1_rule
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. tc Server provides a session timeout parameter in the web.xml configuration file.
Checks: C-89803r1_chk

At the command prompt, execute the following command: grep session-timeout /etc/vco/app-server/web.xml If the value of &lt;session-timeout&gt; is not "30" or is missing, this is a finding.

Fix: F-96853r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Navigate to the <session-config> node. Add the <session-timeout>30</session-timeout> node setting to the <session-config> node.

b
tc Server VCAC must set an inactive timeout for sessions.
AC-12 - Medium - CCI-002361 - V-90113 - SV-100763r1_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
VRAU-TC-000705
Vuln IDs
  • V-90113
Rule IDs
  • SV-100763r1_rule
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. tc Server provides a session timeout parameter in the web.xml configuration file.
Checks: C-89805r1_chk

At the command prompt, execute the following command: grep session-timeout /etc/vcac/web.xml If the value of &lt;session-timeout&gt; is not "30" or is missing, this is a finding.

Fix: F-96855r1_fix

Navigate to and open /etc/vcac/web.xml. Navigate to the <session-config> node. Add the <session-timeout>30</session-timeout> node setting to the <session-config> node.

c
tc Server ALL must be configured to the correct user authentication source.
AC-17 - High - CCI-002314 - V-90115 - SV-100765r1_rule
RMF Control
AC-17
Severity
H
CCI
CCI-002314
Version
VRAU-TC-000710
Vuln IDs
  • V-90115
Rule IDs
  • SV-100765r1_rule
Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. A web server can be accessed remotely and must be able to enforce remote access policy requirements or work in conjunction with enterprise tools designed to enforce policy requirements. vRealize Automation can be configured with a variety of authentication sources. Site policies and procedures will dictate the appropriate authentication mechanism.
Checks: C-89807r1_chk

Obtain the correct configuration data for the Authentication Source from the ISSO. Open a web browser, and type in the vRA URL. 1. Log on to the Tenant Administration Portal. 2. Click on Administration &gt;&gt; Directories Management. 3. Click on "Policies". 4. Click on the "Policy Set" link. 5. Verify that User Authentication is configured correctly. If the Authentication Source is not configured in accordance with site policy, this is a finding.

Fix: F-96857r1_fix

Obtain the correct configuration data for the Authentication Source from the ISSO. Open a web browser, and type in the vRA URL. 1. Log on to the Tenant Administration Portal. 2. Click on Administration >> Directories Management. 3. Click on "Policies". 4. Click on the "Policy Set" link. 5. Modify the Authentication Source in accordance with site policy.

b
tc Server HORIZON must be configured to use the https scheme.
AC-17 - Medium - CCI-002314 - V-90117 - SV-100767r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-002314
Version
VRAU-TC-000715
Vuln IDs
  • V-90117
Rule IDs
  • SV-100767r1_rule
Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. tc Server connections are managed by the Connector object class. By configuring external Connector objects to use the HTTPS scheme, vRA's information in flight will be protected.
Checks: C-89809r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "scheme" is not set to "https" or is missing, this is a finding.

Fix: F-96859r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Configure each <Connector> node with the value 'scheme="https"'.

b
tc Server VCAC must be configured to use the https scheme.
AC-17 - Medium - CCI-002314 - V-90119 - SV-100769r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-002314
Version
VRAU-TC-000720
Vuln IDs
  • V-90119
Rule IDs
  • SV-100769r1_rule
Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. tc Server connections are managed by the Connector object class. By configuring external Connector objects to use the HTTPS scheme, vRA's information in flight will be protected.
Checks: C-89811r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "scheme" is not set to "https" or is missing, this is a finding.

Fix: F-96861r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'scheme="https"'.

b
tc Server ALL must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the web server.
AU-4 - Medium - CCI-001849 - V-90121 - SV-100771r1_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001849
Version
VRAU-TC-000740
Vuln IDs
  • V-90121
Rule IDs
  • SV-100771r1_rule
In order to make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism needs to be able to allocate log record storage capacity. The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.
Checks: C-89813r1_chk

Interview the ISSO. Determine if tc Server ALL is using a logging mechanism that is configured to have a capacity large enough to accommodate logging requirements. If the logging mechanism does not have sufficient capacity, this is a finding.

Fix: F-96863r1_fix

Configure the web server to use a logging mechanism that is configured to allocate log record storage capacity in accordance with NIST SP 800-92 log record storage requirements.

b
tc Server ALL must use a logging mechanism that is configured to provide a warning to the ISSO and SA when allocated record storage volume reaches 75% of maximum log record storage capacity.
AU-5 - Medium - CCI-001855 - V-90123 - SV-100773r1_rule
RMF Control
AU-5
Severity
M
CCI
CCI-001855
Version
VRAU-TC-000755
Vuln IDs
  • V-90123
Rule IDs
  • SV-100773r1_rule
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process logs as required. Log processing failures include: software/hardware errors, failures in the log capturing mechanisms, and log storage capacity being reached or exceeded. If log capacity were to be exceeded, then events subsequently occurring would not be recorded. Organizations must define a maximum allowable percentage of storage capacity serving as an alarming threshold (e.g., web server has exceeded 75% of log storage capacity allocated), at which time the web server or the logging mechanism the web server utilizes will provide a warning to the ISSO and SA at a minimum. This requirement can be met by configuring the web server to utilize a dedicated log tool that meets this requirement.
Checks: C-89815r1_chk

Interview the ISSO. Review site documentation and system configuration. Determine if the system has a logging mechanism that will provide a warning to the ISSO and SA when allocated record storage volume reaches 75% of maximum log record storage capacity. If such an alert mechanism is not in use, this is a finding.

Fix: F-96865r1_fix

Configure the tc Server ALL logging mechanism to alert the ISSO / SA when the logs have reached 75% of storage capacity.

b
tc Server HORIZON must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-90125 - SV-100775r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
VRAU-TC-000760
Vuln IDs
  • V-90125
Rule IDs
  • SV-100775r1_rule
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple devices and log records. Time stamps generated by the web server include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve creates log files in the same format as those created by standard web servers including GMT offset.
Checks: C-89817r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/horizon/localhost_access_log.YYYY-MM-dd.txt If the timestamp does not contain a time zone mapping, this is a finding. Note: Substitute the actual date in the file name. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The +0000 part is the time zone mapping.

Fix: F-96867r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the "pattern" setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <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"/>

b
tc Server VCO must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-90127 - SV-100777r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
VRAU-TC-000765
Vuln IDs
  • V-90127
Rule IDs
  • SV-100777r1_rule
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple devices and log records. Time stamps generated by the web server include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve creates log files in the same format as those created by standard web servers including GMT offset.
Checks: C-89819r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the timestamp does not contain a time zone mapping, this is a finding. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The +0000 part is the time zone mapping.

Fix: F-96869r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the "pattern" setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <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"/>

b
tc Server VCAC must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-90129 - SV-100779r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
VRAU-TC-000770
Vuln IDs
  • V-90129
Rule IDs
  • SV-100779r1_rule
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple devices and log records. Time stamps generated by the web server include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve creates log files in the same format as those created by standard web servers including GMT offset.
Checks: C-89821r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt If the timestamp does not contain a time zone mapping, this is a finding. Note: Substitute the actual date in the file name. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The +0000 part is the time zone mapping.

Fix: F-96871r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the "pattern" setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <Valve className="org.apache.catalina.valves.AccessLogValve" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON must record time stamps for log records to a minimum granularity of one second.
AU-8 - Medium - CCI-001889 - V-90131 - SV-100781r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001889
Version
VRAU-TC-000775
Vuln IDs
  • V-90131
Rule IDs
  • SV-100781r1_rule
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the web server include date and time and must be to a granularity of one second. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve should be configured to ensure that investigators have sufficient information to conduct an appropriate audit.
Checks: C-89823r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/horizon/localhost_access_log.YYYY-MM-dd.txt If the timestamp does not contain a minimum granularity of one second, this is a finding. Note: Substitute the actual date in the file name. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The "57" part is the "seconds" part of the timestamp.

Fix: F-96873r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the 'pattern' setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <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"/>

b
tc Server VCO must record time stamps for log records to a minimum granularity of one second.
AU-8 - Medium - CCI-001889 - V-90133 - SV-100783r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001889
Version
VRAU-TC-000780
Vuln IDs
  • V-90133
Rule IDs
  • SV-100783r1_rule
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the web server include date and time and must be to a granularity of one second. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve should be configured to ensure that investigators have sufficient information to conduct an appropriate audit.
Checks: C-89825r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vco/app-server/localhost_access_log.txt If the timestamp does not contain a minimum granularity of one second, this is a finding. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The "57" part is the "seconds" part of the timestamp.

Fix: F-96875r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the "pattern" setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <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"/>

b
tc Server VCAC must record time stamps for log records to a minimum granularity of one second.
AU-8 - Medium - CCI-001889 - V-90135 - SV-100785r1_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001889
Version
VRAU-TC-000785
Vuln IDs
  • V-90135
Rule IDs
  • SV-100785r1_rule
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the web server include date and time and must be to a granularity of one second. Like all web servers, tc Server logs can be configured to produce a Common Log Format (CLF). The tc Server component known as an AccessLogValve, which represents a component that can be inserted into the request processing pipeline to capture user interaction. The Access Log Valve should be configured to ensure that investigators have sufficient information to conduct an appropriate audit.
Checks: C-89827r1_chk

At the command prompt, execute the following command: tail /storage/log/vmware/vcac/access_log.YYYY-MM-dd.txt If the timestamp does not contain a minimum granularity of one second, this is a finding. Note: Substitute the actual date in the file name. Note: In Common Log Format, a timestamp will look like [06/Feb/2016:23:12:57 +0000]. The "57" part is the "seconds" part of the timestamp.

Fix: F-96877r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Valve className="org.apache.catalina.valves.AccessLogValve"> node. Set the "pattern" setting with "%h %l %u %t &quot;%r&quot; %s %b". Note: The <Valve> node should be configured per the following: <Valve className="org.apache.catalina.valves.AccessLogValve" checkExists="true" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="access_log" requestAttributesEnabled="true" rotatable="false" suffix=".txt"/>

b
tc Server HORIZON application, libraries, and configuration files must only be accessible to privileged users.
CM-5 - Medium - CCI-001813 - V-90137 - SV-100787r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001813
Version
VRAU-TC-000790
Vuln IDs
  • V-90137
Rule IDs
  • SV-100787r1_rule
A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability. To limit changes to the web server and limit exposure to any adverse effects from the changes, files such as the web server application files, libraries, and configuration files must have permissions and ownership set properly to only allow privileged users access.
Checks: C-89829r1_chk

At the command prompt, execute the following command: ls -alR /opt/vmware/horizon/workspace /opt/vmware/horizon/workspace/webapps | grep -E '^-' | awk '$1 !~ /---$/ {print}' If the command produces any output, this is a finding.

Fix: F-96879r1_fix

Remove all world permissions from any listed file with the following command: chmod -R o-rwx /opt/vmware/horizon/workspace /opt/vmware/horizon/workspace/webapps

b
tc Server VCO application, libraries, and configuration files must only be accessible to privileged users.
CM-5 - Medium - CCI-001813 - V-90139 - SV-100789r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001813
Version
VRAU-TC-000795
Vuln IDs
  • V-90139
Rule IDs
  • SV-100789r1_rule
A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability. To limit changes to the web server and limit exposure to any adverse effects from the changes, files such as the web server application files, libraries, and configuration files must have permissions and ownership set properly to only allow privileged users access.
Checks: C-89831r1_chk

At the command prompt, execute the following command: ls -alR /usr/lib/vco/configuration/webapps | grep -E '^-' | awk '$1 !~ /---$/ {print}' If the command produces any output, this is a finding.

Fix: F-96881r1_fix

Remove all world permissions from any listed file with the following command: chmod -R o-rwx /usr/lib/vco/configuration/webapps

b
tc Server VCAC application, libraries, and configuration files must only be accessible to privileged users.
CM-5 - Medium - CCI-001813 - V-90141 - SV-100791r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001813
Version
VRAU-TC-000800
Vuln IDs
  • V-90141
Rule IDs
  • SV-100791r1_rule
A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability. To limit changes to the web server and limit exposure to any adverse effects from the changes, files such as the web server application files, libraries, and configuration files must have permissions and ownership set properly to only allow privileged users access.
Checks: C-89833r1_chk

At the command prompt, execute the following commands: ls -alR /etc/vcac /usr/lib/vcac/server/webapps | grep -E '^-' | awk '$1 !~ /---$/ {print}' If the command produces any output, this is a finding.

Fix: F-96883r1_fix

Remove all world permissions from any listed file with the following command: chmod -R o-rwx /etc/vcac /usr/lib/vcac/server/webapps

b
tc Server HORIZON must be configured with the appropriate ports.
CM-7 - Medium - CCI-001762 - V-90143 - SV-100793r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001762
Version
VRAU-TC-000805
Vuln IDs
  • V-90143
Rule IDs
  • SV-100793r1_rule
Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The web server must provide the capability to disable or deactivate network-related services that are deemed to be non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments. An essential configuration file for tc Server is catalina.properties. The ports that tc Server listens to will be configured in that file.
Checks: C-89835r1_chk

At the command prompt, execute the following command: cat /opt/vmware/horizon/workspace/conf/catalina.properties | grep -E '\.port' Review the listed ports. Verify that they match the list below of tc Server HORIZON ports. base.shutdown.port=-1 base.jmx.port=6969 bio-ssl.https.port=6443 If the displayed ports do not match the above list of ports, this is a finding.

Fix: F-96885r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to the ports specification section. Set the tc Server HORIZON port specifications according to the list below: base.shutdown.port=-1 base.jmx.port=6969 bio-ssl.https.port=6443

b
tc Server VCO must be configured with the appropriate ports.
CM-7 - Medium - CCI-001762 - V-90145 - SV-100795r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001762
Version
VRAU-TC-000810
Vuln IDs
  • V-90145
Rule IDs
  • SV-100795r1_rule
Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The web server must provide the capability to disable or deactivate network-related services that are deemed to be non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments. An essential configuration file for tc Server is catalina.properties. The ports that tc Server listens to will be configured in that file.
Checks: C-89837r1_chk

At the command prompt, execute the following command: cat /etc/vco/app-server/catalina.properties | grep -E '\.port' Review the listed ports. Verify that they match the list below of tc Server VCO ports. ch.dunes.http-server.port=8280 ch.dunes.https-server.port=8281 If the displayed ports do not match the above list of ports, this is a finding.

Fix: F-96887r2_fix

Navigate to and open /etc/vco/app-server/catalina.properties. Navigate to the ports specification section. Set the tc Server VCO port specifications according to the list below: ch.dunes.http-server.port=8280 ch.dunes.https-server.port=8281

b
tc Server VCAC must be configured with the appropriate ports.
CM-7 - Medium - CCI-001762 - V-90147 - SV-100797r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001762
Version
VRAU-TC-000815
Vuln IDs
  • V-90147
Rule IDs
  • SV-100797r1_rule
Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The web server must provide the capability to disable or deactivate network-related services that are deemed to be non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments. An essential configuration file for tc Server is catalina.properties. The ports that tc Server listens to will be configured in that file.
Checks: C-89839r1_chk

At the command prompt, execute the following command: cat /etc/vcac/catalina.properties | grep -E '\.port' Review the listed ports. Verify that they match the list below of tc Server VCAC ports. base.shutdown.port=-1 base.jmx.port=6969 ajp.http.port=8009 ajp.https.port=8443 If the displayed ports do not match the above list of ports, this is a finding.

Fix: F-96889r2_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to the ports specification section. Set the tc Server VCAC port specifications according to the list below: base.shutdown.port=-1 base.jmx.port=6969 ajp.http.port=8009 ajp.https.port=8443

b
tc Server HORIZON must use NSA Suite A cryptography when encrypting data that must be compartmentalized.
SC-13 - Medium - CCI-002450 - V-90149 - SV-100799r1_rule
RMF Control
SC-13
Severity
M
CCI
CCI-002450
Version
VRAU-TC-000820
Vuln IDs
  • V-90149
Rule IDs
  • SV-100799r1_rule
Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. NSA has developed Type 1 algorithms for protecting classified information. The Committee on National Security Systems (CNSS) National Information Assurance Glossary (CNSS Instruction No. 4009) defines Type 1 products as: "Cryptographic equipment, assembly or component classified or certified by NSA for encrypting and decrypting classified and sensitive national security information when appropriately keyed. Developed using established NSA business processes and containing NSA-approved algorithms are used to protect systems requiring the most stringent protection mechanisms." Although persons may have a security clearance, they may not have a "need-to-know" and are required to be separated from the information in question. The web server must employ NSA-approved cryptography to protect classified information from those individuals who have no "need-to-know" or when encryption of compartmentalized data is required by data classification.
Checks: C-89841r1_chk

If the system is not implemented to process compartmentalized information, this requirement is Not Applicable. At the command prompt, execute the following command: grep bio-ssl.cipher.list /opt/vmware/horizon/workspace/conf/catalina.properties If the value of "bio-ssl.cipher.list" does not match the list of NSA Suite A ciphers or is missing, this is a finding.

Fix: F-96891r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to the "bio-ssl.cipher.list" setting. Configure "bio-ssl.cipher.list" with a list of NSA Suite A ciphers.

b
tc Server VCAC must use NSA Suite A cryptography when encrypting data that must be compartmentalized.
SC-13 - Medium - CCI-002450 - V-90151 - SV-100801r1_rule
RMF Control
SC-13
Severity
M
CCI
CCI-002450
Version
VRAU-TC-000825
Vuln IDs
  • V-90151
Rule IDs
  • SV-100801r1_rule
Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. NSA has developed Type 1 algorithms for protecting classified information. The Committee on National Security Systems (CNSS) National Information Assurance Glossary (CNSS Instruction No. 4009) defines Type 1 products as: "Cryptographic equipment, assembly or component classified or certified by NSA for encrypting and decrypting classified and sensitive national security information when appropriately keyed. Developed using established NSA business processes and containing NSA-approved algorithms are used to protect systems requiring the most stringent protection mechanisms." Although persons may have a security clearance, they may not have a "need-to-know" and are required to be separated from the information in question. The web server must employ NSA-approved cryptography to protect classified information from those individuals who have no "need-to-know" or when encryption of compartmentalized data is required by data classification.
Checks: C-89843r1_chk

If the system is not implemented to process compartmentalized information, this requirement is Not Applicable. At the command prompt, execute the following command: grep cipher /etc/vcac/catalina.properties If the value of "cipher" does not match the list of NSA Suite A ciphers or is missing, this is a finding.

Fix: F-96893r1_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to and locate "cipher". Configure the "cipher" with NSA Suite A ciphers.

b
tc Server HORIZON must disable the shutdown port.
SC-5 - Medium - CCI-002385 - V-90153 - SV-100803r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-002385
Version
VRAU-TC-000840
Vuln IDs
  • V-90153
Rule IDs
  • SV-100803r1_rule
An attacker has at least two reasons to stop a web server. The first is to cause a DoS, and the second is to put in place changes the attacker made to the web server configuration. As a Tomcat derivative, tc Server uses a port (defaults to 8005) as a shutdown port. If enabled, a shutdown signal can be sent to tc Server through this port. To ensure availability, the shutdown port should be disabled.
Checks: C-89845r1_chk

At the command prompt, execute the following command: grep base.shutdown.port /opt/vmware/horizon/workspace/conf/catalina.properties If the value of "base.shutdown.port" is not set to "-1" or is missing, this is a finding.

Fix: F-96895r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to the "base.shutdown.port" setting. Add the setting "base.shutdown.port=-1" to the "catalina.properties" file.

b
tc Server VCO must disable the shutdown port.
SC-5 - Medium - CCI-002385 - V-90155 - SV-100805r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-002385
Version
VRAU-TC-000845
Vuln IDs
  • V-90155
Rule IDs
  • SV-100805r1_rule
An attacker has at least two reasons to stop a web server. The first is to cause a DoS, and the second is to put in place changes the attacker made to the web server configuration. As a Tomcat derivative, tc Server uses a port (defaults to 8005) as a shutdown port. If enabled, a shutdown signal can be sent to tc Server through this port. To ensure availability, the shutdown port should be disabled.
Checks: C-89847r1_chk

At the command prompt, execute the following command: grep shutdown /etc/vco/app-server/server.xml If the value of "shutdown" is not set to "-1" or is missing, this is a finding.

Fix: F-96897r1_fix

Navigate to and open /etc/vco/app-server/server.xml. Navigate to the <Server> node. Add the attribute 'port="-1"' to the <Server> node in the "server.xml" file.

b
tc Server VCAC must disable the shutdown port.
SC-5 - Medium - CCI-002385 - V-90157 - SV-100807r1_rule
RMF Control
SC-5
Severity
M
CCI
CCI-002385
Version
VRAU-TC-000850
Vuln IDs
  • V-90157
Rule IDs
  • SV-100807r1_rule
An attacker has at least two reasons to stop a web server. The first is to cause a DoS, and the second is to put in place changes the attacker made to the web server configuration. As a Tomcat derivative, tc Server uses a port (defaults to 8005) as a shutdown port. If enabled, a shutdown signal can be sent to tc Server through this port. To ensure availability, the shutdown port should be disabled.
Checks: C-89849r1_chk

At the command prompt, execute the following command: grep base.shutdown.port /etc/vcac/catalina.properties If the value of "base.shutdown.port" is not set to "-1" or is missing, this is a finding.

Fix: F-96899r1_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to the "base.shutdown.port" setting. Add the setting "base.shutdown.port=-1" to the "catalina.properties" file.

b
tc Server HORIZON must employ cryptographic mechanisms (TLS/DTLS/SSL) preventing the unauthorized disclosure of information during transmission.
SC-8 - Medium - CCI-002418 - V-90159 - SV-100809r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000860
Vuln IDs
  • V-90159
Rule IDs
  • SV-100809r1_rule
Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use modern, secure forms of transport encryption.
Checks: C-89851r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml Navigate to each of the &lt;Connector&gt; nodes. If the value of "sslProtocol" is not set to "TLS" or is missing, this is a finding.

Fix: F-96901r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Note: There are three <Connector> nodes. Configure each <Connector> nodes with the setting 'sslProtocol="TLS"'.

b
tc Server VCAC must employ cryptographic mechanisms (TLS/DTLS/SSL) preventing the unauthorized disclosure of information during transmission.
SC-8 - Medium - CCI-002418 - V-90161 - SV-100811r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000865
Vuln IDs
  • V-90161
Rule IDs
  • SV-100811r1_rule
Preventing the disclosure of transmitted information requires that the web server take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). Transmission of data can take place between the web server and a large number of devices/applications external to the web server. Examples are a web client used by a user, a backend database, an audit server, or other web servers in a web cluster. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use modern, secure forms of transport encryption.
Checks: C-89853r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "sslProtocol" is not set to "TLS" or is missing, this is a finding.

Fix: F-96903r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the setting 'sslProtocol="TLS"'.

b
tc Server HORIZON session IDs must be sent to the client using SSL/TLS.
SC-8 - Medium - CCI-002418 - V-90163 - SV-100813r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000870
Vuln IDs
  • V-90163
Rule IDs
  • SV-100813r1_rule
The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use modern, secure forms of transport encryption.
Checks: C-89855r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "sslProtocol" is not set to "TLS" or is missing, this is a finding.

Fix: F-96905r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Note: There are three <Connector> nodes. Configure each <Connector> nodes with the setting 'sslProtocol="TLS"'.

b
tc Server VCAC session IDs must be sent to the client using SSL/TLS.
SC-8 - Medium - CCI-002418 - V-90165 - SV-100815r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000875
Vuln IDs
  • V-90165
Rule IDs
  • SV-100815r1_rule
The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use modern, secure forms of transport encryption.
Checks: C-89857r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "sslProtocol" is not set to "TLS" or is missing, this is a finding.

Fix: F-96907r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the setting 'sslProtocol="TLS"'.

b
tc Server HORIZON must set the useHttpOnly parameter.
SC-8 - Medium - CCI-002418 - V-90167 - SV-100817r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000885
Vuln IDs
  • V-90167
Rule IDs
  • SV-100817r1_rule
A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. As a Tomcat derivative, tc Server contains a Context object, which represents a web application running within a particular virtual host. One of the configurable parameters of the Context object will prevent the tc Server cookies from being accessed by JavaScript from another site.
Checks: C-89859r1_chk

At the command prompt, execute the following command: grep useHttpOnly /opt/vmware/horizon/workspace/conf/context.xml If the value of "useHttpOnly" is not set to "true" or is missing, this is a finding.

Fix: F-96909r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/context.xml. Navigate to the <Context> node. Add the 'useHttpOnly="true"' setting to the <Context> node. Note: The <Context> node should be configured per the following: <Context useHttpOnly="true">

b
tc Server VCO must set the useHttpOnly parameter.
SC-8 - Medium - CCI-002418 - V-90169 - SV-100819r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000890
Vuln IDs
  • V-90169
Rule IDs
  • SV-100819r1_rule
A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. As a Tomcat derivative, tc Server contains a Context object, which represents a web application running within a particular virtual host. One of the configurable parameters of the Context object will prevent the tc Server cookies from being accessed by JavaScript from another site.
Checks: C-89861r1_chk

At the command prompt, execute the following command: grep useHttpOnly /etc/vco/app-server/context.xml If the value of "useHttpOnly" is not set to "true" or is missing, this is a finding.

Fix: F-96911r1_fix

Navigate to and open /etc/vco/app-server/context.xml. Navigate to the <Context> node. Add the 'useHttpOnly="true"' setting to the <Context> node. Note: The <Context> node should be configured per the following: <Context useHttpOnly="true">

b
tc Server VCAC must set the useHttpOnly parameter.
SC-8 - Medium - CCI-002418 - V-90171 - SV-100821r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000895
Vuln IDs
  • V-90171
Rule IDs
  • SV-100821r1_rule
A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e. HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. As a Tomcat derivative, tc Server contains a Context object, which represents a web application running within a particular virtual host. One of the configurable parameters of the Context object will prevent the tc Server cookies from being accessed by JavaScript from another site.
Checks: C-89863r1_chk

At the command prompt, execute the following command: grep useHttpOnly /etc/vcac/context.xml If the value of "useHttpOnly" is not set to "true" or is missing, this is a finding.

Fix: F-96913r1_fix

Navigate to and open /etc/vcac/context.xml. Navigate to the <Context> node. Add the 'useHttpOnly="true"' setting to the <Context> node. Note: The <Context> node should be configured per the following: <Context useHttpOnly="true">

b
tc Server HORIZON must set the secure flag for cookies.
SC-8 - Medium - CCI-002418 - V-90173 - SV-100823r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000900
Vuln IDs
  • V-90173
Rule IDs
  • SV-100823r1_rule
Cookies can be sent to a client using TLS/SSL to encrypt the cookies, but TLS/SSL is not used by every hosted application since the data being displayed does not require the encryption of the transmission. To safeguard against cookies, especially session cookies, being sent in plaintext, a cookie can be encrypted before transmission. To force a cookie to be encrypted before transmission, the cookie Secure property can be set. As a Tomcat derivative, tc Server is based in part on the Java Servlet specification. Servlet 3.0 (Java EE 6) introduced a standard way to configure secure attribute for the session cookie, this can be done by applying the correct configuration in web.xml.
Checks: C-89865r1_chk

At the command prompt, execute the following command: grep -E '&lt;secure&gt;' /opt/vmware/horizon/workspace/conf/web.xml If the value of the &lt;secure&gt; node is not set to "true" or is missing, this is a finding.

Fix: F-96915r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/web.xml. Navigate to the <session-config> node. Add the <cookie-config> --> <secure> node setting to the <session-config> node. Note: The <cookie-config> --> <secure> node should be configured per the following: <cookie-config> <secure>true</secure> </cookie-config>

b
tc Server VCO must set the secure flag for cookies.
SC-8 - Medium - CCI-002418 - V-90175 - SV-100825r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000905
Vuln IDs
  • V-90175
Rule IDs
  • SV-100825r1_rule
Cookies can be sent to a client using TLS/SSL to encrypt the cookies, but TLS/SSL is not used by every hosted application since the data being displayed does not require the encryption of the transmission. To safeguard against cookies, especially session cookies, being sent in plaintext, a cookie can be encrypted before transmission. To force a cookie to be encrypted before transmission, the cookie Secure property can be set. As a Tomcat derivative, tc Server is based in part on the Java Servlet specification. Servlet 3.0 (Java EE 6) introduced a standard way to configure secure attribute for the session cookie, this can be done by applying the correct configuration in web.xml.
Checks: C-89867r1_chk

At the command prompt, execute the following command: grep -E '&lt;secure&gt;' /etc/vco/app-server/web.xml If the value of the &lt;secure&gt; node is not set to "true" or is missing, this is a finding.

Fix: F-96917r1_fix

Navigate to and open /etc/vco/app-server/web.xml. Navigate to the <session-config> node. Add the <cookie-config> --> <secure> node setting to the <session-config> node. Note: The <cookie-config> --> <secure> node should be configured per the following: <cookie-config> <secure>true</secure> </cookie-config>

b
tc Server VCAC must set the secure flag for cookies.
SC-8 - Medium - CCI-002418 - V-90177 - SV-100827r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000910
Vuln IDs
  • V-90177
Rule IDs
  • SV-100827r1_rule
Cookies can be sent to a client using TLS/SSL to encrypt the cookies, but TLS/SSL is not used by every hosted application since the data being displayed does not require the encryption of the transmission. To safeguard against cookies, especially session cookies, being sent in plaintext, a cookie can be encrypted before transmission. To force a cookie to be encrypted before transmission, the cookie Secure property can be set. As a Tomcat derivative, tc Server is based in part on the Java Servlet specification. Servlet 3.0 (Java EE 6) introduced a standard way to configure secure attribute for the session cookie, this can be done by applying the correct configuration in web.xml.
Checks: C-89869r1_chk

At the command prompt, execute the following command: grep -E '&lt;secure&gt;' /etc/vcac/web.xml If the value of the &lt;secure&gt; node is not set to "true" or is missing, this is a finding.

Fix: F-96919r1_fix

Navigate to and open /etc/vcac/web.xml. Navigate to the <session-config> node. Add the <cookie-config> --> <secure> node setting to the <session-config> node. Note: The <cookie-config> --> <secure> node should be configured per the following: <cookie-config> <secure>true</secure> </cookie-config>

c
tc Server HORIZON must set sslEnabledProtocols to an approved Transport Layer Security (TLS) version.
SC-8 - High - CCI-002418 - V-90179 - SV-100829r1_rule
RMF Control
SC-8
Severity
H
CCI
CCI-002418
Version
VRAU-TC-000915
Vuln IDs
  • V-90179
Rule IDs
  • SV-100829r1_rule
Transport Layer Security (TLS) is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2 approved TLS versions must be enabled and non-FIPS-approved SSL versions must be disabled. NIST SP 800-52 defines the approved TLS versions for government applications. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use the sslEnabledProtocols correctly to ensure that older, less secure forms of transport security are not used.
Checks: C-89871r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "sslEnabledProtocols" is not set to "TLSv1.2,TLSv1.1,TLSv1" or is missing, this is a finding.

Fix: F-96921r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Note: There are three <Connector> nodes. Configure each <Connector> node with the setting 'sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"'.

c
tc Server VCAC must set sslEnabledProtocols to an approved Transport Layer Security (TLS) version.
SC-8 - High - CCI-002418 - V-90181 - SV-100831r1_rule
RMF Control
SC-8
Severity
H
CCI
CCI-002418
Version
VRAU-TC-000920
Vuln IDs
  • V-90181
Rule IDs
  • SV-100831r1_rule
Transport Layer Security (TLS) is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2 approved TLS versions must be enabled and non-FIPS-approved SSL versions must be disabled. NIST SP 800-52 defines the approved TLS versions for government applications. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use the sslEnabledProtocols correctly to ensure that older, less secure forms of transport security are not used.
Checks: C-89873r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "sslEnabledProtocols" is not set to "TLSv1.2,TLSv1.1,TLSv1" or is missing, this is a finding.

Fix: F-96923r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the setting 'sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"'.

b
tc Server HORIZON must remove all export ciphers to protect the confidentiality and integrity of transmitted information.
SC-8 - Medium - CCI-002418 - V-90183 - SV-100833r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000925
Vuln IDs
  • V-90183
Rule IDs
  • SV-100833r1_rule
During the initial setup of a Transport Layer Security (TLS) connection to the web server, the client sends a list of supported cipher suites in order of preference. The web server will reply with the cipher suite it will use for communication from the client list. If an attacker can intercept the submission of cipher suites to the web server and place, as the preferred cipher suite, a weak export suite, the encryption used for the session becomes easy for the attacker to break, often within minutes to hours. An essential configuration file for tc Server is catalina.properties. Properly configured, tc Server will not provide the weaker, export ciphers.
Checks: C-89875r1_chk

At the command prompt, execute the following command: grep bio-ssl.cipher.list /opt/vmware/horizon/workspace/conf/catalina.properties If any export ciphers are listed, this is a finding.

Fix: F-96925r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/catalina.properties. Navigate to the "bio-ssl.cipher.list" setting. Remove any export ciphers from "bio-ssl.cipher.list". Note: To view a list of export ciphers, at the command prompt execute the following command: openssl ciphers 'EXP'

b
tc Server VCAC must remove all export ciphers to protect the confidentiality and integrity of transmitted information.
SC-8 - Medium - CCI-002418 - V-90185 - SV-100835r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
VRAU-TC-000930
Vuln IDs
  • V-90185
Rule IDs
  • SV-100835r1_rule
During the initial setup of a Transport Layer Security (TLS) connection to the web server, the client sends a list of supported cipher suites in order of preference. The web server will reply with the cipher suite it will use for communication from the client list. If an attacker can intercept the submission of cipher suites to the web server and place, as the preferred cipher suite, a weak export suite, the encryption used for the session becomes easy for the attacker to break, often within minutes to hours. An essential configuration file for tc Server is catalina.properties. Properly configured, tc Server will not provide the weaker, export ciphers.
Checks: C-89877r1_chk

At the command prompt, execute the following command: grep ciphers /etc/vcac/catalina.properties If any export ciphers are listed, this is a finding.

Fix: F-96927r1_fix

Navigate to and open /etc/vcac/catalina.properties. Navigate to the "cipher" setting. Remove any export ciphers from "cipher". Note: To view a list of export ciphers, at the command prompt execute the following command: openssl ciphers 'EXP'

b
tc Server HORIZON must use approved Transport Layer Security (TLS) versions to maintain the confidentiality and integrity of information during reception.
SC-8 - Medium - CCI-002422 - V-90187 - SV-100837r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002422
Version
VRAU-TC-000940
Vuln IDs
  • V-90187
Rule IDs
  • SV-100837r1_rule
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use the sslEnabledProtocols correctly to ensure that older, less secure forms of transport security are not used.
Checks: C-89879r1_chk

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the &lt;Connector&gt; nodes. If the value of "sslEnabledProtocols" is not set to "TLSv1.2,TLSv1.1,TLSv1" or is missing, this is a finding.

Fix: F-96929r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to each of the <Connector> nodes. Note: There are three <Connector> nodes. Configure each <Connector> node with the setting 'sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"'.

b
tc Server VCAC must use approved Transport Layer Security (TLS) versions to maintain the confidentiality and integrity of information during reception.
SC-8 - Medium - CCI-002422 - V-90189 - SV-100839r1_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002422
Version
VRAU-TC-000945
Vuln IDs
  • V-90189
Rule IDs
  • SV-100839r1_rule
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Protecting the confidentiality and integrity of received information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the network. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPsec tunnel. tc Server connections are managed by the Connector object class. The Connector object can be configured to use a range of transport encryption methods. Many older transport encryption methods have been proven to be weak. vRA should be configured to use the sslEnabledProtocols correctly to ensure that older, less secure forms of transport security are not used.
Checks: C-89881r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "sslEnabledProtocols" is not set to "TLSv1.2,TLSv1.1,TLSv1" or is missing, this is a finding.

Fix: F-96931r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the setting 'sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"'.

b
tc Server ALL must have all security-relevant software updates installed within the configured time period directed by an authoritative source.
SI-2 - Medium - CCI-002605 - V-90191 - SV-100841r1_rule
RMF Control
SI-2
Severity
M
CCI
CCI-002605
Version
VRAU-TC-000950
Vuln IDs
  • V-90191
Rule IDs
  • SV-100841r1_rule
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. The web server will be configured to check for and install security-relevant software updates from an authoritative source within an identified time period from the availability of the update. By default, this time period will be every 24 hours. VMware delivers product updates and patches regularly. It is crucial that system administrators coordinate installation of product updates with the site ISSO to ensure that updated and patched files are uploaded onto the system as soon as prescribed.
Checks: C-89883r1_chk

Interview the ISSO. Review the policies and procedures used to ensure that all security-related upgrades are being installed within the configured time period directed by an authoritative source. If all security-related upgrades are not being installed within the configured time period directed by an authoritative source, this is a finding.

Fix: F-96933r1_fix

Ensure that patches and updates from an authoritative source are applied at least within 24 hours after they have been received.

b
tc Server ALL must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
CM-6 - Medium - CCI-000366 - V-90193 - SV-100843r1_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VRAU-TC-000960
Vuln IDs
  • V-90193
Rule IDs
  • SV-100843r1_rule
Configuring the web server to implement organization-wide security implementation guides and security checklists guarantees compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the web server, including the parameters required to satisfy other security control requirements. VMware delivers product updates and patches regularly. It is crucial that system administrators coordinate installation of product updates with the site ISSO to ensure that updated and patched files are uploaded onto the system as soon as prescribed.
Checks: C-89885r1_chk

Interview the ISSO. Verify that this Security Technical Implementation Guide (STIG) is the most current STIG available for tc Server on vRA. Assess all of the organization's vRA installations to ensure that they are fully compliant with the most current tc Server STIG. If the most current version of the tc Server was not used, or if the tc Server configuration is not compliant with the most current tc Server STIG, this is a finding.

Fix: F-96935r1_fix

Obtain the most current tc Server ALL STIG. Verify that tc Server ALL is configured with all current requirements.

b
tc Server HORIZON must limit the number of maximum concurrent connections permitted.
AC-10 - Medium - CCI-000054 - V-90341 - SV-100991r1_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
VRAU-TC-000005
Vuln IDs
  • V-90341
Rule IDs
  • SV-100991r1_rule
Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a web site, facilitating a denial-of-service attack. Unless the number of requests is controlled, the web server can consume enough system resources to cause a system crash. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests. Each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the value of the maxThreads attribute.
Checks: C-90037r1_chk

At the command prompt, execute the following command: grep maxThreads /opt/vmware/horizon/workspace/conf/server.xml If the value of "maxThreads" is not "300" or is missing, this is a finding.

Fix: F-97083r1_fix

Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to and locate <Executor>. Configure the <Executor> with the value 'maxThreads="300"'. Note: The <Executor> node should be configured per the following: <Executor maxThreads="300" minSpareThreads="50" name="tomcatThreadPool" namePrefix="tomcat-http--"/>

b
tc Server VCAC must use cryptography to protect the integrity of remote sessions.
AC-17 - Medium - CCI-001453 - V-90343 - SV-100993r1_rule
RMF Control
AC-17
Severity
M
CCI
CCI-001453
Version
VRAU-TC-000080
Vuln IDs
  • V-90343
Rule IDs
  • SV-100993r1_rule
Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even when data appears to be static, the non-displayed logic in a web page may expose business logic or trusted system relationships. The integrity of all the data being exchanged between the user and web server must always be trusted. To protect the integrity and trust, encryption methods should be used to protect the complete communication session. HTTP connections in tc Server are managed through the Connector object. Setting the Connector's SSLEnabled flag, SSL handshake/encryption/decryption is enabled.
Checks: C-90039r1_chk

Navigate to and open /etc/vcac/server.xml. Navigate to the &lt;Connector&gt; node. If the value of "SSLEnabled" is not set to "true" or is missing, this is a finding.

Fix: F-97085r1_fix

Navigate to and open /etc/vcac/server.xml. Navigate to the <Connector> node. Configure the <Connector> node with the value 'SSLEnabled="true"'.

b
tc Server ALL must exclude installation of utility programs, services, plug-ins, and modules not necessary for operation.
CM-7 - Medium - CCI-000381 - V-90345 - SV-100995r1_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
VRAU-TC-000355
Vuln IDs
  • V-90345
Rule IDs
  • SV-100995r1_rule
Just as running unneeded services and protocols is a danger to the web server at the lower levels of the OSI model, running unneeded utilities and programs is also a danger at the application layer of the OSI model. Office suites, development tools, and graphical editors are examples of such programs that are troublesome. Because tc Server is installed as part of the entire vRA application, and not installed separately, VMware has ensured that no unnecessary utilities and programs have been included in tc Server.
Checks: C-90041r1_chk

Interview the ISSO. Review the web server documentation and deployed configuration to determine if utility programs, services, plug-ins, and modules not necessary for operation have been removed. If utility programs, services, plug-ins, and modules not necessary for operation have not been removed, this is a finding.

Fix: F-97087r1_fix

Remove all utility programs, services, plug-ins, and modules not necessary for operation.

b
tc Server ALL must only allow authenticated system administrators to have access to the keystore.
IA-5 - Medium - CCI-000186 - V-90347 - SV-100997r1_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000186
Version
VRAU-TC-000450
Vuln IDs
  • V-90347
Rule IDs
  • SV-100997r1_rule
The web server's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt communications between the web server and clients. By gaining access to the private key, an attacker can pretend to be an authorized server and decrypt the SSL traffic between a client and the web server. tc Server stores the server's private key in a keystore file. The vRA keystore file is tcserver.keystore, and this file must be protected to only allow system administrators and other authorized users to have access to it.
Checks: C-90043r1_chk

At the command prompt, execute the following command: ls -al /opt/vmware/horizon/workspace/conf/tcserver.keystore Verify that file permissions are set to "640" or more restrictive. Verify that the owner is horizon and group-owner is www. If either of these conditions are not met, this is a finding.

Fix: F-97089r1_fix

At the command prompt, execute the following commands: chown horizon:www /opt/vmware/horizon/workspace/conf/tcserver.keystore chmod 640 /opt/vmware/horizon/workspace/conf/tcserver.keystore

b
tc Server ALL log files must be moved to a permanent repository in accordance with site policy.
AU-4 - Medium - CCI-001851 - V-90349 - SV-100999r1_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001851
Version
VRAU-TC-000750
Vuln IDs
  • V-90349
Rule IDs
  • SV-100999r1_rule
A web server will typically utilize logging mechanisms for maintaining a historical log of activity that occurs within a hosted application. This information can then be used for diagnostic purposes, forensics purposes, or other purposes relevant to ensuring the availability and integrity of the hosted application. Log files must be periodically moved from the web server to a permanent storage location. This serves two beneficial purposes. First, the web server's resources are freed up for productions. Also, this ensures that the site has, and enforces, policies designed to preserve the integrity of historical logs.
Checks: C-90045r1_chk

Interview the ISSO. Review the site policy for moving log files from the web server to a permanent repository. Ensure that log files are being moved from the web server in accordance with the site policy. If the site does not have a policy for periodically moving log files to an archive repository or such policy is not being enforced, this is a finding.

Fix: F-97091r1_fix

Develop and enforce a site procedure for moving log files periodically from the web server to a permanent repository in accordance with site retention policies.