Compliance readiness (SOC 2, HIPAA)
See each SOC 2 and HIPAA Security Rule control with its live state computed from the product, export the evidence with the matrix filled in, run in PHI mode (no model text stored, run inputs purged after N days, every run view recorded), and confirm the quarterly access review.
Minctrl makes your company audit-ready: every SOC 2 (TSC 2017 — Security, Availability, Confidentiality) and HIPAA Security Rule (45 CFR 164.308–316) control is mapped to the feature that implements it, the evidence Minctrl produces, and what your company must do itself. It does not issue a SOC 2 report or a HIPAA attestation, and Minctrl holds no SOC 2 report of its own: a report comes from an independent auditor who examines your controls, your signed policies, training records, risk assessment and vendor reviews over a period. That part is yours.
Everything here is on Settings → Compliance (/settings/compliance). The matrices, policy
templates, a subprocessor list template and a BAA checklist are in the repository under
docs/compliance/.
Live control status
GET /compliance/status (owner, admin, or an API key with audit:read) reads each signal from the
product:
| Signal | ok when |
|---|---|
| SSO required | the SSO connection is on and required |
| MFA through your IdP | never — it is your IdP's; with SSO required it shows not read (attest it with the IdP's configuration) |
| Separation of duties / publishing needs a green suite | the governance switch is on |
| Audit chain verifies | every link and every RFC 3161 token verifies |
| External timestamp | a granted stamp within twice the interval |
| SIEM delivery | at least one sink delivering, none failing |
| Last dump / last restore test | read from the backup report (MINCTRL_BACKUP_REPORT_FILE, else MINCTRL_BACKUP_REPORT_URL): a dump within 8 h with an off-site copy; a PASS within 8 days. Older is stale |
| API key rotation | no active key older than 90 days |
| Members without activity | every active member signed in within 90 days |
| Quarterly access review | one confirmed within 100 days and none open |
| Connectors live vs shadow | always — shows how many irreversible connectors are bound live |
| PHI mode, run-view logging, retention, model text storage | on (text storage: off) |
Each signal is ok, attention, or not_read: it could not be read, or Minctrl cannot see it.
not_read is never green. A control shows the worst of its signals; a control with no product
signal shows company — its evidence is your own document. A failing signal never hides the rest.
Backups are read from a report the backup scripts write. On the stock server
(infra/prod) backup.sh and restore-test.sh write /var/backups/minctrl/report/report.json
after every good dump and every restore test, and the api container reads it read-only at
MINCTRL_BACKUP_REPORT_FILE=/run/minctrl/backup-report/report.json (set in
infra/prod/docker-compose.yml):
{"version": 1, "generated_at": "2026-11-01T06:00:07Z",
"last_dump": {"at": "2026-11-01T06:00:05Z", "name": "minctrl-20261101T060000Z-scheduled.dump",
"size": 81234, "offsite": true},
"last_restore_test": {"at": "2026-11-01T04:30:00Z", "result": "PASS",
"dump": "minctrl-20261101T000000Z-scheduled.dump", "source": "s3:minctrl-backups/dumps"}}Elsewhere, point MINCTRL_BACKUP_REPORT_FILE at a file in that format, or set
MINCTRL_BACKUP_REPORT_URL to a URL answering it (the file wins when both are set). A dump older
than 8 h or a restore test older than 8 days is stale (attention); no report, a missing file or
one that does not parse is not read. The Helm chart's CronJobs write no report: on Kubernetes
the evidence is the Jobs' logs unless you publish one.
Evidence pack
POST /audit-chain/evidence-pack now carries a compliance/ folder, every file hashed in
manifest.json:
| File | Contents |
|---|---|
controls.json | every signal and control with its state at generation time |
matrix.csv, matrix.md | the control matrix filled with the live states |
access-review.json | members and roles now with their last sign-in, and the period's access reviews |
change-log.json | process_published / process_rolled_back entries of the period (seq + hash), and policy changes |
incident-events.json | the period's incident-relevant entries (SLA breaches, failing sinks, break-glass sign-ins, suspensions, revoked keys…) |
HIPAA data handling (PHI mode)
PUT /compliance/settings (owner or admin; each switch that moves is a policy_changed entry):
| Switch | What it does |
|---|---|
phi_mode | model prompt/output text is never stored (only model, hashes, tokens, cost, latency), run inputs and the model content of run traces are purged after the retention, every opening of a run is recorded, and the audit chain receives no form, extracted or decided values (see below). Forces the two below. The page shows a banner until Require SSO is on. |
phi_retention_days (1–3650, default 30) | the compliance worker (hourly; COMPLIANCE_TICK_SECONDS) purges finished runs older than this: it empties their inputs, deletes their documents, and removes from their trace every LLM step's output values, its tool calls' inputs and results, its proposals' inputs, what extraction read from documents and the values signed at review gates. Tool names, hashes, tokens, cost, decisions and the step path stay. POST /compliance/phi/purge runs it now. One phi_inputs_purged entry names the runs and counts what was removed per run — never a value, a key name or a hash. |
phi_access_logging | GET /process-runs/{id} records phi_run_viewed (who, which run) before the run is shown — once per viewer and run per 15 minutes (PHI_VIEW_LOG_WINDOW_SECONDS). If the entry cannot be written the run is not shown (503). |
llm_store_text | whether model prompt/output text may be stored; off and locked in PHI mode (409 if asked). |
The audit chain in PHI mode. The chain is permanent, so while PHI mode is on, gate_signed,
gate_approval_recorded, gate_signal_failed and extraction_reviewed entries are written with
a form's field names and count instead of its values, an extraction review's corrected
fields with their confidence but without the model's or the reviewer's value, and a decision's
table and matched rules without its outputs. Entries written before PHI mode was turned on keep
what they held. The signer's free-text note is kept as written — do not put PHI in it.
Not reached by the purge — account for them in your risk analysis: a run still waiting at a gate
or running (it needs its inputs and trace to resume), a finished run inside its retention
(its trace and inputs are complete until it ages past it), gate form values of gates that do not
review an extraction (kept in the run's decisions and notes), connector results of declared tool
steps, Temporal's workflow history, backups taken before the purge (they age out), and anything
a connector sent elsewhere. Sign a BAA
before PHI enters Minctrl (docs/compliance/baa-checklist.md).
Quarterly access review
At the start of each quarter Minctrl opens an access review for every company that existed before
the quarter began: a snapshot of members and roles with their last sign-in, recorded as
access_review_opened. Each owner gets a reminder through the same notification channels as gate
notices (email, Slack, Teams; their preferences and quiet hours). An owner may also open one at any
time. The owner confirms the list they see; if membership changed since it was shown the
confirmation is refused (409) and the new list is shown. access_review_confirmed records who,
the list's hash and size, and the note.
| Endpoint | Who |
|---|---|
GET /compliance/access-reviews | owner, admin, audit:read key |
GET /compliance/access-reviews/current | owner, admin |
POST /compliance/access-reviews | owner |
POST /compliance/access-reviews/{id}/confirm {snapshot_hash, note?} | owner |
Single sign-on and SCIM
Sign in with your company's identity provider (SAML 2.0 or OpenID Connect — Okta, Microsoft Entra ID, Google Workspace, Auth0), require it for your domains, map IdP groups to roles, and provision members with SCIM 2.0.
Triggers — webhooks and schedules
Start runs of a saved process from another system or on a cron — a URL that is its own credential, an optional HMAC signature, idempotent retries, and a schedule that fires each slot exactly once.