Formal Network Verification

Examine routing behaviour, traffic paths and access-control effects on a model before changes reach the production network.

Pins and strings linking diagrams on a board — modelling paths and dependencies before a change

Verification before change

Network behaviour can be examined before configuration changes are applied in production.

Formal network verification builds a model from device configurations and uses it to analyse routing, traffic flow and the effect of access-control policy.

Pankkih helps identify the likely impact of a change before it is carried out on the live network. Practical network architecture and operations are covered on Network; the broader service description is on Services.

What can be checked?

Practical example

Before a routing or firewall change, you can check whether a branch site still reaches data-centre services — and whether the same change would unintentionally allow traffic between otherwise isolated segments.

Comparing the current and proposed configurations highlights differences in reachability and in what traffic is permitted.

Technology

Batfish is an open-source network analysis and validation tool. It builds a model from device configurations and can be used to examine routing, traffic reachability, filtering rules and the effect of proposed changes.

Batfish supports several vendors, including Cisco, Juniper and Fortinet. Feature and syntax support vary by vendor and software release. MikroTik RouterOS should not be treated as fully supported. Devices outside tool support may need other analysis, model adaptation or a narrower scope.

Our contribution is the engineering around the tool: selecting which devices and policies to model, turning requirements into checks, interpreting the output and converting findings into concrete configuration changes and a clear report.

What you get

Discuss network validation. Related: Network, Services, Expertise, Solutions. Public routing view: Looking Glass.