--- title: "Enable Intelligent Virtual Execution (IVX) engine integration for an admin domain" slug: "enable-intelligent-virtual-execution-ivx-engine-integration-for-an-admin-domain" tags: ["Integration", "IPS 11.1.x"] updated: 2026-11-19T12:30:36Z published: 2026-11-19T12:30:36Z canonical: "docs.trellix.com/enable-intelligent-virtual-execution-ivx-engine-integration-for-an-admin-domain" --- > ## 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. # Enable Intelligent Virtual Execution (IVX) engine integration for an admin domain You can configure the details for the integration at an admin domain so that the corresponding Sensors and child domains can inherit these settings. However, you must enable the integration at the Sensor level for the Sensor and the Manager to be able to communicate with Intelligent Virtual Execution (IVX) engine. 1. In the Manager, select the **Devices** tab. 2. Select the required domain from the **Domain** drop-down list and then select **Global**. 3. Select **IPS Device Settings** → **IVX Integration**. 4. Select **Enable IVX Integration** checkbox. 5. Choose **Enable IVX** or **Enable IVX Cloud** configure them. **Enabling IVX Integration for an admin domain** ![Enabling IVX Integration for an admin domain](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-07326dc0-26b8-bd77-7c20-3ebdc4603143.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) **Option definitions** | Option | Definition | | --- | --- | | **Enable IVX Integration** | Select this option to integrate the Manager and Sensor with the IVX appliance or IVX Cloud. **Enable IVX**: Enables IVX appliance integration **Enable IVX Cloud**: Enables IVX Cloud integration After you select, you will be able to view and configure the details for the integration. > [!NOTE] > Note > > At any instance, you can choose to integrate either IVX or IVX Cloud with Trellix IPS, but not both of them together. | | **Save** | Click **Save** when you enable or disable IVX Integration. | ### Enable and Configure integration with IVX Appliance 1. To enable and configure an IVX appliance integration, select the **Enable IVX** option. **Enabling IVX Appliance Integration for an admin domain** ![Enabling IVX Appliance Integration for an admin domain](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d0ef8c2c-acd6-957c-1851-4f7703a9acfd.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) **Option definitions** | Option | Definition | | --- | --- | | **IVX Appliance Configuration** | **Cluster Status** | Displays the status of the cluster that an IVX broker node belongs to. - ![GUID-E9D50264-CAFF-4207-8FAC-77D0B81FDCF3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-aaf997ab-fe3f-0cb2-30a0-e2b608c0ee6e(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**Ready**: Cluster is ready and all the broker nodes are active. - ![GUID-28FE5921-ACF1-491C-B376-930A589BF74C-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-34eb39b2-4d3f-f2e3-e0db-9029d8dbfe3d(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D): Any state other than **Ready** when one or more brokers are affected. - **---**: Not available. > [!NOTE] > Note > > The file submission to the cluster happens if the status is either ![GUID-E9D50264-CAFF-4207-8FAC-77D0B81FDCF3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-aaf997ab-fe3f-0cb2-30a0-e2b608c0ee6e(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) or ![GUID-28FE5921-ACF1-491C-B376-930A589BF74C-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-34eb39b2-4d3f-f2e3-e0db-9029d8dbfe3d(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D). However, in the ![GUID-28FE5921-ACF1-491C-B376-930A589BF74C-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-34eb39b2-4d3f-f2e3-e0db-9029d8dbfe3d(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) state, a few broker nodes might be down/not reachable but the file submission continues to happen to the active broker nodes. | | **Broker Nodes Configured** | Lists the IP address of the broker nodes configured for communication. | | **Listening Port** | Displays the port that IVX appliance will listen for connections from Sensor and Manager. The default port is 443 and users cannot change it. | | **Enable Certificate Validation** | Displays the status of the certificate validation as **Enabled** or **Disabled**. | | **Enable Proxy for IVX Communication** | Displays the status of the proxy communication as **Enabled** or **Disabled**. | | **Add IVX Cluster** | Allows you to add a cluster consisting of IVX broker nodes. | | **Remove IVX Cluster** | Use this option if you plan to remove an existing cluster. | | **Save** | Saves the integration details in the Manager database and applies it to the inherited child domain(s)/device(s). | > [!NOTE] > Note > > The **Add IVX Cluster**, **Remove IVX Cluster**, and **Save** options will be hidden if: > > - You are viewing this page as a user with read-only access (or) > - Manager is in Standby mode 2. The **Add IVX Cluster** option allows you to add a cluster and its associated broker nodes. Click **Add IVX Cluster**displayed in the image Enabling IVX Integration for an admin domain. 3. A new page opens where you can configure the cluster and its associated broker nodes. **Adding broker nodes to a cluster** ![Adding broker nodes to a cluster](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-c5e24d13-a786-ea87-e264-2b7dd863a850.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) **Option definitions** | Option | Definition | | --- | --- | | **Cluster Details** > [!NOTE] > Note > > Configuration made in this section will be applicable to all the broker nodes that you add. | **Enable Certificate Validation** | Select this option if you have configured CA signed certificate on the IVX appliance. If the certificate is configured on the appliance, it is recommended to enable this option to ensure secure communication. | | **Enable Proxy for IVX communication** | Select this option if you deployed proxy server between the IPS (Sensor and Manager) and the IVX appliance. You need to configure proxy server at device level page and enable proxy option under the **IVX Appliance Configuration** section. | | **Listening Port (TCP)** | This is the port that IVX appliance will listen for connections from Sensor and Manager. The default port is 443 and users cannot change it. | | **Cluster Status** | Displays the status of the cluster that an IVX broker node belongs to. - ![GUID-E9D50264-CAFF-4207-8FAC-77D0B81FDCF3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-aaf997ab-fe3f-0cb2-30a0-e2b608c0ee6e(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**Ready**: Cluster is ready and all the broker nodes are active. - ![GUID-28FE5921-ACF1-491C-B376-930A589BF74C-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-34eb39b2-4d3f-f2e3-e0db-9029d8dbfe3d(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D): Any state other than **Ready** when one or more brokers are affected. - **---**: Not available. | | **Broker Nodes** | **Server Address** | Enter the IP address (IPv4/IPv6) or Host Name of the IVX broker for communicating with the Manager and Sensor. | | **Username** | Username of the IVX broker node. | | **Manager to IVX Authentication Status** | Displays the authentication status of the Manager with the IVX appliance. - ![GUID-E9D50264-CAFF-4207-8FAC-77D0B81FDCF3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-aaf997ab-fe3f-0cb2-30a0-e2b608c0ee6e(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**Successful**: Manager to IVX authentication is successful. - ![GUID-33513EA0-E7A4-45A2-BEFE-EBAD9042CC8D-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-4c0fc6a0-7115-e80c-0ae5-e6225528b781(1).jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**Unsuccessful**: Manager to IVX authentication failed. User needs to recheck the credentials entered. - **---**: Yet to be configured. | | **Manager to IVX Authentication Failure Reason** | In case of Manager to IVX authentication failure, this column displays the reason for failure which helps users to take corrective actions and attain successful authentication. In case of a successful connection, the column displays the status as **---**. | | **Test connection** | Click to verify if the Manager is able to communicate with the broker node(s) using the details you configured. A **Result** pop-up appears displaying the status of the connection for all the configured broker nodes. > [!NOTE] > Note > > When you click **Test connection**, the action is performed over all the newly added and existing broker nodes and the result is displayed. | | ![GUID-8D2203E5-2C86-4970-8BBE-0E051DDA1A11-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dacf3482-cd76-d277-b253-1daffd3c0fa7(3).jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) | Click this button to add a broker node. > [!NOTE] > Note > > You can add a maximum of **5** broker nodes within a cluster. > [!NOTE] > Note > > Users should ensure that the broker nodes added in this section belong to the same IVX cluster. | | ![GUID-C5DB3A60-0A1C-4C8F-83A6-37EAFFF00433-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-2ebd8f05-a000-f22e-5dff-257981fc8b48(3).jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) | Click this button to remove newly added or existing broker nodes. You can delete only one node at a time. | | **Next** | Click this option upon modifying the broker node(s). | | **Cancel** | Click this option to cancel the add/delete operation performed on the broker nodes. | > [!NOTE] > Note > > **Cluster Status**, **Manager to IVX Authentication Status**, and **Manager to IVX Authentication Failure Reason** are updated only when you save the configuration changes. 4. Upon clicking ![GUID-8D2203E5-2C86-4970-8BBE-0E051DDA1A11-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dacf3482-cd76-d277-b253-1daffd3c0fa7(3).jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D), **Add Broker Node** panel appears in the right pane. **Adding broker node details** ![Adding broker node details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-feba9e24-91ea-4a6f-a62d-03da522be632.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) **Option definitions** | Option | Definition | | --- | --- | | **Server Address** | Enter the IP address (IPv4/IPv6) or Host Name of the IVX broker for communicating with the Manager and Sensor. | | **Username** | Enter the username of the IVX broker node. | | **Password** | Enter the password of the IVX broker node. | | **Add** | Click **Add** upon entering the broker node details. > [!NOTE] > Note > > The **Add** button remains grayed out if you enter invalid IP address. | | **Update** | Double-click an existing broker node if you plan to make any modifications in it. Upon updating the fields with valid inputs, click **Update**. | Upon configuring the cluster and the broker nodes, click **Next**. You will be redirected to the **IVX Integration** home page., click **Save**. Once the changes are saved, the **IVX Appliance Configuration** section appears as shown below: **IVX Appliance Configured** ![IVX Appliance Configured](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a8e1b899-e3be-bf2e-8079-04bc79891a16.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) > [!NOTE] > Note > > If you plan to modify an existing cluster, double-click the cluster to go to the next page where you can update the **Cluster Details** and the **Broker Nodes**. Follow the above steps to make the modifications. ### Enable and Configure integration with IVX Cloud 1. To enable and configure IVX cloud integration, select the **Enable IVX Cloud** option. **Enabling IVX Integration for an admin domain** ![Enabling IVX Integration for an admin domain](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-50fcfa80-00df-7330-836c-39948c5ac416.jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D) **Option definitions** | Option | Definition | | --- | --- | | **IVX Cloud Integration** | **Host Name** | Enter the host name for the IVX Cloud service (that is, the domain name on which IVX Cloud service is hosted). > [!NOTE] > Note > > You need to add a firewall exception to the domain (that you enter as **Host Name**) to ensure uninterrupted communication. For more information, see [Set the desktop firewall](/network-and-platform/docs/set-the-desktop-firewall-3). | | **API Key** | Enter the API key created in the IVX Cloud portal. This key is used for authentication and it retrieves the IVX Cloud service status. > [!NOTE] > Note > > The maximum character length supported is 6000. | | **Service Status** | Displays the status of IVX Cloud service. - ![GUID-E9D50264-CAFF-4207-8FAC-77D0B81FDCF3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-aaf997ab-fe3f-0cb2-30a0-e2b608c0ee6e(3).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**RUNNING**: The IVX Cloud service is running and is available for malware file polling and retrieving the analysis reports. The details of subscription and the files daily quota are also displayed underneath the **RUNNING** status. - ![GUID-33513EA0-E7A4-45A2-BEFE-EBAD9042CC8D-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-4c0fc6a0-7115-e80c-0ae5-e6225528b781(1).jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)**Failed**: User needs to recheck the configuration settings and the status of the IVX Cloud service. The failure reason is displayed which can be useful in troubleshooting the issue. - **---**: Not applicable. | | **Listening Port** | This is the port that IVX will listen for connections from Sensor and Manager. The default port is 443 and users cannot change it. | | **Enable Proxy for IVX Cloud Communication** | Select this option if you deployed proxy server between the Sensor and IVX Cloud. You need to configure proxy server at device level page and enable proxy option under the **IVX Cloud Integration** section. | | **Test connection** | Click to verify if the Manager is able to communicate with IVX Cloud using the details you configured. If the details entered are correct and the IVX Cloud service is running, a **Successful** dialog-box appears. This ensures that the Sensors submit suspicious files for analysis, and the Manager retrieves the analysis result and display it in the user interface. Click **OK** to close the dialog-box. If there is an issue, an **Error** dialog-box appears displaying the failure reason which can be useful in troubleshooting. > [!NOTE] > Note > > When you click **Test connection**, the action is performed over the currently selected configuration. | | **Save** | Saves the integration details in the Manager database and applies it to the inherited child domain(s)/device(s). | > [!NOTE] > Note > > The **Service Status** is updated only when you save the configuration changes. Upon saving the integration details, the **IVX Cloud Integration** section appears as shown below: **IVX Cloud integrated at domain level** ![IVX Cloud integrated at domain level](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-fd617977-e929-2f6f-906a-636629da6e93.jpg?sv=2026-02-06&spr=https&st=2026-11-20T11%3A16%3A39Z&se=2026-11-20T12%3A16%3A39Z&sr=c&sp=r&sig=3uLL63qEWhq9My87s8VO4L10%2FcPblFqdZkZaqcMtUYY%3D)