Cyber Security
Lab Curriculum.

BUG FOUND: security learners who know threats in theory, but cannot triage a real alert.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Networking basics: TCP/IP, DNS, HTTP, ports, and firewalls.
2. Common vulnerabilities: OWASP Top 10 concepts, injection, XSS, broken access control.
3. Log reading: web, auth, and system logs; finding anomalies.
4. Authentication and authorisation basics: passwords, sessions, MFA, least privilege.
5. Security tools basics: scanners, Burp-style proxy concepts, and safe lab practice.
6. Incident triage: severity, containment, evidence, and communication.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: log files, a vulnerable practice app, scanner output, browser DevTools.

• BUG #1: Phishing alert — triage the alert, check headers/links, decide true vs false positive, document actions.
• BUG #2: SQL injection in a login form — reproduce safely in the lab, fix with parameterised queries, verify the fix.
• BUG #3: Misconfigured access lets a low-privilege user see admin data — find the access-control flaw, fix it, test all roles.
• BUG #4: Suspicious logins — trace the pattern, contain the account, reset safely, and write an incident note.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Trace an attack path through logs and code to its entry point; write a timeline.
• Audit a small codebase for injection, XSS, and broken access control; rank findings by risk.
• Fix a vulnerability without breaking the feature, with regression tests.
• Review a peer's fix for completeness: is the root cause fixed, or only one symptom?

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — an incident report + patched system, with a hardening checklist and a retest proving the vulnerability is closed.

$ ship → PROOF — exact output: incident report, patched code/config, retest evidence, and a hardening checklist.

$ run --lab cyber-security → ✓ SHIPPED, job-ready