Skip to main content
Applies to BloodHound Enterprise and CE
Yes you can! You can find all the details here
Yes you can!You can remove generic data by using one of the following three (3) options:
  1. Cypher commands in the Explore UI
    • Requires enable_cypher_mutations: true in config. For more info click here
  2. Admin UI → Database Management page
    • The following checkboxes will be displayed
    • All Data
    • Active Directory Data
    • Azure Data
    • … X Data (there will be 0 or more checkboxes here that allow you to delete any data that had been ingested with a source_kind provided)
    • Sourceless Data (checking this box will delete all entities that do not have a kind that can be found in the source_kinds table. You can observe the source_kinds your BloodHound instance is currently aware of by calling GET api/v2/graphs/source_kinds.)
  3. API: Clear-Database
No, not yet.In the initial BloodHound 8.0 release, OpenGraph nodes and edges are not supported in the Search or Pathfinding tab, so the Cypher tab must be used to query the data manually.
Have you built a cool project using OpenGraph and want it featured here? Already got your project in the list and need to update something? Open a “Library Change” issue on the BloodHound Docs repo and we’ll get it added for you!Submissions from the community will have a icon next to them while those by SpecterOps employees will have a SpecterOps icon.
Slow ingestion speeds are commonly seen when using a Neo4j graph database and are typically resolved by switching to a PostgreSQL backend. For full, officially supported OpenGraph functionality, use a PostgreSQL backend (see Requirements).To switch to a PostgreSQL graph database, set "graph_driver": "pg" in your bloodhound.config.json file and restart the BloodHound services/containers. You will need to re-ingest any data into the new database.
⌘I