Part 7, Response · Step 2: Verify
Live, dead, or unknown: triage the queue
Sort the queue by what each check proved. TruffleHog asks each issuing service about each key. One is verified: it works. One is rejected, a key revoked in March, though its copy is still in the commit. One matches the documented example value. The last check failed with a timeout, so its result is unknown.
Why it matters. Unknown is not safe, and unverified is not a false positive. Those findings stay open until someone can check them another way.
See it in the lesson Part 7 recap
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?
- 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
- One key, three teams: rotate without an outage