# Isis Compliance Incident Response Runbook

Last Updated: 2026-02-24  
Scope: Isis retention/provenance, policy metadata governance, regional
compliance, and auditability incidents  
Primary Owners: `@oshun/security`, `@oshun/devops`, `@oshun/isis-team`

## Purpose

Provide deterministic support and incident-response procedures for compliance
events affecting Isis workflows and outputs:

1. Retention/deletion policy drift or stale-record accumulation.
2. Provenance lineage gaps or missing metadata links.
3. Missing/invalid governance or licensing metadata on outputs.
4. Region/retention policy violations for enterprise tenants.

## Incident Intake (Support First Response)

Collect before escalation:

- Environment and affected tenant/project
- Detection source (support ticket, monitor, audit request)
- Affected workflow/output IDs
- First observed timestamp (UTC)
- Compliance requirement impacted (retention, provenance, licensing, residency)
- Regulatory/contractual deadline sensitivity
- Current customer impact (export blocked, legal hold, audit exception)

## Severity Classification

| Severity | Trigger                                                               | SLA (Ack)      |
| -------- | --------------------------------------------------------------------- | -------------- |
| SEV-1    | Confirmed data-retention/legal-hold breach with external exposure     | 15 min         |
| SEV-2    | Sustained compliance control failure across active production traffic | 30 min         |
| SEV-3    | Isolated policy finding with bounded scope and immediate remediation  | 2 hours        |
| SEV-4    | Documentation/reporting discrepancy without runtime control failure   | 1 business day |

## 15-Minute Triage Checklist

1. Validate compliance baseline report:

```bash
STRICT=true \
ISIS_DATABASE_URL="postgres://..." \
scripts/isis/verify_data_retention_compliance.sh
```

2. Inspect retention policy and application state:

```bash
curl -s "$ISIS_OUTPUT_REGISTRY_BASE_URL/api/v1/policies" \
  -H "X-API-Key: $ISIS_COMPLIANCE_API_KEY" | jq

curl -s -X POST "$ISIS_OUTPUT_REGISTRY_BASE_URL/api/v1/policies/apply" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ISIS_COMPLIANCE_API_KEY" \
  -d '{"dryRun":true}' | jq
```

3. Check provenance integrity remediations:

```bash
curl -s -X POST "$ISIS_OUTPUT_REGISTRY_BASE_URL/api/v1/outputs/admin/provenance/backfill" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ISIS_COMPLIANCE_API_KEY" \
  -d '{"dryRun":true,"limit":200}' | jq
```

4. Validate governance and metadata policy engines:

```bash
pnpm --filter @isis/web exec vitest run \
  src/security/content-governance-policy-utils.spec.ts \
  src/security/model-provenance-licensing-utils.spec.ts \
  src/security/region-retention-compliance-utils.spec.ts \
  --reporter=dot
```

5. Determine whether incident is:
   - runtime policy-enforcement failure,
   - historical data quality/backfill gap,
   - configuration drift,
   - reporting-only discrepancy.

## Containment Playbooks

### A. Retention and Deletion Non-Compliance

1. Pause non-essential bulk exports for affected tenant/project.
2. Execute retention apply in controlled mode (staging first, then production).
3. Re-run compliance verification report and compare deltas.
4. If unresolved, open SEV incident and assign legal/compliance liaison.

### B. Provenance/Lineage Integrity Gaps

1. Run provenance backfill in dry-run, then execute mode after validation.
2. Validate no orphan provenance rows or broken links remain.
3. Sample affected outputs and confirm provenance completeness in Outputs
   UI/API.

### C. Metadata Governance Violations

1. Force strict policy mode for impacted tenants/projects where configured.
2. Require explicit review acknowledgement for non-block findings.
3. Persist reviewed compliance dispositions in output metadata.
4. Block external distribution for unresolved `block` findings.

## Recovery Validation

Compliance incident can close only when all are true:

- Retention compliance report passes or documented risk acceptance is approved.
- Provenance and lineage integrity checks are clean for incident scope.
- Governance/licensing/region-retention policy evaluations pass or have approved
  disposition records.
- Audit artifacts are attached to incident ticket.

## Support Escalation Matrix

| Scenario                                           | Escalate To                               |
| -------------------------------------------------- | ----------------------------------------- |
| Potential legal/regulatory breach                  | `@oshun/security` + legal/compliance lead |
| Multi-tenant metadata integrity failure            | `@oshun/security` + `@oshun/isis-team`    |
| Retention cleanup/backfill execution failures      | `@oshun/devops` + `@oshun/isis-team`      |
| Policy engine regression in studio/output surfaces | `@oshun/security` + `@oshun/frontend`     |

## Communication Templates

### Incident Start

`Isis compliance incident declared (SEV-X): <control area>. Containment started. Next update in 15 minutes.`

### Incident Update

`Isis compliance incident update: <affected scope>, <checks completed>, <remaining risk>, <ETA>.`

### Incident Resolved

`Isis compliance incident resolved: remediation validated, evidence archived, and follow-up controls assigned.`

## Evidence Checklist

- Retention compliance report JSON artifact.
- Backfill/apply command outputs and timestamps.
- Affected output/workflow sample IDs and final disposition.
- Incident timeline, owner assignments, and post-incident actions.

## Related Artifacts

- `docs/domains/isis/runbooks/data-retention-compliance.md`
- `apps/isis/output-registry/src/routes/policies.ts`
- `apps/isis/output-registry/src/routes/outputs.ts`
- `apps/isis/web/src/security/content-governance-policy-utils.ts`
- `apps/isis/web/src/security/model-provenance-licensing-utils.ts`
- `apps/isis/web/src/security/region-retention-compliance-utils.ts`
