All modules
Available · Path Visibility

NETiDENT PathView

Network Path & Dependency Mapping

Network Path & Dependency Mapping

app.netident.io/pathview
Path & Dependency Mapping
+5
Monitored paths
312
-0.6ms
End-to-end RTT
11.8ms
+0.3%
Healthy paths
98.1%
+2
Degraded
6
End-to-end pathapp-prod-01 → customer
bottleneck · agg-sw-04
app-prod-01source0.2ms
core-rtr-01core1.4ms
agg-sw-04aggregation8.7ms
wan-edgeMPLS2.1ms
branch-rtrlast-mile3.0ms
customerservice
Service impactdownstream
Payments APIvia agg-sw-04 · +6.8ms14 svc
VoIP trunkjitter on MPLS hop3 svc
Branch VPNlast-mile flapping22 svc
Backup replrerouted via wan-rtr-075 svc
Recent path changes
app-prod-01 → customer3m
Hop added: agg-sw-04
db-cluster-a → dr-site27m
Rerouted core-rtr-02 → 01
voip-gw → pstn1h
MPLS label changed

Product mockup — representative of the PATHVIEW interface.

Overview

End-to-end visibility into network paths and service dependencies — from core to access, branch, last-mile, and customer service.

Key capabilities

  • End-to-end path visualization
  • Topology & dependency mapping
  • Service impact & downstream analysis
  • Path change detection

Security & Compliance

NETiDENT PathView 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 PathView in your network

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