A key’s day

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:

  1. Job runner’s debug log
  2. Central log platform
  3. Vendor support ticket
  4. Storage export, with a public link
  5. Public page’s JavaScript bundle
  6. Build artifact the pipeline keeps

The day, step by step

  1. Meet the key · 9:00 AM Meet the key.
  2. Debug log · 10:15 AM Debug logging writes the key down.
  3. Log platform · 10:16 AM Shipped to a log platform forty people can search.
  4. Support bundle · 11:40 AM Attached to a vendor’s support ticket.
  5. Storage export · 2:00 PM Exported to storage, with a public link.
  6. Public site · 3:30 PM Built into a public web page.
  7. Redeploy · 4:10 PM Deleted and redeployed, but still served.
  8. Detect · 4:45 PM A report, then TruffleHog finds the rest.
  9. Verify · 4:47 PM Is it still live?
  10. Analyze and notify · 5:05 PM The owner gets the alert, and two teams find out they depend on it.
  11. Rotate · 6:00 PM Swap in a new key.
  12. 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