--- title: "Investigation — Investigate an attack using Trellix EDR" slug: "investigation-investigate-an-attack-using-trellix-edr" tags: ["Product Usage", "EDR", "Endpoint Security"] updated: 2026-09-18T11:46:20Z published: 2026-09-18T11:46:20Z canonical: "docs.trellix.com/investigation-investigate-an-attack-using-trellix-edr" stale: true --- > ## 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. # Investigation — Investigate an attack using Trellix EDR Investigate the alert to determine if it's a false positive or malicious activity. For a quick overview, see the following workflow. 1. Initial alert analysis: 1. Review alert details in the EDR workspace > [Monitoring](/v1/docs/monitoring-threats-1) dashboard. 2. For specific details about the alert, review the [Alerting](/v1/docs/check-individual-alert-details-1) dashboard: 1. The name, data, and time of the impacted endpoint. 2. The process name, which is, the command or script that triggered the alert. 3. The technique ID, if available, which will correspond to a MITRE ATT&CK™ Matrix knowledge base article. See the section "Threat behavior" in [Analyze threats](/v1/docs/analyze-threats-1). 4. Review tactics and behaviors of adversaries that prompted EDRF to identify it as a suspicious indicator. See the section "Mapping of techniques observed and suspicious indicators" in [Analyze threats](/v1/docs/analyze-threats-1). 5. Use Trellix Wise to generate a Knowledge graph, which depicts the sequence of events and processes involved in the potential attack. See [Search for historical data on a single endpoint](/v1/docs/search-for-historical-data-on-a-single-endpoint-1). 3. If the alert is still a potential threat, proceed to Step 2 Enrichment and deeper investigation. 2. Enrichment and deeper investigation: 1. Create an investigation for this potential threat using [Generative AI](/v1/docs/investigate-threats-using-generative-ai-1). 2. The operating system assigns a unique process ID (PID) to all processes. EDRF uses PID in its system monitoring, forensic investigation and threat remediation. Use a device search, which uses PID to follow all actions related to a specific threat, including network and DNS connections. 3. Run a [real-time search query](/v1/docs/search-real-time-data-of-endpoints-for-investigation-and-threat-hunting) to obtain the latest information from your endpoints. 4. Use [Historical Search](/v1/docs/search-for-historical-data-on-a-single-endpoint) on an endpoint to gather suspicious activity such as IOC hashes, trace time, and loaded DLLs over a defined timeframe.