Secure postmortems operations

Separate runtime and operator roles for blameless postmortem for tokenizer-induced summarization outage. Runtime may only perform the narrow actions that EM facilitating review of INC-SUM-TOK-87 needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to action 'be more careful' with no owner — recurrence in 6 weeks.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident INC-SUM-TOK-87 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: actions are owned, dated, verifiable; contributing factors include process not only code.

Abuse cases unique to this lab include the privilege path implied by action 'be more careful' with no owner — recurrence in 6 weeks. 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 blameless postmortem for tokenizer-induced summarization outage 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 blameless postmortem for tokenizer-induced summarization outage, the human stakeholder is EM facilitating review of INC-SUM-TOK-87, and the incident id you design against is INC-SUM-TOK-87. Re-state the oracle in your notes — postmortem published with 3 actions; action A1 verified by test that fails on old tokenizer pin — and keep the invariant visible: actions are owned, dated, verifiable; contributing factors include process not only code. Track actions_closed_on_time and recurrence_90d as the scoreboard. Surface under change control: summarization service. If you only have forty minutes, finish the fixture for action 'be more careful' with no owner — recurrence in 6 weeks before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.