Skip to content

docs(eden): record the first collection and what collecting really took - #1538

Merged
Gerrrt merged 2 commits into
mainfrom
docs/eden-first-collection
Nov 16, 2026
Merged

Gerrrt merged 2 commits into
mainfrom
docs/eden-first-collection

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Nov 16, 2026

Copy link
Copy Markdown
Owner

What changed

  • docs/runbooks/build-the-bloodhound-guest.md §7 step 2: the collection step, three lines before, now records who to collect as and how, and the three obstacles the first real run hit.
  • docs/changelog.md: an entry with the collection's result and the same findings.

No code or infrastructure change. eden already holds the ingested graph.

Why

The rebuilt eden held an empty graph. A SharpHound collection was run and ingested on 2026-11-16 — 370 nodes, 3,914 edges (48 users, 73 groups, the 6 domain computers, 14 OUs, 5 GPOs, the domain). Getting there surfaced three things the runbook never said:

  • Which user, and its password. AD\acooper, a population user (Give the lab domain users and deliberate weaknesses, one tag at a time #449); its password is printed on phoenix by population-credentials.yml, not stored. Signed in at carbuncle's console, since a plain domain user is not in Remote Desktop Users.
  • Defender. It quarantines SharpHound through AMSI as the assembly loads, so a folder exclusion is not enough — a process exclusion, or toggling real-time protection in the Windows Security UI, is. The detection was left in place: it is the SOC event Run Wazuh on Saruman — the heaviest component in ADR-0007 #266 exists to raise.
  • The network collectors do not work here. bloodhound-ce-python and netexec authenticate, but both DCs enforce LDAP signing and have no LDAPS certificate (no AD CS in the lab), so neither can collect. SharpHound on a domain host is the only path.

Blast radius

None. Two documentation files.

  • No change to network segmentation or firewall rules
  • No new port published to a VLAN that could not already reach the service
  • No credential added outside secrets/*.sops.yaml

Verification

  • Graph read from app-db: 370 nodes, 3,914 edges, broken down by kind as above (was 1 node, 0 edges before the ingest).

  • python3 scripts/check_docs.py: OK. ./scripts/lint.sh: passed, with yamllint, ruff (×2) and ansible-lint skipped on eden.

  • make validate passes

  • Deployed to the lab and confirmed working

  • Docs updated (docs/, service README, or docs/roadmap.md)

🤖 Generated with Claude Code

The rebuilt guest's graph was empty until a SharpHound run was ingested on
2026-11-16 (370 nodes, 3914 edges). build-the-bloodhound-guest.md §7 now
records the population user and its phoenix-printed password, that Defender
catches SharpHound through AMSI (and the detection is the SOC signal, left
in place), that the network collectors cannot work against DCs that enforce
LDAP signing with no LDAPS cert, and that the UI is Hicks-only for upload.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings November 16, 2026 14:40
@Gerrrt
Gerrrt enabled auto-merge (squash) November 16, 2026 14:40

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

The runbook still omits required Ansible prerequisites, administrator elevation and Defender-exclusion cleanup, and viable steps for collector delivery and archive retrieval.

3 open issues
What changed in this PR

Documents the first SharpHound collection ingested into the rebuilt eden guest and adds practical guidance to the BloodHound deployment runbook. This PR changes documentation only, with no code or infrastructure changes.

Changes:

  • Expands collection guidance with the user identity, credential retrieval, and obstacles encountered during the run.
  • Documents archive transfer through a Hicks workstation and cleanup after ingestion.
  • Records the collection result: 370 nodes and 3,914 edges.
File Description
docs/​runbooks/​build-the-bloodhound-guest.md Expands collection and ingestion instructions with operational lessons.
docs/​changelog.md Records the November 16 ingest results and collection obstacles.

Review effort: Balanced

Address Copilot's review of #1538:

- population-credentials.yml needs the checkout's ansible/ directory and the
  exported proxmox env (ansible/README.md); the earlier repo-root shell has
  neither. Give the full preamble.
- AD\acooper is an ordinary user and cannot change Defender. Elevate as the
  endpoint's local labadmin for the exclusion / RT toggle, then collect back
  in acooper's session, and remove the process exclusion afterwards (not just
  re-enable protection).
- RDP is off on all six guests and acooper has no SSH key, so carbuncle cannot
  be reached that way. Deliver SharpHound to carbuncle and pull the zip back
  with phoenix-initiated scp as the built-in Administrator, naming the key and
  the archive path.

Refs #1538.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Gerrrt
Gerrrt merged commit 72b54c2 into main Nov 16, 2026
8 checks passed
@Gerrrt
Gerrrt deleted the docs/eden-first-collection branch November 16, 2026 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants