Cover security and operational gates

Separate runtime and operator roles for Prometheus+Grafana board for AI answer API golden signals. Runtime may only perform the narrow actions that SRE watching error budget during a model bump needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to dashboard averages hide tenant Acme 40% error rate.

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

basicAuth: true

Rehearse the rollback or kill switch timed against a clock. Record actor, reason, prior revision/secret/flag, and verification query. Invariant reminder: alerts require multi-window evidence; missing scrape ≠ healthy silence.

Abuse cases unique to this lab include the privilege path implied by dashboard averages hide tenant Acme 40% error rate. 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 Prometheus+Grafana board for AI answer API golden signals 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 Prometheus+Grafana board for AI answer API golden signals, the human stakeholder is SRE watching error budget during a model bump, and the incident id you design against is MON-TENANT-BLIND-9. Re-state the oracle in your notes — inject 5% 500s for 10m → Alert AnswerErrorBurn fires; recovery clears within 15m — and keep the invariant visible: alerts require multi-window evidence; missing scrape ≠ healthy silence. Track alert_precision on game-day ≥ 0.9 and scrape_up == 1 as the scoreboard. Surface under change control: GET /metrics. If you only have forty minutes, finish the fixture for dashboard averages hide tenant Acme 40% error rate before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.