| Finding ID |
Severity |
Title |
Description |
|
V-222968
|
High |
Tomcat must use FIPS-validated ciphers on secured connectors. |
Connectors are how Tomcat receives requests over a network port, passes them to hosted web applications via HTTP or AJP, and then sends the results back to the requestor. Cryptographic ciphers are associated with the connector to create a secured connector. To ensure encryption strength is adequately maintained, the ciphers... |
|
V-223010
|
Medium |
The application server must alert the system administrator (SA) and information system security offer (ISSO), at a minimum, in the event of a log processing failure. |
Logs are essential to monitor the health of the system, investigate changes that occurred to the system, or investigate a security incident. When log processing fails, the events during the failure can be lost. To minimize the timeframe of the log failure, an alert needs to be sent to the... |
|
V-223006
|
Medium |
Tomcat users in a management role must be approved by the ISSO. |
Deploying applications to Tomcat requires a Tomcat user account that is in the "manager-script" role. Any user accounts in a Tomcat management role must be approved by the ISSO. |
|
V-223005
|
Medium |
ENFORCE_ENCODING_IN_GET_WRITER must be set to true. |
Some clients try to guess the character encoding of text media when the mandated default of ISO-8859-1 should be used. Some browsers will interpret as UTF-7 when the characters are safe for ISO-8859-1. This can create the potential for a XSS attack. To defend against this, enforce_encoding_in_get_writer must be set... |
|
V-223004
|
Medium |
ALLOW_BACKSLASH must be set to false. |
When Tomcat is installed behind a proxy configured to only allow access to certain Tomcat contexts (web applications), an HTTP request containing "/\../" may allow attackers to work around the proxy restrictions using directory traversal attack methods. If allow_backslash is true the '\' character will be permitted as a path... |
|
V-223000
|
Medium |
Changes to $CATALINA_HOME/lib/ folder must be logged. |
The $CATALINA_HOME/lib folder contains library files for the Tomcat Catalina server. These are in the form of java archive (jar) files. To provide forensic evidence in the event of file tampering, changes to contents in this folder must be logged. For Linux OS flavors other than Ubuntu, use the relevant... |
|
V-222999
|
Medium |
Changes to $CATALINA_BASE/conf/ folder must be logged. |
The $CATALINA_BASE/conf folder contains configuration files for the Tomcat Catalina server. To provide forensic evidence in the event of file tampering, changes to contents in this folder must be logged. For Linux OS flavors other than Ubuntu, use the relevant OS commands. This can be done on the Ubuntu OS... |
|
V-222998
|
Medium |
Changes to $CATALINA_HOME/bin/ folder must be logged. |
The $CATALINA_HOME/bin folder contains startup and control scripts for the Tomcat Catalina server. To provide forensic evidence in the event of file tampering, changes to content in this folder must be logged. For Linux OS flavors other than Ubuntu, use the relevant OS commands. This can be done on the... |
|
V-222997
|
Medium |
AccessLogValve must be configured for Catalina engine. |
|
|
V-222996
|
Medium |
Tomcat server must be patched for security vulnerabilities. |
Tomcat is constantly being updated to address newly discovered vulnerabilities, some of which include denial-of-service attacks. To address this risk, the Tomcat administrator must ensure the system remains up to date on patches.
Satisfies: SRG-APP-000435-AS-000163, SRG-APP-000456-AS-000266 |
|
V-222995
|
Medium |
The application server, when categorized as a high availability system within RMF, must be in a high-availability (HA) cluster. |
A MAC I system is a system that handles data vital to the organization's operational readiness or effectiveness of deployed or contingency forces. A MAC I system must maintain the highest level of integrity and availability. By HA clustering the application server, the hosted application and data are given a... |
|
V-222994
|
Medium |
Certificates in the trust store must be issued/signed by an approved CA. |
Use of self-signed certificates creates a lack of integrity and invalidates the certificate based authentication trust model. Certificates used by production systems must be issued/signed by a trusted Root CA and cannot be self-signed. For systems that communicate with industry partners, the DoD ECA program supports the issuance of DoD-approved... |
|
V-222993
|
Medium |
Multifactor certificate-based tokens (CAC) must be used when accessing the management interface. |
Password authentication does not provide sufficient security control when accessing a management interface. DOD has specified that a CAC will be used when authenticating and passwords will only be used when CAC authentication is not a plausible solution. Tomcat provides the ability to do certificate based authentication and client authentication;... |
|
V-222991
|
Medium |
$CATALINA_BASE/work/ folder must be owned by tomcat user, group tomcat. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222988
|
Medium |
$CATALINA_BASE/logs/ folder must be owned by tomcat user, group tomcat. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222987
|
Medium |
$CATALINA_BASE/conf/ folder must be owned by root, group tomcat. |
Tomcat file permissions must be restricted. The standard configuration is to have Tomcat files contained in the conf/ folder as members of the "tomcat" group. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that... |
|
V-222986
|
Medium |
$CATALINA_HOME folder must be owned by the root user, group tomcat. |
Tomcat file permissions must be restricted. The standard configuration is to have the folder where Tomcat is installed owned by the root user with the group set to tomcat. The $CATALINA_HOME environment variable should be set to the location of the root directory of the "binary" distribution of Tomcat. |
|
V-222984
|
Medium |
Tomcat user account must be a non-privileged user. |
Use a distinct non-privileged user account for running Tomcat. If Tomcat processes are compromised and a privileged user account is used to operate the Tomcat server processes, the entire system becomes compromised.
Sample passwd file:
tomcat:x:1001:1001::/opt/tomcat/usr/sbin/nologin
The user ID is stored in field 3 of the passwd file. |
|
V-222983
|
Medium |
Tomcat user account must be set to nologin. |
When installing Tomcat, a user account is created on the OS. This account is used in order for Tomcat to be able to operate on the OS but does not require the ability to actually log in to the system. Therefore when the account is created, the account must not... |
|
V-222981
|
Medium |
LockOutRealms failureCount attribute must be set to 5 failed logins for admin users. |
A LockOutRealm adds the ability to lock a user out after multiple failed logins. Setting the failureCount attribute to 5 will lock out a user account after 5 failed attempts.
LockOutRealm is an implementation of the Tomcat Realm interface that extends the CombinedRealm to provide user lock out functionality if... |
|
V-222980
|
Medium |
LockOutRealms must be used for management of Tomcat. |
A LockOutRealm adds the ability to lock a user out after multiple failed logins. LockOutRealm is an implementation of the Tomcat Realm interface that extends the CombinedRealm to provide user lock out functionality if there are too many failed authentication attempts in a given period of time. A LockOutRealm is... |
|
V-222979
|
Medium |
Idle timeout for the management application must be set to 10 minutes. |
Tomcat can set idle session timeouts on a per application basis. The management application is provided with the Tomcat installation and is used to manage the applications that are installed on the Tomcat Server. Setting the idle timeout for the management application will kill the admin user's session after 10... |
|
V-222977
|
Medium |
ErrorReportValve showReport must be set to false. |
The Error Report Valve is a simple error handler for HTTP status codes that will generate and return HTML error pages. It can also be configured to return pre-defined static HTML pages for specific status codes and/or exception types. Disabling showReport will result in no error message or stack trace... |
|
V-222975
|
Medium |
ErrorReportValve showServerInfo must be set to false. |
The Error Report Valve is a simple error handler for HTTP status codes that will generate and return HTML error pages. It can also be configured to return pre-defined static HTML pages for specific status codes and/or exception types. Disabling showServerInfo will only return the HTTP status code and remove... |
|
V-222974
|
Medium |
Clusters must operate on a trusted network. |
|
|
V-222971
|
Medium |
Tomcat servers must mutually authenticate proxy or load balancer connections. |
Tomcat servers are often placed behind a proxy when exposed to both trusted and untrusted networks. This is done for security and performance reasons. Tomcat does provide an HTTP server that can be configured to make hosted applications available to clients directly. However, this HTTP server has performance limitations and... |
|
V-222970
|
Medium |
Access to Tomcat manager application must be restricted. |
The Tomcat manager application is used to manage the Tomcat server and the applications that run on Tomcat. By default, the manager application is only accessible via the localhost. Exposing the management application to any network interface that is available to non-administrative personnel leaves the Tomcat server vulnerable to attempts... |
|
V-222969
|
Medium |
Access to JMX management interface must be restricted. |
Java Management Extensions (JMX) is used to provide programmatic access to Tomcat for management purposes. This includes monitoring and control of java applications running on Tomcat. If network access to the JMX port is not restricted, attackers can gain access to the application used to manage the system. |
|
V-222967
|
Medium |
Keystore file must be protected. |
Keystore file contains authentication information used to access application data and data resources. Access to the file must be protected.
The default location is in the .keystore file stored in the home folder of the user account used to run Tomcat, although some administrators may choose to locate the file... |
|
V-222966
|
Medium |
DOD root CA certificates must be installed in Tomcat trust store. |
Tomcat truststores are used to validate client certificates. On the Ubuntu OS, by default, Tomcat uses the "cacerts" file as the CA trust store. The file is located in the /etc/ssl/certs/java/ folder with a link to the file in $JAVA_HOME/lib/security/cacerts. However, this location can be modified by setting the value... |
|
V-223009
|
Low |
Connector address attribute must be set. |
Connectors are how Tomcat receives requests over a network port, passes them to hosted web applications via HTTP or AJP, and then sends back the results to the requestor. The "address" attribute specifies which network interface the connector listens on. If no IP address is specified, the connector will listen... |
|
V-223008
|
Low |
Connectors must be approved by the ISSO. |
Connectors are how Tomcat receives requests over a network port, passes them to hosted web applications via HTTP or AJP and then sends back the results to the requestor. A port and a protocol are tied to each connector. Only connectors approved by the ISSO must be installed. ISSO review... |
|
V-223007
|
Low |
Hosted applications must be documented in the system security plan. |
The ISSM/ISSO must be cognizant of all applications operating on the Tomcat server, and must address any security implications associated with the operation of the applications.
If unknown/undocumented applications are operating on the Tomcat server, these applications increase risk for the system due to not being managed, patched or monitored... |
|
V-223003
|
Low |
RECYCLE_FACADES must be set to true. |
If RECYCLE_FACADES is true or if a security manager is in use, a new facade object will be created for each request. This reduces the chances that a bug in an application might expose data from one request to another. This setting is configured using environment variable settings. For Linux... |
|
V-223002
|
Low |
STRICT_SERVLET_COMPLIANCE must be set to true. |
Strict Servlet Compliance forces Tomcat to adhere to standards specifications including but not limited to RFC2109. RFC2109 sets the standard for HTTP session management. This setting affects several settings which primarily pertain to cookie headers, cookie values, and sessions. Cookies will be parsed for strict adherence to specifications.
Note that... |
|
V-223001
|
Low |
Application servers must use NIST-approved or NSA-approved key management technology and processes. |
Class 3 PKI certificates are used for servers and software signing rather than for identifying individuals. Class 4 certificates are used for business-to-business transactions. Utilizing unapproved certificates not issued or approved by DoD or CNS creates an integrity risk. The application server must utilize approved DoD or CNS Class 3... |
|
V-222990
|
Low |
$CATALINA_BASE/temp folder permissions must be set to 750. |
Tomcat's file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with the group Tomcat. While root has read/write privileges, tomcat group only has read and world has no permissions. The exceptions are the logs, temp and work directory that are owned by... |
|
V-222989
|
Low |
$CATALINA_BASE/temp/ folder must be owned by tomcat user, group tomcat. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222985
|
Low |
Application user name must be logged. |
The access logfile format is defined within a Valve that implements the org.apache.catalina.valves.AccessLogValve interface within the /opt/tomcat/server.xml configuration file: The %u pattern code is included in the pattern element and logs the username used to authenticate to an application. Including the username pattern in the log configuration provides useful information... |
|
V-222982
|
Low |
LockOutRealms lockOutTime attribute must be set to 600 seconds (10 minutes) for admin users. |
A LockOutRealm adds the ability to specify a lockout time that prevents further attempts after multiple failed logins. Setting the lockOutTime attribute to 600 will lock out a user account for 10 minutes. Further authentication failures during the lock out time will cause the lock out timer to reset to... |
|
V-222976
|
Low |
Default error pages for manager application must be customized. |
Default error pages that accompany the manager application provide educational information on how to configure user accounts and groups for accessing the manager application. These error pages provide responses to 401 (Unauthorized), 403 (Forbidden), and 404 (Not Found) JSP error codes and should not exist on production systems. |
|
V-222973
|
Low |
Tomcat must be configured to limit data exposure between applications. |
If RECYCLE_FACADES is true or if a security manager is in use, a new facade object will be created for each request. This reduces the chances that a bug in an application might expose data from one request to another. This setting is configured using environment variable settings. For Linux... |
|
V-222965
|
High |
LDAP authentication must be secured. |
JNDIRealm is an implementation of the Tomcat Realm interface. Tomcat uses the JNDIRealm to look up users in an LDAP directory server. The realm's connection to the directory is defined by the 'connectionURL' configuration attribute. This attribute is usually an LDAP URL that specifies the domain name of the directory... |
|
V-222964
|
High |
TLS must be enabled on JMX. |
Java Management Extensions (JMX) provides the means for enterprises to remotely manage the Java VM and can be used in place of the local manager application that comes with Tomcat.
JMX management is configured via the Tomcat CATALINA_OPTS setting maintained in the /etc/systemd/system/tomcat.service file for Ubuntu systemd Unix. For Linux... |
|
V-222931
|
High |
Default password for keystore must be changed. |
Tomcat currently operates only on JKS, PKCS11, or PKCS12 format keystores. The JKS format is Java's standard "Java KeyStore" format, and is the format created by the keytool command-line utility which is included in the JDK. The PKCS12 format is an internet standard, and is managed using OpenSSL or Microsoft's... |
|
V-222963
|
Medium |
JMX authentication must be secured. |
Java Management Extensions (JMX) provides the means to remotely manage the Java VM. When enabling the JMX agent for remote monitoring, the user must enable authentication. |
|
V-222962
|
Medium |
Tomcat management applications must use LDAP realm authentication. |
Using the local user store on a Tomcat installation does not meet a multitude of security control requirements related to user account management. To address this risk, Tomcat must be configured to utilize an LDAP or Active Directory installation that provides a centralized user account store that is configured to... |
|
V-222961
|
Medium |
Applications in privileged mode must be approved by the ISSO. |
The privileged attribute controls if a context (application) is allowed to use container provided servlets like the Manager servlet. It is false by default and should only be changed for trusted web applications.
Set to true to allow the context (application) to use container servlets, like the manager servlet. Use... |
|
V-222956
|
Medium |
Autodeploy must be disabled. |
Tomcat allows auto-deployment of applications while Tomcat is running. This can allow untested or malicious applications to be automatically loaded into production. Autodeploy must be disabled in production.
This requirement is NA for test and development systems on non-production networks. For DevSecOps application environments, the ISSM may authorize autodeploy functions... |
|
V-222955
|
Medium |
The deployXML attribute must be set to false in hosted environments. |
The Host element controls deployment. Automatic deployment allows for simpler management, but also makes it easier for an attacker to deploy a malicious application. Automatic deployment is controlled by the autoDeploy and deployOnStartup attributes. If both are false, only Contexts defined in server.xml will be deployed, and any changes will... |
|
V-222952
|
Medium |
Unapproved connectors must be disabled. |
Connectors are how Tomcat receives requests, passes them to hosted web applications, and then sends back the results to the requestor. Tomcat provides HTTP and Apache JServ Protocol (AJP) connectors and makes these protocols available via configured network ports. Unapproved connectors provide open network connections to either of these protocols... |
|
V-222951
|
Medium |
The shutdown port must be disabled. |
Tomcat listens on TCP port 8005 to accept shutdown requests. By connecting to this port and sending the SHUTDOWN command, all applications within Tomcat are halted. The shutdown port is not exposed to the network as it is bound to the loopback interface. Set the shutdown attribute in $CATALINA_BASE/conf/server.xml. |
|
V-222950
|
Medium |
Stack tracing must be disabled. |
Stack tracing provides debugging information from the application call stacks when a runtime error is encountered. If stack tracing is left enabled, Tomcat will provide this call stack information to the requestor which could result in the loss of sensitive information or data that could be used to compromise the... |
|
V-222949
|
Medium |
Tomcat user UMASK must be set to 0027. |
For Unix-based systems, umask settings affect file creation permissions. If the permissions are too loose, newly created log files and applications could be accessible to unauthorized users via the file system. Ensure the Tomcat OS user account has the correct file creation permission settings by validating the OS umask settings... |
|
V-222948
|
Medium |
$CATALINA_HOME/bin folder permissions must be set to 750. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222947
|
Medium |
Jar files in the $CATALINA_HOME/bin/ folder must have their permissions set to 640. |
Tomcat's file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with the group Tomcat. While root has read/write privileges, tomcat group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned... |
|
V-222946
|
Medium |
$CATALINA_BASE/conf folder permissions must be set to 750. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222945
|
Medium |
Files in the $CATALINA_BASE/conf/ folder must have their permissions set to 640. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222944
|
Medium |
Files in the $CATALINA_BASE/logs/ folder must have their permissions set to 640. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222943
|
Medium |
$CATALINA_BASE/logs folder permissions must be set to 750. |
Tomcat file permissions must be restricted. The standard configuration is to have all Tomcat files owned by root with group Tomcat. While root has read/write privileges, group only has read permissions, and world has no permissions. The exceptions are the logs, temp, and work directories that are owned by the... |
|
V-222942
|
Medium |
The first line of request must be logged. |
The access logfile format is defined within a Valve that implements the org.apache.catalina.valves.AccessLogValve interface within the /opt/tomcat/server.xml configuration file: The "%r" pattern code is included in the pattern element and logs the first line associated with the event, namely the request method, URL path, query string, and protocol (""" simply... |
|
V-222940
|
Medium |
Remote hostname must be logged. |
The access logfile format is defined within a Valve that implements the org.apache.catalina.valves.AccessLogValve interface within the /opt/tomcat/server.xml configuration file: The %h pattern code is included in the pattern element and logs the remote hostname. Including the hostname pattern in the log configuration provides useful information about the connecting host that... |
|
V-222939
|
Medium |
Date and time of events must be logged. |
The access logfile format is defined within a Valve that implements the org.apache.catalina.valves.AccessLogValve interface within the /opt/tomcat/server.xml configuration file: The %t pattern code is included in the pattern element and logs the date and time of the event. Including the date pattern in the log configuration provides useful information about... |
|
V-222938
|
Medium |
AccessLogValve must be configured per each virtual host.
|
Application servers utilize role-based access controls in order to specify the individuals who are allowed to configure application component loggable events. The application server must be configured to select which personnel are assigned the role of selecting which loggable events are to be logged.
Satisfies: SRG-APP-000090-AS-000051, SRG-APP-000095-AS-000056, SRG-APP-000100-AS-000063, SRG-APP-000101-AS-000072, SRG-APP-000503-AS-000228,... |
|
V-222937
|
Medium |
Tomcat servers behind a proxy or load balancer must log client IP. |
When running Tomcat behind a load balancer or proxy, default behavior is for Tomcat to log the proxy or load balancer IP address as the client IP. Desired behavior is to log the actual client IP rather than the proxy IP address. The RemoteIpValve logging component instructs Tomcat to grab... |
|
V-222936
|
Medium |
The Java Security Manager must be enabled. |
The Java Security Manager (JSM) is what protects the Tomcat server from trojan servlets, JSPs, JSP beans, tag libraries, or even from inadvertent mistakes. The JSM works the same way a client's web browser isolates a running web application via a sandbox, the difference being the sandbox is running on... |
|
V-222935
|
Medium |
Connectors must be secured. |
The unencrypted HTTP protocol does not protect data from interception or alteration which can subject users to eavesdropping, tracking, and the modification of received data. To secure an HTTP connector, both the secure and scheme flags must be set. |
|
V-222934
|
Medium |
DefaultServlet must be set to readonly for PUT and DELETE. |
The DefaultServlet is a servlet provided with Tomcat. It is called when no other suitable page can be displayed to the client. The DefaultServlet serves static resources as well as directory listings and is declared globally in $CATALINA_BASE/conf/web.xml. By default, Tomcat behaves as if the DefaultServlet is set to "true"... |
|
V-222933
|
Medium |
Cookies must have http-only flag set. |
|
|
V-222932
|
Medium |
Cookies must have secure flag set. |
|
|
V-222930
|
Medium |
AccessLogValve must be configured for each application context.
|
|
|
V-222929
|
Medium |
TLS 1.2 must be used on secured HTTP connectors.
|
Using older versions of TLS introduces security vulnerabilities that exist in the older versions of the protocol. Tomcat by default will use all available versions of the SSL/TLS protocols unless the version is explicitly defined in the SSL configuration attribute for the associated connector. This introduces the opportunity for the... |
|
V-222927
|
Medium |
Secured connectors must be configured to use strong encryption ciphers.
|
|
|
V-222960
|
Low |
Documentation must be removed. |
Tomcat provides documentation and other directories in the default installation which do not serve a production use. These files must be deleted. |
|
V-222959
|
Low |
Tomcat default ROOT web application must be removed. |
The default ROOT web application includes the version of Tomcat that is being used, links to Tomcat documentation, examples, FAQs, and mailing lists. The default ROOT web application must be removed from a publicly accessible Tomcat instance and a more appropriate default page shown to users. It is acceptable to... |
|
V-222958
|
Low |
Example applications must be removed. |
Tomcat provides example applications, documentation, and other directories in the default installation which do not serve a production use. These files must be deleted. |
|
V-222957
|
Low |
xpoweredBy attribute must be disabled. |
Individual connectors can be configured to display the Tomcat server info to clients. This information can be used to identify Tomcat versions which can be useful to attackers for identifying vulnerable versions of Tomcat. Individual connectors must be checked for the xpoweredBy attribute to ensure they do not pass Tomcat... |
|
V-222954
|
Low |
DefaultServlet directory listings parameter must be disabled. |
The DefaultServlet serves static resources as well as directory listings. It is declared globally in $CATALINA_BASE/conf/web.xml and by default is configured with the directory "listings" parameter set to disabled. If no welcome file is present and the "listings" setting is enabled, a directory listing is shown. Directory listings must be... |
|
V-222953
|
Low |
DefaultServlet debug parameter must be disabled. |
The DefaultServlet serves static resources as well as serves the directory listings (if directory listings are enabled). It is declared globally in $CATALINA_BASE/conf/web.xml and by default is configured with the "debug" parameter set to 0, which is disabled. Changing this to a value of 1 or higher sets the servlet... |
|
V-222941
|
Low |
HTTP status code must be logged. |
The access logfile format is defined within a Valve that implements the org.apache.catalina.valves.AccessLogValve interface within the /opt/tomcat/server.xml configuration file: The %s pattern code is included in the pattern element and logs the server response code associated with the event e.g. 200 OK or 400 Bad Request. Including the status pattern... |
|
V-222928
|
Low |
HTTP Strict Transport Security (HSTS) must be enabled. |
HTTP Strict Transport Security (HSTS) instructs web browsers to only use secure connections for all future requests when communicating with a website. Doing so helps prevent SSL protocol attacks, SSL stripping, cookie hijacking, and other attempts to circumvent SSL protection.
Implementing HSTS requires testing of your web applications to ensure... |
|
V-222926
|
Low |
The number of allowed simultaneous sessions to the manager application must be limited.
|
The manager application provides configuration access to the Tomcat server. Access to the manager application must be limited and that includes the number of sessions allowed to access the management application. A balance must be struck between the number of simultaneous connections allowed to the management application and the number... |
