Part 3, Systems · Step 10: Analyze and notify
Which key to fix first
Sized by what the key can do, then sent to its owner. First the team checks what the key can do: take payments, issue refunds, and read customer records. Then the alert goes to Diego’s payments team, who own the key, with all five places it was copied.
Why it matters. What a key can reach sets how urgent it is. The alert has to reach someone who can replace it.
See it in the lesson Part 3 recap
This really happened: tj-actions/changed-files, 2025
Wiz found dozens of public repositories whose build logs had leaked secrets and notified the owners.
Sources
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.
More topics
- 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?
- 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