AppSec
A four-tier application-security course — OWASP Top 10:2025 on Juice Shop and WebGoat, checkpoints, auto-scored labs and a gated capstone.
What the course covers
- 1. Course Map, Lab Environment & the Web Trust Model — Stand up the lab environment; state the web's trust model in one sentence; locate every later module on the course map.
- 2. HTTP, Sessions & Browser Security Mechanics — Read a raw HTTP request/response; explain same-origin policy and CORS from memory; name the security-relevant cookie attributes.
- 3. Threat Modeling: STRIDE, DREAD & Attack Trees — Produce a data-flow diagram for a real feature; run STRIDE across every arrow; score findings with DREAD; expand one finding into an attack tree.
- 4. Secure Code Review Methodology — Trace a trust boundary from entry point to sink; apply a fixed checklist to any diff; distinguish a flagged pattern from a proven exploit.
- 5. Reconnaissance & Attack Surface Mapping — Map a target's exposed services and technologies from the outside; read an nmap scan; separate passive from active recon.
- 6. A01 — Broken Access Control & SSRF — Distinguish authentication from authorization in code; recognize an IDOR/BOLA pattern on sight; design an SSRF egress allow-list.
- 7. A02 — Security Misconfiguration — Run a misconfiguration recon pass from the shell; explain why this category is a drift problem, not a code defect.
- 8. A03 — Software Supply Chain Failures — Run and triage an SCA scan; generate and read an SBOM; explain the three attack surfaces this 2025 category now covers.
- 9. A04 — Cryptographic Failures — Spot a fast-hash-for-passwords mistake; verify a TLS handshake from the shell; write a key-management plan.
- 10. A05 — Injection — Apply the "data vs. code" mental model across SQL, command, NoSQL and template injection; tune a SAST rule against a real finding.
- 11. A06 — Insecure Design — Separate a design flaw from an implementation bug; write abuse cases for a feature; place insecure design correctly in the SDLC.
- 12. A07 — Authentication Failures — Audit a login flow against a fixed checklist; decode and read a JWT's structure; list the five checks a JWT verifier must perform.
- 13. A08 — Software or Data Integrity Failures — Recognize an unsafe deserialization pattern; explain CI/CD as an integrity boundary; map where signing and provenance verification belong in a pipeline.
- 14. A09 — Security Logging & Alerting Failures — Write a log entry that's useful and safe; design alerting rules that would catch a real attack pattern; explain why 2025 renamed this category to stress alerting.
- 15. A10 — Mishandling of Exceptional Conditions — Tell fail-open from fail-closed on sight; find every security-relevant try/catch in a route handler; design an edge-case test matrix.
- 16. Client-Side Security: XSS, CSP, CSRF & CORS — Distinguish reflected, stored and DOM-based XSS; write a CSP that blocks inline script without breaking the app; explain why CSRF and permissive CORS are different trust failures.
- 17. SAST at Scale: Bandit, Semgrep, CodeQL — Pick the right static-analysis tool for a task; tune a ruleset so engineers don't learn to ignore it; write a custom rule.
- 18. DAST & API Security Testing — Run and read an OWASP ZAP scan; confirm a DAST finding manually; map an API to the OWASP API Security Top 10.
- 19. Fuzzing & Dynamic Testing — Fuzz a function with a coverage-guided fuzzer; connect a crash to a Module 15 exceptional-condition failure mode; add a time-boxed fuzz job to CI.
- 20. Penetration Testing Methodology & Reporting — Run the PTES/OWASP WSTG phases in order; write a finding report someone else can reproduce without you in the room.
- 21. DevSecOps: CI/CD Security Gates & Secrets Management — Wire SAST, SCA and secret scanning into a CI pipeline as a blocking gate; design a secrets-management pattern that survives rotation and compromise.
- 22. Container & Cloud-Native AppSec — Scan and harden a container image; apply least-privilege and deny-by-default principles at the Kubernetes layer.
- 23. Building an AppSec Program: SAMM, Champions, Metrics — Score an organization against OWASP SAMM; design a security-champions rollout; pick metrics that change behavior instead of just getting reported.
- Projects