Exposure Validation Finder

Attack path analysis

Attack path analysis maps how vulnerabilities, misconfigurations and identity permissions connect into routes toward critical assets. Some tools test those routes; others model them in a graph without touching production.

What it proves

That a route exists from one foothold to a named asset, and which single fix breaks the most routes. Good tools rank "choke points": one misconfigured group policy may sit on hundreds of paths.

There are two methods. Executed path validation runs the steps, like SafeBreach Propagate or the attack path modules of automated pentesting tools. Modelled analysis builds a graph from configuration data and computes reachability, which is how XM Cyber describes its approach: it validates attack paths in a modelled environment rather than running attacks.

What it does not prove

A modelled path is a prediction. It assumes the controls along the route behave as configured. If the EDR would have stopped step three, the model may not know. An executed path is proof, but only for the routes the tool tried in the window it ran.

How it differs from its neighbours

Automated pentesting executes paths and often finds them as it goes. Exposure management platforms use attack paths as one input to rank everything else. BAS rarely builds paths at all; it tests techniques one by one.

Who buys it

Identity and cloud security teams, and vulnerability management leads who are drowning in findings and need a reason to fix one thing first. It suits estates where Active Directory and cloud permissions are the main risk.

Vendors that fit

Listed alphabetically: documented first, then partial claims. The note under each name is a summary of what the vendor's own pages claim, as read on 3 November 2026.

Documented (7)

Partial (1)

The pilot worksheet for attack path analysis