BloodHound Glossary

Learn the terminology used in BloodHound software and documentation.

Attack Path

A chain of abusable privileges and user behaviors that create direct and indirect connections between principals. In BloodHound, Attack Paths are visualized in the graph by nodes and edges. Learn more in What is Attack Path Management.

• Identity-based Attack Path—An Attack Path is based on identity or an already authenticated principal. BloodHound’s main goal is to help visualize and manage Attack Paths.

Attack Path Management (APM)

The process of identifying, analyzing, and managing the Attack Paths that an adversary might exploit to reach high-value objects or compromise the network’s security. BloodHound helps visualize and manage Attack Paths through Attack Path Management.

Choke Point

A privilege or user behavior (called edges) that, like the driveway to a house, connects the rest of the environment through an object or collection of objects (called nodes). For example, any Edge into the collection of Tier Zero nodes is a Tier Zero Choke Point. This is a privilege or user behavior the adversary must abuse to compromise a Tier Zero object.

Choke points are significant points of control and defense in the network security architecture. They represent the optimal location to block the largest number of Attack Paths. BloodHound Enterprise calculates exposure for all choke points.

Collector

A collector, collector client, or data collector is software that collects Attack Path-related data from a directory. For example, SharpHound and AzureHound.

Cypher

Cypher is a graph query language used to interact with BloodHound’s database. It’s similar to SQL for traditional databases. To use it, see Searching with Cypher.

Directory

A service that stores identities and their attributes, such as Active Directory (AD) and Entra ID (formerly Azure Active Directory). BloodHound collects data from these directories to build its graph of nodes and edges.

Edge

An edge is part of the graph construct and represents a relationship between two nodes, indicating some form of interaction. See About BloodHound Edges.

Enterprise Access Model (EAM)

A security framework developed by Microsoft that defines a privileged access strategy[1] with the ultimate goal of preventing privilege escalation through identity-based Attack Paths. In most cases, EAM supersedes and replaces tiering.

Escalation (ESC)

The process of exploiting vulnerabilities or misconfigurations to gain higher privileges or access levels than initially granted. In BloodHound, escalation encompasses various techniques an attacker can use to move from lower-privileged principals to higher-privileged ones or sensitive objects.

BloodHound detects and visualizes escalations as Attack Paths to help organizations identify and remediate privilege escalation risks.

Exposure

A risk measurement that quantifies the extent to which principals in a directory have Attack Paths to Tier Zero objects. It encompasses both principals with one-step paths (UserA -[ForceChangePassword]-> TierZero), and multi-step paths (UserA -[ForceChangePassword]-> UserB -[GenericAll]-> TierZero). Exposure is measured in two ways:

• Exposure count—The number of principals with a Tier Zero Attack Path.

• Exposure percentage—The percentage of principals in the directory with a Tier Zero Attack Path.

BloodHound Enterprise calculates exposure for all choke points.

Finding

A specific instance of a vulnerability that an attacker could abuse to gain access to, and eventually take control of, a network. Each finding can be categorized as a specific Attack Path type.

There are two types of findings in BloodHound:

• List-based finding—A finding for a specific principal where the vulnerability is related to the principal itself, such as a misconfiguration. Because of this nature, list-based findings do not necessarily have an exposure metric, but they will have an impact metric.

• Relationship-based finding—A finding for a pair of principals—a target that is privileged (such as belonging to Tier Zero) and a source/origin that is not—that can be compromised by one or more connections between said principals. Each relationship-based finding may be composed of one or many individual Attack Paths.

  A relationship-based finding can have an exposure metric (the exposure risk of the source/origin principal being compromised) and an impact metric (the impact risk of the target principal being compromised).

FOSS

Stands for Free and Open Source Software. For example, “BloodHound CE is a FOSS project.”

Graph

The graph database used by BloodHound. It stores the relationships between nodes and edges and feeds BloodHound functionality like visualizing and understanding complex Attack Paths and environment risks.

Impact

A risk measurement that quantifies how much control of your environment an affected asset has. Specifically:

• Impact count—The number of principals/objects that could be compromised through an Attack Path.

• Impact percentage—The percentage of the environment that could be impacted by a specific identity vulnerability.

Impact is closely related to exposure, which measures the percentage of principals with a Tier Zero Attack Path. Together, these metrics help organizations prioritize remediation by understanding which Attack Paths pose the greatest risk.

Kind

The schema-level classification or label applied to nodes in the graph, analogous to an entity type, not an individual node instance. Examples of node kinds include users, computers, groups, and domains. See About BloodHound Nodes.

Node

A node is part of the graph construct and represents an entity in the environment as stored in the BloodHound graph. Nodes typically correspond to objects and can represent a wide variety of entities from different data sources, including directory objects (users, computers, groups, domains, trusts) and other assets discovered through integrations like OpenGraph. Two nodes can be connected by an edge. See About BloodHound Nodes.

Object

An entity encompassing both directory-level entities from Active Directory and Entra ID directories and other assets discovered through data integrations like OpenGraph. Examples include users, groups, computers, organizational units (OUs), domains, trusts, and cloud resources.

Objects are synonymous with nodes and represent distinct elements contributing to the network’s overall structure and security posture. An object can also be referred to as an “asset”.

Principal

A type of object that can authenticate and be assigned permissions within the environment, also known as a security principal.

Examples of principals include users and computers in Active Directory and users, virtual machines, and service principal objects in Entra ID and Azure. Principals are typically represented as nodes in the graph and play a central role in identity Attack Path mechanisms.

Privilege

A level of access or permission a principal has on a specific object within the infrastructure.

Privileges are generally more granular permissions that define how or to what extent a user or system can interact with specific resources, like reading, writing, or executing a file. While similar to rights, privileges focus on resource-specific actions and are a subset of broader rights.

Remediation

The process of fixing or mitigating security risks identified during the analysis of Attack Paths with BloodHound.

Right

Rights are broad permissions granted to a user, group, or system to perform specific actions at a system or role level, such as logging in or accessing a network. They are sometimes used interchangeably with privileges but typically encompass higher-level abilities that define what someone can do across the system.

Tenant

Refers to a dedicated instance of BloodHound that contains its own data, configurations, and user access controls.

Tier Zero/High Value

The most critical and sensitive objects in the network, typically including domain controllers and other core infrastructure components. The term stems from tiering.

Tiering/Tier Model

The process of categorizing objects and privileges based on their criticality and importance to the organization. The term stems from Microsoft’s Active Directory tier model, which in most cases is superseded and replaced by the Enterprise Access Model. See Enterprise Access Model (EAM).