Part 6 recap · Logs and public assets
Logs and public assets: the short version
If a system can print it, ship it, or serve it, the key can leave. Make every copy useless.
Take the full lesson Part 7 recap: Response
Where the copies are
Issued by the payment service, kept in the vault, then 6 copies:
- Job runner’s debug log
- Central log platform
- Vendor support ticket
- Storage export, with a public link
- Public page’s JavaScript bundle
- Build artifact the pipeline keeps
The day, step by step
- Meet the key · 9:00 AM Meet the key.
- Debug log · 10:15 AM Debug logging writes the key down.
- Log platform · 10:16 AM Shipped to a log platform forty people can search.
- Support bundle · 11:40 AM Attached to a vendor’s support ticket.
- Storage export · 2:00 PM Exported to storage, with a public link.
- Public site · 3:30 PM Built into a public web page.
- Redeploy · 4:10 PM Deleted and redeployed, but still served.
- Detect · 4:45 PM A report, then TruffleHog finds the rest.
- Verify · 4:47 PM Is it still live?
- Analyze and notify · 5:05 PM The owner gets the alert, and two teams find out they depend on it.
- Rotate · 6:00 PM Swap in a new key.
- Confirm · 6:20 PM Confirmed: the old key is dead.
How it ended
Swap in a new key. Once the old key is off, the log lines, the vendor’s bundle, the export, and the cached page all hold a key that no longer opens anything.
Confirmed: the old key is dead. The copies outside the company were never going to come back. Turning the key off was the only fix that reached them.
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.