Skip to content
Roadmap0/111
not startedstudy day 5 of 6 · covers original day 6

Study application security foundations

P1 AssistantS0
not started0/5 blocks
0/5
Jump & context

Week 1: Application Foundations, Model Trust, Tools & Authorization Boundaries

The five hours

  1. 01

    Concepts & system design

    60 min

    R02 — OWASP ASVS access control

    R03 — OWASP API1: BOLA

    R40 — OWASP WSTG API & auth testing

    Read the assigned sections; map the mechanism, threat model and trade-offs.

  2. 02

    Project implementation

    120 min

    Study IDOR/BOLA, input validation, SQL injection parameterization, CORS vs. CSRF, and safe error contracts. Wrap the chat loop in a minimal FastAPI endpoint.

    Build, integrate, debug and improve the increment in the active project.

  3. 03

    Security lab

    60 min

    Prove User A cannot read or modify User B's conversation by changing conversation_id in the request (use test principal headers).

    Test the abuse case, failure path, authorization bypass or resource limit.

  4. 04

    Verification & evidence

    30 min

    Endpoint threat model and automated IDOR/BOLA access-control test passing.

    Add or run regression tests; record the 9-point evidence record.

  5. 05

    Deliberate practice & Socratic review

    30 min

    Answer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?

    Re-explain the hardest concept aloud, inspect one edge case, update the gap log.

  6. total5 h

Read today · inside the concepts block

R02 R03 R40

Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.

Free resources for this day

5 curated
  • docsOWASP Foundation
    OWASP API Security Top 10

    API1 BOLA, API2 broken authentication, API4 resource consumption, API7 SSRF, and API8 misconfiguration are the checklist you map your new FastAPI endpoint against, with attacker/victim framing per item.

    R03S0moved 2026-11-11
  • videoPwnFunction · 8:14
    Insecure Direct Object Reference (IDOR) Explained

    Shows the request-id swap that turns your own record into someone else's, which is the exact test you run against a conversation endpoint that trusts a client-supplied id.

    R03checked 2026-11-11
  • videoTejas Kumar · 8:11
    CSRF and CORS Explained

    Separates the two confusable browser controls: CORS relaxes same-origin reads, CSRF abuses ambient credentials, which is why a CORS preflight is not a CSRF defence.

    S0checked 2026-11-11
  • articlePortSwigger Web Security Academy
    Insecure direct object references (IDOR)

    Explains where IDOR sits inside broken access control and why parameterized ownership checks on the server, not hidden ids, are the actual fix.

    R03R40checked 2026-11-11
  • labPortSwigger Web Security Academy
    Lab: Insecure direct object references

    A free lab where you retrieve another user's chat transcript by changing an id in the request, mirroring the BOLA test you then write against your own endpoint.

    R40R02checked 2026-11-11

Evidence record · 9-point standard

0/9

A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.

Day notes

empty

The two source formulations

verbatim · nothing summarised

Project & Stage Target

P1 | S0

Core Implementation

Study IDOR/BOLA, input validation, SQL injection parameterization, CORS vs. CSRF, and safe error contracts. Wrap the chat loop in a minimal FastAPI endpoint.

Security Lab

Prove User A cannot read or modify User B's conversation by changing conversation_id in the request (use test principal headers).

Verification & Evidence

Endpoint threat model and automated IDOR/BOLA access-control test passing.

Read Today (60m Concepts Block)

R02 (OWASP ASVS access control), R03 (OWASP API1: BOLA), R40 (OWASP WSTG API & auth testing).

---