Security Overview
Muin's security model: role-based access, audit logging, two-factor authentication, data encryption, and compliance controls.
Muin is built on a privacy-first, security-first foundation. Every tenant’s data is isolated at the database level, all traffic is encrypted, and every sensitive action is logged in a tamper-evident audit trail.
Access Control
Role-Based Access (RBAC)
Every user in Muin has a role that determines what they can see and do. Roles are defined at the organization level and scoped to modules. See Roles & Permissions for the full role matrix.
Multi-Factor Authentication (MFA)
MFA can be enforced organization-wide from Settings → Security → Authentication:
- TOTP (Time-based One-Time Password) — Google Authenticator, Authy, or any TOTP app
- SMS OTP — one-time codes sent by text message
- Passkeys — biometric / hardware key authentication (WebAuthn)
Admins can require MFA for all users or only for users with elevated permissions.
Session Management
Active sessions are listed under Settings → Security → Sessions. Admins can revoke any session remotely. Users can view their own sessions from their profile.
Session tokens expire after 7 days of inactivity by default (configurable per tenant).
Audit Trail
Every sensitive action in Muin is recorded in the audit log — who did what, when, from which IP address. See Audit Logs for full details.
Data Encryption
- At rest: All data is encrypted using AES-256 at the storage level.
- In transit: All connections use TLS. HTTP connections are redirected to HTTPS, and the application’s database connections require TLS with certificate verification.
- Sensitive fields: Personal and financial fields (SSNs, dates of birth, phone numbers, addresses, tax IDs, payment credentials, integration tokens, MFA seeds) receive a second, independent layer of AES-256-GCM authenticated encryption at the application layer before they are written to the database — so a database backup alone does not expose them.
Privacy & Data Residency
Muin uses AWS Bedrock for AI features — your data is never sent to third-party AI providers. See Why Privacy-First AI Matters for the architectural reasoning.
Data residency: all tenant data is stored in US-East (N. Virginia) by default. Contact support for EU or custom residency requirements.
Compliance Controls
| Control | Available |
|---|---|
| Role-based access | Yes |
| MFA enforcement | Yes |
| Audit log export | Yes |
| GDPR data export / deletion | Yes |
| SOC 2 audit readiness | Yes (see SOC Audit) |
| Custom data retention | Yes |
Next Steps
- Roles & Permissions — configure what each role can access
- Audit Logs — view and export the activity trail