Difference between revisions of "Tomcat hardening"
Jump to navigation
Jump to search
old>Admin (Created page with " === CRSF filter === In the APPLICATION web.xml (webapps\<app>\WEB_INF\web.xml) add the following sections <filter> <filter-name>CsrfFilter</filter-name> <filter-c...") |
m (28 revisions imported) |
||
| (27 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
=== | === Update tomcat (recommended) === | ||
In the | Versions below 8 contain vulnerbilities | ||
=== Secure SSL ciphers (recommended) === | |||
Change the HTTP connector please use the following ciphers (<tomcat>\conf\server.xml) | |||
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256 | |||
List updated: 2018-02-07 | |||
=== Secure headers (recommended) === | |||
In the SERVER web.xml (<tomcat>\conf\web.xml) uncomment the following sections | |||
<filter> | <filter> | ||
<filter-name> | <filter-name>httpHeaderSecurity</filter-name> | ||
<filter-class>org.apache.catalina.filters. | <filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class> | ||
<async-supported>true</async-supported> | |||
<init-param> | <init-param> | ||
<param-name>antiClickJackingOption</param-name> | |||
<param-value>SAMEORIGIN</param-value> | |||
</init-param> | </init-param> | ||
</filter> | </filter> | ||
<filter-mapping> | <filter-mapping> | ||
<filter-name> | <filter-name>httpHeaderSecurity</filter-name> | ||
<url-pattern>/*</url-pattern> | <url-pattern>/*</url-pattern> | ||
</filter-mapping> | </filter-mapping> | ||
=== Additional CRSF filtering (optional) === | |||
The TS platform is allrady safe from CRSF attacks. CRSF tokens are generated at login and required for all data altering transactions. | |||
The TS implemetation does not use rotating or pagespecific CRSF tokens, so if additional security is needed use the [https://www.owasp.org/index.php/Category:OWASP_CSRFGuard_Project OWASP implementation]. | |||
=== Additional security filters (optional) === | |||
Tempus Serva comes with multiple additional security features | |||
* Lock user session to IP | |||
* Lock service to listed countries | |||
* Use passcode sent by SMS | |||
The filters are activated by uncommenting the code in the applications /WEB-INF/web.xml. | |||
Note that the filters can be set any part of the application: login, designer, webiterface and rest. | |||
=== Validating your site === | |||
You can use the following services to check the security of your intsallation | |||
==== Test SSL ==== | |||
Tip: Remember to check "Do not show the results on the boards" | |||
[https://www.ssllabs.com/ssltest/ https://www.ssllabs.com/ssltest/] | |||
==== Test Headers ==== | |||
https://tools.geekflare.com/report/header-security-test | |||
Latest revision as of 11:55, 10 December 2021
Update tomcat (recommended)
Versions below 8 contain vulnerbilities
Secure SSL ciphers (recommended)
Change the HTTP connector please use the following ciphers (<tomcat>\conf\server.xml)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256
List updated: 2018-02-07
Secure headers (recommended)
In the SERVER web.xml (<tomcat>\conf\web.xml) uncomment the following sections
<filter>
<filter-name>httpHeaderSecurity</filter-name>
<filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>
<async-supported>true</async-supported>
<init-param>
<param-name>antiClickJackingOption</param-name>
<param-value>SAMEORIGIN</param-value>
</init-param>
</filter>
<filter-mapping> <filter-name>httpHeaderSecurity</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
Additional CRSF filtering (optional)
The TS platform is allrady safe from CRSF attacks. CRSF tokens are generated at login and required for all data altering transactions.
The TS implemetation does not use rotating or pagespecific CRSF tokens, so if additional security is needed use the OWASP implementation.
Additional security filters (optional)
Tempus Serva comes with multiple additional security features
- Lock user session to IP
- Lock service to listed countries
- Use passcode sent by SMS
The filters are activated by uncommenting the code in the applications /WEB-INF/web.xml.
Note that the filters can be set any part of the application: login, designer, webiterface and rest.
Validating your site
You can use the following services to check the security of your intsallation
Test SSL
Tip: Remember to check "Do not show the results on the boards"
https://www.ssllabs.com/ssltest/