>_ ~/cybersecurity-atlas

Cybersecurity
Knowledge Base

A curated atlas of 278 notes across 17 branches — organized by learning phase, from foundational substrate to specialty operations. Each note is atomic, with attacker/defender duality, references, and links to playbooks that turn it into action.

278
Notes
17
Branches
16
Playbooks
17
Registries
The learning path

Read it in order. Each phase is the prerequisite for the next.

Start at 00 · Orientation for the vocabulary. Walk through Substrate → Paired → Operator → Specialty. ★ Always-on (privacy, OPSEC) threads through everything.

Open the Start Here guide
00
Start here
Orientation
1 branch · 8 notes
01
How things work
Substrate
3 branches · 65 notes
02
Offense ↔ Defense
Paired
2 branches · 33 notes
03
Hands-on
Operator
4 branches · 48 notes
04
Go deep
Specialty
6 branches · 67 notes
Cross-cutting
Always-on
1 branch · 33 notes
00
Phase 00 · Start here

Orientation

Mental models, the CIA triad, and threat modeling — the language you'll use everywhere else.

Phase overview
1 branch · 8 notes
01
Phase 01 · How things work

Substrate

Networking, cryptography, browser trust, OS behavior. The substrate that every attack and defense touches.

Phase overview
3 branches · 65 notes
02
Phase 02 · Offense ↔ Defense

Paired

Attack and detection as paired thinking. Every offensive primitive has a defensive signature; learn them together.

Phase overview
2 branches · 33 notes
03
Phase 03 · Hands-on

Operator

Recon, exposure mapping, privilege escalation, and the practical workflows of an offensive operator.

Phase overview
4 branches · 48 notes
04
Phase 04 · Go deep

Specialty

Pick what your job demands: cloud, identity, DevSecOps, wireless, binary exploitation, API security.

Phase overview
6 branches · 67 notes
Phase ★ · Cross-cutting

Always-on

Privacy, anonymity, OPSEC. Practice continuously — these aren't a phase, they're a posture.

Phase overview
1 branch · 33 notes
Featured Note
Web Security 3 min read

Cross-Site Scripting (XSS)

XSS happens when attacker-controlled input is rendered in a browser context in a way that causes the browser to interpret it as executable code instead of inert...

#cybersecurity#web-security#xss
Reference system

Reference registries

The registries keep citations normalized behind the learning branches, so atomic notes stay compact and high-signal.