NetFlow / IPFIX / sFlow

In telecommunications, NetFlow, IPFIX, and sFlow are flow-export protocols that summarize traffic into records (5-tuple, byte and packet counts, timing) for monitoring and security analytics. Operators use them at scale across IP backbones, IPX, and mobile data networks because full packet capture would be prohibitively expensive.

Categories: SignalingRoaming and InterconnectThreats and Attacks

NetFlow / IPFIX / sFlow in context

Signaling protocols carry the control-plane instructions that set up calls, register subscribers, hand over sessions and route SMS. SS7, Diameter, GTP-C and SIP are the four dominant families, and interconnect exposure of any of them is treated by GSMA FS.11 / FS.19 / FS.20 as a top-tier telecom risk.

Roaming and interconnect are where two operators, often with an IPX or GRX carrier in between, exchange signaling and user-plane traffic. Trust boundaries here are the primary attack surface for location tracking, SMS interception and fraud, which is why GSMA now mandates SEPP with PRINS on 5G interconnect.

To place NetFlow / IPFIX / sFlow in the wider telecom-security picture, review ISUP, Firewall, GTP Firewall, FASG, Monitoring and Roaming Security Architecture.

Related terms

Related topic hubs

  • Roaming Security IPX/GRX interconnect risk, home-routed vs local-breakout, SEPP.
  • SS7 Security SS7/MAP/CAP/SCCP attacks and defenses across 2G/3G interconnect.
  • Diameter Security 4G/LTE Diameter threats across IPX/roaming and DEA defenses.
  • Diameter Attacks S6a IDR/PUR/CLR abuse, subscriber tracking, LTE signaling attacks.

More from the TelcoSec Glossary

Browse the full TelcoSec Glossary, the Ultimate Guide to Mobile Network Security, or the P1 Arsenal of telecom-security tools.