--- title: "Configuring proxy based outbound SSL decryption at the domain level" slug: "configuring-proxy-based-outbound-ssl-decryption-at-the-domain-level" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:46Z published: 2026-10-05T15:40:46Z canonical: "docs.trellix.com/configuring-proxy-based-outbound-ssl-decryption-at-the-domain-level" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring proxy based outbound SSL decryption at the domain level ## Before you begin To enable proxy based outbound SSL decryption, you must purchase the license and add it in the Manager. The license required for proxy based SSL decryption is the same for both inbound and outbound. To enable proxy based outbound SSL decryption, perform the following steps: > [!NOTE] > Note > > Jumbo frame traffic with SSL encryption will not be decrypted even if SSL decryption is enabled. ## Task 1. Go to **Devices** → **** → **Global** → **IPS Device Settings** → **SSL Decryption**. 2. On the **Outbound** tab, select **Decryption Settings** tab. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-478AB49F-1A77-4181-85FA-5138317EC6C8-low.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A25%3A27Z&se=2026-11-20T05%3A25%3A27Z&sr=c&sp=r&sig=sSjYLFtk97jmC7dfGb%2BU3PthSlYIcwPPMgNn9Gc%2Fao0%3D) 3. Select the **Enable Outbound Decryption** checkbox. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-1122D5D2-8251-4A4B-91CA-73E393AC8F97-low.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A25%3A27Z&se=2026-11-20T05%3A25%3A27Z&sr=c&sp=r&sig=sSjYLFtk97jmC7dfGb%2BU3PthSlYIcwPPMgNn9Gc%2Fao0%3D) 4. Select the required action from the **Untrusted/Expired Server Certificate** drop-down. The reasons for failure can be due to the Sensor not being able to validate the web server's certificate. This happens when the certificate signed by a CA is not on the Sensor's trusted CA list. The descriptions for the possible Sensor actions in case of a failure are as follows: | Action | Description | | --- | --- | | **Decrypt** | The Sensor decrypts the flows from the web server. | | **Block Flow** | The Sensor blocks the flows from the web server. | 5. Click **Save**. > [!NOTE] > Note > > If a valid license is not assigned to a Sensor, a warning **The device requires a valid proxy decryption license** is displayed in the **Deploy Pending Changes** page for that particular Sensor. To assign a valid license, see section [Add license to the Manager](/network-and-platform/docs/add-license-to-the-manager-1). 6. If you change the mode of operation for SSL decryption, or disable SSL decryption, a reboot of the Sensor is required. > [!NOTE] > Note > > Reboot of the Sensor is required after you enable outbound SSL decryption for the feature to function. If you have already configured proxy based inbound SSL decryption, reboot is not required. 1. Go to, **Manager** → **** → **Troubleshooting** → **Logs** → **Faults**. 2. View the critical messages for the corresponding Sensor to see if a Sensor reboot is required. 3. If yes, perform a full reboot of the Sensor.