Eleven domains, one field. Each branch below is a discipline you can build a career in; together they form a single system that decides what to protect, builds it securely, defends it while it runs, and attacks it on purpose to check the work.
These ideas run through every domain on the map. Learn them first, then look for them in each branch.
Foundations on the left: governance, architecture, identity, data, and cloud. On the right, the delivery lifecycle (building software, operating it, and adversarially testing it), then people, AI, and the moving edge. Hover a branch to focus on it.
A mind map shows the taxonomy; this shows the machine. Security runs as a loop across three moments in time — decide, build, run — with offensive security stress-testing the last two and every outcome feeding back into the first. Regulators, suppliers, and attackers act on the loop from outside.
One sentence each, enough to know which door you're walking through, plus what each domain feeds and what feeds it.
Decides what must be protected, to what standard, and who is accountable, including what the law requires when something goes wrong.
Feeds: requirements, test scope, response duties
Fed by: regulators, incidents, findings, metrics
Makes security structural, from trust boundaries and cryptography to networks, edge devices, operating systems, and hardware.
Feeds: secure designs, build standards
Fed by: requirements, threat intel
Controls who — and what — can do which actions where; the foundation that zero trust is built on.
Feeds: access decisions in every domain
Fed by: access policy, audit findings
Follows the data itself: classifying, encrypting, and governing it wherever it lives or moves.
Feeds: protection requirements, recovery capability
Fed by: privacy rules, risk decisions
Secures what you run on someone else's infrastructure: identities, workloads, and configuration.
Feeds: hardened platforms, runtime telemetry
Fed by: architecture standards, access policy
Secures the software you build and the tools you build it with, so the secure path is the default path.
Feeds: hardened releases, software inventories
Fed by: requirements, supplier code, offensive findings
Keeps running systems defended by knowing what you have, patching what's exposed, and responding to what gets through.
Feeds: fix priorities, risk metrics, incident lessons
Fed by: telemetry, threat intel, offensive findings
Attacks your own systems on purpose to prove whether the defenses actually hold.
Feeds: fixes, regression tests, detection tuning
Fed by: test scope, written authorization, threat intel
Covers the layer software can't: people, buildings, and the social engineering that targets both.
Feeds: phishing reports, insider risk signals
Fed by: awareness policy, threat intel
Protects AI systems and agents from manipulation and escape, and tracks how attackers use AI themselves.
Feeds: agent containment rules, AI risk findings
Fed by: AI governance, model suppliers, attacker techniques
The moving edge — industrial control networks, digital assets, and the coming post-quantum transition.
Feeds: new requirements for every domain
Fed by: new technology, research, regulators