Prerequisites
Before you begin, ensure that the following prerequisites are met:| Prerequisite | Description |
|---|---|
| Ensure graph database is PostgreSQL | For best performance, BloodHound requires PostgreSQL as the graph database rather than Neo4j |
| Configure the collector | Configure the OpenHound collector to gather data from your JAMF Pro tenant |
Register the Extension
The Jamf extension includes a schema that tells BloodHound how to model and analyze data from your JAMF Pro tenant. You must register the extension before you upload data generated by the JamfHound collector. On the OpenGraph Management page, upload the Jamf schema file (bhe-jamfhound-extension.json).
Import Cypher Queries
The Jamf collector provides custom Cypher queries to help you identify attack paths and misconfigurations in your JAMF Pro tenant. These queries are included in thecustom-queries directory of the Jamf extension.
To use these queries, you must first import the custom-queries/*.json files into BloodHound. You can then run the queries on the Explore page.
Cypher queries that reference node or edge kinds not present in the database will fail without the extension schema (for example:
failed to translate kinds: unable to map kinds: Okta_ApiServiceIntegration). Community Edition users can work around this by removing the unrecognized node and edge kinds from the queries until the extension schema becomes available for BloodHound Community Edition.Next Steps
- Explore the JamfHound node types and edge types in the schema reference
- Try the JamfHound Cypher queries on the Explore page
- Learn about JAMF Pro attack paths and what to look for
- Use JamfHound’s specialized queries to create or update Cypher-based Privilege Zone rules
- Join the
#jamfchannel on the BloodHound Community Slack for questions and discussion