Part 2 recap · People
People: the short version
Deleting the message isn’t the fix. Killing the key is.
Take the full lesson Part 3 recap: Systems
Where the copies are
Issued by the payment service, kept in a shared doc, then 5 copies:
- Direct message
- Team channel post
- Ticket screenshot
- Ticket log file
- Setup guide, earlier version
The day, step by step
- Meet the key · 9:00 AM Meet the key.
- Direct message · 9:40 AM Pasted into a chat to unblock a teammate.
- Team channel · 10:15 AM Reposted in a team channel.
- Ticket · 11:00 AM Attached to a ticket, twice.
- Wiki page · 1:30 PM Written into a setup guide, “for convenience.”
- Edit · 3:00 PM Removed from the guide, still in its history.
- Search · 4:00 PM Search now reaches every copy.
- Detect · 4:30 PM TruffleHog reads the chat, tickets, and wiki.
- Verify · 4:35 PM Is it still live?
- Notify and triage · 4:50 PM The alert goes to the owner, not to who shared it.
- Rotate · 5:30 PM Swap in a new key.
- Confirm · 5:45 PM Confirmed: the old key is dead.
How it ended
Swap in a new key. Every step before this found the problem. This step removes it.
Confirmed: the old key is dead. The leftover copies are harmless now, because their key is off.
Keep going
- Try TruffleHog open source Scan a repository or a folder on your laptop.
- See TruffleHog Enterprise Continuous scanning, routing to owners, and re-checks.
- Talk to the team Ask how this would work in your environment.