From source/destination IPs to path computation, path-traffic analysis, and firewall policy create/push — making “where should this policy land” computable, verifiable, and operable.
Talk about a similar project
Opening or tightening connectivity between two endpoints usually means manually tracing routes, guessing intermediate devices, then editing policies on multiple firewalls. Unclear paths, opaque traffic, and scattered rules lead to misses and misconfigs — and little time to validate inside a change window.
After the user enters source and destination IPs, the system computes an end-to-end traffic path from routing data, identifies key hops and traffic characteristics along that path, then generates and deploys firewall policies on the relevant devices. Path reports and dry-runs run before live push; steps stay auditable and replayable.
Policy changes moved from hand-chasing routes to path-driven policy orchestration: paths are visible, traffic along the path is analyzable, and firewall rules can land automatically — with clearer risk control and a steadier delivery cadence.
One place to submit and track policy changes driven by source/destination IPs. Search by request ID and follow statuses from submitted through review, approval, rejection, and deployed — so business and network/security teams share one timeline.
Hop-by-hop path and interfaces from source to destination, plus dry-run previews of intended firewall policies and conflicts. Intent is clear before live push, cutting trial-and-error in the change window.
Period totals for requests, success, in progress, and rejected — with outcome distribution to spot throughput and bottlenecks. Leaders see path analysis and policy automation health without digging through tickets.
Inventory of routers, switches, firewalls, and other managed devices — IP, type, access protocol, series, and health. Path computation and policy push run against a verifiable device baseline.
Aggregated routes across devices, searchable by prefix, receiving device, and type — with next hop, VRF/context, egress interface, and zone. Path computation and firewall policy orchestration rest on real forwarding data.