--- title: "Task list for finding the source of asymmetric Flows" slug: "task-list-for-finding-the-source-of-asymmetric-flows" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:26Z published: 2026-09-12T20:42:26Z canonical: "docs.trellix.com/task-list-for-finding-the-source-of-asymmetric-flows" --- > ## 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. # Task list for finding the source of asymmetric Flows If you suspect that the traffic monitored by your appliance contains asymmetric flows, follow these guidelines to locate the source of the asymmetric traffic. > [!WARNING] > Important > > To avoid depleting system resources and degrading appliance performance, enable this feature only while you are collecting and viewing the statistics needed to investigate asymmetric flows in the network. 1. Check the ratio of asymmetric traffic to non-asymmetric traffic. See [Viewing the number of asymmetric flows using the CLI](/network-and-platform/docs/viewing-the-number-of-asymmetric-flows-using-the-cli). > [!NOTE] > Note > > On SmartVision Mode sensors, the suspicious objects that Trellix Unified Multiflow Engine (FUME) sends to the virtual machine (VM) to detect multiflow attacks are limited .exe and .dll files over SMB and SMB 2. 2. If the ratio is high, begin caching statistics about the asymmetric traffic flows. See [Enabling asymmetric flow statistics collection using the CLI](/network-and-platform/docs/enabling-asymmetric-flow-statistics-collection-using-the-cli). 3. Analyze the cached traffic flow statistics. Statistics for SYN‑only flows and non-SYN‑only asymmetric flows are listed separately. Within each list, statistics for the most frequently occurring flow profiles are listed first. See [Viewing the asymmetric flow statistics using the CLI](/network-and-platform/docs/viewing-the-asymmetric-flow-statistics-using-the-cli). 4. (Optional) If a list is at or near its capacity of 100 unique flow profiles, you can refresh the cache, enabling the appliance to collect statistics for the latest traffic. See [Refreshing the asymmetric flow statistics cache using the CLI](/network-and-platform/docs/refreshing-the-asymmetric-flow-statistics-cache-using-the-cli). 5. **IMPORTANT!** When you are no longer actively investigating asymmetric flows, stop caching asymmetric traffic flow statistics. See [Disabling asymmetric flow statistics collection using the CLI](/network-and-platform/docs/disabling-asymmetric-flow-statistics-collection-using-the-cli).