data-ingestion

Automate SharpHound and AzureHound data ingestion into BloodHound Enterprise deployments.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill data-ingestion-dreadnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-ingestion
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/bloodhound-enterprise/skills/data-ingestion
Command: npx skills add https://github.com/dreadnode/capabilities --skill data-ingestion-dreadnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stale or incomplete SharpHound/AzureHound collection data leads to inaccurate, outdated security findings in BloodHound Enterprise, and manual ingestion is prone to errors like file format mismatches, partial uploads, and processing backlogs that delay analysis.

Core Features & Use Cases

  • End-to-End Ingest Guidance: Walks you through validating collection files, managing upload jobs, monitoring processing, and verifying graph updates to ensure data is loaded correctly.
  • Error Handling & Guardrails: Provides clear steps to handle failed uploads, stuck processing jobs, and partial collection runs to avoid corrupting the BHE graph state.
  • Use Case: After completing a new Active Directory assessment with SharpHound, use this skill to push the collection output to BloodHound Enterprise and confirm the graph is updated with the latest asset and relationship data before running attack path analysis.

Quick Start

Use the data-ingestion skill to upload the SharpHound collection zip files from your latest Active Directory assessment to your BloodHound Enterprise deployment and confirm the graph is updated with the new data.

Frequently Asked Questions about data-ingestion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload SharpHound collection data to BloodHound Enterprise?

Automating BloodHound Enterprise data ingestion involves validating collection files, managing upload jobs, monitoring processing pipelines, and verifying graph updates without manual API interaction. This ensures the graph state accurately reflects the latest Active Directory security assessment data.

What happens if AzureHound collection uploads fail or get stuck during processing?

If AzureHound collection uploads fail or processing jobs get stuck, you must handle the errors to avoid corrupting the BloodHound Enterprise graph state. Proper error handling addresses partial collection runs, file format mismatches, and processing backlogs to prevent delayed or inaccurate security analysis.

How do I validate Active Directory collection files before pushing them to BloodHound?

Validating Active Directory collection files involves checking the SharpHound and AzureHound output formats before managing upload jobs. This validation step is crucial because file format mismatches and partial uploads can lead to processing backlogs and corrupt the security analysis graph state.

Can I automate BloodHound Enterprise graph updates after an Active Directory assessment?

Yes, you can automate BloodHound Enterprise graph updates by ingesting SharpHound and AzureHound collection output after an Active Directory assessment. This automation manages upload jobs and monitors processing pipelines to refresh stale deployment posture data for attack path analysis.

Why are my BloodHound Enterprise security findings outdated after a SharpHound collection run?

BloodHound Enterprise security findings become outdated when stale or incomplete SharpHound collection data is not properly ingested. Manual ingestion is prone to errors like partial uploads and processing backlogs, which delay the graph state updates required for accurate attack path analysis.