>_ ~/cybersecurity-atlas CybersecurityKnowledge 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. Explore Notes View Playbooks 278Notes 17Branches 16Playbooks 17Registries The learning pathRead 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 00Start hereOrientation1 branch · 8 notes 01How things workSubstrate3 branches · 65 notes 02Offense ↔ DefensePaired2 branches · 33 notes 03Hands-onOperator4 branches · 48 notes 04Go deepSpecialty6 branches · 67 notes ★Cross-cuttingAlways-on1 branch · 33 notes 00Phase 00 · Start hereOrientationMental models, the CIA triad, and threat modeling — the language you'll use everywhere else.Phase overview 1 branch · 8 notes 8 notesFoundationsPhase 0 mental models — what cybersecurity is, the CIA triad as a decision tool, threat-modeling quickstart, and the attacker-defender duality.Explore 01Phase 01 · How things workSubstrateNetworking, cryptography, browser trust, OS behavior. The substrate that every attack and defense touches.Phase overview 3 branches · 65 notes 15 notesCryptographyHashes, encryption, signatures, key exchange, TLS/PKI, password storage, and token correctness.Explore 23 notesNetworkingReachability, HTTP, proxies, DNS, TLS, and packet-level observation.Explore 27 notesWeb SecurityBrowser behavior, sessions, access control, and server-side exploit patterns.Explore 02Phase 02 · Offense ↔ DefensePairedAttack and detection as paired thinking. Every offensive primitive has a defensive signature; learn them together.Phase overview 2 branches · 33 notes 20 notesOffensive Security / ReconDiscovery, validation, and handoff from recon into concrete testing.Explore 13 notesDetection EngineeringTelemetry, behavioral analytics, correlation, and detection tradeoffs.Explore 03Phase 03 · Hands-onOperatorRecon, exposure mapping, privilege escalation, and the practical workflows of an offensive operator.Phase overview 4 branches · 48 notes 11 notesAttack Surface MappingWhat is exposed, reachable, discoverable, and drifting from intended design.Explore 11 notesOSINTPublic-source collection, evidence quality, and ethical handling of clues.Explore 10 notesLinux Privilege EscalationLocal boundary failures, enumeration, and safe escalation hypothesis testing.Explore 16 notesSecurity PlaybooksRepeatable procedures for turning concepts into practical tests.Explore 04Phase 04 · Go deepSpecialtyPick what your job demands: cloud, identity, DevSecOps, wireless, binary exploitation, API security.Phase overview 6 branches · 67 notes 11 notesWireless SecurityWi-Fi frames, handshakes, rogue access points, and local-network MITM.Explore 15 notesAPI SecurityAuthorization, token trust, inventory drift, and machine-readable abuse.Explore 11 notesCloud SecurityIAM, metadata, storage, network boundaries, secrets, and logging controls.Explore 13 notesDevSecOpsSecure delivery, CI/CD hardening, supply chain, secrets, and release trust.Explore 12 notesIdentity & Active DirectoryKerberos, BloodHound graph analysis, DCSync, and AD attack-path engineering across offense and defense.Explore 5 notesBinary ExploitationMemory corruption, stack and heap overflows, exploit mitigations, reverse engineering, and the modern exploitation arms race at the binary level.Explore ★Phase ★ · Cross-cuttingAlways-onPrivacy, anonymity, OPSEC. Practice continuously — these aren't a phase, they're a posture.Phase overview 1 branch · 33 notes 33 notesPrivacy, Anonymity & OPSECVPN threat models, Tor, metadata leakage, compartmentalization, and OPSEC failure modes.Explore 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. Cybersecurity Reference Registry Reference Registry - Detection Engineering Reference Registry - Privacy, Anonymity & OPSEC Reference Registry — API Security Reference Registry — Attack Surface Mapping Reference Registry — Binary Exploitation Reference Registry — Cloud Security Reference Registry — Cryptography Reference Registry — DevSecOps Reference Registry — Identity and Active Directory Reference Registry — Linux Privilege Escalation Reference Registry — Networking Reference Registry — Offensive Security Reference Registry — OSINT Reference Registry — Playbooks Reference Registry — Web Security Reference Registry — Wireless Security