Cheat notes · Module 04 · When it happens
Capstone: team-catalog
A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.
The idea
Audit a second team hand-over and defend your path analysis. Team-catalog has a covered register, an attacker notebook and an evidence-backed hand-over.
Remember
- Surface: The capstone fixture contains decoys and controls that already work.
- Trust: Choose evidence that can falsify a hypothesis before editing controls.
- Evidence: A valid signature can still represent a build from untrusted input.
- Owner: assign the control and retest to a named team.
Pitfalls
- A single control can be lifted or misconfigured; test independent layers.
- Preserve useful run evidence before disabling the path or rotating credentials.
Commands
./scripts/validate.sh | Check evidence files without executing learner code. |
git log --oneline -3 | Find the recent commits that changed the surface. |
Test yourself
Answer in your head first, then open the answer.
What is the objective?
The capstone fixture contains decoys and controls that already work.
What do you test?
Identify fourteen seeded gaps across seven surfaces, rank the cheapest path, test a harmless canary, close two independent boundaries and update both evidence files.
What evidence proves the fix?
Team-catalog has a covered register, an attacker notebook and an evidence-backed hand-over.
Where module 04 leaves you: Team-catalog has a covered register, an attacker notebook and an evidence-backed hand-over.