Set privacy and network egress boundaries

Separate runtime and operator roles for Ollama-backed local router with policy-controlled cloud fallback. Runtime may only perform the narrow actions that legal analyst summarizing NDAs that must not leave the laptop by default needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to fallback silently ships full NDA text to cloud when Ollama is down.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident LOCAL-FALLBACK-PII-03 should be impossible if these controls hold. Output allowlists and schema checks stay in force on error paths.

Rehearse the rollback or kill switch timed against a clock. Record actor, reason, prior revision/secret/flag, and verification query. Invariant reminder: cloud fallback requires explicit policy flag + redaction pass; local p95 ≤ 6s for 512 tokens.

Abuse cases unique to this lab include the privilege path implied by fallback silently ships full NDA text to cloud when Ollama is down. Prove a read-only role cannot mutate. Break-glass tokens expire; leftover tokens fail the drill. Dependency pin/digest story matters when images or models move under you. Document how to rotate the credential that Ollama-backed local router with policy-controlled cloud fallback uses without a full outage window longer than your dual-run plan. Security evidence is part of ship, not an appendix nobody reads.

List network egress destinations and justify each. Ensure debug endpoints are off by default in the shipping config. Verify that error responses do not echo secrets or raw stack frames to clients. For multi-tenant paths, add a cross-tenant probe fixture. Time the rollback drill twice — once with the author, once with a peer. Store the drill transcript beside the threat notes for the incident id. In this chapter the product is Ollama-backed local router with policy-controlled cloud fallback, the human stakeholder is legal analyst summarizing NDAs that must not leave the laptop by default, and the incident id you design against is LOCAL-FALLBACK-PII-03. Re-state the oracle in your notes — local llama3.2:3b answers fixture brief at ≥ 25 tok/s; fallback path logs reason=local_timeout — and keep the invariant visible: cloud fallback requires explicit policy flag + redaction pass; local p95 ≤ 6s for 512 tokens. Track local_share ≥ 0.8 and cloud_fallback_with_pii == 0 as the scoreboard. Surface under change control: POST http://127.0.0.1:11434/api/generate. If you only have forty minutes, finish the fixture for fallback silently ships full NDA text to cloud when Ollama is down before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.