Secure disaster recovery operations

Separate runtime and operator roles for regional RAG platform restore with PostgreSQL + object storage + vector indexes. Runtime may only perform the narrow actions that DR lead failing over region A → B within RTO 2h / RPO 15m needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to traffic cut before vector rebuild finishes — fluent ungrounded answers.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident DR-2026-07-30 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: restore validates citation gold set before traffic; corrupt snapshot rejected.

Abuse cases unique to this lab include the privilege path implied by traffic cut before vector rebuild finishes — fluent ungrounded answers. 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 regional RAG platform restore with PostgreSQL + object storage + vector indexes 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 regional RAG platform restore with PostgreSQL + object storage + vector indexes, the human stakeholder is DR lead failing over region A → B within RTO 2h / RPO 15m, and the incident id you design against is DR-2026-07-30. Re-state the oracle in your notes — drill DR-2026-07-30: restore completes 97m; gold citation_precision ≥ 0.95 — and keep the invariant visible: restore validates citation gold set before traffic; corrupt snapshot rejected. Track rto_minutes, rpo_minutes, citation_precision_post_restore as the scoreboard. Surface under change control: region-b https://b.rag.example. If you only have forty minutes, finish the fixture for traffic cut before vector rebuild finishes — fluent ungrounded answers before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.