MitDesk — Compliance & Evidence
| Show what your AI did: a tamper-evident audit chain, Art. 30 records and data-subject exports. |
Technical name minddesk_compliance.
Edition: Business and above. See Editions and how the modules fit together.
This module adds evidence to the audit log. It helps you answer an auditor or a data protection officer. It supports your own compliance work. It is not a certification.
What it adds
- A hash chain. Every audit row gets a content hash when it is written. A background job (every 5 minutes) links the rows into one chain, so the chain can be a few minutes behind.
- Verify the chain. Verify chain now recomputes everything and lists every break it finds.
- Retention. Each artifact has a retention time. The default is to keep for ever. Pruning writes a reseed anchor, so the gap is visible.
- Legal holds. A hold on a data subject and/or a date range beats retention. A hold with neither is a global freeze.
- Exports. Processing-record support (Art. 30), a data-subject (DSAR) export, an AI governance report, an egress attestation and erasure requests.
- Controls scan. A fixed set of ISA 240 checks over accounting entries and point-of-sale data. It does not use a model.
Limits that always apply
- Audit rows cannot be edited. Writing or deleting an audit row is refused, also for privileged users. Only chain maintenance may write the chain fields.
- Financial rows stay. Pruning removes old non-financial rows. Financial rows are kept.
- Signing fails closed. If you set up anchor signing (Ed25519) and the key cannot be loaded, MitDesk raises an error. It does not write unsigned anchors.
Where you find it
- Cockpit ▸ Compliance
- Governance ▸ Compliance: Audit Anchors, Evidence register, Integrity Incidents, Processing-record support, DSAR export, Erasure requests, AI governance report, Retention policies, Legal holds, Egress attestation
What to know
- Tamper-evident is not tamper-proof. The chain shows later edits and deletions. It cannot protect you if the server itself is taken over, because the signing key lives there.
- Anchors are hashes. The optional Ed25519 signature shows that the key holder signed those bytes. It is not a qualified electronic signature or a trusted timestamp.
Requirements
Needs minddesk.
Related
- Compliance support
- Audit and evidence
- The modules: every module and what it needs.
- Installing MitDesk: how to add it.