GREYCORTEX Mendel 5.0’s new Traffic flow map shows a host’s communication partners and helps security analysts follow that communication step by step.
You have a host worth investigating. The next thing you need to know is whom it communicates with, which way the traffic runs, and which services it uses. That will tell you whether its behavior is normal or not. A workstation that talks to a file server, a DNS server and a gateway looks like normal behavior. But the same workstation reaching forty internal hosts on one port does not behave typically. The same event on two different hosts can mean two different things, and the communication is what separates them.
In this deep dive, we look closely at the Traffic Flow Map: how to read it and how to follow a connection.
Missed part one? How to Prioritize Host Investigations →
What the Traffic Flow Map Shows
The Traffic flow map is a visual map of network communication. It shows who talked to whom and which services they used, over the time range you select. The host you investigate sits in the center, its peers sit around it, and every line is a connection.
You choose the metric the map is drawn from:
- Data volume
- Flows
- Packets
- Retransmissions
- Unreplied flows, as a percentage or as an absolute number
Color does the first round of triage for you. Blue lines carry traffic in both directions. Orange lines mark connections with unreplied flows or retransmissions, so a link with a problem is visible before you read a single number.
The map is built on Mendel’s new data model and stays fast on networks with thousands of hosts.
Step-by-step Investigation with the Traffic Flow Map
The map opens from the Traffic flow map button in the Host Dialog, or from the Network menu. It always shows the time range you have selected, and zoom, pan and filters keep the view readable. Switching off the external subnets is usually the first thing to do, because they add a large number of peers.
1. Choose the metric. The map is drawn from flow count by default. Switch the metric when your question changes: data volume for large transfers, retransmissions or unreplied flows for links that are not working as they should. The metric decides which peers appear and which connections are emphasized.
2. Get the details without leaving the map. Hover over a connection to see the data sent in each direction, the destination, the application response time, the round-trip time and the main port. Hover over a host to see its IP details.
3. Follow the path. Click any peer to expand it and see its own peers. This is how you follow a communication path across the network, one host at a time, without going back to the filters for every new address.
4. Open the connection. Select a line to drill down into the services behind it. Mendel shows how much data each service sends and receives, along with the total volume. You can then go one step further and examine the individual flow records.
You can then go one step further and examine the individual flow records.
Continue with part three: How to Investigate a Security Event →
What the Traffic Flow Map Gives You
Most of the work in a host investigation goes on context: what this host normally communicates with, and which of its connections deserves a closer look. The Traffic flow map gives you that context in one view. You see the most significant peers, direction and volume at once, you find weak or failing links by their color, and you open the exact flow records behind any line you want to check. You form the judgment there, and you confirm it in the flows.
At this point you know which host to investigate, what kind of machine it is, and who it talks to. What is still open are the events themselves: what each alert detected, and whether it deserves your time. That is the question the AI Assistant answers, and it is the subject of part three.
Want to see the full investigation workflow in Mendel 5.0?
Get the recording →
Categories
- Company News (38)
- Product News (31)
- IT/OT Security (42)
- Webinars (6)