Part 6, Logs and public assets · Step 8: Detect
Keys outside the code: logs, vendors, and public files
A report, then TruffleHog finds the rest. Zoe on the red team finds the key in the cached JavaScript and reports it. Nadia scans what the team can reach: the storage bucket and the page’s build output. She also connects the log pipeline, and because debug logging is still on, the job’s next log line carries the key straight into the scan. All of them hold the same key. The runner’s own log and the vendor’s copy are outside the scan.
Why it matters. One report found one copy. The scan finds the others it can reach, and says plainly which it can’t.
See it in the lesson Part 6 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
- Live, dead, or unknown: triage the queue
- One key, three teams: rotate without an outage