Part 1, Code · Step 13: Analyze
What sits behind a key: owner, reach, permissions, activity
What can it reach? TruffleHog shows which account the key belongs to and what it can do. A Stripe secret key has full access to every Stripe API, so this one can make charges, issue refunds, and read customer records. Anyone holding a copy can do the same until the key is shut off.
Why it matters. Knowing the reach tells the team how urgent this is and who owns it.
See it in the lesson Part 1 recap
This really happened: Toyota, 2022
A contractor’s public repository held a key to a customer data server for almost five years. When it was found, Toyota’s access records couldn’t confirm or rule out that someone had used it.
Try it with TruffleHog open source
Shows detailed permissions for about 20 of the most commonly leaked key types.
trufflehog analyze
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
- 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