Overview#
Kerberos forgery that grants domain admin access in Active Directory. Requires theft of the KRBTGT hash and is mitigated by rotation and tiered admin models.
Core objectives#
- Establish shared definitions of Golden Ticket Attack for security, engineering, and leadership teams.
- Connect Golden Ticket Attack activities to measurable risk reduction and resilience goals.
- Provide onboarding notes so new team members can quickly understand how Golden Ticket Attack works here.
Implementation notes#
- Identify the primary owner for Golden Ticket Attack, the data sources involved, and the systems affected.
- Document the minimum viable process, tooling, and runbooks that keep Golden Ticket Attack healthy.
- Map Golden Ticket Attack practices to standards such as ISO/IEC 27001, NIST CSF, or CIS Controls.
Operational signals#
- Leading indicators: early warnings that Golden Ticket Attack might degrade (e.g., backlog growth, noisy alerts, or missed SLAs).
- Lagging indicators: realized impact that shows Golden Ticket Attack failed or needs investment (e.g., incidents, audit findings).
- Feedback loops: retrospectives and metrics reviews that tune Golden Ticket Attack continuously.
Related practices#
- Align Golden Ticket Attack with defense-in-depth planning, threat modeling, and disaster recovery tests.
- Communicate updates to stakeholders through concise briefs, dashboards, and internal FAQs.
- Pair Golden Ticket Attack improvements with tabletop exercises to validate expectations.