Back to catalog
Static reviewDevelopment

Skill dossier

mapping-attack-paths-with-bloodhound-ce

Source declaration

Collect Active Directory data with SharpHound and Entra ID data with AzureHound, ingest into BloodHound Community Edition, and analyze on-prem, cloud, and hybrid attack paths using built-in queries and custom Cypher. Use during authorized red-team or penetration-test engagements to map privilege-escalation chains toward domain/tenant compromise.

The author's original description, preserved in English. It describes intent, not verified performance.

Collect Active Directory data with SharpHound and Entra ID data with AzureHound, ingest into BloodHound Community Edition, and analyze on-prem, cloud, and hybrid attack paths using built-in queries and custom Cypher. Use during authorized red-team or penetration-test engagements to map privilege-escalation chains toward domain/tenant compromise.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Collect Active Directory data with SharpHound and Entra ID data with AzureHound, ingest into BloodHound Community Edition, and analyze on-prem, cloud, and hybrid attack paths using built-in queries and custom Cypher. Use during authorized red-team or penetration-test engagements to map privilege-escalation chains toward domain/tenant compromise. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L86]
  • Step 1: Deploy BloodHound CE and log in [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L88]
  • Step 2: Collect on-prem AD data with SharpHound [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L97]
  • Step 3: Collect Entra ID / Azure data with AzureHound [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L118]
  • Step 4: Ingest data into BloodHound CE [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L132]
  • Step 5: Mark owned principals [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L152]
  • Step 6: Run built-in analysis queries [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L155]
  • Step 7: Author custom Cypher for bespoke paths [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L165]
  • Step 8: Prioritize and document [Source statement; provisional, not tested. Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L193]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L1-L22]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
5
Markdown files
3
scripts
1
references
2
Size
30.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/mapping-attack-paths-with-bloodhound-ce/LICENSEOther11 KB
skills/mapping-attack-paths-with-bloodhound-ce/references/api-reference.mdReference2.2 KB
skills/mapping-attack-paths-with-bloodhound-ce/references/standards.mdReference1.2 KB
skills/mapping-attack-paths-with-bloodhound-ce/scripts/agent.pyScript4.7 KB
skills/mapping-attack-paths-with-bloodhound-ce/SKILL.mdInstruction11.8 KB

SKILL.md frontmatter

{
  "name": "mapping-attack-paths-with-bloodhound-ce",
  "description": "Collect Active Directory data with SharpHound and Entra ID data with AzureHound, ingest into BloodHound Community Edition, and analyze on-prem, cloud, and hybrid attack paths using built-in queries and custom Cypher. Use during authorized red-team or penetration-test engagements to map privilege-escalation chains toward domain/tenant compromise.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "bloodhound-ce",
    "sharphound",
    "azurehound",
    "active-directory",
    "entra-id",
    "attack-paths",
    "cypher",
    "hybrid-identity"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.AM-03"
  ],
  "mitre_attack": [
    "T1069"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  6. 06
    Action

    Step 1: Deploy BloodHound CE and log in

    Source-described action candidate under “Step 1: Deploy BloodHound CE and log in”; not verified execution.

Inspect all extracted workflow candidates (25 candidate steps)
  1. 07
    Action

    Step 2: Collect on-prem AD data with SharpHound

    Source-described action candidate under “Step 2: Collect on-prem AD data with SharpHound”; not verified execution.

  2. 08
    Action

    Step 3: Collect Entra ID / Azure data with AzureHound

    Source-described action candidate under “Step 3: Collect Entra ID / Azure data with AzureHound”; not verified execution.

  3. 09
    Action

    Run AzureHound `list` with credentials, a JWT, or a refresh token, writing a single JSON file.

    Source-described action candidate under “Step 3: Collect Entra ID / Azure data with AzureHound”; not verified execution.

  4. 10
    Action

    Step 4: Ingest data into BloodHound CE

    Source-described action candidate under “Step 4: Ingest data into BloodHound CE”; not verified execution.

  5. 11
    Input

    Upload the SharpHound ZIP and the AzureHound JSON through Administration -> File Ingest, or POST to the API.

    Source-described input candidate under “Step 4: Ingest data into BloodHound CE”; not verified execution.

  6. 12
    Action

    Step 5: Mark owned principals

    Source-described action candidate under “Step 5: Mark owned principals”; not verified execution.

  7. 13
    Action

    Step 6: Run built-in analysis queries

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  8. 14
    Action

    Shortest Path to Domain Admins

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  9. 15
    Action

    Kerberoastable accounts with a path to high value

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  10. 16
    Action

    AS-REP roastable users

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  11. 17
    Action

    Principals with DCSync rights

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  12. 18
    Action

    ADCS misconfigurations (ESC1-ESC8 edges in CE)

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  13. 19
    Action

    Computers with unconstrained delegation

    Source-described action candidate under “Step 6: Run built-in analysis queries”; not verified execution.

  14. 20
    Action

    Step 7: Author custom Cypher for bespoke paths

    Source-described action candidate under “Step 7: Author custom Cypher for bespoke paths”; not verified execution.

  15. 21
    Action

    Use Cypher for paths the built-ins do not cover, including hybrid AD-to-Entra chains.

    Source-described action candidate under “Step 7: Author custom Cypher for bespoke paths”; not verified execution.

  16. 22
    Action

    Step 8: Prioritize and document

    Source-described action candidate under “Step 8: Prioritize and document”; not verified execution.

  17. 23
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  18. 24
    Action

    Key Edge / Path Types

    Source-described action candidate under “Key Edge / Path Types”; not verified execution.

  19. 25
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

57 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

25 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 25 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

30 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 30 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/mapping-attack-paths-with-bloodhound-ce/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/mapping-attack-paths-with-bloodhound-ce
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.