KeyDrift
Free scan
The Secret Leak Field Manual

Appendix C · Incident record template

The Secret Leak Field Manual · 3 min read

Copy this whole file per incident. Fill every field with what is known at the time; write "unknown" rather than guessing — the record's value is precision, and unknowns mark the audit work. Masked values only, everywhere, always.

FieldEntry
Incident ID / ticket
Date opened (UTC)
Severity rating + one-sentence rationaleFrom the Chapter 3 rubric
Incident leadName and role
RespondersNames and roles
StatusOpen / contained / closed

The credential

FieldEntry
Provider and classe.g. Stripe restricted key (rk_live_)
Masked valueFirst 8 + last 4 only: rk_live_…XXXX
Fingerprint / hashIf tooling produced one
Scope modelWhat the credential can reach
Created onProvider console date
Revoked/rotated onTimestamp from Chapter 6 playbook
Attribution notese.g. "Stripe or Clerk shape; confirmed Stripe"

Discovery

FieldEntry
Found byInternal scan / external report / usage anomaly / other
Found whereChapter 1 surface number(s) + exact location (URL, log path, commit)
Found whenUTC timestamp
Evidence attachedScreenshot paths, report links (masked)

Exposure window

FieldEntry
Earliest plausible exposureBest-evidenced estimate + how derived (commit date, deploy date, retention window)
Revocation timeUTC
Window lengthFor the audit in Chapter 5
Usage anomalies foundWhat, where observed, timestamps; or "none found" + which logs were checked

Actions ledger

Time (UTC)ActionOwnerNotes
Record opened
Classified
Replacement staged
Rotation deployed
Old credential revoked
Artifacts rebuilt + caches purged
Copies swept (list each location)CI vars · vault · .env files · previews · trackers
Old key verified deadMethod + result
Deployed surface rescanned cleanTool + timestamp

Copies disposition

LocationDispositionCleaned / scheduled / accepted-with-reason
Production bundle
Preview deployments
CI variables/contexts
Local machines
Third parties/vendors
AI sessions/tools

Disclosure

FieldEntry
Counsel consultedY/N, when
Processor/platform notifiedWho, when (payment-class exposures notify the processor as routine)
Customers affected / notifiedFacts established from usage audit, not assumptions
Regulatory analysis statusOwned by counsel

Root cause and changes

State the cause structurally ("the value wore a public env prefix", "CI job printed environment"), never personally.

Change madePrevents which recurrenceTicket

Open items at closure

  • [ ] Every copy dispositioned
  • [ ] Audit window fully covered by retained logs
  • [ ] Structural fix shipped and verified by rescan
  • [ ] Drill scheduled to test this incident's lessons