Master security engineering
From understanding the fundamentals to confidently designing systems that survive attackers. 8 parts, 27 chapters, 81 topics. Open a chapter, click a topic to read it, tick it when you are done.
Prerequisites
The words every security design is written in: how a request travels, what one machine does, how crypto primitives fit together, and how identity is proven.
- What happens when you log inBeginner
- DNS, DNSSEC and why it mattersBeginner
- TCP vs UDP, ports, NATBeginneron the way
- HTTP semantics and headers that matterBeginneron the way
- TLS and PKI in practiceIntermediate
Fundamentals
The habits of thought: threat modelling, trust boundaries, defence in depth, and how to talk about risk like an engineer.
Building blocks
The boxes you draw in nearly every secure design: edge, identity, secrets, logging, scanning. For each: the problem it solves, when to add it, what it costs.
Identity & access
SSO at scale, authorisation models that survive growth, and access that expires on its own.
Cloud & platform
IAM that stays least-privilege, Kubernetes that is hard to escape, data protection built on KMS.
Detection & response
Pipelines that never lose an auth event, detections written like software, response that contains before humans wake up.
Operations & scale
Vulnerability backlogs, the edge at scale, rotation that runs itself.
Architecture at scale
Reference architectures, multi-tenant isolation and the metrics that let you run security like engineering.
Do not read it all. Start at part 00.
Start design problems once you have seen the building blocks. Let them show you the gaps, then come back here for the chapter that fills each one.