NetFlow and IPFIX

Flow export protocols (NetFlow, sFlow, IPFIX) summarize network conversations and send them to a collector. That data is a map of who talks to whom across the environment, valuable reconnaissance when harvested from an exposed collector, and the unauthenticated export path lets an attacker forge flow records to inject false traffic or mislead monitoring.

1 phút đọccập nhật 7 thg 10, 2026florianamette1 người đóng góp
Hỏi trợ lý của bạn (MCP)Sửa trên GitHub

Flow-export protocols, Cisco NetFlow, sFlow, and the IETF-standard IPFIX, have routers and switches summarize the conversations passing through them (source, destination, ports, protocol, byte and packet counts) and export those records to a collector over UDP. For an attacker the flow data is a ready-made map of the network's communication: who talks to whom, on which services, and how much, which is high-value reconnaissance obtained without touching the hosts. Harvesting that map from an exposed collector or its storage reveals the environment's structure and relationships. And because the export path is unauthenticated UDP, an attacker who can send to the collector forges flow records to inject false traffic, hide real flows, or mislead the capacity and security monitoring built on the data.

Subtopics#

References#