Skip to main content

Creating a Mitigation Graph

Learn how to create a mitigation graph that maps attack routes to your business assets.

Updated over 5 months ago

Overview

This article explains how to create a mitigation graph in Hyver — a powerful visualization that maps how attackers could reach your business assets through a series of vulnerabilities. You’ll see how each route is built and how it represents real risks based on actual penetration data.

This is your starting point for building an actionable view of your organization’s exposure.


What the Mitigation Graph Shows

The mitigation graph illustrates all known attack routes — potential paths an attacker might take to reach your organization’s critical business assets:

Each route:

  • Starts from a threat source (left side)

  • Passes through positions (representing assets or vulnerabilities)

  • Ends at one or more business assets (right side)

Attackers typically move step-by-step, gaining control over intermediate assets (positions) until they reach their target. These routes are based on actual red team activity or verified vulnerabilities uncovered in your environment.


How the Graph Is Built

The graph is composed of edges (lines) that connect positions:

  • Each edge represents a finding — a confirmed vulnerability or security issue that enables an attacker to move forward.

  • As attackers move from position to position, each edge opens up a new opportunity for access.

  • Some attack routes connect directly to a business asset; most involve several intermediate steps.

This layered structure helps you understand both the complexity and feasibility of an attack path.


Wrap-up / Next Steps

Creating a mitigation graph is the first step in turning security findings into a visual strategy for risk reduction. Once the graph is built, you can use it to explore, filter, highlight, and plan targeted mitigation actions.

If you're ready to build your first graph, make sure you have the right permissions and follow the recommended creation workflow.

Did this answer your question?