Security

This page describes the concrete security controls applied across the Varolio platform. Controls are listed per layer; where a control differs by deployment scenario, the difference is noted.

Edge protection

• AWS WAF fronts the public API surface with AWS managed rule groups — IP reputation list, common rule set, known bad inputs, and SQLi — plus per-IP rate limiting. Blocked-request spikes raise CloudWatch alarms, and WAF logs are retained with sensitive headers (authorization, cookies) redacted.
• TLS 1.2+ is enforced on every external boundary (port 443). Client-side TLS terminates at an internet-facing Application Load Balancer with an ACM certificate; plain HTTP is redirected to HTTPS.
• Webhook authenticity is verified per channel: Microsoft Graph validationToken, Svix signatures for Recall.ai (Notetaker), and HMAC verification for WhatsApp.

Encryption

Tenant isolation

• Every query is scoped by account and workspace at minimum, and the caller's membership in both is verified on every request; a request without a tenant scope is rejected at the API boundary. Many operations enforce stricter scopes on top — down to the specific inbox or individual user (for example, reading a thread requires access to that inbox, not just the workspace).
• Object-storage keys are namespaced per workspace — the API never issues a key for a workspace other than the caller's.
• Integration credentials are stored per tenant and resolved at runtime for the requesting workspace only.
• In Dedicated Cloud and Cloud-Prem, account- and VPC-boundary isolation applies on top of all the application-layer controls.

Access control within a tenant

Tenant isolation is only the outer boundary — inside a workspace, access follows the customer's organizational hierarchy:

• User-scoped data — threads, meetings, and mailbox content are scoped to the individual user (inbox owner), not shared tenant-wide. A user sees their own data plus what their role and team membership explicitly grant.
• Organizational RBAC — permissions are managed at the account, workspace, and inbox level. Team structure can be administered manually in Varolio, or
• Synced from the organization's IAM — Varolio can connect to the customer's directory (for example Microsoft Entra ID / Active Directory) and derive team membership and access from existing security groups, so access reviews stay in the customer's own IAM.

Identity and access

• User authentication via the customer's identity provider over OIDC SSO (for example Microsoft Entra ID).
• API authorization via JWTs carrying account-, workspace-, and inbox-scoped RBAC.
• Rate limiting at two layers: per-IP at the WAF edge, plus application-layer limits backed by Redis.

Operator access

• Varolio operator access is SSO-gated and uses short-lived credentials; there is no inbound access from the public internet to operator tooling.
• In Cloud SaaS and Dedicated Cloud, operator activity is recorded in Varolio's cloud audit logs; dedicated environments have their own per-environment audit trail.
• In Cloud-Prem, Varolio operates through a customer-created, revocable identity (IAM role / service account / service principal) with scoped Kubernetes RBAC, and every action lands in the customer's own audit log in real time. Revoking the grant is a one-line change on the customer's side.

Release integrity

• Every production change passes a CI suite and peer-reviewed pull-request approval before deployment.
• Deploys are GitOps-driven rolling updates per environment; the API tier runs multiple replicas so requests are not interrupted, and rollback to the previous revision is available.
• Dedicated and Cloud-Prem environments receive the same builds through the same pipeline, with upgrade windows schedulable per customer.

Backups and availability

• Managed database backups with point-in-time recovery; object-storage versioning on internal buckets.
• Multi-AZ deployment within the environment's region by default.
• Environment-specific recovery objectives (RPO/RTO) are documented per engagement.

Data handling notes

• Mailbox access is read-only (Microsoft Graph Mail.Read, customer-authorized OAuth) — Varolio never sends, replies to, or modifies email.
• Message text sent to AI providers travels over TLS to the providers listed in Application Architecture — AI providers, using enterprise API endpoints whose terms exclude the use of customer inputs for foundation-model training.
• In BYO Data Store and Cloud-Prem deployments, content data (threads, cases, attachments, embeddings) resides on customer-controlled infrastructure.