Review Project 1 provider abstraction
Jump & context
Week 13: Responsible Disclosure, Cross-Project Architecture Review & Project 1 Hardening
The five hours
- 01
Concepts & system design
60 min· read · map the mechanismR06 — Ollama security
R11 — Model provenance
R12 — Safetensors
Read the assigned sections; map the mechanism, threat model and trade-offs.
- 02
Project implementation
120 min· build · integrate · debugAudit
P1provider abstraction, model configuration, artifact provenance, safe loading, and network exposure. Integrate `C8` (Incident diagnosis & recovery recommendations): allowP1to inspect a restricted read-only slice of structured logs/traces/health signals, classify failures, and propose human-approved recovery steps.Build, integrate, debug and improve the increment in the active project.
- 03
Security lab
60 min· attack your own systemVerify
C8diagnostic tools are strictly read-only and cannot execute shell commands or mutate state without explicit approval.Test the abuse case, failure path, authorization bypass or resource limit.
- 04
Verification & evidence
30 min· test · record evidencePinned
P1model manifest +C8read-only diagnostic boundary tests.Add or run regression tests; record the 9-point evidence record.
- 05
Deliberate practice & Socratic review
30 min· explain aloud · update gapsAnswer 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.
- total5 h
Read today · inside the concepts block
R06 R11 R12API endpoints, model management, Modelfiles, and local runtime network binding security.
Model cards, tokenizer/config files, embedding usage, and repository commit-hash revision pinning.
Zero-copy safe tensor format overview vs. unsafe pickle deserialization risks.
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- docsOllama · docsOllama Documentation
Documents the API surface, model management, and Modelfile behaviour, plus the OLLAMA_HOST binding default — the network-exposure check in the P1 audit starts here.
R06checked 2026-11-11 - videoTech With Tim · 14:01Learn Ollama in 15 Minutes - Run LLM Models Locally for FREE
Demonstrates the local HTTP server and Python client against a running daemon, which is exactly the surface you probe for unauthenticated /api/generate and /api/pull access.
R06checked 2026-11-11 - videoLeon van Zyl · 14:22Run AI Models Locally: Ollama Tutorial (Step-by-Step Guide + WebUI)
Covers Modelfile authoring and the API endpoints step by step, giving the artifact-provenance trail (which base model, which parameters) that the provider abstraction must record.
R06checked 2026-11-11 - articleSnyk Labs · technical articleVulnerabilities in Deep Learning File Formats
Walks pickle deserialization to arbitrary code execution and contrasts it with safetensors' raw-tensor-only layout, which is the safe-loading argument the audit has to make per artifact format.
R12R11checked 2026-11-11 - repoProtect AI (GitHub) · CLI + librarymodelscan
Scans H5, pickle, and SavedModel artifacts for unsafe operators before load, giving the P1 audit a runnable gate for the model-loading path rather than a policy statement.
R12checked 2026-11-11
Evidence record · 9-point standard
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
emptyThe two source formulations
verbatim · nothing summarisedProject & Capability Target
Project 1 Hardening (C8 integration) | M1, M4
Core Implementation
Audit P1 provider abstraction, model configuration, artifact provenance, safe loading, and network exposure. Integrate `C8` (Incident diagnosis & recovery recommendations): allow P1 to inspect a restricted read-only slice of structured logs/traces/health signals, classify failures, and propose human-approved recovery steps.
Security Lab
Verify C8 diagnostic tools are strictly read-only and cannot execute shell commands or mutate state without explicit approval.
Verification & Evidence
Pinned P1 model manifest + C8 read-only diagnostic boundary tests.
Read Today (60m Concepts Block)
R06 (Ollama security), R11 (Model provenance), R12 (Safetensors).
---