SSL must be enabled on Apache Tomcat.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224792	SRG-APP-000439	ISEC-06-551600	SV-224792r1013885_rule	2024-08-20	3

Description
Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, applications need to leverage transmission protection mechanisms, such as TLS, TLS VPNs, or IPSEC. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.

Description

Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, applications need to leverage transmission protection mechanisms, such as TLS, TLS VPNs, or IPSEC. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.

ℹ️ Check
To configure SSL support on Tomcat, run the ISEC7 integrated installer or use the following manual procedure: Log in to the ISEC7 SPHERE server. Open the server.xml file located at <Drive>:\Program Files\ISEC7 SPHERE\Tomcat\conf with Notepad.exe. Select Edit >> Find and search for port="443". If the connector is not present add: ex: <Connector SSLEnabled="true" maxParameterCount="1000" maxThreads="200" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"> <SSLHostConfig certificateVerification="false" ciphers="HIGH:!aNULL:!MD5:!3DES:!ARIA:!SHA:!CAMELLIA:!AES128-CCM8:!AES128-CCM:!AES256-CCM8:!AES256-CCM:!DHE" honorCipherOrder="true" protocols="+TLSv1.2,+TLSv1.3"> <Certificate certificateKeyAlias="https" certificateKeystoreFile="" certificateKeystoreType="Windows-MY"/> </SSLHostConfig> </Connector> Modifying the certificateKeystoreFile path and certificateKeystorePassword as needed or leveraging the Windows-MY certificateKeystoreType instead. If the connector has been commented out, remove the comment characters. Save the file. Restart the ISEC7 SPHERE Web service.

ℹ️ Check

To configure SSL support on Tomcat, run the ISEC7 integrated installer or use the following manual procedure: Log in to the ISEC7 SPHERE server. Open the server.xml file located at <Drive>:\Program Files\ISEC7 SPHERE\Tomcat\conf with Notepad.exe. Select Edit >> Find and search for port="443". If the connector is not present add: ex: <Connector SSLEnabled="true" maxParameterCount="1000" maxThreads="200" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"> <SSLHostConfig certificateVerification="false" ciphers="HIGH:!aNULL:!MD5:!3DES:!ARIA:!SHA:!CAMELLIA:!AES128-CCM8:!AES128-CCM:!AES256-CCM8:!AES256-CCM:!DHE" honorCipherOrder="true" protocols="+TLSv1.2,+TLSv1.3"> <Certificate certificateKeyAlias="https" certificateKeystoreFile="" certificateKeystoreType="Windows-MY"/> </SSLHostConfig> </Connector> Modifying the certificateKeystoreFile path and certificateKeystorePassword as needed or leveraging the Windows-MY certificateKeystoreType instead. If the connector has been commented out, remove the comment characters. Save the file. Restart the ISEC7 SPHERE Web service.

✔️ Fix
To configure SSL support on Tomcat, run the ISEC7 integrated installer or use the following manual procedure: Log in to the ISEC7 SPHERE server. Open the server.xml file located at <Drive>:\Program Files\ISEC7 SPHERE\Tomcat\conf with Notepad.exe. Select Edit >> Find and search for port="443". If the connector is not present add: ex: <Connector SSLEnabled="true" maxParameterCount="1000" maxThreads="200" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"> <SSLHostConfig certificateVerification="false" ciphers="HIGH:!aNULL:!MD5:!3DES:!ARIA:!SHA:!CAMELLIA:!AES128-CCM8:!AES128-CCM:!AES256-CCM8:!AES256-CCM:!DHE" honorCipherOrder="true" protocols="+TLSv1.2,+TLSv1.3"> <Certificate certificateKeyAlias="https" certificateKeystoreFile="" certificateKeystoreType="Windows-MY"/> </SSLHostConfig> </Connector> Modifying the certificateKeystoreFile path and certificateKeystorePassword as needed or leveraging the Windows-MY certificateKeystoreType instead. If the connector has been commented out, remove the comment characters. Save the file. Restart the ISEC7 SPHERE Web service.

✔️ Fix

To configure SSL support on Tomcat, run the ISEC7 integrated installer or use the following manual procedure: Log in to the ISEC7 SPHERE server. Open the server.xml file located at <Drive>:\Program Files\ISEC7 SPHERE\Tomcat\conf with Notepad.exe. Select Edit >> Find and search for port="443". If the connector is not present add: ex: <Connector SSLEnabled="true" maxParameterCount="1000" maxThreads="200" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"> <SSLHostConfig certificateVerification="false" ciphers="HIGH:!aNULL:!MD5:!3DES:!ARIA:!SHA:!CAMELLIA:!AES128-CCM8:!AES128-CCM:!AES256-CCM8:!AES256-CCM:!DHE" honorCipherOrder="true" protocols="+TLSv1.2,+TLSv1.3"> <Certificate certificateKeyAlias="https" certificateKeystoreFile="" certificateKeystoreType="Windows-MY"/> </SSLHostConfig> </Connector> Modifying the certificateKeystoreFile path and certificateKeystorePassword as needed or leveraging the Windows-MY certificateKeystoreType instead. If the connector has been commented out, remove the comment characters. Save the file. Restart the ISEC7 SPHERE Web service.