Skip to content

Attack Path Analysis

Attack Path Analysis connects individual findings, identities, and resources into the chains an attacker could actually follow. Instead of a flat list of issues, you see how an adversary moves from an initial foothold toward a high-value target — and which single fix breaks the most chains.

BenefitCapabilityBusiness value
Real contextGraph-based path discoveryFix exploitable chains, not isolated alerts
Sharp prioritiesFeasibility and business-risk scoringEffort goes to the paths that matter
Choke pointsIdentifies steps shared by many pathsOne fix can break many attacks

RedCloud builds a graph of resources and identities and finds the routes between them, including a knowledge graph used for shortest-path reasoning. Each route is broken into discrete steps, mapped to MITRE ATT&CK tactics and techniques (see MITRE ATT&CK).

The engine models privilege-escalation steps and lateral movement across identities and services — for example, a service account that can be impersonated, then used to grant itself more access.

Some risks only emerge when several conditions line up (for example, a public resource plus an over-privileged identity plus a missing control). RedCloud detects these toxic combinations even when each individual finding looks benign.

Each path receives a score that reflects feasibility (how reachable and exploitable the steps are) and business risk (the value of what’s at the end). A realism scorer and blast-radius analysis sharpen the ranking so the most dangerous, most achievable paths surface first.

  1. Run a scan (a full profile gives the richest graph).
  2. Open Attack Analysis → Attack Paths (or Top Paths for the highest-scoring ones).
  3. Expand a path to see its steps, kill-chain stages, and MITRE mapping.
  4. Use the Path Narrative for a plain-language summary.
  5. Fix the shared choke-point steps first, then revalidate.
  • Prioritize steps that appear in many paths — they’re the highest-leverage fixes.
  • Pair path analysis with Blast Radius to understand worst-case impact.
  • Re-run after remediation to confirm the chain is broken.