Need a detailed architecture review, questionnaire responses, or a security deep-dive for your organization? Contact us or reach out to your TrueFoundry account team.
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.Architecture overview
TrueFoundry SaaS uses a split-plane design:
TrueFoundry SaaS security architecture — edge protection, split control and gateway planes, encrypted state, and controlled internal access
Key properties of this design:
- Prompt and response storage is under your control. Logging configs 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.
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 with dashboard and API access (SIEM export coming soon)
- Optional request logging and redaction via logging configs
Shared responsibility
Compliance
TrueFoundry SaaS maintains SOC 2 Type II, GDPR, and HIPAA programs. Reports and trust documentation are available at trust.truefoundry.com.
Our compliance certifications
Compliance certifications apply to TrueFoundry’s managed infrastructure. For self-hosted deployments, compliance depends on your own infrastructure and controls — see Self-Hosted Security.
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.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.
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.
- 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.
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 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)
- Unused users and virtual accounts removed
- Model and resource access scoped per application need (Gateway Access Control)
- Team assignments configured for active users and PATs
Tokens
- Production workloads use VATs, not PATs (API Keys)
- PAT maximum lifetime set below the one-year platform cap under Settings > Security
- VAT auto-rotation enabled for production accounts
- Tokens stored in a secret manager (or secret store sync), never in source control
AI Gateway
- Guardrails enabled on production endpoints (PII, prompt injection, content filtering)
- Rate limits and budget limits configured
- Logging 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 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 enabled for sensitive tools
Monitoring
- Security contact known — report incidents or suspected issues to security@truefoundry.com
- Quarterly access review scheduled
- Status page subscribed at status.truefoundry.com
- Audit logs 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
- We follow responsible disclosure and aim to respond within 48 hours
- Advisories are published on trust.truefoundry.com