Security & Data Handling
How Monad protects your data in transit and at rest, how it handles and retains that data, and where to manage access.
Encryption in transit
All traffic to and from Monad is encrypted with TLS. This covers push inputs (HTTP, OTLP, Splunk HEC, syslog), pull connections to your sources, and delivery to your output destinations. In self-managed deployments you provide the TLS certificates that terminate traffic at the gateway and HTTP input — see TLS certificates.
Encryption at rest
Sensitive data that Monad stores is encrypted at rest using AES-256-GCM, with an envelope-encryption model:
- Each Monad organization is issued its own Data Encryption Key (DEK).
- Every DEK is wrapped by a Key Encryption Key (KEK) before it is stored; unwrapping a DEK requires the KEK.
Who holds the KEK depends on how Monad is deployed:
- Monad Cloud (SaaS): Monad manages the KEK on your behalf.
- Self-managed (Helm): you supply and are the sole custodian of the KEK, which never leaves your cluster. Enable key encryption and provide the key material as described in Key encryption key.
Tenant isolation
Monad Cloud is a multi-tenant service in which each customer's data is logically isolated:
- The organization is the tenant boundary. Your inputs, outputs, transforms, enrichments, pipelines, secrets, and data are scoped to your Monad organization. Users, roles, and API keys are organization-scoped as well — a credential issued for one organization cannot read or act on another organization's resources.
- Cryptographic separation at rest. Each organization is issued its own Data Encryption Key (see Encryption at rest), so each tenant's data at rest is protected under a distinct key.
- Enforced on every request. Access is checked against organization RBAC for each API and UI operation, so the isolation boundary holds consistently across the platform.
Data handling & retention
Monad is a streaming pipeline, not a data store. Records are ingested, transformed, and routed to your destinations in-stream:
- Monad does not maintain a long-term datastore of your event data. In-flight records are buffered, encrypted at rest, until they are delivered (see Reliability & Delivery). If a destination or pipeline step is erroring, its buffered records are retained and retried until delivery succeeds or you purge them; there is no fixed expiry. Records are not retained after delivery.
- Routing is storage- and vendor-neutral: your data is delivered only to the outputs you configure. Monad does not require you to land it in a Monad-owned store, and cloning one event to multiple destinations does not create a Monad-side copy of that data.
Access control & auditing
- Role-based access control (RBAC). Scope what each user can view, create, modify, or delete with default or custom roles — see Organization RBAC.
- Single sign-on (SSO). Connect your identity provider for centralized authentication — see SSO.
- API keys. Issue scoped keys for programmatic access — see API Keys.
- Audit logs. Administrative and configuration actions are recorded and retrievable through the Monad API — see the Audit Logs API.
Access to your AWS accounts
AWS inputs that you configure with an IAM role ARN (for example, SQS S3) reach your account by assuming a role you create and control. No long-lived AWS keys are involved on either side.
- You define the access. Your role's trust policy names Monad's delegate role,
arn:aws:iam::339712996529:role/monad-app, and requires your Monad organization ID as thests:ExternalId(in a sub-org, the sub-org's ID; see Which organization ID to use). The permissions policy you attach is the complete set of actions Monad can take, and AWS enforces it on every call. - How Monad assumes the role. The connector uses its own short-lived, automatically rotated workload identity to assume the delegate role, then assumes your role with your organization ID as the external ID.
Monad adds no session policy or session tags, and each session is named
monad_followed by the connector's node ID, so its activity is easy to isolate in your CloudTrail. - Session credentials. Assumed-role credentials use the AWS default lifetime of 15 minutes. They are held only in the connector process's memory, are never written to disk, a database, a secrets store, or logs, and are replaced by a fresh role assumption when they expire.
- The external ID is not a secret. Monad uses your organization ID, following AWS guidance for third-party access, to prevent another Monad customer from causing Monad to assume your role.
- Revoking access. Remove Monad's delegate role from your role's trust policy to stop new sessions. Revoke active sessions on the role in the IAM console ends any sessions already issued.
Compliance
Monad undergoes an independent SOC 2 Type II examination on an annual basis, covering the Security and Availability Trust Services Criteria.
The current SOC 2 report, along with Monad's other security documentation and certifications, is available through the Monad Trust Center. Reports are released to customers and prospects under NDA — request access from the Trust Center.