On Secure Bridge Setup, you can find operational concepts for a secure BRIDGE setup. Find here some additional security recommendations to consider for BRIDGE hardening.
Disabling TLS 1.0
Bridge 7.2.0 As of BRIDGE 7.2.0, TLS 1.0 is disabled by default. Still, you can use this guide to re-enable it if necessary.
If you do not have any clients that need TLS 1.0, we recommend to disable this protocol for the BRIDGE from the security point of view. To be downwards compatible with MagicDraw 17 (see note), we did not implement this to the standard BRIDGE installation.
MagicDraw 17 uses Java 6, and thus only supports protocols up to TLS 1.0. So, if you disable Tomcat TLS 1.0 on your BRIDGE, you will not be able to deploy services directly from MagicDraw 17 to this BRIDGE (a handshake error will occur).
This does not affect repositories that have been compiled with MagicDraw 17. They can be uploaded via the BRIDGE UI nevertheless.
To do disable TLS 1.0, you have to edit the Tomcat and Apache configuration files of the BRIDGE as shown in the table below.
This file will get overwritten on BRIDGE updates! The old configuration file is copied to server.xml.old.
Copy the Apache templates that have been provided with your BRIDGE installation from folder
- Apply changes to the files as described above. Consider the notes!
- Restart the BRIDGE to apply the changed Apache configuration.