One lab a week. The group reviews a small system: what matters, what is exposed, and which records would let you see trouble.
A written defense of a design on your own clock. You name impacts and the habits that keep a failure from shipping.
- 01
What is worth protecting
Assets, people, and the failures that would actually matter.
- 02
Identity and access
Who is allowed to do what, drawn so someone else can check it.
- 03
How web applications fail
Classes of failure and their impact, and the habits that close them.
- 04
A network as a map
Enough structure to say where a control belongs.
- 05
Logs that notice trouble
The record you would want, and the data you would refuse to keep.
- 06
Failing more safely
Defaults, secrets, and what happens when a part is wrong.
- 07
A defense review
One small system, written up so an owner could act on it.