Securing the software itself — the defensive counterpart to exploitation-concepts’s vulnerability categories. Where that note explains why injection, XSS, and broken access control work mechanically, this folder covers the specific controls that prevent them.
Reading order
- input-validation-and-output-encoding — [Beginner] — allowlisting, parameterized queries (the actual fix for injection), context-aware output encoding (the actual fix for XSS)
- secure-authentication — [Intermediate] — password hashing (bcrypt/Argon2), salting, MFA, session management, JWT pitfalls
- https-and-tls — [Intermediate] — the TLS handshake, certificates and the chain of trust, HSTS, common misconfigurations
- security-headers-and-same-origin-policy — [Advanced] — same-origin policy, CORS, CSP, clickjacking defenses, CSRF-protecting cookie flags
Related
- API security — the same principles for machine clients, minus the browser: BOLA, JWT, SSRF, the OWASP API Top 10
- cybersecurity curriculum map
- network-security — the network-layer counterpart to this folder’s application-layer focus
- exploitation-concepts — the offensive framing of the same vulnerability classes
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering