Skip to content

Replace JAMFHound repo and fix mermaid diagram renders #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
so-lcain wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Replace JAMFHound repo and fix mermaid diagram renders #229

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6d6df95
Update JAMFHound_Internal repo to JamfHound external in reference lin…
so-lcain Mar 18, 2026
087a6d4
Merge branch 'main' into repo_update
JonasBK Mar 23, 2026
f0cded0
Merge branch 'main' into repo_update
JonasBK Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 37 additions & 37 deletions docs/opengraph/extensions/jamfhound/reference/edges/jamf_azmatchedemail.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,37 +1,37 @@
---
title: 'jamf_AZMatchedEmail'
description: 'Represents a cross-platform identity correlation where the JAMF principal''s email attribute matches an Azure AD account''s email.'
---
<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
## Edge Schema
- Source: [jamf_Account](/opengraph/extensions/jamfhound/reference/nodes/jamf_account), [jamf_DisabledAccount](/opengraph/extensions/jamfhound/reference/nodes/jamf_disabledaccount), [jamf_ComputerUser](/opengraph/extensions/jamfhound/reference/nodes/jamf_computeruser)
- Destination: [AZUser](/resources/nodes/az-user)
- Traversable: ❌
## General Information
The non-traversable `jamf_AZMatchedEmail` edge represents a cross-platform identity correlation created during post-processing. When the Jamf principal's email attribute matches an Azure AD account's email, this edge is created to link the identities across environments. This edge is generated by the `checkAzureUsers` utility rather than the main collection flow.
```mermaid
graph LR
A("jamf_Account
john.admin")
B("AzureAD_User
john.admin\@contoso.com")
C("jamf_ComputerUser
bob.smith")
D("AzureAD_User
bob.smith\@contoso.com")
E("jamf_DisabledAccount
bob.former")
F("AzureAD_User
bob\@former.localhost")
A -- jamf_AZMatchedEmail --> B
C -- jamf_AZMatchedEmail --> D
E -- jamf_AZMatchedEmail --> F
```
---
title: 'jamf_AZMatchedEmail'
description: 'Represents a cross-platform identity correlation where the JAMF principal''s email attribute matches an Azure AD account''s email.'
Copy link
Copy Markdown
Contributor

@jeff-matthews jeff-matthews Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the double apostrophes in "principal" and "account" expected?

Copy link
Copy Markdown
Contributor

@JonasBK JonasBK Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope.. Seems to be generated by my script somehow. I'll dig into it and get it fixed

---

<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>

## Edge Schema

- Source: [jamf_Account](/opengraph/extensions/jamfhound/reference/nodes/jamf_account), [jamf_DisabledAccount](/opengraph/extensions/jamfhound/reference/nodes/jamf_disabledaccount), [jamf_ComputerUser](/opengraph/extensions/jamfhound/reference/nodes/jamf_computeruser)
- Destination: [AZUser](/resources/nodes/az-user)
- Traversable: ❌

## General Information

The non-traversable `jamf_AZMatchedEmail` edge represents a cross-platform identity correlation created during post-processing. When the Jamf principal's email attribute matches an Azure AD account's email, this edge is created to link the identities across environments. This edge is generated by the `checkAzureUsers` utility rather than the main collection flow.


```mermaid
graph LR
A("jamf_Account
john.admin")
B("AzureAD_User
john.admin\@contoso.com")
C("jamf_ComputerUser
bob.smith")
D("AzureAD_User
bob.smith\@contoso.com")
E("jamf_DisabledAccount
bob.former")
F("AzureAD_User
bob\@former.localhost")

A -- jamf_AZMatchedEmail --> B
C -- jamf_AZMatchedEmail --> D
E -- jamf_AZMatchedEmail --> F
Comment thread
JonasBK marked this conversation as resolved.
```
60 changes: 30 additions & 30 deletions docs/opengraph/extensions/jamfhound/reference/edges/jamf_matchedemail.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,30 +1,30 @@
---
title: 'jamf_MatchedEmail'
description: 'Represents an identity correlation where the JAMF computer user''s email attribute matches the JAMF account''s email.'
---
<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
## Edge Schema
- Source: [jamf_ComputerUser](/opengraph/extensions/jamfhound/reference/nodes/jamf_computeruser)
- Destination: [jamf_Account](/opengraph/extensions/jamfhound/reference/nodes/jamf_account), [jamf_DisabledAccount](/opengraph/extensions/jamfhound/reference/nodes/jamf_disabledaccount)
- Traversable: ✅
## General Information
The traversable `jamf_MatchedEmail` edge represents an identity correlation where the Jamf computer user's email attribute matches the Jamf account's email, indicating they are likely the same person. This links physical device access to Jamf administrative privileges.
```mermaid
graph LR
A("jamf_ComputerUser
jsmith\@corp.com")
B("jamf_Account
jsmith\@corp.com")
C("jamf_ComputerUser
jdoe\@corp.com")
D("jamf_DisabledAccount
jdoe\@corp.com")
A -- jamf_MatchedEmail --> B
C -- jamf_MatchedEmail --> D
```
---
title: 'jamf_MatchedEmail'
description: 'Represents an identity correlation where the JAMF computer user''s email attribute matches the JAMF account''s email.'
Copy link
Copy Markdown
Contributor

@jeff-matthews jeff-matthews Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the double apostrophes in "user" and "account" expected?

---

<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>

## Edge Schema

- Source: [jamf_ComputerUser](/opengraph/extensions/jamfhound/reference/nodes/jamf_computeruser)
- Destination: [jamf_Account](/opengraph/extensions/jamfhound/reference/nodes/jamf_account), [jamf_DisabledAccount](/opengraph/extensions/jamfhound/reference/nodes/jamf_disabledaccount)
- Traversable: ✅

## General Information

The traversable `jamf_MatchedEmail` edge represents an identity correlation where the Jamf computer user's email attribute matches the Jamf account's email, indicating they are likely the same person. This links physical device access to Jamf administrative privileges.

```mermaid
graph LR
A("jamf_ComputerUser
jsmith\@corp.com")
B("jamf_Account
jsmith\@corp.com")
C("jamf_ComputerUser
jdoe\@corp.com")
D("jamf_DisabledAccount
jdoe\@corp.com")
A -- jamf_MatchedEmail --> B
C -- jamf_MatchedEmail --> D
```
8 changes: 4 additions & 4 deletions docs/opengraph/extensions/jamfhound/reference/privilege-zone-rules.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ icon: "gem"

<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
The following Cypher rules define the default Privilege Zone for the JamfHound extension.
Each rule is defined in a JSON file located in the [PrivilegeZoneRules](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/PrivilegeZoneRules) directory of the JamfHound repository.
Each rule is defined in a JSON file located in the [PrivilegeZoneRules](https://github.com/SpecterOps/JamfHound/tree/main/Src/PrivilegeZoneRules) directory of the JamfHound repository.

## Tenant

Expand All @@ -17,7 +17,7 @@ MATCH (n:jamf_Tenant)
RETURN n
```

This rule is defined in the [tenant.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/PrivilegeZoneRules/tenant.json) file.
This rule is defined in the [tenant.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/PrivilegeZoneRules/tenant.json) file.

## Tier Zero Principals

Expand All @@ -29,7 +29,7 @@ WHERE n.Tier = 0
RETURN n
```

This rule is defined in the [tier0-principals.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/PrivilegeZoneRules/tier0-principals.json) file.
This rule is defined in the [tier0-principals.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/PrivilegeZoneRules/tier0-principals.json) file.

## Tier One Principals

Expand All @@ -41,5 +41,5 @@ WHERE n.Tier = 1
RETURN n
```

This rule is defined in the [tier1-principals.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/PrivilegeZoneRules/tier1-principals.json) file.
This rule is defined in the [tier1-principals.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/PrivilegeZoneRules/tier1-principals.json) file.

40 changes: 20 additions & 20 deletions docs/opengraph/extensions/jamfhound/reference/queries.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ icon: code

<img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
The following custom Cypher queries can be imported into BloodHound to enhance visibility.
Each query is defined in a JSON file located in the [Queries](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries) directory of the JamfHound repository.
Each query is defined in a JSON file located in the [Queries](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries) directory of the JamfHound repository.
<Info>
This file is automatically generated from the [JSON query files](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries)
This file is automatically generated from the [JSON query files](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries)
that are bundled with the `JamfHound` collector.
</Info>

Expand All @@ -23,7 +23,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Account_Access_by_Name.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Account_Access_by_Name.json) file.
This query can be imported into BloodHound from the [Jamf_Account_Access_by_Name.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Account_Access_by_Name.json) file.

## Account to Account Attack Paths

Expand All @@ -35,7 +35,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Account_to_Account_Attack_Paths.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Account_to_Account_Attack_Paths.json) file.
This query can be imported into BloodHound from the [Jamf_Account_to_Account_Attack_Paths.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Account_to_Account_Attack_Paths.json) file.

## Account to Tenant Edges

Expand All @@ -47,7 +47,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Account_to_Tenant_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Account_to_Tenant_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_Account_to_Tenant_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Account_to_Tenant_Edges.json) file.

## All Account Paths

Expand All @@ -59,7 +59,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_All_Account_Paths.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_All_Account_Paths.json) file.
This query can be imported into BloodHound from the [Jamf_All_Account_Paths.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_All_Account_Paths.json) file.

## All Computers

Expand All @@ -70,7 +70,7 @@ MATCH p=(s:jamf_Computer)
RETURN p
```

This query can be imported into BloodHound from the [Jamf_All_Computers.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_All_Computers.json) file.
This query can be imported into BloodHound from the [Jamf_All_Computers.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_All_Computers.json) file.

## All Groups

Expand All @@ -81,7 +81,7 @@ MATCH p=(s:jamf_Group)
RETURN p
```

This query can be imported into BloodHound from the [Jamf_All_Groups.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_All_Groups.json) file.
This query can be imported into BloodHound from the [Jamf_All_Groups.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_All_Groups.json) file.

## All Nodes and Edges

Expand All @@ -94,7 +94,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_All_Nodes_and_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_All_Nodes_and_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_All_Nodes_and_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_All_Nodes_and_Edges.json) file.

## API Client Attack Paths to Tenant

Expand All @@ -107,7 +107,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_API_Client_Attack_Paths_to_Tenant.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_API_Client_Attack_Paths_to_Tenant.json) file.
This query can be imported into BloodHound from the [Jamf_API_Client_Attack_Paths_to_Tenant.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_API_Client_Attack_Paths_to_Tenant.json) file.

## API Client Immediate Edges

Expand All @@ -119,7 +119,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_API_Client_Immediate_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_API_Client_Immediate_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_API_Client_Immediate_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_API_Client_Immediate_Edges.json) file.

## Chained Targeted Filtering

Expand All @@ -146,7 +146,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Chained_Targeted_Filtering.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Chained_Targeted_Filtering.json) file.
This query can be imported into BloodHound from the [Jamf_Chained_Targeted_Filtering.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Chained_Targeted_Filtering.json) file.

## Expanded Tier 1 to Tier 0 Paths

Expand All @@ -160,7 +160,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Expanded_Tier_1_to_Tier_0_Paths.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Expanded_Tier_1_to_Tier_0_Paths.json) file.
This query can be imported into BloodHound from the [Jamf_Expanded_Tier_1_to_Tier_0_Paths.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Expanded_Tier_1_to_Tier_0_Paths.json) file.

## Group Administrators Filtered Relationships

Expand All @@ -176,7 +176,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Group_Administrators_Filtered_Relationships.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Group_Administrators_Filtered_Relationships.json) file.
This query can be imported into BloodHound from the [Jamf_Group_Administrators_Filtered_Relationships.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Group_Administrators_Filtered_Relationships.json) file.

## Group Administrators Targeted Edges

Expand All @@ -189,7 +189,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Group_Administrators_Targeted_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Group_Administrators_Targeted_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_Group_Administrators_Targeted_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Group_Administrators_Targeted_Edges.json) file.

## Group Edges to Accounts

Expand All @@ -202,7 +202,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Group_Edges_to_Accounts.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Group_Edges_to_Accounts.json) file.
This query can be imported into BloodHound from the [Jamf_Group_Edges_to_Accounts.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Group_Edges_to_Accounts.json) file.

## Matched Email Edges

Expand All @@ -214,7 +214,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Matched_Email_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Matched_Email_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_Matched_Email_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Matched_Email_Edges.json) file.

## Tier 1 to Tier 0 Attack Paths

Expand All @@ -230,7 +230,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Attack_Paths.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Attack_Paths.json) file.
This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Attack_Paths.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Attack_Paths.json) file.

## Tier 1 to Tier 0 Direct Edges

Expand All @@ -243,7 +243,7 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Direct_Edges.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Direct_Edges.json) file.
This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Direct_Edges.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Direct_Edges.json) file.

## Tier 1 to Tier 0 Without Contains

Expand All @@ -257,5 +257,5 @@ RETURN p
LIMIT 1000
```

This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Without_Contains.json](https://github.com/SpecterOps/JAMFHound_Internal/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Without_Contains.json) file.
This query can be imported into BloodHound from the [Jamf_Tier_1_to_Tier_0_Without_Contains.json](https://github.com/SpecterOps/JamfHound/tree/main/Src/Queries/Jamf_Tier_1_to_Tier_0_Without_Contains.json) file.

2 changes: 1 addition & 1 deletion docs/opengraph/extensions/jamfhound/reference/schema.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ icon: circle-nodes
**Source Kind:** jamf_Base

<Info>
This file is automatically generated from the [schema_enterprise.json](https://github.com/SpecterOps/JAMFHound_Internal/blob/main/schema/schema_enterprise.json) file
This file is automatically generated from the [schema_enterprise.json](https://github.com/SpecterOps/JamfHound/blob/main/schema/schema_enterprise.json) file
that is bundled with JAMF (JamfHound).
</Info>

Expand Down
Loading