Secure runbooks operations

Separate runtime and operator roles for executable queue-backlog runbook for embedding ingestion pipeline. Runtime may only perform the narrow actions that secondary on-call clearing ingest.lag_minutes > 45 needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to runbook says 'restart something' without naming deployment or verifying lag.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident INC-INGEST-9021 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: every command is copy-pasteable; mutating steps need change ticket; verify after each step.

Abuse cases unique to this lab include the privilege path implied by runbook says 'restart something' without naming deployment or verifying lag. 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 executable queue-backlog runbook for embedding ingestion pipeline 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 executable queue-backlog runbook for embedding ingestion pipeline, the human stakeholder is secondary on-call clearing ingest.lag_minutes > 45, and the incident id you design against is INC-INGEST-9021. Re-state the oracle in your notes — drill INC-INGEST-9021: lag 60→5 minutes in ≤ 25m following runbook v1.4 — and keep the invariant visible: every command is copy-pasteable; mutating steps need change ticket; verify after each step. Track drill_completion_minutes and lag_minutes as the scoreboard. Surface under change control: ingest worker + queue metrics. If you only have forty minutes, finish the fixture for runbook says 'restart something' without naming deployment or verifying lag before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.