> ## Documentation Index
> Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SaaS security

> How TrueFoundry secures managed SaaS — architecture overview, shared responsibility, and a security checklist for your tenant.

This page covers the security posture of TrueFoundry's **managed SaaS** control plane and AI Gateway, plus practices you should follow in your tenant.

For compliance reports, questionnaires, and deeper trust documentation, visit [trust.truefoundry.com](https://trust.truefoundry.com). For self-hosted deployments, see [Self-Hosted Security](/docs/platform/onprem-security).

<Info>
  Need a detailed architecture review, questionnaire responses, or a security deep-dive for your organization? [Contact us](mailto:security@truefoundry.com) or reach out to your TrueFoundry account team.
</Info>

## Security philosophy

TrueFoundry's security strategy is anchored in **defense in depth** and **secure by design**. No single control is trusted to be sufficient — every layer assumes the layer above it can fail. Security requirements are part of design review, not retrofitted after implementation.

| Layer           | What we focus on                                                                      |
| --------------- | ------------------------------------------------------------------------------------- |
| **Edge**        | WAF, DDoS protection, TLS 1.2+, global load balancing                                 |
| **Network**     | Segmented service communication, no public admin interfaces                           |
| **Compute**     | Hardened containers, least privilege, continuous image scanning                       |
| **Data**        | Encryption at rest and in transit, per-tenant secret isolation                        |
| **Identity**    | SSO for internal access, short-lived credentials, least privilege                     |
| **Application** | AuthN/AuthZ on every gateway request, RBAC, audit logging, guardrails                 |
| **Process**     | Automated security scanning on every change, code review, regular penetration testing |

## Architecture overview

TrueFoundry SaaS uses a **split-plane** design:

<Frame caption="TrueFoundry SaaS security architecture — edge protection, split control and gateway planes, encrypted state, and controlled internal access">
  <img src="https://mintcdn.com/truefoundry/YDJx3MzK1-sY1Iu7/images/docs/platform/saas-security-architecture-public.svg?fit=max&auto=format&n=YDJx3MzK1-sY1Iu7&q=85&s=f6fb0c8c058d7f2c400286cde1a447f9" style={{ width: "100%", height: "auto" }} alt="Architecture diagram. Customer users and admins reach the control plane, and applications and agents reach the gateway planes, through an edge layer providing WAF, DDoS protection, and TLS 1.2+ load balancing. The control plane is active-passive across multiple regions with UI and API services, backend microservices, a message bus for config sync and cache, and a telemetry collector. Stateful services hold an encrypted database, an envelope-encrypted secrets store, and blob storage for logs and traces with 90-day retention. Gateway planes run active-active and stateless across multiple regions, performing authentication, authorization, rate and budget limits, and guardrails in memory. The gateway connects to the control plane over a bootstrap-token-then-short-lived-certificate channel and syncs config over TLS. TrueFoundry internal access uses SSO with MFA, VPN, and just-in-time approval-gated access with zero standing access." width="1080" height="700" data-path="images/docs/platform/saas-security-architecture-public.svg" />
</Frame>

| Plane             | Role                                                       | Security posture                                                               |
| ----------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **Control plane** | Dashboard, APIs, configuration, identity, policy           | Managed by TrueFoundry; multi-tenant with strong logical isolation             |
| **Gateway plane** | LLM and MCP proxy — auth, rate limits, guardrails, routing | Stateless, horizontally scaled; policy evaluated in memory on the request path |
| **Edge**          | Public entry for UI, API, and gateway traffic              | WAF and DDoS protection in front of origin infrastructure                      |

Key properties of this design:

* **Prompt and response storage is under your control.** [Logging configs](/docs/ai-gateway/logging-config) let you decide whether request bodies are logged, and let you redact sensitive patterns. A deny rule always wins.
* **Provider credentials stay in the platform.** Applications authenticate to the gateway with TrueFoundry tokens; LLM provider keys are managed centrally and never need to live in your app code.
* **The gateway request path does not depend on auxiliary systems.** Authentication, authorization, rate limiting, and routing run against in-memory state so live traffic is not blocked by control-plane outages.

For regional layout and failover behavior, see [Disaster Recovery](/docs/platform/disaster-recovery) and [Globally Distributed SaaS Gateway](/docs/ai-gateway/globally-distributed-saas).

## What TrueFoundry protects

### Tenant isolation

* Every tenant operates on its own subdomain; backend services scope all queries and API calls by tenant
* Secrets are encrypted per tenant so ciphertext from one tenant cannot be decrypted with another tenant's keys
* SSO, provisioning, roles, rate limits, budgets, and guardrails are configured and evaluated independently per tenant

### Encryption and secrets

* Data encrypted **at rest** (AES-256) and **in transit** (TLS)
* Tenant secrets (including LLM provider keys) use envelope encryption; plaintext keys are not persisted on gateway disks
* Access to infrastructure and storage uses short-lived, role-based credentials rather than long-lived static keys wherever possible

### Platform access and operations

* TrueFoundry personnel access production with identity SSO, MFA, and least privilege — no broad standing access by default
* Admin interfaces are not exposed on the public internet
* Continuous monitoring, vulnerability management with severity-based patch SLAs, and regular penetration testing
* SaaS patches are applied by TrueFoundry as part of managed operations

### Product controls available to you

* SSO / SAML / OIDC, RBAC, teams, and virtual accounts
* Personal Access Tokens (PATs) and Virtual Account Tokens (VATs) with lifetime and rotation controls
* Gateway guardrails, rate limits, budget limits, and access rules
* [Audit logging](/docs/platform/audit-logging) with dashboard and API access (SIEM export coming soon)
* Optional request logging and redaction via [logging configs](/docs/ai-gateway/logging-config)

## Shared responsibility

| Area                                          | TrueFoundry                                       | You                                             |
| --------------------------------------------- | ------------------------------------------------- | ----------------------------------------------- |
| Infrastructure patching and hardening         | Owns                                              | —                                               |
| Edge protection, WAF, DDoS                    | Owns                                              | —                                               |
| Encryption at rest and in transit             | Owns                                              | —                                               |
| Tenant secret encryption                      | Owns                                              | —                                               |
| Vulnerability management and pentesting       | Owns                                              | —                                               |
| SSO, MFA, and user lifecycle                  | Provides the controls                             | Configure and enforce                           |
| Roles, teams, and least privilege             | Provides the controls                             | Assign and review                               |
| API tokens (PATs / VATs)                      | Provides the controls                             | Create, rotate, store safely                    |
| Gateway guardrails, rate and budget limits    | Provides the controls                             | Configure for your apps                         |
| Audit log and trace retention in your systems | Dashboard and API access; SIEM export coming soon | Ingest and retain as needed                     |
| Provider API keys in application code         | —                                                 | Do not embed; use TrueFoundry provider accounts |

## Compliance

TrueFoundry SaaS maintains **SOC 2 Type II**, **GDPR**, and **HIPAA** programs. Reports and trust documentation are available at [trust.truefoundry.com](https://trust.truefoundry.com).

<Frame caption="Our compliance certifications">
  <Columns cols={3}>
    <Card>
      <img src="https://mintcdn.com/truefoundry/VhkkzLbS0sN_6xZz/images/icons/SOC.png?fit=max&auto=format&n=VhkkzLbS0sN_6xZz&q=85&s=01bddac60c60b709fc49096ed82c33fe" alt="SOC 2 Type II logo" width="679" height="679" data-path="images/icons/SOC.png" />
    </Card>

    <Card>
      <img src="https://mintcdn.com/truefoundry/VhkkzLbS0sN_6xZz/images/icons/gdpr.png?fit=max&auto=format&n=VhkkzLbS0sN_6xZz&q=85&s=18b9e6154fa6892052755a4649298261" alt="GDPR logo" width="679" height="679" data-path="images/icons/gdpr.png" />
    </Card>

    <Card>
      <img src="https://mintcdn.com/truefoundry/VhkkzLbS0sN_6xZz/images/icons/hipaa.png?fit=max&auto=format&n=VhkkzLbS0sN_6xZz&q=85&s=d53d0d7925d1a759c429e61d100fc1cb" alt="HIPAA logo" width="679" height="679" data-path="images/icons/hipaa.png" />
    </Card>
  </Columns>
</Frame>

<Info>
  Compliance certifications apply to TrueFoundry's managed infrastructure. For self-hosted deployments, compliance depends on your own infrastructure and controls — see [Self-Hosted Security](/docs/platform/onprem-security).
</Info>

## Data residency

TrueFoundry SaaS is globally distributed and can accommodate data residency requirements.

* **Choose your region** — select the region where the AI Gateway is deployed and where request logs and traces are stored.
* **Bring your own storage** — connect your own blob storage (Amazon S3, Azure Blob, or Google Cloud Storage) so logs and traces stay in buckets you control.

## Data privacy

* **Data minimization** — only the data required to operate the platform is collected and processed.
* **Configurable retention** — request logs and traces follow the retention you configure.
* **Right to deletion** — deletion requests are supported in line with privacy regulations.
* **GDPR** — data subject access, rectification, and deletion are supported, and privacy is built into the architecture (privacy by design).
* **Data processing agreements** — standard DPAs are available and are signed with all sub-processors.

## Sub-processors

TrueFoundry SaaS uses the following sub-processors. A Data Processing Agreement is signed with each.

| Sub-processor  | Purpose                                                 | Data location                    |
| -------------- | ------------------------------------------------------- | -------------------------------- |
| **AWS**        | Hosting, storage, and security monitoring               | Europe                           |
| **Cloudflare** | Edge network — WAF, DDoS protection, and load balancing | Global (traffic in transit only) |
| **FusionAuth** | Authentication                                          | Europe                           |
| **Sentry**     | Error and crash logs (no PII such as user prompts)      | United States                    |
| **PostHog**    | Product usage analytics                                 | Europe                           |

## Vulnerability management

* TrueFoundry scans all images and artifacts and does not ship software with a critical known vulnerability that has a fix available.
* Vulnerabilities are triaged by CVSS severity and patched by TrueFoundry across the SaaS control plane and gateway fleet as part of managed operations — there are no patch SLAs for you to track and no upgrades for you to apply.
* Regular penetration testing is performed by internal and external experts; reports are available at [trust.truefoundry.com](https://trust.truefoundry.com).

## Availability and incident response

* **Globally distributed gateway** — deployed across multiple regions and cloud providers with automatic failover to healthy regions.
* **Multi-region control plane** — active-passive across two regions with disaster recovery enabled. See [Disaster Recovery](/docs/platform/disaster-recovery).
* **24/7 monitoring** — a dedicated team monitors SaaS infrastructure around the clock and is paged for incidents.
* **Status transparency** — component status and subscription options are available at [status.truefoundry.com](https://status.truefoundry.com).

## Security best practices checklist

Security is a **shared responsibility**. TrueFoundry secures the platform and provides a broad set of controls — SSO, RBAC, token lifetime and rotation, guardrails, rate and budget limits, access rules, and audit logging — so you can secure your own tenant. Using these controls correctly is your part of the model, and this checklist is the general path to doing that.

Use it during onboarding and revisit it in quarterly reviews.

### Identity

* [ ] [SSO](/docs/platform/sso/overview) configured with your corporate IdP (Okta, Microsoft Entra ID, Google, Keycloak, etc.)
* [ ] MFA enforced through your IdP
* [ ] Username/password login disabled after SSO is verified — Coming soon
* [ ] Control plane IP allowlisting configured under **Settings > Security** — Coming soon

### Access

* [ ] Users have least-privilege roles ([Manage User Roles and Permissions](/docs/platform/manage-user-roles-and-permissions))
* [ ] Unused users and virtual accounts removed
* [ ] Model and resource access scoped per application need ([Gateway Access Control](/docs/ai-gateway/gateway-access-control))
* [ ] Team assignments configured for active users and PATs

### Tokens

* [ ] Production workloads use **VATs**, not PATs ([API Keys](/docs/generating-truefoundry-api-keys))
* [ ] PAT maximum lifetime set below the one-year platform cap under **Settings > Security**
* [ ] [VAT auto-rotation](/docs/platform/virtual-account-management#configure-auto-rotation-of-virtual-account-tokens) enabled for production accounts
* [ ] Tokens stored in a secret manager (or [secret store sync](/docs/platform/virtual-account-management#configure-secret-store-sync-for-virtual-account-tokens)), never in source control

### AI Gateway

* [ ] [Guardrails](/docs/ai-gateway/ecosystem) enabled on production endpoints (PII, prompt injection, content filtering)
* [ ] [Rate limits](/docs/ai-gateway/ratelimiting) and [budget limits](/docs/ai-gateway/budget-limiting-v2) configured
* [ ] [Logging](/docs/ai-gateway/logging-config) and trace export configured for the retention you need
* [ ] Provider keys stored in TrueFoundry provider accounts, not in application code

### MCP Gateway

* [ ] [MCP Gateway authentication](/docs/ai-gateway/mcp/mcp-gateway-auth-security) applied for every server
* [ ] OAuth-based MCP servers used wherever possible; API-key-based MCP servers avoided unless necessary, and their keys rotated regularly
* [ ] [Tool approval](/docs/ai-gateway/mcp/mcp-tool-approval) enabled for sensitive tools

### Monitoring

* [ ] Security contact known — report incidents or suspected issues to **[security@truefoundry.com](mailto:security@truefoundry.com)**
* [ ] Quarterly access review scheduled
* [ ] Status page subscribed at [status.truefoundry.com](https://status.truefoundry.com)
* [ ] [Audit logs](/docs/platform/audit-logging) exported to your SIEM — Coming soon
* [ ] Security alert email configured under **Settings > Security** to receive automated alerts — Coming soon

## Report a vulnerability

If you discover a security issue in TrueFoundry:

* Email **[security@truefoundry.com](mailto:security@truefoundry.com)**
* We follow responsible disclosure and aim to respond within **48 hours**
* Advisories are published on [trust.truefoundry.com](https://trust.truefoundry.com)

## Request more detail

This page is intentionally high-level for public documentation. For a fuller SaaS security architecture brief, threat-model discussion, or customer security questionnaire, contact **[security@truefoundry.com](mailto:security@truefoundry.com)** or your TrueFoundry account team.