Set up the development environment

1. 01

   Concepts & system design

   60 min· read · map the mechanismtimer

   R06 — Ollama API & deployment security

   R39 — OWASP Threat Modeling: assets & trust boundaries

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

2. 02

   Project implementation

   120 min· build · integrate · debugtimer

   Set up dev environment, Python project structure, Git workflow, and local Ollama runtime. Draw initial data-flow diagram (user -> application -> model -> tools/storage). Record exact model/runtime version and source.

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

3. 03

   Security lab

   60 min· attack your own systemtimer

   Inspect listening ports (netstat/ss/lsof) and ensure the Ollama runtime is bound to 127.0.0.1 and not exposed to untrusted networks.

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

4. 04

   Verification & evidence

   30 min· test · record evidencetimer

   Commit environment manifest, model version record, and initial attack-surface list.

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

5. 05

   Deliberate practice & Socratic review

   30 min· explain aloud · update gapstimer

   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

• R06Ollama Documentation↗ docs.ollama.com

  API endpoints, model management, Modelfiles, and local runtime network binding security.

• R39OWASP Threat Modeling↗ owasp.org

  Four-question framework & STRIDE: assets, trust boundaries, data flows, threat identification, and mitigation tracking.

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

• docsOWASP Foundation
  Threat Modeling

  Gives the four-question framework and STRIDE prompt set you apply to the user -> application -> model -> tools/storage diagram, so threat identification starts from data flows and trust boundaries instead of a vulnerability list.

  R39S1moved 2026-11-11
• videoNetsec Explained · 21:49
  STRIDE Threat Modeling for Beginners - In 20 Minutes

  Walks a diagram element by element applying the six STRIDE categories, which is exactly the pass you run over each trust boundary in your first data-flow diagram.

  R39S1checked 2026-11-11
• videoTech With Tim · 14:02
  Learn Ollama in 15 Minutes - Run LLM Models Locally for FREE

  Shows pulling, running, and calling a local model so you can record the exact model tag and runtime version, and see which local port the daemon binds for the runtime half of the diagram.

  R06checked 2026-11-11
• articlenathanleclaire.com
  Playing Around With Ollama for Local LLM

  Hands-on tour of the local API surface (generate/chat endpoints, model listing) from a shell, which is the fastest way to see what your local runtime actually exposes before you build on it.

  R06M1checked 2026-11-11
• repoGitHub
  OWASP/threat-dragon

  Open-source data-flow diagram and STRIDE editor whose model (trust boundaries, flows, per-element threats) is the artifact day 1 asks you to produce.

  R39S1checked 2026-11-11

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