--- title: "What's new" slug: "what-s-new-25" tags: ["Release Notes", "IPS 11.1.x"] updated: 2026-10-01T07:59:03Z published: 2026-10-01T07:59:03Z canonical: "docs.trellix.com/what-s-new-25" --- > ## 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. # What's new ### New features This release of Trellix Intrusion Prevention System does not include any new feature. ### Enhancements This release of Trellix Intrusion Prevention System includes the following enhancements: **IPS support for multiple IVX brokers** Previously, IPS allowed users to integrate with a single IVX appliance broker node for malware analysis of files. Starting with this release of 11.1, IPS allows users to configure up to 5 IVX appliance broker nodes under the cluster. The Sensor submits files to the broker nodes in round robin manner for analysis and result polling, meaning better file submission rate and high availability are achieved. Also, users can now configure broker nodes on IPv6 addresses unlike the earlier releases which supported only IPv4 communications. In case of failed Manager-IVX or Sensor-IVX authentication, users can now view failure reason on the Manager UI which allows them to take corrective actions to attain successful authentication. > [!NOTE] > Note > > At Device level, if you are inheriting admin domain configuration, make sure that both the Manager and the Sensor are running on software version 11.1 Update 4 or later. In case of heterogeneous scenarios where you are on a 11.1 Update 4 Manager and an older Sensor that supports only one broker node on IPv4, make sure you have added only one IPv4 broker address at Global level. If you have added an IPv6 address and the settings get inherited to the older Sensor, the file detection will not happen. > [!NOTE] > Note > > It is highly recommended that you upgrade both the Manager and Sensor to 11.1 Update 4 or later releases to utilize multiple brokers which are connected over IPv4 and IPv6 addresses. The following Sensor CLI commands are added: **Normal Mode** | Command | Description | | --- | --- | | `ivx lookup sha256` | This command performs lookup on the entered SHA256 hash and returns details such as the verdict, report id, and the query time. | | `show ivxcloud config` | This command displays the IVX Cloud configuration details. | | `show ivxcloud stats` | This command displays statistics specific to IVX Cloud. | | `show ivxcloud status` | This command displays the connection status of the IVX Cloud. | The following Sensor CLI commands are updated: **Normal Mode** | Command | Description | | --- | --- | | `show ivx config` | This command now displays the configuration details of all the IVX broker nodes attached to the Sensor. | | `show ivx stats brokerid` | This command now displays the statistics specific to the IVX broker nodes attached to the Sensor. | | `show ivx status brokerid` | This command now displays the connection status of the IVX broker nodes attached to the Sensor. | The following Sensor CLI command is updated: **Debug Mode** | Command | Description | | --- | --- | | `show mgmtcfg` | This command now displays the IVX broker node management configuration. | For more information on IVX integration, refer to the section [Integrating Trellix IPS and IVX](/network-and-platform/docs/integrating-trellix-ips-and-ivx) in [Trellix Intrusion Prevention System 11.1.x Integration Guide](/network-and-platform/docs/trellix-intrusion-prevention-system-11-1-x-integration-guide). **Device software deployment improvements in the Manager** In this release of 11.1, several enhancements have been made on the IPS Manager to improve and speed up the device software deployment operations. This is to cater to the bulk deployment requirements of network environments where large or very large number of Sensors are deployed. The Manager takes the following actions while handling bulk Sensor software upgrade requests: - The Manager reserves 100 GB under required free disk space for Manager operations and considers an additional file size of 1.2 GB to be generated for each software deployment request. When the Manager receives the software deployment requests in batches, it checks the number of Sensors selected, and calculates the free disk space required to complete the deployment operation. If there is insufficient disk space, an error message is displayed in the UI stating the available disk space and space required to complete the upgrade task. This enables the Manager to maintain optimal performance, secure sufficient disk space to keep other processes running, and avoid any software upgrade failure scenario. - Software deployments are critical operations and performed under approved/scheduled maintenance window. If the Manager receives multiple deployment requests in queue along with device software update requests, such as signature file and SSL keys deployments, it prioritizes the software deployment requests ahead of all other requests. It also performs disk usage optimization for each deployment to help you perform more deployments at a faster speed, and complete the critical task of software deployments within the approved/scheduled maintenance time. > [!NOTE] > Note > > Very large Sensor deployments mean that the number of Sensors deployed is more than 100. Large Sensor deployments have Sensors numbering between 36 and 100+. For more information, refer to the section [Large Sensor deployments](/network-and-platform/docs/large-sensor-deployments) in [Trellix Intrusion Prevention System 11.1.x Product Guide](/network-and-platform/docs/trellix-intrusion-prevention-system-11-1-x-product-guide-1). **Deployment of IPS Manager on Kernel-based Virtual Machine (KVM)** Starting with this release of 11.1, users can deploy IPS Manager on Kernel-based Virtual Machine (KVM) using the respective qcow2 image available in the [Trellix Download Server](https://www.trellix.com/en-us/downloads/my-products.html). Refer to the table *KVM server requirements for MLOS* in the *Installation Parameters* section to understand the server requirements for Manager deployments on KVM. For more information, refer to the section [Create a Manager instance using qcow2 file](/network-and-platform/docs/create-a-manager-instance-using-a-qcow2-file-2) in [Trellix Intrusion Prevention System 11.1.x Installation Guide](/network-and-platform/docs/trellix-intrusion-prevention-system-11-1-x-installation-guide-1). **Support for external file reputation through Trellix Threat Intelligence Exchange (TIE)** Starting with this release of 11.1, IPS allows users to integrate an external file reputation provider to the existing list of TIE providers. This will allow the sensor to receive a reputation score for the file from the External Provider. For more information, refer to the sections [How the integration works](/network-and-platform/docs/how-the-integration-works-1) and [Viewing Threat Intelligence Exchange detection in the Manager](/network-and-platform/docs/viewing-threat-intelligence-exchange-detection-in-the-manager-1) in [Trellix Intrusion Prevention System 11.1.x Integration Guide](/network-and-platform/docs/integration-with-trellix-epolicy-orchestrator-on-premises). **Cache implementation for Trellix Threat Intelligence Exchange (TIE) / Global Threat Intelligence (GTI) File Reputation** Starting with this release of 11.1, caching support is extended to Trellix TIE/GTI File Reputation service. Following Sensor CLI commands are updated for TIE/GTI cache implementation: **Normal Mode** | Command | Description | | --- | --- | | `clearmalwarecache` | This command now allows users to clear cache entries related to TIE/GTI engine made in the Sensor. | | `malwarecache` | This command now enables or disables malware cache for TIE/GTI engine. | **Debug Mode** | Command | Description | | --- | --- | | `show malwareserverstats` | This command now includes an entry called `Artemis Cache hit Cnt` to display the number of times TIE/GTI cache is being read. | > [!NOTE] > Note > > Either Trellix GTI or TIE server can be configured with Trellix IPS solution at a time. For more information, see the sections [IPS CLI Commands - Normal Mode](/network-and-platform/docs/ips-cli-commands-normal-mode-3) and [IPS CLI Commands - Debug Mode](/network-and-platform/docs/ips-cli-commands-debug-mode-3) in [Trellix Intrusion Prevention System 11.1.x Product Guide](/network-and-platform/docs/trellix-intrusion-prevention-system-11-1-x-product-guide-1). ### Rebranding updates This is solely for informational purposes, there is no action required. You will notice the following changes: **Product name** - Trellix Vector Execution is renamed to Trellix Intelligent Virtual Execution - Server (Trellix VX/ IVX) and Trellix Detection as a Service is renamed to Trellix Intelligent Virtual Execution Cloud (Trellix IVX Cloud/ IVX Cloud). The associated software, hardware, features, and options bearing the old product name are renamed to the new product name. - Trellix Investigation Analysis is renamed to Trellix Network Investigator (NI). The associated software, hardware, features, and options bearing the old product name are renamed to the new product name. **Terminology updates in the UI** This release contains the following terminology updates in the Manager UI: | **Navigation Path** | **Prior to 11.1.7.71** | **11.1.7.71 and later** | | --- | --- | --- | | **Devices** → **** → **Global** → **IPS Device Settings** → **IVX Integration** | Enable **Enable MVX Integration** check-box and select **Enable VX**. - To add a broker node, enter the details of the broker node and click **Save**. - To edit a broker node, update the details and click **Save**. | Enable **Enable IVX Integration** check-box and select **Enable IVX**. - Click **Add IVX Cluster**. To add broker nodes, click the ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-72053356-4c05-0f24-325f-27e024879a39.png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A18%3A59Z&se=2026-11-20T17%3A18%3A59Z&sr=c&sp=r&sig=JICNNqSPcICWZDyvifs716bzWrGMjqJwaD2%2Bwdvbfq4%3D) icon located at the at the bottom-left corner of the page. The **Add Broker Node** panel opens to the right of the page. Enter the broker node details and click **Add**. Then, click **Next**. In the **IVX Integration** parent page, click **Save**. - To modify a broker node in the cluster, double-click the cluster. Double-click the broker node that you want to modify. The **Add Broker Node** panel opens to the right of the page. Update the IVX broker details and click **Update**. Then, click **Next**. In the **IVX Integration** parent page, click **Save**. - To delete a broker node in the cluster, double-click the cluster. Choose the broker node that you want to delete and click ![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(1).jpg?sv=2026-02-06&spr=https&st=2026-11-20T16%3A18%3A59Z&se=2026-11-20T17%3A18%3A59Z&sr=c&sp=r&sig=JICNNqSPcICWZDyvifs716bzWrGMjqJwaD2%2Bwdvbfq4%3D). Then, click **Next**. In the **IVX Integration** parent page, click **Save**. | | **Devices** → **** → **Devices** → **Setup** → **IVX Integration** | Disable **Inherit Settings?** check-box, enable **Enable MVX Integration** check-box, and select **Enable VX**. - To add a broker node, enter the details of the broker node and click **Save**. - To edit a broker node, update the details and click **Save**. | Disable **Inherit Settings?** check-box, enable **Enable IVX Integration** check-box, and select **Enable IVX**. - Click **Add IVX Cluster**. To add broker nodes, click the ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-72053356-4c05-0f24-325f-27e024879a39.png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A18%3A59Z&se=2026-11-20T17%3A18%3A59Z&sr=c&sp=r&sig=JICNNqSPcICWZDyvifs716bzWrGMjqJwaD2%2Bwdvbfq4%3D) icon located at the at the bottom-left corner of the page. The **Add Broker Node** panel opens to the right of the page. Enter the broker node details and click **Add**. Then, click **Next**. In the **IVX Integration** parent page, click **Save**. - To modify a broker node in the cluster, double-click the cluster. Double-click the broker node that you want to modify. The **Add Broker Node** panel opens to the right of the page. Update the IVX broker details and click **Update**. Then, click **Next**. In the **IVX Integration** parent page, click **Save**. - To delete a broker node in the cluster, double-click the cluster. Choose the broker node that you want to delete and click ![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(1).jpg?sv=2026-02-06&spr=https&st=2026-11-20T16%3A18%3A59Z&se=2026-11-20T17%3A18%3A59Z&sr=c&sp=r&sig=JICNNqSPcICWZDyvifs716bzWrGMjqJwaD2%2Bwdvbfq4%3D). Then, click **Next**. In the **IVX Integration** parent page, click **Save**. | **IPS CLI enhancements** The following Sensor CLI commands are updated: **Normal Mode** | Command | Description | | --- | --- | | `clearmalwarecache` | This command has been updated with respect to the rebranding changes made on MVX. If users plan to delete cache entries of IVX, they need to issue the command `clearmalwarecache ivx`. | | `malwarecache` | This command has been updated with respect to the rebranding changes made on MVX. If users plan to enable or disable malware cache of IVX engine, they need to use the syntax `malwarecache <enable \| disable> ivx`. | The following Sensor CLI commands are updated: **Debug Mode** | Command | Description | | --- | --- | | `set malwareEngine` | This command has been updated with respect to the rebranding changes made on MVX. If users plan to enable/disable the IVX malware engine for Advanced Malware inspection, they need to issue the syntax `set malwareEngine ivx <enable \| disable`. | | `show ni status` | The syntax and output of this command have been updated with respect to rebranding changes made on Trellix NI. | | `getnistats` | The syntax and output of this command have been updated with respect to rebranding changes made on Trellix NI. | | `clearnistats` | The syntax and output of this command have been updated with respect to rebranding changes made on Trellix NI. | | `ninetflowstat` | The syntax and output of this command have been updated with respect to rebranding changes made on Trellix NI. | > [!NOTE] > Note > > Apart from the above listed commands, a few more commands have been updated where the output displays the rebranding changes. As these changes do not have impact over the commands you input, they have not been listed here. For more information, see [CLI Commands](/network-and-platform/docs/introduction-28) in [Trellix Intrusion Prevention System 11.1.x Product Guide](/network-and-platform/docs/trellix-intrusion-prevention-system-11-1-x-product-guide-1). ### Updated platform, environment, or operating system support This release provides the following enhancements related to platforms, environments, or operating systems: **JDK upgrade** Starting with this release of 11.1, the IPS Manager uses JDK version 8u392 that includes additional security against new vulnerabilities. **Apache Tomcat server upgrade** Starting with this release of 11.1, Tomcat server used in the IPS Manager is upgraded to version 9.0.83 which provides a collection of security fixes.