Skip to main content
Applies to BloodHound Enterprise only The Findings Table is an alternate view on the Attack Paths page. Use it to review many at once, compare finding state across environments and zones, and triage high-volume result sets faster.
A view of the Attack Paths page that shows the table view
Each row in the table represents a single finding. The table displays the following columns:
Some findings, typically called list-based findings, do not have a source principal.

Use cases

Use the Findings Table to focus an investigation on a set of findings:
  • Triage findings at scale: Review a dense list of Attack Path findings and sort by Risk, date, status, or contextual columns. When Findings Prioritization is disabled, sort by severity instead.
  • Focus an investigation: Filter by Attack Path, object, severity, platform, environment, zone, and status to move from a broad result set to a smaller set that matches your investigation goal.
  • Compare scope across environments or zones: Select multiple environments or zones and review the matching findings together.
  • Review finding state and recency: Use Status, First Seen, and Last Seen to understand whether findings are open, accepted, remediated, deprecated, or orphaned, and when BloodHound Enterprise last updated them.
  • Investigate or remediate a finding: Select a finding to open it in Explore or review its remediation plan.
  • Preserve table context: Use the page URL to return to or share the same view, filters, and sort order.

Prerequisites

Before you can use the Findings Table, you must have the following:
  • BloodHound Enterprise with the Findings Table Early Access feature enabled on the Early Access Features page.
  • Access to the environments you want to analyze.
    This feature is available through Early Access. Enable Findings Table on the Administration > Early Access Features page to access it.
    If Environment Targeted Access Control (ETAC) is enabled on your tenant, it can limit which findings and environments appear for your account. Two users can see different rows for the same filters depending on their access.

Identify new findings

To quickly identify new findings, look for a purple New badge in the First Seen column of the Findings Table. The table displays the badge when a finding’s First Seen timestamp is within the past 24 hours.
The New badge in the Findings Table
The badge replaces the timestamp for the duration of that window. After 24 hours, the table displays the formatted First Seen date again.
The New state is calculated from the First Seen timestamp and is not provided by the API. A finding recreated after it was archived can display both New and Regression.

Take action on a finding

Select a finding to open an action menu and continue your investigation or remediation workflow.
1

Select a finding

Click a row to highlight it and display the action menu at the bottom of the table.
The Attack Paths table view with the action menu open
To clear the selection, click the same row again or click outside the table.
2

Choose an action

Select one of the following actions:
  • Remediation Plan: Opens the Remediation page filtered to the selected finding, environment, and privilege zone.
  • Explore: Opens the finding in Explore.
    • Relationship-based findings open in Pathfinding with the path between the source and target principals.
    • List-based findings open in Search.
  • Copy: Opens a submenu with Copy Source and Copy Target options to copy a principal’s name to your clipboard.

Filter findings

Use filters to narrow the result set: The filters support multi-select. For Objects, search by an object’s name or identifier, then select it from the results. Selecting All Objects removes the object filter.
Your filter and view selections are captured in the page URL. You can bookmark or share a link to return to the same table view.

Sort findings

You can sort by each visible table column and resize column width. Sorting reorders the full result set for the current filters. For example:
  • When Findings Prioritization is enabled, the table sorts by Risk by default, with the highest-priority findings first. The table uses zone and first-seen time as secondary sort fields.
  • Sort by First Seen to distinguish newer findings from findings that have persisted across analysis runs.
  • Sort by Last Seen to review the most recently updated findings for the current filters.

Export findings

Export the findings that match the current filters and sort order to a CSV file.
The export includes all matching findings, not only the rows currently loaded in the table.
1

Configure the table

Apply filters and sorting to define the findings you want to export.
2

Download the findings

Select the download icon next to the findings count.BloodHound saves the file as findings_YYYY-MM-DD.csv.
When Findings Prioritization is enabled, the file also includes the prioritization score and rank.
The export supports a maximum of 200,000 findings. If the current result set exceeds this limit, refine the results with filters before downloading. The download icon is unavailable when no findings match, while the result count is loading, or when the table cannot load its results.

Prioritize findings

Findings Prioritization helps you decide where to start when many findings compete for attention. It supplements severity with additional risk signals and provides a ranked starting queue for investigation and remediation.
This feature is available through Early Access. Enable Findings Prioritization on the Administration > Early Access Features page to access it.
When enabled, a Risk column replaces the Severity column in the table and uses severity-specific colors. A lower rank indicates a higher-priority finding. Use Findings Prioritization as guidance for triage and remediation. It does not replace severity or your organization’s knowledge of business context, compensating controls, and remediation effort. Once enabled, BloodHound Enterprise calculates a prioritization score for each finding during the next analysis run.
BloodHound Enterprise requests an analysis run when you enable the feature. Wait for analysis to complete before you use the new ranks.

How prioritization works

BloodHound Enterprise calculates a prioritization score during analysis, then converts that score into a ranked order using competition ranking. Findings with the same score receive the same rank, and the next rank skips the positions occupied by the tie. For example, if two findings tie for second place, the ranks are 1, 2, 2, 4; not 1, 2, 2, 3. A higher-ranked finding represents a stronger combination of the following factors present in the enterprise’s graph data: BloodHound calculates proximity during analysis when Findings Prioritization is enabled. It uses an analysis-generated Zone node for Tier Zero to calculate this distance. The table displays the resulting rank. A target already in Tier Zero receives the strongest proximity signal.

Rank and operational context

A finding can rank above another finding with the same—or even higher—severity when its combined exposure, impact, starting-object breadth, and proximity to Tier Zero indicate a larger remediation opportunity. Use the rank to create a starting queue, then apply operational context before you act, such as:
  • Business importance of affected assets
  • Existing compensating controls
  • Ownership and change windows
  • Remediation effort and potential disruption
  • Current investigations or accepted risk
The color of the rank in the Risk column indicates the finding’s severity. Findings Prioritization supplements severity; it does not redefine it.

When rank changes

BloodHound recalculates prioritization during analysis. The rank does not update dynamically between analysis runs. A finding’s rank can change after analysis when graph data, exposure, impact, starting objects, proximity to Tier Zero, or the set of open and accepted findings changes. Review the latest analysis before using a rank to plan remediation.
If BloodHound has not calculated a rank for a finding, the Risk column displays -. For example, archived findings do not have a rank.

Finding status lifecycle

A finding moves through a lifecycle as BloodHound Enterprise detects it, as you act on it, and as your environment changes. The Status column reflects where a finding is in that lifecycle. The diagram separates active findings from system-archived outcomes.

Status definitions

The following table describes the stored value and meaning of each finding status, and whether the status marks a finding as archived.
Open findings use normal emphasis, while accepted and archived findings are dimmed so you can focus on findings that need attention without checking the Status column for every row.

User-driven transitions

You control the transition between Open and Accepted:
  • Open to Accepted: Accept the finding and set an acceptance duration. BloodHound records an acceptance expiration for the finding. For steps, see Risk Acceptance.
  • Accepted to Open: Remove the acceptance manually, or wait for the acceptance period to expire. In both cases, the finding returns to Open.

System-driven transitions

BloodHound sets the archived statuses automatically during analysis. You cannot set these statuses manually:
  • Remediated: A subsequent analysis run no longer detects the Attack Path or vulnerable principal. Use this status to confirm that a risk was actually removed.
  • Orphaned: The environment associated with the finding (such as an Active Directory domain or Azure tenant) is archived or removed and is no longer collected.
  • Deprecated: The finding type is removed from (or deprecated in) the current schema, for example when an OpenGraph extension no longer defines it.
Remediated, Orphaned, and Deprecated are terminal, archived states. When BloodHound archives a finding, it records an archive time and updates the finding’s last-updated time.First Seen reflects when the finding was first created, and Last Seen reflects the most recent update, including a status change. Open and Accepted findings are not archived and continue to count toward your posture.