All modules
Available · Traffic

NETiDENT iFlow

Network Traffic Flow Analytics

Network Traffic Flow Analytics

app.netident.io/iflow
Traffic Flow Analytics
+8%
Total flows
4.2M
+12%
Throughput
18.4G
+41
Unique hosts
3,914
+2
Anomalies
5
Traffic by applicationlast 60 min
Web VoIP Bulk
Peak 5-min
22.1 Gbps
12% vs 1h
Protocol mix
4.2M
flows
HTTPS44%
RTP / VoIP22%
SMB16%
DNS10%
Other8%
Top talkers
app-prod-012.8 TB
db-cluster-a2.2 TB
media-edge-31.7 TB
backup-svc1.2 TB
Top conversationsby volume
10.20.4.1110.30.9.5HTTPS412 GB
10.20.4.27172.16.0.9SMB318 GB
10.12.1.4010.0.0.4Backup287 GB
10.30.9.58.8.8.8RTP201 GB
10.20.4.1110.40.2.2HTTPS164 GB

Product mockup — representative of the IFLOW interface.

Overview

Deep visibility into traffic behavior and bandwidth usage — who is using the network, which applications, and where congestion occurs.

Key capabilities

  • Top talkers, conversations & protocols
  • NetFlow, sFlow, IPFIX, J-Flow
  • Anomaly & congestion detection
  • Capacity planning support

Security & Compliance

NETiDENT iFlow is engineered to the platform's shared security standard — a FIPS 140 validated cryptographic module, ISO 27001-aligned controls, and TLS enforced at nginx.

FIPS 140-2 / 3Validated module

FIPS-validated cryptographic module with a fail-closed security posture gate.

  • Password hashing: PBKDF2
  • Secrets at rest: AES-256-GCM
  • Posture gate: Fail-closed
  • Validated module: GoFIPS 140 · fips140=on
ISO/IEC 27001Compliant

Information-security controls: audit logging, RBAC, encryption at rest, session handling.

  • Audit log: Append-only, role-protected
  • RBAC: Granular permissions
  • Encryption at rest: AES-256-GCM (Vault Transit)
  • Token lifecycle: Expiry + refresh
TLS 1.2 / 1.3Compliant

Encrypted transport terminated at nginx, with HSTS, secure headers, and enforced HTTPS.

  • TLS termination: nginx · TLS 1.2 / 1.3
  • HSTS + secure headers: Enabled
  • HTTPS enforcement: Enforced

Reflects implemented security controls and cryptographic posture from internal audit. Validated-module status applies where a FIPS-validated runtime is deployed.

See NETiDENT iFlow in your network

Request a tailored walkthrough and see how NETiDENT iFlow fits your operations.