--- title: "Network Detection and Response 4.2.0 Release Notes" slug: "network-detection-and-response-4-2-0-release-notes" updated: 2026-11-18T15:04:06Z published: 2026-11-18T15:04:06Z canonical: "docs.trellix.com/network-detection-and-response-4-2-0-release-notes" --- > ## 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. # Network Detection and Response 4.2.0 Release Notes ## Release summary Trellix Network Detection and Response (Trellix NDR) version 4.2.0 introduces the Advanced Correlation and Analytics Engine. This engine provides high-fidelity stream processing, expanded cloud telemetry, and enterprise platform security enhancements. The release also adds Active Directory user logon ingestion and cloud DNS logging for AWS Route 53 and Infoblox to improve visibility across network or identity data and extend support across hybrid environments. It supports Trellix Insights enrichment and alert forwarding to Trellix Helix, Google Security Operations, and Microsoft Sentinel. The release includes user interface enhancements and security infrastructure updates. ### Release rating #### Critical This release addresses functional issues that affect standard workflows or high-severity security vulnerabilities that cause potential data loss, service outages, system crashes, or major compatibility blockers. - **Customer action**: Required. Install this release immediately, during the next available maintenance window, to protect your environment from vulnerabilities or to restore failed services. ## What’s new - [**Trellix Insights enrichment**](/network-and-platform/docs/investigate-alerts-using-trellix-insights-data-1): Queries the Trellix Insights threat intelligence database to enrich network alerts with actionable intelligence such as campaign details and reputation scores for IP addresses, domains, and indicators of compromise (IOCs), improving alert fidelity, reducing false positives, and accelerating investigation and response through deeper threat context. - [**Amazon Route 53 DNS log ingestion**](/network-and-platform/docs/integrate-trellix-ndr-console-with-amazon-route-53-1): Ingests internal DNS queries from Amazon Route 53 Resolver and VPC logs, extending NDR visibility into cloud environments. - [**Infoblox BloxOne Cloud integration**](/network-and-platform/docs/integrating-ndr-with-infoblox-1): Ingests DNS logs from the Infoblox Cloud portal through S3 buckets to detect suspicious DNS activities. - [**Microsoft Sentinel integration**](/network-and-platform/docs/integrating-ndr-with-microsoft-sentinel-1): Forwards alerts to Microsoft Sentinel to improve cross-source threat correlation in Sentinel cloud workflows. - [**Google Security Operations (Google SecOps) integration**](/network-and-platform/docs/integrating-trellix-ndr-console-with-google-security-operations-1): Forwards alerts to Google SecOps to accelerate investigation and response in SecOps workflows. - [**Trellix Helix integration using Comm Broker**](/network-and-platform/docs/integrating-with-trellix-helix): Enables forwarding of Trellix NDR alerts to Trellix Helix through Comm Broker to correlate discrete, multi-vector threat events. - [**NetFlow record ingestion**](/network-and-platform/docs/integrate-the-netflow-collector-1): Enables NetFlow data ingestion. Ingested NetFlow records can be searched and viewed in the NDR Web UI. - [**Local password policy enforcement**](/network-and-platform/docs/local-password-policy): Introduces enhanced local password policy management in the NDR Web UI to enforce strong password requirements. - [**Active Directory integration**](/network-and-platform/docs/detecting-user-anomalies-1): Ingests user logon events directly from Microsoft Active Directory. This detects credential abuse and eliminates Trellix Logon Collector dependencies. - [**Multi-LDAP group mapping**](/network-and-platform/docs/configure-ldap-or-active-directory-authentication-2): Supports mapping multiple Active Directory or LDAP groups to application-specific roles. This enables nested group traversal and flexible access control. - **RDP anomalies customization**: Expands detection coverage for Remote Desktop Protocol (RDP) attacks and anomalies. This update also reduces false-positive alerts. - [**User anomaly detection**](/network-and-platform/docs/detecting-user-anomalies-1): Compares Active Directory logon events with historical baselines to detect anomalous user behavior in real time. The system generates alerts for suspicious activities, such as unusual host access, non-standard sign-in hours, and brute-force attempts. - [**Nozomi Guardian alerts enrichment**](/network-and-platform/docs/integrating-with-nozomi-guardian-2): Pairs with Nozomi Guardian to ingest operational technology asset telemetry. The user interface displays context-aware descriptions and next-step panels for ingested alerts. - [**Syslog server configuration**](/network-and-platform/docs/configure-syslog-server-from-the-integration-hub-1): Adds Syslog server configuration to the **Integration Hub**. - [**Trellix Wise settings**](/network-and-platform/docs/investigating-alerts-using-trellix-wise-2): Adds a setting to turn on or turn off Trellix Wise generative AI investigations. - [**Trellix Wise daily API limits**](/network-and-platform/docs/investigating-alerts-using-trellix-wise-2#licensing-and-daily-api-request-limits1): Replaces the Trellix Wise trial license model with a daily API call limit based on the installed product edition. Trellix NDR Essentials and Core support up to 100 calls per day. Trellix NDR Enterprise supports up to 1,000 calls per day. The console displays a notification when the limit is reached. - [**Main menu usability enhancements**](/network-and-platform/docs/the-network-detection-and-response-dashboard-2): - Displays a numerical pop-up when you hover over **Alerts** and **Assets** in the main navigation menu. - For **Alerts**, the pop-up displays the number of open or new alerts by severity: Critical, High, Medium, and Low. - For **Assets**, the pop-up displays the number of assets by risk level: Critical, High, Medium, and Low. - Allows you to mark frequently used pages as **Favorites** in the main navigation menu for quick access. The first marked favorite becomes the default landing page the next time you sign in. - [**Large-scale search and storage limits**](/network-and-platform/docs/searching-with-trellix-ndr-console-2): Supports exporting up to one million search results. You can search across the entire configured retention period instead of a 30-day window. ## Resolved issues **General** | **Issue ID** | **Description** | | --- | --- | | NDR-2191 | Critical Nozomi alerts displayed with a medium severity in the Trellix NDR Web UI. The system calculated risk status using only the internal MITRE scoring hierarchy. | | NDR-2792 | Administrators could map only a single group per role in the LDAP role configuration. This limitation reduced administrative flexibility in multi-group Active Directory environments. | | NDR-2816 | Selecting a severity segment within the donut chart on the **Alert List** page caused the user interface layout to break. | | NDR-3220 | Search parameters in the user interface restricted query date ranges to 30 days and capped the returned event table entries. | | NDR-3354 | Data retention settings configured on non-master data nodes overrode master appliance policies. This configuration caused the system to purge data prematurely after 30 days. | | NDR-3737 | Administrators lacked a configuration option to control the visibility of the Trellix Wise feature across the Trellix NDR Web UI. | | NDR-3761 | Cluster maintenance purge policies triggered based on secondary data node configurations instead of master settings. This behavior led to unexpected data trimming at 30 days. | | NDR-4479 | Updating asset tables in PostgreSQL generated database errors when handling extended asset attribute values. The input values exceeded the 40-character length limit. | | NDR-4717 | The Nozomi Sandbox integration failed to display alerts on the console. API client HTTP requests timed out and lacked validation for missing MITRE tactic fields. | | NDR-6224 | Email reconstruction failed to load email body content and metadata in the user interface. A keyword mapping mismatch prevented the command-line output from parsing correctly. | | NDR-6241 | Hovering over an IP address on alert view pages caused a user interface rendering glitch. Tooltips and table elements shifted position continuously. | | NDR-6414 | Trellix Helix ingested forwarded alerts as an unknown class. Invalid JSON wrapping over Syslog headers caused this parsing and classification failure. | | NDR-6524 | Email reconstruction requests returned blank views in both Director and Data Node modes. Data mapping discrepancies between the pivot engine and the user interface caused this issue. | | NDR-6696 | The Trellix NDR Web UI displayed inaccurate trial expiration errors for licensed deployments. | | NDR-6410 | The alert suppression feature lacked custom duration settings and restricted suppression to exact matches for alert names, target IP addresses, and source IP addresses. | | NDR-6878 | The system lacked automated pipelines for Syslog alert forwarding and Host OS severity mapping. | | NDR-1773 | Azure Network Detection and Response Console (NDRC) deployments lacked a Microsoft Sentinel integration for forwarding alerts and returning to the console. | | NDR-6382 | Trellix NDR failed to receive SmartVision alerts from Network Security (NX) appliances due to a date format parsing exception. | | NDR-6848 | Trellix NDR failed to validate Trellix Wise licenses and incorrectly displayed trial expiration warnings for fully licensed deployments. | | NDR-6509 | The `go-elatbatch` service used to go down due to a race condition. | | NDR-6760 | Administrators could not configure proxy settings for the DTI cloud because executing the `dtigateway` command caused the console interface to go blank in an air-gapped network. | | NDR-7143 and NDR-7461 | System dump generation failed because unclosed database connections related to VLAN pivot data records exhausted the PostgreSQL connection pool. | | NDR-2581 | Users could not download complete search results because the user interface restricted data exports and limited query date ranges to 30 days. | | NDR-3221 | The user interface limited search result exports for high-volume queries. Users could not download complete datasets exceeding one million records. | | NDR-7309 | Trellix NDR failed to receive SmartVision alerts from Network Security (NX) appliances due to a date format parsing exception. | **Installation** | **Issue ID** | **Description** | | --- | --- | | NDR-4263 | Initial network connectivity delays during environment startup caused the Nozomi import service authentication to fail. This failure permanently shut down worker threads. | **Security fixes** | **Issue ID** | **Description** | | --- | --- | | NDR-3219 | Security audits identified vulnerabilities in legacy user interface libraries. The system also contained unflagged session cookies and failed to revoke session tokens upon closing browsers. | | NDR-3222 | Local user authentication lacked configurable complexity and expiration controls. Administrators could not enforce character minimums, password history, maximum password age, or account lockouts. | | NDR-3887 | Abnormal browser termination without an explicit logout allowed web session cookies to remain active. This behavior left sessions susceptible to reuse. | | NETFIM-7869 | Security scans identified vulnerable third-party JavaScript dependencies in the user interface. | **Performance** | **Issue ID** | **Description** | | --- | --- | | NDR-3550 | The `ia-eve-route` process encountered parsing errors when processing incoming sensor event files. The files contained unexpected array objects or zero-width character encodings. | | NDR-3561 | Search queries executed through the Network Investigator (NI) Director user interface experienced high latency when querying across multiple data nodes with large event volumes. | | NDR-3565 | High-volume sensor event streams triggered `ia-eve-route` parsing errors. This behavior caused event backlog processing stalls on the Trellix NDR Web UI. | | NDR-5575 | High-throughput event ingestion under heavy traffic loads caused recurring `ia-eve-route` parsing errors and service crashes on Network Investigator (NI) nodes. | | NDR-6246 | Critical Nozomi alerts displayed with a medium severity in the Trellix NDR Web UI. The system calculated risk status using only the internal MITRE scoring hierarchy. High-frequency Kafka message queue logs and Java Virtual Machine (JVM) error dumps rapidly consumed space on the root partition. This consumption caused system service halts. | ## Known issues For a complete list of Trellix Network Detection and Response known issues, see [KB000015816](https://support.trellix.com/s/article/000015816). ## Upgrade and installation information ### Release information This section details the release date, build numbers, and installation packages included in this release. **Release date**: November 18, 2026 **Build information**: 4.2.0.69536 | **Component** | **Build number** | | --- | --- | | Trellix Network Detection and Response Console | 4.2.0.69536 | **Platform-specific packages** | **Deployment type** | **Package / Build** | | --- | --- | | Upgrade package | `4.2.0.69536.fe` | | VMware vSphere | `4.2.0.69536.ova` | | KVM | `4.2.0.69536.iso` | | Hyper-V | `10.0.20348.1.iso` | | AWS | `4.2.0.69536.ami` > [!NOTE] > Note > > The AWS AMI is shared upon request. | | Azure | `4.2.0.69536.vhd` > [!NOTE] > Note > > The Azure VHD is shared upon request. | ### Prerequisites - Install a valid Trellix NDR Core or Enterprise software license to support real-time anomaly detection engines and multi-vendor integrations. - Open ports TCP 22, TCP 1194, and UDP 1194 on intermediate firewalls so cluster appliances can communicate over an isolated private network. - Allowlist the required domains for Trellix Insights, Trellix Wise, and Trellix Helix. ### Upgrade impact | **Component** | **Impact** | | --- | --- | | Temporary service outage | The Trellix NDR appliance reboots automatically after the upgrade completes. The upgrade temporarily interrupts packet capture and access to the management console. | | Metadata sync outage | Upgrading paired Packet Capture (PX) appliances temporarily interrupts metadata synchronization and PCAP download capabilities. | ### Supported upgrade path The following table lists the supported upgrade paths to the current release. If your environment is running one of the versions listed in the table, follow the corresponding upgrade path to successfully upgrade to **Trellix NDR 4.2.0**. | **Current version** | **Supported upgrade path** | | --- | --- | | 3.x.x | 4.0.x → 4.2.x | | 4.0.x or 4.1.x | 4.2.x | ## Deprecated items - **Trellix Logon Collector (TLC) dependency**: Trellix NDR removes the dependency on the legacy Trellix Logon Collector (TLC) service. Administrators must migrate domain synchronization configurations to the native Microsoft Active Directory integration via the web interface or API. ## Additional information - [**Trellix Thrive**](https://support.trellix.com/): Access the unified portal for technical support, product downloads, support case management, diagnostic tools, knowledge base articles, product training, webinars, and community interaction. > [!NOTE] > Note > > Access to the Trellix Thrive Portal requires login using valid Trellix customer support, partner, or employee credentials. - [**Trellix Network Detection and Response Documentation**](https://docs.trellix.com/network-and-platform/docs/network-detection-and-response-ndr): For detailed technical information, including product guides, release notes, installation or deployment instructions, and configuration guidelines for Trellix NDR, visit our documentation portal at [docs.trellix.com](https://docs.trellix.com). - [**Rollback information**](/network-and-platform/docs/reverting-to-a-previous-software-version) - [**Trellix Product Compatibility Matrix (KB000015942)**](https://support.trellix.com/s/article/000015942)