--- title: "Configuring proxy based outbound SSL decryption at the device level" slug: "configuring-proxy-based-outbound-ssl-decryption-at-the-device-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-device-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 device 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: ## Task 1. Go to **Devices** → **** → **Devices** → **** → **Setup** → **SSL Decryption**. 2. On the **Outbound** tab, select **Decryption Settings** tab. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-CCFB08CF-BA34-4754-86B4-4BB905025D64-low.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A29%3A26Z&se=2026-11-20T05%3A29%3A26Z&sr=c&sp=r&sig=nxTqfDZpAetzSNBCu4TNvuzhgkP6B3SUhxBrKQlN3wY%3D) 3. Deselect **Inherit Settings** to override the settings of the parent domain. 4. Select the **Enable Outbound Decryption** checkbox. The **Proxy Decryption License** displays as **Present**. > [!NOTE] > Note > > The **Proxy Decryption License** displays as **Required** if a license is not assigned. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-8811170B-2E80-413A-87ED-67B7C58E7E2F-low.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A29%3A26Z&se=2026-11-20T05%3A29%3A26Z&sr=c&sp=r&sig=nxTqfDZpAetzSNBCu4TNvuzhgkP6B3SUhxBrKQlN3wY%3D) 1. Click the tooltip of **Proxy Decryption License** to view the status. The **Proxy Decryption License for ** window opens. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-F5FFFC73-46A0-4773-BC84-80EF375E0172-low.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A29%3A26Z&se=2026-11-20T05%3A29%3A26Z&sr=c&sp=r&sig=nxTqfDZpAetzSNBCu4TNvuzhgkP6B3SUhxBrKQlN3wY%3D) 2. [Optional] Click **Change License** or **Unassign**. If you click **Change License**, it redirects you to **Proxy Decryption** tab, in the **Licenses** page in the **Manager** tab. If you click **Unassign**, a warning message pops up, click **OK**. The current license will be unassigned and the Sensor will operate without a license. 5. Select the required action from the **Untrusted/Expired Server Certificate** drop-down. The reasons for failure can be due 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. | 6. 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). 7. 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, the 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.