AccessLogValve must be configured for Catalina engine.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-222997 | TCAT-AS-001560 | SV-222997r1016518_rule | CCI-000172 | medium |
| Description | ||||
| The <Engine> container represents the entire request processing machinery associated with a particular Catalina Service. It receives and processes all requests from one or more connectors, and returns the completed response to the connector for transmission back to the client. The AccessLogValve will log activity for the Catalina service. Exactly one engine element MUST be nested inside a service element, following all of the corresponding connector elements associated with the service. Satisfies: SRG-APP-000495-AS-000220, SRG-APP-000381-AS-000089, SRG-APP-000499-AS-000224, SRG-APP-000504-AS-000229 | ||||
| STIG | Date | |||
| Apache Tomcat Application Server 9 Security Technical Implementation Guide | 2025-02-11 | |||
Details
Check Text (C-222997r1016518_chk)
As an elevated user on the Tomcat server, edit the $CATALINA_BASE/conf/server.xml file.
Review the <Engine> element. Ensure one AccessLog <Valve> element is nested within the engine element.
If a <Valve className="org.apache.catalina.valves.AccessLogValve" .../> element is not defined, this is a finding.
EXAMPLE:
<Engine name="Standalone" ...>
...
<Valve className="org.apache.catalina.valves.AccessLogValve"
prefix="catalina_access_log" suffix=".txt"
pattern="common"/>
...
</Engine>
Fix Text (F-24658r985899_fix)
As a privileged user on the Tomcat server, edit the $CATALINA_BASE/conf/server.xml file.
Create a <Valve> element that is nested beneath the <Host> element containing an AccessLogValve.
EXAMPLE:
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="false">
...
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %t %u "%r" %s %b" />
...
</Host>
Restart the Tomcat server:
sudo systemctl restart tomcat
sudo systemctl daemon-reload