A seven-part series
A key’s day
Each part follows a made-up key through the best case: someone notices, and the old key is shut off and confirmed dead. Parts 1–4 show how it spreads. Part 5 turns on scanning at six layers, Part 6 finds it in logs and public files, and Part 7 walks the response.
Deleting a leaked key doesn’t turn it off. Each part shows why, and what does.
Start with Part 1: Code About 15 minutes. No sign-up, nothing saved.
How a key spreads
- Part 1 Start here Code One developer’s shortcut copies the key from her laptop into shared code, Git history, and the build.
- Part 2 People Chat, tickets, and docs move the key, one helpful paste at a time.
- Part 3 Systems Automation copies the key into images, logs, and backups, with no person involved.
- Part 4 Agents An AI coding agent copies the key into its settings, chat, and commits, and a bad package hunts for it.
Scanning, public leaks, and the response
- Part 5 Coverage The same leaks, with TruffleHog set up at six layers. Each copy is caught where it lands.
- Part 6 Logs and public assets A key that a nightly job uses spills into logs, a vendor’s ticket, a public link, and a web page.
- Part 7 Response Four findings, one live key, three teams that depend on it. Triage without guessing, then prove the fix.
Jump to a topic
- A key kept in a vault still gets copied outPart 1, Code, step 4: Laptop
- Deleted from the code, and it still worksPart 1, Code, step 9: Git history
- Bundled scanners and the noisy queuePart 1, Code, step 12: Verify
- What sits behind a key: owner, reach, permissions, activityPart 1, Code, step 13: Analyze
- The owner chase: whose key is this?Part 2, People, step 10: Notify and triage
- Which key to fix firstPart 3, Systems, step 10: Analyze and notify
- Replace a key without breaking anythingPart 1, Code, step 15: Rotate
- Proof it’s dead, time to fix, and what auditors ask forPart 1, Code, step 16: Confirm
- Keys in AI agents and AI training dataPart 4, Agents, step 8: Detect
- Hosted or self-hosted: where the scanner runsPart 5, Coverage, step 2: Deploy the scanners
- Hooks, CI, history, chat, and builds: what each layer catchesPart 5, Coverage, step 3: Pre-commit hook
- Keys outside the code: logs, vendors, and public filesPart 6, Logs and public assets, step 8: Detect
- Live, dead, or unknown: triage the queuePart 7, Response, step 2: Verify
- One key, three teams: rotate without an outagePart 7, Response, step 5: Coordinate
Short reads
A short page for each part, to print or share. No clicking through.
- Part 1 recap: Code
- Part 2 recap: People
- Part 3 recap: Systems
- Part 4 recap: Agents
- Part 5 recap: Coverage
- Part 6 recap: Logs and public assets
- Part 7 recap: Response
Topic summaries
- A key kept in a vault still gets copied out
- Deleted from the code, and it still works
- Bundled scanners and the noisy queue
- What sits behind a key: owner, reach, permissions, activity
- The owner chase: whose key is this?
- Which key to fix first
- Replace a key without breaking anything
- Proof it’s dead, time to fix, and what auditors ask for
- Keys in AI agents and AI training data
- Hosted or self-hosted: where the scanner runs
- Hooks, CI, history, chat, and builds: what each layer catches
- Keys outside the code: logs, vendors, and public files
- Live, dead, or unknown: triage the queue
- One key, three teams: rotate without an outage
Meet the cast
The same people show up in every part. The person who leaks a key is rarely the one who owns it, and the owner is often not the one who ships the fix. Follow anyone through a part to see where they come in.
Show all 25 people
Builders
Write the code and copy the key to get work done.
Owners and operators
Own the key, the places it lives, and the systems that use it.
Security
Set the rules, find the copies, and decide what is urgent.
Leadership and risk
Fund the work, make time for it, and prove it was done.
-
Uma Product manager
Rarely sees the key, but the deadline shapes the shortcuts people take.
Follow them: Part 1
Machines
Copy and use the key with no person in the loop.
Outside the team
Not on the team, but can reach a copy.
-
Guest contractor Outside the company
Can search anything the guest account can see.
Follow them: Part 2
The parts can be taken in any order. Nothing is saved: a refresh always starts over.