[ SYSTEM_DIRECTORY / SECURITY_& TRUST — GOVERNANCE ]

Security & Trust — Governance

Cryptographic trust infrastructure designed to keep your source code private.

+ + + +
Certification
SOC 2 Type II
Ongoing
Data residency
EU — Stockholm
GDPR compliant
Transport
mTLS pinned
Agent and CLI channels
Code Access
Read-Only OAuth
Zero write permissions
01

Verifiable Audits.

A historical ledger of compliance events is cryptographically signed using a local Merkle Tree, rendering your historical records tamper-proof and mathematically incontestable.

02

Isolation by Design.

All endpoint telemetry is secured via bidirectional mTLS with cryptographic device pinning, and multi-tenant data is strictly partitioned by organization-isolated database structures.

03

Zero Code Storage.

Code scanning is performed dynamically in temporary memory on the build runner or CLI host. Mima never writes, stores, or transmits your raw codebase files.

04

GitHub Read-Only Isolation.

Connecting repository data uses read-only OAuth flows. Mima has zero permission to write code, modify pull requests, or alter your repository settings.

Each compliance snapshot is hashed bottom-up into a Merkle tree. The root is signed and appended to your compliance ledger. Click verify to walk the path.

[ Cryptographic Merkle Hash Path ]
H_0: 8f2bH_1: 4a9dH_2: e2c9H_3: 1b7fH_01: 9c1dH_23: f4a8sha256(7f3a9b1c...e91c4d)
STATE NODES: 4PROOF DEPTH: 3 LEVELS
[ Audit Receipt ]UNCHECKED
TenantACME Holdings GmbH
Device keydev-9b1c-4d8e-7f3a
Merkle rootsha256(7f3a…e91c)
Certificateclient-mTLS verified
MIMA-SIG: 3045022100e4ab78c3b9de281f9b37583a21dcf982e04db1a7f39b1c4e91c2d0f01a3d3c