Self-hosted security

​

Deployment architecture

​

Harden the Helm installation

​

1. Enforce pod and container security contexts

tfyNats:
  container:
    merge:
      securityContext:
        capabilities:
          drop:
            - ALL
        readOnlyRootFilesystem: true
        allowPrivilegeEscalation: false
  podTemplate:
    merge:
      spec:
        securityContext:
          fsGroup: 1000
          runAsUser: 1000
          runAsNonRoot: true

​

2. Enable network policies

networkPolicy:
  enabled: true
  allowedIngressFrom:
    # Prometheus scrapes
    - namespace: tfy-prometheus
    # Ingress controller (recommended: restrict to controller pods)
    - namespace: ingress-nginx
      podSelector:
        app.kubernetes.io/name: ingress-nginx

​

3. Encrypt keys and secrets

• Use an external secret manager — connect AWS SSM Parameter Store / Secrets Manager, GCP Secret Manager, or Azure Key Vault as a Secret Store integration, and reference secrets by FQN so provider keys live in your KMS-backed store. See Secret manager in the AI Gateway.
• Use a customer-managed KMS key — configure a custom KMS Key ARN for the AWS Secret Manager / Parameter Store secret store so you control the encryption key and its rotation.
• Encrypt the database at rest — use managed PostgreSQL with encryption at rest enabled (KMS) and require TLS with DB_SSL_MODE (require, verify-ca, or verify-full). See How to enable SSL for PostgreSQL connections.
• Encrypt blob storage at rest — enable server-side encryption (SSE-KMS) on the bucket that holds request logs and traces.

​

4. Encrypt traffic in transit

• Terminate TLS 1.2+ at your ingress for the dashboard, API, and gateway endpoints.
• Optionally enable in-pod TLS termination on the proxy for end-to-end encryption inside the cluster. See How to enable in-pod TLS termination.
• Require SSL to PostgreSQL as above; inject custom CA certificates where needed via custom CA certificate injection.

​

5. Grant least-privilege cloud access

• Give the control plane and gateway access to storage and secrets through scoped IAM roles (IRSA on EKS, Workload Identity on GKE, Managed Identity on AKS) rather than long-lived static keys.
• Restrict the S3 (or equivalent) policy to the minimal actions required. See How to restrict AWS S3 permissions to a minimal set.
• Ensure your database security group allows traffic only from the Kubernetes node groups.
• Do not grant anyone in the organization direct access to the TrueFoundry PostgreSQL database or the S3 bucket. These hold configuration, secrets, request logs, and traces. Access should be limited to the control plane and gateway workloads via their scoped IAM roles — not developers, analysts, or admins. Restrict human access to break-glass procedures only, and audit any such access.

​

Edge protection (WAF)

• Use your platform’s WAF — Cloudflare, AWS WAF (with ALB/CloudFront), Azure Front Door / Application Gateway WAF, or GCP Cloud Armor.
• Enable OWASP-style managed rule sets (SQL injection, XSS, path traversal), rate limiting, and bot/DDoS protection at the edge.
• Terminate TLS at the edge and forward only to your ingress; keep origins off the public internet where possible (private endpoints, security groups).
• Keep the control plane private — do not expose the control plane URL (dashboard and API) to the public internet. Restrict it to a VPN or your private network. Unlike the gateway, which serves your applications, the control plane is admin-facing and does not need public exposure.

​

What leaves your environment

{
  "clusters": [
    {
      "clusterName": "example-cluster",
      "kubernetesVersion": "v1.33.4",
      "provider": "aws",
      "tenantName": "tenant1",
      "controlPlaneVersion": "0.90.0",
      "controlPlaneURL": "https://example-company.truefoundry.cloud",
      "truefoundryControlPlane": true,
      "controlPlaneProvider": "aws",
      "isConnected": true
    }
  ]
}

{
  "addons": [
    {
      "name": "truefoundry",
      "version": "0.90.0",
      "healthStatus": "Healthy",
      "syncStatus": "Synced",
      "sourceNamespace": "argocd",
      "destinationNamespace": "truefoundry",
      "addonName": "truefoundry"
    }
  ],
  "autopilotStatistics": {
    "clusterName": "example-cluster",
    "tenantName": "tenant1",
    "autopilot": { "addons": false, "service": false },
    "p50CpuUsage": 4.49,
    "p50CpuRequested": 65.822,
    "p50CpuAllocatable": 211.02,
    "p50MemoryUsage": 133.447,
    "p50MemoryRequested": 255.933,
    "p50MemoryAllocatable": 649.102,
    "p50GpuCountUsage": 0,
    "p50GpuCountRequested": 0,
    "p50GpuCountProvisioned": 0,
    "p50GpuMemoryUsage": 0,
    "p50GpuMemoryProvisioned": 0
  }
}

{
  "tenantName": "tenant1",
  "data": {
    "1738800000": {
      "usage": {
        "inputTokens": 125000,
        "outputTokens": 48000,
        "totalTokens": 173000,
        "totalRequestCount": 1250,
        "totalErrorCounts": 12,
        "providerWiseModelCounts": { "openai": 800, "anthropic": 350, "azure": 100 },
        "guardrailsRuntime": {
          "totalEligibleRequests": 1250,
          "guardrailPass": 1200,
          "guardrailFail": 35,
          "guardrailMutate": 10,
          "guardrailRunError": 5
        },
        "routingData": { "totalRouting": 1250, "tfyRateLimited": 8, "tfyBudgetLimited": 3 },
        "totalMCPToolCalls": 75
      },
      "config": {
        "models": { "totalProviderAccounts": 5, "totalModels": 12, "totalVirtualModels": 3 },
        "guardrails": { "totalGuardrailGroups": 4, "totalGuardrailIntegrations": 6 },
        "mcpServers": { "totalMcpGroups": 2, "totalMcpServers": 8 },
        "rules": {
          "totalRateLimitRules": 15,
          "totalBudgetLimitRules": 8,
          "totalGuardrailConfigRules": 6,
          "otelExportConfigured": true
        },
        "prompts": { "totalPrompts": 24, "totalPromptVersions": 67 }
      }
    }
  }
}

​

Vulnerability management

• Rolling track — security fixes ship in the next regular release. Staying within 3 months of the latest release keeps you covered.
• Stable track — an on-demand maintenance patch is shipped against your current Stable version within the SLA window. TrueFoundry does not proactively monitor older versions, so notify your Customer Support Manager or the support channel to start the SLA clock.

​

Logging and monitoring

• Enable auditing and logging across your systems and network devices, and forward them to your SIEM. For example, integrate AWS CloudTrail with CloudWatch to correlate events and alert on potential incidents.
• Scrape TrueFoundry component metrics with your monitoring stack and alert on anomalies. See Control plane monitoring.
• Maintain monitoring of security alerts for continuous oversight and rapid response.
• Review TrueFoundry audit logs for user and API activity in the platform.

​

Security checklist

​

Deployment and network

• Control plane URL is not exposed to the public internet — access restricted to a VPN or your private network
• A WAF fronts both the control plane and the AI Gateway
• Ingress terminates TLS 1.2+ for the dashboard, API, and gateway
• Origins kept off the public internet where possible (private endpoints, security groups)

​

Helm hardening

• Pod and container security contexts enforced, including the NATS override
• Network policies enabled (networkPolicy.enabled: true) with allowedIngressFrom scoped to monitoring and ingress
• Cluster CNI enforces NetworkPolicy

​

Data protection

• Provider keys and secrets stored in an external secret manager with a customer-managed KMS key
• PostgreSQL encrypted at rest and requires SSL (DB_SSL_MODE)
• Blob storage encrypted at rest (SSE-KMS)
• No direct human access to the TrueFoundry database or S3 bucket — workloads only, via scoped IAM roles

​

Access

• Storage and secrets accessed through scoped IAM roles (IRSA / Workload Identity / Managed Identity), not static keys
• S3 (or equivalent) policy restricted to the minimal actions required
• SSO configured with your IdP and least-privilege roles assigned

​

Upgrades and monitoring

• Upgrade at least once a month to pick up the latest changes and security updates from TrueFoundry
• Staying on a supported release track
• TrueFoundry images scanned in your own registry
• Component metrics scraped and alerting configured
• Audit logs and infrastructure logs forwarded to your SIEM

​

Report a vulnerability

• Email security@truefoundry.com
• We follow responsible disclosure and aim to respond within 48 hours
• Advisories are published on trust.truefoundry.com