Skip to content

BloodHound

BloodHound is an open source toolset to collect and analyze relational data within an Active Directory and/or Azure environment. BloodHound uses graph theory to reveal hidden and often unintended relationships within these environments to allow Attackers and Defenders to identify highly complex attack paths that would otherwise be impossible to quickly identify.

BloodHound has become an industry-standard tool for both red teams and blue teams to attack and defend Active Directory environments. For details on how to use BloodHound, see the SpecterOps/BloodHound documentation.

Compatibility note

As of November 2026, NodeZero supports BloodHound Community Edition (CE) v9.7+. NodeZero provides its BloodHound data as a PostgreSQL dump file.

Installing and Setting Up BloodHound

For a standard BloodHound CE installation, see BloodHound's Community Edition Quickstart.

To load NodeZero's BloodHound data, install BloodHound CE with Docker Compose as described in Using a NodeZero Pentest's BloodHound Data. This method lets you switch BloodHound to its PostgreSQL graph driver and restore the dump before BloodHound starts.

You need:

  • Docker with Docker Compose v2.
  • At least 8 GB RAM, 4 CPU cores, and 10 GB of free disk space. Large environments need more – see BloodHound's quickstart for sizing guidance.

How Does NodeZero Use BloodHound?

After NodeZero discovers and verifies a domain user credential, it uses a BloodHound data collector to gather information on the Active Directory or Entra environment. NodeZero stores this data in a PostgreSQL-backed BloodHound graph in our ephemeral architecture during the life of the pentest, and uses it to identify complex attack paths that might lead to compromising the domain or Entra ID tenant.

After the pentest finishes, the BloodHound data is backed up. Horizon3 customers who wish to use NodeZero's BloodHound collections to inform their own red/blue/purple team operations can request the data from a pentest.

Obtaining NodeZero's BloodHound Data

The ability to download NodeZero's collected BloodHound data is a paid feature, unavailable on trials. If you would like to request access to this feature, contact Horizon3 Customer Success.

NodeZero provides the data as a PostgreSQL dump file.

Using a NodeZero Pentest's BloodHound Data

Load the PostgreSQL dump into the database that BloodHound CE uses, then start BloodHound with its PostgreSQL graph driver enabled. Run these commands in an empty working directory.

  1. Download the BloodHound CE Docker Compose file.

    curl -L https://raw.githubusercontent.com/SpecterOps/BloodHound/v9.7.1/examples/docker-compose/docker-compose.yml -o docker-compose.yml
    
  2. Set BloodHound to use the PostgreSQL graph driver, pin the BloodHound image to a supported version, and have BloodHound create a new admin account on startup.

    export GRAPH_DRIVER=pg
    export BLOODHOUND_TAG=9.7.1
    export bhe_recreate_default_admin=true
    

    The NodeZero dump includes the user accounts from the pentest's BloodHound instance, so BloodHound doesn't create an admin account with an initial password on its own. The bhe_recreate_default_admin replaces that admin account with a new one that you can log into.

    To keep these settings across terminal sessions, instead add GRAPH_DRIVER=pg, BLOODHOUND_TAG=9.7.1, and bhe_recreate_default_admin=true to an .env file in the same directory.

  3. Start only the PostgreSQL database, and wait for it to be ready.

    docker compose up -d --wait app-db
    
  4. Restore the NodeZero dump into the bloodhound database, replacing <DUMP_FILE_PATH> with the path to the file you downloaded.

    docker compose exec -T app-db pg_restore -U bloodhound -d bloodhound --clean --if-exists --no-owner < <DUMP_FILE_PATH>
    
  5. Start BloodHound.

    docker compose up -d
    
  6. Open http://localhost:8080/ui/login in a browser and log in as admin. To find the initial password, run:

    docker compose logs bloodhound | grep "Initial Password"
    

    Reset the password when prompted.

  7. Turn off bhe_recreate_default_admin and restart BloodHound. If you leave it on, BloodHound replaces the admin account and its password every time it starts.

    unset bhe_recreate_default_admin
    docker compose up -d
    

    If you used an .env file, remove the bhe_recreate_default_admin=true line instead of running unset.

Securing your BloodHound instance

The default Docker Compose file makes BloodHound available on 127.0.0.1 only, and uses default PostgreSQL credentials. Change the credentials before you make the instance reachable from other hosts. The Docker Compose file also starts a Neo4j container, which BloodHound doesn't use with the PostgreSQL graph driver. To remove it, see BloodHound's Custom Installation guide.