Part 1, Code · Step 4: Laptop
A key kept in a vault still gets copied out
Copied to a laptop. Diego’s payments team keeps the key in the team vault, the one official copy. Sam opens it, clicks Copy, and pastes the key into a file to start testing. The vault did its job. Now the key is on her clipboard and in a file on her laptop.
Why it matters. Every copy of the key is one more place it can leak from.
See it in the lesson Part 1 recap
This really happened: CircleCI, 2023
Malware on one engineer’s laptop stole a signed-in session. CircleCI then told every customer to rotate the secrets they had stored in it.
Try it with TruffleHog open source
Can scan files and folders on the laptop when someone runs it.
trufflehog filesystem ./billing
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
- 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
- Live, dead, or unknown: triage the queue
- One key, three teams: rotate without an outage