Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are NetFlow and IPFIX?

Flow records summarise who talked to whom, when, and how much. They cost a fraction of full packet capture and remain useful when everything on the wire is encrypted.

Illustration for the cybersecurity term NetFlow and IPFIX
Home / Blog / Cybersecurity Terms / What Are NetFlow and IPFIX?
17 November 2026

What Are NetFlow and IPFIX?

What Are NetFlow and IPFIX?

A flow record is a summary of a conversation: source and destination addresses, ports, protocol, the interface it crossed, start and end times, and the packet and byte counts. It contains no payload. Cisco introduced NetFlow in the 1990s as an accounting feature; the IETF standardised the idea as IP Flow Information Export in RFC 7011, published in 2013, which is essentially NetFlow version 9 with an open specification and extensible templates.

How the Data Is Produced

A router, switch, or firewall maintains a cache of active flows keyed on the traffic tuple. Counters increment as packets arrive. A flow is exported when it ends — a TCP FIN or RST — or when an inactive timeout elapses, typically fifteen seconds, or when an active timeout forces export of a long-running conversation, usually at sixty seconds or a few minutes. Records are sent to a collector over UDP.

The template mechanism in NetFlow v9 and IPFIX is what makes the format durable. Rather than a fixed record layout, the exporter periodically sends a template describing the fields it will use, then sends records matching it. That allows vendor extensions, application identifiers, URLs from deep packet inspection engines, and MAC addresses, all without a new protocol version.

Sampling matters enormously for security use. High-throughput platforms sample one packet in a thousand or more, which is fine for capacity planning and useless for detecting a low-volume beacon. Where you need security visibility, export unsampled flows from a device that can manage it, or use a dedicated flow generator fed by a tap.

NetFlow, IPFIX, and sFlow

NetFlow v9 / IPFIXsFlow
MethodStateful flow cache on the deviceStatistical packet sampling
CompletenessEvery flow, if unsampledSampled, always
Device costMemory and CPU for the cacheVery low
Security valueHighLimited; good for volumetrics

Version 5 of NetFlow still appears on older equipment. It is fixed-format, IPv4 only, and should be replaced where possible.

What Flow Data Detects

Because it records relationships rather than content, flow data stays useful when payloads are encrypted, which is now nearly all of them.

Retention, Storage, and Practicalities

The argument for flows over full packet capture is economic. Packet capture at ten gigabits per second consumes roughly a hundred terabytes a day; the corresponding flow data is a few gigabytes. That difference is what makes ninety days or a year of retention realistic, and long retention is exactly what incident investigation needs, given that intrusions are routinely discovered months after they began.

Practical notes. Export from the right places: the internet edge, between internal segments, and from cloud virtual networks, where AWS VPC Flow Logs, Azure NSG flow logs, and Google VPC Flow Logs provide the same data. Expect to see each conversation twice when two devices both export it, and deduplicate at the collector. Remember that NAT destroys attribution unless you also collect translation logs. And treat flow records as personal data under UK GDPR where they can be linked to an individual, with a stated retention period and access controls.

Open-source collectors including nfdump, ElastiFlow, and Akvorado handle collection and analysis; commercial NDR platforms add behavioural analytics on top. Our SOC Maturation Services include designing the telemetry set, of which flow data is usually the best value per pound.

FAQ – Frequently Asked Questions

Do Flow Records Contain Packet Contents?

No. A flow record holds metadata about a conversation: addresses, ports, protocol, timestamps, and counts. There is no payload, so you cannot recover the content of a file transfer or read an email from flow data. That limitation is also the strength, because the records remain meaningful when the traffic itself is encrypted and they are far smaller to store.

How Long Should I Retain Flow Data?

Ninety days is a reasonable minimum and twelve months is better, because intrusions are frequently discovered long after they started and flow history is what lets you scope them. Storage cost is modest compared with packet capture. Set the period formally, document it in your records of processing under UK GDPR, and apply access controls to the archive.

Is Sampled Flow Data Useful for Security?

Only partly. Sampling at one in a thousand is adequate for capacity planning and for spotting volumetric attacks, but it will miss low-volume command-and-control beacons and small exfiltration channels entirely. Where security visibility is the goal, export unsampled flows from a device with capacity to do so, or generate flows from a dedicated sensor on a tap.

Can I Get Flow Data From Cloud Environments?

Yes. AWS VPC Flow Logs, Azure NSG and virtual network flow logs, and Google Cloud VPC Flow Logs all produce equivalent records for traffic inside your cloud networks. The field sets differ slightly from IPFIX, and most analysis platforms normalise them. Enabling them is usually a small cost and one of the highest-value cloud telemetry sources available.

Related Terms

You May Be Interested In These

What Is Cyber Insurance?

Cybersecurity Terms

17 November 2026

What Is Cyber Insurance?

Read More
What Is Risk Assessment?

Cybersecurity Terms

17 November 2026

What Is Risk Assessment?

Read More
What Is Root and Jailbreak Detection?

Cybersecurity Terms

17 November 2026

What Is Root and Jailbreak Detection?

Read More