--- title: "Investigating with Trellix NI - A use case scenario" slug: "investigating-with-trellix-ni-a-use-case-scenario" tags: ["Integration", "IPS 11.1.x"] updated: 2026-11-19T12:30:36Z published: 2026-11-19T12:30:36Z canonical: "docs.trellix.com/investigating-with-trellix-ni-a-use-case-scenario" --- > ## 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. # Investigating with Trellix NI - A use case scenario In the use case presented below, it is assumed that Trellix NI is integrated with Trellix IPS, which means that the Manager and attached Sensors are able to successfully communicate with the NI appliance and send alert data, flow records and L7 metadata information to NI. It is also assumed that the Trellix NI is connected to a PX appliance which is added to the Client Group configured and associated with the IPS Manager at the domain and/or device level. > [!NOTE] > Note > > Some screenshots and related web features referenced in this section may vary slightly from the latest NI Web UI. > [!WARNING] > Important > > The IP addresses and ports shown in this use case have been used for representation purpose only. **The use case** The **Analysis** → **** → **Attack Log** page in the Manager shows an alert named **HTTP: MOVEit Transfer Shell Upload Activity Detected (CVE-2023-34362)** which looks suspicious and you want to investigate it further by analyzing the corresponding flow record and alert entry available on the NI Web UI for the same alert. **Suspicious Alert identified on IPS Manager** ![Suspicious Alert identified on IPS Manager](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-701dda67-33f2-63d4-ddbd-e6efe60c91e6.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D) You can obtain the Attacker IP Address/port or Target IP address/port from the **Summary** tab of the selected alert and then look for the same alert entry in the **Alerts** page of the NI Web UI. The screenshot below shows the same alert entry located in the **Alerts** page of NI Web UI. **Alert entry located on the Alerts page in NI** ![Alert entry located on the Alerts page in NI](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-21801bf4-b7c2-f7e6-3d30-1f65d6fb0c8f.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D) Selecting the alert provides you with detailed information about the alert in **Threat Highlights** section under the **Details** tab. To analyze the event further, click the **View** link beside the **ALERTURL** field, which redirects you to the Web UI of the associated PX appliance. On the PX Web UI, you are redirected to the **History** tab of the **Search** page with an entry for the alert being analyzed. You can view the depth of the search (here, the alert), date and time when it was created, number of items found in the search, and its status. If you wish to download the PCAP file related to the alert event, click **Session Analysis** and then **Download PCAP** button. **The details of the alert as shown on PX Web UI** ![The details of the alert as shown on PX Web UI](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-f6f715dc-6da6-adda-3d66-00460fe364b5.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D) > [!NOTE] > Note > > For more information on the PX Platform and how to use it for network investigation, refer to [PX Series User Guide](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/px_ug_6-1_pdf.pdf?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D). You can also correlate the alert under analysis to the corresponding netflow to drill down further into the network event. To identify the corresponding netflow, navigate to the **Dashboards** page of NI Web UI and construct a search query in NI **Query Bar** using the Attacker/Target IP address or any other data related to the alert. Searching with the query `doc_values_type:flowANDsourceIPv4Address:192.168.0.1` shows the corresponding flow entry in the **Event Table** of the NI **Dashboards** page, as shown in the screenshot below: **Corresponding flow entry identified on NI Dashboard** ![Corresponding flow entry identified on NI Dashboard](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-25066d50-3033-3359-9108-6ce3b64414a2.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D) To analyze the packet(s) associated with the netflow being analyzed, select the flow entry on NI and click **Reconstruct** (![GUID-69BB0396-3D51-40F2-8F2B-CA570FE145B3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dcdc70bc-dfc7-80f0-3bba-8e9abc57419f.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D)) icon. It redirects you to the **Packets** tab within the **Dashboards** page where you can view the number of connections within the flow. You can also view all packets associated with the flow, packet flow direction, source and destination IPs, source and destination ports, and the packet protocol for each packet session. The **Packets** tab also allows you to review the hex data of any selected packets in the **Hex Details** section. Post your analysis on the information available on the **Packets** tab, you may download and collect all packets of interest for the selected flow in the PCAP format by clicking the **Download Merged PCAP** button, which you can further analyze by using any third-party applications, such as WireShark. **Packets tab showing the reconstructed packet data of the selected netflow** ![Packets tab showing the reconstructed packet data of the selected netflow](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d27899b6-2427-45e7-c757-71c0c74a67b8.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A38%3A56Z&se=2026-11-20T12%3A38%3A56Z&sr=c&sp=r&sig=l1uA7TDjV3peIa33EYz21wr44DG0pIHpVti9MnH3ycM%3D)