Paths/DevOps Engineer/Security & Hardening / Secrets & Credentials
Rotate a Leaked Credential
A key that leaked is a key you rotate, not one you delete. Issue a replacement credential, protect it like the original, and leave a trail that proves the rotation happened.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/credentials exists○
- File ~/credentials/api-key.txt exists with mode 600○
- File ~/credentials/rotation.log records the rotation○
02Walkthrough
1 of 6 revealed- 01
Create the credentials directory
Keep live credentials in one folder with strict permissions, never scattered in project trees.
mkdir ~/credentials - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list