This article provides the steps on how to change the Cloud CA to fix the Cloud CA leak issue in Trend Micro Web Security (TMWS).
If some decryption rules use the cross-sign CA, cross-sign your own CA using the new CA CSR. Refer to the TMWS Online Help topic: Cross-signing the CA Certificate for TMWS Cloud Proxy.
To replace the old on-premises with TMWS 3.4.1 version, do the following:
Log on the management console and go to Policies > Global Settings to download the new HTTPS root ca.
Deploy the new cert to your clients and make sure your clients have trusted this new CA.
For steps on how to deploy the certificate, refer to the TMWS Online Help topic: TMWS Certificate Deployment.Please make sure you have finished the Step 2 before running the following steps or your end users may get certificate untrusted warning message when visiting the Internet.
- Rename the cert name from "current_cloud_ca_cert.cer" to "current_cloud_ca_cert.pem" as the default CA file.
Go to Policies > HTTPS INSPECTION > Decryption Rules.If the Decryption Rules is disabled, enable this feature in the Global Settings page.
- Click one Rule Name to edit the Decryption Rule.
Click Choose file to select the cert file renamed in Step 2 if using the old default CA, or select the new cross-signed CA prepared in the Precondition.
Then it will show the new default CA info as shown in the following image:
Or show the new cross-signed CA, for example:
- Click Save.
- Update all other https policies based on Step 3.
- Users can add new https policies with the new default CA in default.
Users can configure one https rule to decrypt all traffic if there is not one that exist before. Then users can trigger the https traffic in the client to check the https cert chain.