| 2.5 Disable client-facing stack traces (check for defined exception type) | SYSTEM AND INFORMATION INTEGRITY |
| 2.6 Turn off TRACE (check server.xml) | SYSTEM AND INFORMATION INTEGRITY |
| 2.6 Turn off TRACE (check web.xml config files) | SYSTEM AND INFORMATION INTEGRITY |
| 3.1 Set a nondeterministic Shutdown command value. | CONFIGURATION MANAGEMENT |
| 4.1 Restrict access to $CATALINA_HOME | CONFIGURATION MANAGEMENT |
| 4.2 Restrict access to $CATALINA_BASE | CONFIGURATION MANAGEMENT |
| 4.3 Restrict access to Tomcat configuration directory | CONFIGURATION MANAGEMENT |
| 4.4 Restrict access to Tomcat logs directory | CONFIGURATION MANAGEMENT |
| 4.5 Restrict access to Tomcat temp directory | CONFIGURATION MANAGEMENT |
| 4.6 Restrict access to Tomcat binaries directory | CONFIGURATION MANAGEMENT |
| 4.7 Restrict access to Tomcat web application directory | CONFIGURATION MANAGEMENT |
| 4.8 Restrict access to Tomcat catalina.policy | CONFIGURATION MANAGEMENT |
| 4.9 Restrict access to Tomcat catalina.properties | CONFIGURATION MANAGEMENT |
| 4.10 Restrict access to Tomcat context.xml | CONFIGURATION MANAGEMENT |
| 4.11 Restrict access to Tomcat logging.properties | CONFIGURATION MANAGEMENT |
| 4.12 Restrict access to Tomcat server.xml | CONFIGURATION MANAGEMENT |
| 4.13 Restrict access to Tomcat tomcat-users.xml | CONFIGURATION MANAGEMENT |
| 4.14 Restrict access to Tomcat web.xml | CONFIGURATION MANAGEMENT |
| 6.2 Ensure SSLEnabled is set to True for Sensitive Connectors(verify SSLEnabled is set to true) | SYSTEM AND COMMUNICATIONS PROTECTION |
| 6.3 Ensure scheme is set accurately | SYSTEM AND COMMUNICATIONS PROTECTION |
| 6.4 Ensure secure is set to true only for SSL-enabled Connectors (verify secure is set to true) | SYSTEM AND COMMUNICATIONS PROTECTION |
| 6.5 Ensure sslProtocol is set to TLS for Secure Connectors (verify sslProtocol is set to TLS) | SYSTEM AND COMMUNICATIONS PROTECTION |
| 7.2 Specify file handler in logging.properties (check if java.util.logging.ConsoleHandler exists in web application) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if java.util.logging.ConsoleHandler exists inin default) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if java.util.logging.ConsoleHandler logging is enabled in default) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if java.util.logging.ConsoleHandler logging is enabled in web application) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if org.apache.juli.FileHandler exists in default) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if org.apache.juli.FileHandler exists in web application) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if org.apache.juli.FileHandler logging is enabled in default) | AUDIT AND ACCOUNTABILITY |
| 7.2 Specify file handler in logging.properties (check if org.apache.juli.FileHandler logging is enabled in web application) | AUDIT AND ACCOUNTABILITY |
| 7.4 Ensure directory in context.xml is a secure location - configuration | AUDIT AND ACCOUNTABILITY |
| 7.4 Ensure directory in context.xml is a secure location - permissions | CONFIGURATION MANAGEMENT |
| 7.5 Ensure pattern in context.xml is correct | AUDIT AND ACCOUNTABILITY |
| 7.6 Ensure directory in logging.properties is a secure location (check application log directory is secure) | CONFIGURATION MANAGEMENT |
| 7.6 Ensure directory in logging.properties is a secure location (check log directory location) | AUDIT AND ACCOUNTABILITY |
| 7.6 Ensure directory in logging.properties is a secure location (check prefix application name) | AUDIT AND ACCOUNTABILITY |
| 8.1 Restrict runtime access to sensitive packages | ACCESS CONTROL |
| 9.1 Starting Tomcat with Security Manager | CONFIGURATION MANAGEMENT |
| 10.1 Ensure Web content directory is on a separate partition from the Tomcat system files (verify Web content directory) | CONFIGURATION MANAGEMENT |
| 10.4 Force SSL when accessing the manager application | SYSTEM AND COMMUNICATIONS PROTECTION |
| 10.6 Enable strict servlet Compliance | CONFIGURATION MANAGEMENT |
| 10.7 Turn off session facade recycling | CONFIGURATION MANAGEMENT |
| 10.13 Do not allow symbolic linking | ACCESS CONTROL |
| 10.14 Do not run applications as privileged | ACCESS CONTROL |
| 10.15 Do not allow cross context requests | CONFIGURATION MANAGEMENT |
| 10.17 Enable memory leak listener (verify present) | SYSTEM AND INFORMATION INTEGRITY |
| 10.18 Setting Security Lifecycle Listener (check for config component) | SYSTEM AND INFORMATION INTEGRITY |
| 10.18 Setting Security Lifecycle Listener (check for umask present in startup) | ACCESS CONTROL |
| 10.18 Setting Security Lifecycle Listener (check for umask uncommented in startup) | ACCESS CONTROL |
| 10.19 Use the logEffectiveWebXml and metadata-complete settings for deploying applications in production | |
