Security at DispatchDesk
DispatchDesk implements SOC 2-aligned controls. We have not completed a SOC 2 audit observation period, and no SOC 2 report is available yet. Below we distinguish control design — what is implemented and verifiable today — from operating effectiveness, which requires an audit period we have not yet completed.
Section A — Control design (implemented today)
Most rows below are wired to a runtime check that runs live when this page renders — those states are computed at request time, not written by hand. Rows labelled Attested instead surface the most recent recorded control attestation from the append-only evidence log (a dated statement), not a live pass/fail probe.
| Control | State | Live evidence |
|---|---|---|
| Encrypted backup + restore round-trip (self-test verified) | In progress | In progress — no restore-proof artifact found (expected WP-02 selftest artifact at /app/data/evidence/backup_selftest.json). (checked 2026-08-10T23:35:11.812Z) |
| Off-site nightly encrypted backups (Backblaze B2, object-lock) | In progress | In progress — no off-site nightly backup target wired in this deploy (Backblaze B2 bucket + object-lock + nightly schedule pending). The encrypted backup/restore tooling is proven locally by the row above; off-site scheduling is the remaining step. (checked 2026-08-10T23:35:11.812Z) |
| Tenant isolation — forced row-level security on tenant data | Implemented | Implemented — live pg_class check: all 10 crown-jewel tenant tables carry ENABLE + FORCE row-level security (customer, job, service_call, dispatch_attempt, credit_ledger, call_transcript, escalation, call_outcome, wallet, token_ledger). (checked 2026-08-10T23:35:11.812Z) |
| Lead data storage — Postgres under RLS + TTL, legacy flat file retired | In progress | In progress — PG lead table not present yet. (checked 2026-08-10T23:35:11.816Z) |
| Administrative access — MFA + private tailnet only | Attested | Attested — the MFA/tailnet admin-access attestation recorded as an evidence_event attestation (latest 2026-07-24T23:01:17.745Z). This row shows the recorded statement, not a live pass/fail probe. (checked 2026-08-10T23:35:11.819Z) |
| Secret management — secrets in the platform secret store, rotations recorded | Attested | Attested — the secret-management/rotation record recorded as an evidence_event attestation (latest 2026-07-24T23:01:17.745Z). This row shows the recorded statement, not a live pass/fail probe. (checked 2026-08-10T23:35:11.820Z) |
| Append-only security-evidence log with daily hash anchoring | Implemented | Implemented — append-only evidence_event log verified live: 2 row(s), hash chain valid; latest daily anchor 2026-07-24 covers 2 event(s), hash 7e902328164447ab…. (checked 2026-08-10T23:35:11.821Z) |
| Incident-response, breach-notification and rollback runbooks | Implemented | Implemented — incident-response, breach-notification, rollback and alert-class runbooks present (4 files under docs/runbooks/, checked live). (checked 2026-08-10T23:35:11.824Z) |
Section B — Operating effectiveness
Observation period not started. No attestation exists.