Part 1, Code · Step 12: Verify
Bundled scanners and the noisy queue
Is it still live? TruffleHog checks the key with the service that issued it. It still works, so this is a real exposure, not a false alarm.
Why it matters. A live key needs action now. A dead one can wait.
See it in the lesson Part 1 recap
What the research found: GitGuardian, 2025
70% of the secrets found leaked on public GitHub in 2022 still worked in 2025. Finding a key doesn’t mean anyone shut it off.
What verification can’t confirm
- Not every key can be tested. Some services have no safe way to check a key, and some private keys or internal passwords have nothing to test against.
- Some keys only work inside a private network, so a check from outside can’t reach the service.
- Checks fail for other reasons too, like rate limits, timeouts, and outages. Those come back as unknown, not dead.
- Unverified doesn’t mean safe. It means the check couldn’t prove the key works.
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
- 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