As part of compliance for most companies and organizations, unsecured cryptographic protocols must be disabled. Currently, only TLS 1.2 is recommended to be used in accessing Trend Micro Deep Security Manager (DSM) admin console.
To restrict the access to TLS 1.2 only:
- Make sure you have either of the following minimum versions and builds:
- Deep Security Manager 9.5 Service Pack (SP) 1 Patch 2 Build 9.5.6511
- Deep Security 9.6. Patch 1
- Stop the Deep Security Manager Service.
- Open the configuration.properties file located under C:\Program Files\Trend Micro\Deep Security Manager.
- Add the following entry at the end of file and save it:
protocols=TLSv1.2You can define more than one protocol by separating them with a comma (,). For example, protocols=TLSv1,TLSv1.1,TLSv1.2.
- Start the Deep Security Manager Service.
- Use packet capture software (e.g. WireShark) to inspect the traffic and verify that TLS 1.2 is being used in communication.
The procedure above may have some limitations. Windows Powershell deployment scripts generated by DSM may fail during execution, but it does not affect Linux platforms. As a workaround, manually add the following line in the script:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12;