Security

Security and trust boundaries

Plain-language summary of how MUON treats custody, authority, and evidence — including what is shipped today and what is still open.

Talk to us about enterprise fit →

Last updated 2026-08-01. This page describes the product posture, not a certification.

Local-first custody

MUON runs on your machine. Mission data, memory, and audit events stay in your local brain database unless you explicitly export or sync them. MUON does not custody your vendor CLI credentials — Claude Code, Codex, Cursor, and OpenCode authenticate with their own vendor flows.

Governed actions, not blind automation

Sensitive edits, shell commands, and ship gates require human approval or an explicit standing grant you can revoke. Agents receive least-privilege profiles compiled per role and per vendor. MUON refuses to auto-approve on a schedule or from an unattended event.

Audit evidence

Approvals, gate reads, and operator resolutions are stamped with principal identity and request ids where the schema supports it (migration 0043). Event rows are append-only. A full procurement-grade audit UI, MCP export, and webhook stream are follow-ups — the columns exist; the enterprise surface is not complete.

Secret handling in logs

Error and diagnostic paths pass through a shared redactor that strips bearer tokens, key-shaped strings, and control characters before anything reaches stderr or CI. A build-time scan fails if secret-handling files log without going through it.

Attestation status

Not yet attested: SOC 2 Type II, ISO 27001, and third-party penetration test reports are not available for v0. Internal adversarial tests cover gate refusal, MCP tool annotation, and vendor profile containment. Results are tracked in-repo, not by an external auditor.

Shared responsibility

You are responsible for: keeping vendor CLIs updated, protecting your machine and operator token, reviewing approvals, and not committing secrets into repositories MUON governs. MUON is responsible for: compiling deny-first profiles, fencing memory partitions, and failing closed when authority cannot be verified.

Vulnerability disclosure

Report security issues to security@muonlabs.dev (placeholder — replace before public launch). We aim to acknowledge reports within 3 business days and provide a remediation timeline within 14 days for confirmed issues affecting confidentiality, integrity, or availability of governed actions.

Need a deeper review for procurement? Start with enterprise contact — we will share architecture docs and the current test posture under NDA.

Enterprise