Secure incident response operations

Separate runtime and operator roles for correctness incident for invalid RAG citations (SEV2). Runtime may only perform the narrow actions that incident commander coordinating mitigate → communicate → verify needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to team debugs for an hour without declaring — customers keep seeing wrong policy cites.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident INC-RAG-CIT-2201 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: declare early; preserve evidence; mitigation scoped; no blame in channel.

Abuse cases unique to this lab include the privilege path implied by team debugs for an hour without declaring — customers keep seeing wrong policy cites. 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 correctness incident for invalid RAG citations (SEV2) 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 correctness incident for invalid RAG citations (SEV2), the human stakeholder is incident commander coordinating mitigate → communicate → verify, and the incident id you design against is INC-RAG-CIT-2201. Re-state the oracle in your notes — INC-RAG-CIT-2201: feature flag off in 8m; customer update sent; groundedness restored — and keep the invariant visible: declare early; preserve evidence; mitigation scoped; no blame in channel. Track time_to_declare_m, time_to_mitigate_m, customer_update_sent as the scoreboard. Surface under change control: POST /v1/rag/answer. If you only have forty minutes, finish the fixture for team debugs for an hour without declaring — customers keep seeing wrong policy cites before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.