CIS Apache Tomcat 8 L1 v1.1.0 Middleware

Audit Details

Name: CIS Apache Tomcat 8 L1 v1.1.0 Middleware

Updated: 3/6/2024

Authority: CIS

Plugin: Unix

Revision: 1.9

Estimated Item Count: 54

File Details

Filename: CIS_Apache_Tomcat_8_L1_v1.1.0_Middleware.audit

Size: 112 kB

MD5: cea7849be6301b53d5675aca9ea5892b
SHA256: 7b4b73978bc41969e83b461460984aa106328214fead46ad178c1124a59960a2

Audit Items

DescriptionCategories
2.5 Disable client facing Stack Traces - check for defined exception type

CONFIGURATION MANAGEMENT

2.6 Turn off TRACE - check server.xml

CONFIGURATION MANAGEMENT

2.6 Turn off TRACE - check web.xml config files

CONFIGURATION MANAGEMENT

3.1 Set a nondeterministic Shutdown command value

ACCESS CONTROL

4.1 Restrict access to $CATALINA_HOME

ACCESS CONTROL

4.2 Restrict access to $CATALINA_BASE

ACCESS CONTROL

4.3 Restrict access to Tomcat configuration directory

ACCESS CONTROL

4.4 Restrict access to Tomcat logs directory

ACCESS CONTROL

4.5 Restrict access to Tomcat temp directory

ACCESS CONTROL

4.6 Restrict access to Tomcat binaries directory

ACCESS CONTROL

4.7 Restrict access to Tomcat web application directory

ACCESS CONTROL

4.8 Restrict access to Tomcat catalina.properties

ACCESS CONTROL

4.9 Restrict access to Tomcat catalina.policy

ACCESS CONTROL

4.10 Restrict access to Tomcat context.xml

ACCESS CONTROL

4.11 Restrict access to Tomcat logging.properties

ACCESS CONTROL

4.12 Restrict access to Tomcat server.xml

ACCESS CONTROL

4.13 Restrict access to Tomcat tomcat-users.xml

ACCESS CONTROL

4.14 Restrict access to Tomcat web.xml

ACCESS CONTROL

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 SSL Protocol is set to TLS for Secure Connectors - verify sslProtocol is set to TLS

SYSTEM AND COMMUNICATIONS PROTECTION

6.6 Control the maximum size of a POST request that will be parsed for parameter

SYSTEM AND INFORMATION INTEGRITY

7.2 Specify file handler in logging.properties files - check if java.util.logging.ConsoleHandler exists in web application

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if java.util.logging.ConsoleHandler exists inin default

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if java.util.logging.ConsoleHandler logging is enabled in default

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if java.util.logging.ConsoleHandler logging is enabled in web application

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if org.apache.juli.FileHandler exists in default

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if org.apache.juli.FileHandler exists in web application

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - check if org.apache.juli.FileHandler logging is enabled in default

AUDIT AND ACCOUNTABILITY

7.2 Specify file handler in logging.properties files - 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

ACCESS CONTROL

7.4 Ensure directory in context.xml is a secure location - permissions

ACCESS CONTROL

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

ACCESS CONTROL

7.6 Ensure directory in logging.properties is a secure location - check log directory location

ACCESS CONTROL

7.6 Ensure directory in logging.properties is a secure location - check prefix application name

ACCESS CONTROL

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

SYSTEM AND COMMUNICATIONS PROTECTION

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

CONFIGURATION MANAGEMENT

10.14 Do not run applications as privileged

ACCESS CONTROL

10.15 Do not allow cross context requests

ACCESS CONTROL

10.17 Enable memory leak listener - verify present

CONFIGURATION MANAGEMENT

10.18 Setting Security Lifecycle Listener - check for config component

CONFIGURATION MANAGEMENT

10.18 Setting Security Lifecycle Listener - check for umask present in startup

CONFIGURATION MANAGEMENT

10.18 Setting Security Lifecycle Listener - check for umask uncommented in startup

CONFIGURATION MANAGEMENT