mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
1.4 KiB
1.4 KiB
Workflows - DCSync Domain Persistence
DCSync Attack Chain
1. Prerequisites
├── Domain Admin or account with replication rights
├── Network access to Domain Controller (TCP/135, dynamic RPC)
└── Tool: Mimikatz (Windows) or secretsdump.py (Linux)
2. Credential Extraction
├── Extract KRBTGT hash (Golden Ticket capability)
├── Extract Administrator hash (immediate DA access)
├── Extract all domain hashes (comprehensive dump)
└── Extract service account hashes (lateral movement)
3. Golden Ticket Persistence
├── Forge Golden Ticket with KRBTGT hash
├── Set arbitrary user, SID, and group memberships
├── Import ticket into current session
└── Access any resource in the domain
4. DCSync Rights Persistence
├── Create low-profile account in AD
├── Grant DS-Replication-Get-Changes-All rights
├── Verify rights with ACL enumeration
└── Account can now perform DCSync independently
Golden Ticket Lifecycle
Creation: KRBTGT hash + Domain SID → Golden Ticket (10-year validity)
Usage: Import ticket → Access any service in domain
Survival: Persists through password resets (except double KRBTGT reset)
Detection: Anomalous TGT lifetime, non-existent users, impossible SIDs
Cleanup: Double KRBTGT password reset (with 10+ hour gap between resets)