--- title: "Define the non-standard ports at the domain and Sensor levels" slug: "define-the-non-standard-ports-at-the-domain-and-sensor-levels-3" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:29:02Z published: 2026-11-19T12:29:02Z canonical: "docs.trellix.com/define-the-non-standard-ports-at-the-domain-and-sensor-levels-3" --- > ## 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. # Define the non-standard ports at the domain and Sensor levels Trellix IPS validates standard ports used across various protocols using the signature set. You can add more than one non-standard port per protocol; however, you can only add one port at a time. If multiple ports have been added for a single protocol, all entered non-standard ports appear in one entry. Consider you added two non-standard ports, 1121 and 1281 for FTP traffic (standard FTP port is 21). Each non-standard port was added separately, yet both appear in the same entry. 1. To define non-standard ports for an admin domain: 1. Click the **Devices** tab. 2. From the **Domain** drop-down list, select the domain you want to work in. 3. On the left pane, click the **Global** tab. 4. Select **IPS Device Settings** → **Non-Standard Ports.** 2. To define non-standard ports for a Sensor: 1. Click the **Devices** tab. 2. Select the domain from the **Domain** drop-down list. 3. On the left pane, click the **Devices** tab. 4. Select the device from the **Device** drop-down list. 5. Select **Setup** → **Advanced** → **Non-Standard Ports.** 3. Click ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a265d0b5-4039-16f5-7bb1-cb4512697e13(8).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D) and specify the options in the corresponding fields. ![GUID-56A36AC8-C885-4AC8-8960-85FA64A08C39-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-7973b9a4-7902-09c5-84e0-eaecc3b5de35(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D) | Option | Definition | | --- | --- | | **Protocol** | Lists the protocols for which you can specify the non-standard ports. | | **Enable SSL** | To specify the non-standard port for HTTPS, select HTTP as the **Protocol** and select **Enable SSL**. | | **Transport** | The **Transport** protocol is automatically selected based on the protocol selected. If applicable, you can toggle between TCP and UDP. | | **Standard Port Number** | Automatically displays the standard port number for the selected protocol. | | **Non-Standard Port Number** | Type a port number between 1 and 65535. You cannot enter a standard port number in this field. | | **Save** | Saves the non-standard ports for the corresponding protocol. | | **Cancel** | Ends adding the non-standard ports. | The Manager does not allow you to configure a standard port number for a protocol as the non-standard port. In such an event, the Manager displays the error "The non-standard port number cannot be same as the standard port number." If the assigned non-standard port is a standard port for another protocol, the Manager displays the error "The input non-standard port number is the standard port number for .The update configuration to Sensor fails on set of this non-standard port number. Please try again with different settings." If you upgrade from an older version of the Manager, and if there is a conflict between the non-standard port assigned and the standard port in the signature set, the signature set update fails. In this scenario, manually update the conflicting port number. 4. Click **Save**. 5. Perform a configuration update for the Sensor from **Devices** → **** → **Global** → **Device Manager**. Select the **Sensors** tab. Select the Sensor and click **Deploy**. Select the required configurations from **Sync: ** window and click **Deploy**. For more information, see [Deploy pending changes to a device](/network-and-platform/docs/deploy-pending-changes-to-a-device-10). > [!NOTE] > Note > > You can also perform configuration update from **Devices** → **** → **Devices** → **** → **Deploy Pending Changes**. Select the required configurations and click **Deploy**.