Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Network traffic analysis builds a baseline of normal communication and flags departures from it, catching intrusions that produce no malware and no failed login.

What Is Network Traffic Analysis?
Signature-based detection answers the question “have I seen this before?”. Network traffic analysis answers a different one: “is this normal for this host?”. It collects traffic metadata and, increasingly, enriched protocol data continuously, learns what each device, segment, and user ordinarily does, and surfaces behaviour that departs from that model. The approach catches what signatures cannot — a legitimate administrative tool being used by the wrong person, a server that has started talking to an address it has never contacted, data leaving through a channel that is technically permitted.
Three data sources are typically combined. Flow records give the who, when, and how much at low cost. Protocol metadata from a sensor such as Zeek adds structure: DNS queries and answers, TLS handshake details including the certificate and the JA3 or JA4 client fingerprint, HTTP headers where visible, SMB and Kerberos activity. Selective packet capture provides full detail for the conversations that warrant it.
From that the platform builds profiles: which ports a host normally uses, the volume and direction of its traffic by time of day, the set of peers it talks to, the services it offers. Peer grouping matters as much as individual baselining — a finance workstation behaving like a domain controller is interesting precisely because its peers do not behave that way.
Most traffic is encrypted, and inspection of payloads is largely over. Traffic analysis is less affected than deep packet inspection because it was never primarily about content. Timing, sizes, direction, and connection patterns survive encryption. TLS handshake metadata remains partially visible, and client fingerprinting identifies the software originating a connection even when the content is opaque — a Python or Go client fingerprint from a finance workstation is worth investigating whatever it is carrying.
The caveat is honest: encrypted traffic analysis produces probabilistic signals, not proof. It tells you where to look, and the confirmation usually comes from the endpoint.
Sensor placement determines what you can see. The internet edge catches command-and-control and exfiltration. Internal segment boundaries catch lateral movement, which is where most organisations have no visibility at all. Data centre east-west traffic catches server-to-server abuse. Cloud environments need their own approach using VPC flow logs and mirrored traffic.
Use a network tap rather than a SPAN port wherever packet-level data matters, since SPAN drops frames under load exactly when an incident is generating load. Expect a baselining period of several weeks, and expect the first month of alerts to be dominated by legitimate oddities — the backup job, the vulnerability scanner, the monitoring system that touches every host.
Tooling spans open source and commercial. Zeek with Suricata and an Elasticsearch stack, Security Onion as a packaged distribution, or a commercial NDR platform. The distinction between NTA and NDR is mostly that NDR adds response actions and case management.
Traffic analysis is the complement to endpoint detection, not a substitute. EDR sees process lineage and what ran; traffic analysis sees everything with a network interface, including devices no agent can be installed on — OT controllers, medical equipment, cameras, printers, and unmanaged contractor laptops. In environments where agent coverage is structurally incomplete, it is the only detection available.
It also produces the data you need afterwards. When an incident is declared, the history of which hosts talked to which destinations is what scopes it. Our SOC Maturation Services cover sensor placement, baselining, and turning anomaly output into alerts an analyst can act on.
Network traffic analysis describes the detection capability: baselining, anomaly detection, and protocol analysis. Network detection and response describes a product category that adds investigation workflow, case management, threat intelligence enrichment, and automated response such as blocking a host. The underlying analysis is the same; NDR packages it with the operational tooling around it.
Yes, with limits. Connection timing, packet sizes, direction, volumes, and peer relationships are unaffected by encryption, and TLS handshake metadata including client fingerprints remains partially visible. This detects beaconing, exfiltration, and unusual client software without decryption. What it cannot do is confirm the content, so findings usually need endpoint or log evidence to close out.
Start at the internet edge for command-and-control and exfiltration, then add internal segment boundaries, which is where lateral movement appears and where most organisations are blind. Data centre east-west traffic comes next. Use network taps rather than SPAN ports where packet data matters, because SPAN ports drop frames under exactly the load conditions an incident creates.
In most estates, yes. EDR covers only devices that can run an agent, which excludes OT controllers, medical devices, printers, cameras, network equipment, and unmanaged contractor machines. Traffic analysis sees everything with a network interface. It also retains the conversation history that lets you scope an incident weeks after the fact, which endpoint telemetry rarely does.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.