Title

The Tomcat server must produce log records containing information to establish what type of events occurred. (Cat II impact)

Discussion

Information system logging capability is critical for accurate forensic analysis. Without being able to establish what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible. Log record content that may be necessary to satisfy the requirement of this control includes time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Application servers must log all relevant log data that pertains to the application server. Examples of relevant data include, but are not limited to, Java Virtual Machine (JVM) activity, HTTPD/Web server activity, and application server-related system process activity.

Check Content

Review the server.xml configuration file for an entry for the AccessLogValve. An example looks like: <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %t %r %s %b"/> If the %r or common is not included in the pattern, this is a finding. If the AccessLogValve line does not exist in the server.xml, this is a finding.

Fix Text

Configure the application server to include the event type in the log data.

Additional Identifiers

Rule ID: SV-46446r3_rule

Vulnerability ID: V-35159

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.