Handle the keys and passwords a running system needs, well enough to say where each one lives and who can read it, to rotate one without an outage, and to respond correctly when one is exposed

Keeping a Secret in Production

Every system holds credentials, and most hold them worse than their owners think. This course covers where a secret can live, how a program gets one at run time, rotating without downtime, and what to actually do when one leaks.

8 lessons, written and corrected before you arrived. Reading them here needs no account. The first reads the whole way through; the others open and then stop, because a page nobody owns cannot tell who is reading it. Starting the course gives you your own copy, where every idea has problems standing under it and you can ask about any sentence.

Start reading

01Longer Than the List You Would Write From MemoryAsk anybody which credentials their system holds and you get four. The real number is thirty, and the ones left off the list are the ones nobody is looking after.
02Deleting It Does Not Undo Itopening onlyEverybody knows not to commit a secret. Fewer people know why removing it afterwards changes nothing, and that knowing why decides what you do in the first ten minutes.
03Two Questions Decide Every Place a Secret Can Sitopening onlyFile, environment, secret manager, kernel keyring, hardware module. They differ on exactly two things that matter, and comparing them on anything else wastes the afternoon.
04Follow the Chain Until It Stopsopening onlyA process has no credentials and must end up with all of them. Every scheme for that is a chain, and the only question worth asking is where the chain stops.
05One Component Falls, and Then Whatopening onlyMost estates give every service the same identity and therefore the same reach. Scoping is the work that turns one compromise into a small compromise.
06Both Values Have to Work for a Whileopening onlyRotation is a sequencing problem, not a security problem. Get the order right and nothing notices; get it wrong and everything fails at once, which is why nobody rotates.
07Nobody Published It and It Is Publishedopening onlyMost credentials that escape were never mishandled. They were logged, captured in an error report, printed by a build, or visible in a process list.
08The Order Is Not the One That Feels Urgentopening onlyA credential is exposed. The instinct is to find out what happened. The correct first move is to make the value worthless, and everything else comes after.