A seven-part series

A key’s day

Each part follows a made-up key through the best case: someone notices, and the old key is shut off and confirmed dead. Parts 1–4 show how it spreads. Part 5 turns on scanning at six layers, Part 6 finds it in logs and public files, and Part 7 walks the response.

Deleting a leaked key doesn’t turn it off. Each part shows why, and what does.

Start with Part 1: Code About 15 minutes. No sign-up, nothing saved.

How a key spreads

  1. Part 1 Start here Code One developer’s shortcut copies the key from her laptop into shared code, Git history, and the build. 16 steps · about 15 min
  2. Part 2 People Chat, tickets, and docs move the key, one helpful paste at a time. 12 steps · about 10 min
  3. Part 3 Systems Automation copies the key into images, logs, and backups, with no person involved. 12 steps · about 10 min
  4. Part 4 Agents An AI coding agent copies the key into its settings, chat, and commits, and a bad package hunts for it. 12 steps · about 10 min

Scanning, public leaks, and the response

  1. Part 5 Coverage The same leaks, with TruffleHog set up at six layers. Each copy is caught where it lands. 12 steps · about 10 min
  2. Part 6 Logs and public assets A key that a nightly job uses spills into logs, a vendor’s ticket, a public link, and a web page. 12 steps · about 10 min
  3. Part 7 Response Four findings, one live key, three teams that depend on it. Triage without guessing, then prove the fix. 9 steps · about 8 min

Jump to a topic

Short reads

A short page for each part, to print or share. No clicking through.

Topic summaries

Meet the cast

The same people show up in every part. The person who leaks a key is rarely the one who owns it, and the owner is often not the one who ships the fix. Follow anyone through a part to see where they come in.

Show all 25 people

Builders

Write the code and copy the key to get work done.

  • Sam Software engineer

    Has a deadline. Security steps that slow the work get skipped, and deleting a key feels like fixing it.

    Follow them: Part 1 Part 2 Part 4 Part 5 Part 7

  • Priya Software engineer, teammate

    Reviews many changes a day. A key inside a config file is easy to miss.

    Follow them: Part 1 Part 2 Part 4 Part 5 Part 6

  • Jun Data engineer

    Pipelines and notebooks hold connection strings, and their output can print a key.

    Follow them: Part 2 Part 3 Part 6 Part 7

Owners and operators

Own the key, the places it lives, and the systems that use it.

Security

Set the rules, find the copies, and decide what is urgent.

  • Nadia Application security engineer

    Code security tools that scan for keys as an add-on flag test values and random strings, so the few live keys get lost in the noise.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7

  • Leo Security operations analyst

    Spends more time asking who owns a key than acting on it, and needs to know what uses a key before anyone shuts it off.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7

  • Grace Cloud security and identity engineer

    Long-lived keys with broad access are the ones that hurt most when they leak.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7

  • Ray Security architect

    A scanner has to read raw values to check them, so access and data handling need answers first.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5

  • Ava Security program manager

    Chases owners across teams for every finding, and a ticket marked done does not prove the key was replaced.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7

  • Zoe Red team engineer

    Finds keys others missed, but does not own or fix them.

    Follow them: Part 1 Part 2 Part 6

Leadership and risk

Fund the work, make time for it, and prove it was done.

  • Uma Product manager

    Rarely sees the key, but the deadline shapes the shortcuts people take.

    Follow them: Part 1

  • Marcus Engineering manager

    The team gets the fix tickets. Needs a clear owner and no surprise fire drills.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 7

  • Elena VP of Engineering

    Weighs time spent on fixes against the roadmap, and pushes back on tools that slow developers.

    Follow them: Part 1 Part 2 Part 3 Part 4

  • Carmen Chief information security officer

    Not hands-on. Wants confidence that scanning covers everything and hears about high-impact exposures.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 7

  • Tom Governance, risk, and compliance lead

    Needs proof that each live key was replaced, not just deleted.

    Follow them: Part 1 Part 2 Part 3 Part 4 Part 5 Part 7

  • Ines Legal and privacy counsel

    Steps in only when an exposed key could reach customer or regulated data.

    Follow them: Part 1 Part 3 Part 4 Part 6 Part 7

Machines

Copy and use the key with no person in the loop.

  • CI job Build pipeline

    Uses keys at build time and can print them into logs or bake them into images.

    Follow them: Part 1 Part 3 Part 5

  • Backup job Nightly backup

    Copies whatever is there, keys included, and keeps it for months.

    Follow them: Part 3

  • Coding agent AI coding assistant

    Can read a key into its chat history and push it like any other change.

    Follow them: Part 4

Outside the team

Not on the team, but can reach a copy.

  • Guest contractor Outside the company

    Can search anything the guest account can see.

    Follow them: Part 2

  • Attacker Outside the company

    Needs only one copy that still works.

    Follow them: Part 4

The parts can be taken in any order. Nothing is saved: a refresh always starts over.