# Security & Compliance - GateLLM

> GateLLM security & compliance: self-hosted, BYOK keys never leave your network, GDPR/CCPA/DPA, enterprise SSO, crash-safe billing and audit.

Canonical: https://www.gatellm.io/security/

## Security & Compliance
Security, privacy, and compliance for enterprise procurement. Fully self-hosted; data never leaves your network.
### Data never leaves your network
Under BYOK, API keys live in gateway memory only — never persisted or transmitted.

Requests route through the gateway straight to vendor APIs; data stays within your private network end to end.

GateLLM itself does not store, train on, or cache request content.
### Transport & key security
TLS 1.3 end to end.

Keys in memory only; on restart, injected from your secrets — never on disk.

Client admission control: gate by User-Agent with differentiated policies.
### Enterprise compliance
GDPR / CCPA / DPA ready.

SOC 2 Type II / ISO 27001 controls aligned (certification in preparation).

SSO (OIDC: Azure AD / Okta / generic, plus SAML 2.0 + SCIM 2.0).
### Audit & billing correctness
Request-level audit logs, exportable to internal ops and billing systems.

Crash-safe billing: pre-deduct → settle → refund; billing stays correct across process crashes via an in-flight ledger and per-request audit.

Management API to programmatically manage quotas, budgets, usage, and cost.
### Security Architecture Layers (Whitepaper Summary)
Network layer: the gateway process is deployed within your VPC / on-premises data center; inbound/outbound traffic is controlled by the security groups / network policies you configure; requests go directly to downstream model providers' official APIs, without passing through any Processor relay server.

Gateway process layer: stateless design; keys are loaded from encrypted configuration into memory and never persisted; any replica can serve any request, supporting horizontal scaling and instant failover; on restart, keys are re-injected from your secrets.

Key layer: BYOK model-provider keys live only in the gateway process memory, are never written to persistent storage, and cannot be read in plaintext by operations personnel; client admission control gates by User-Agent with differentiated policies.

Data layer: runtime prompts / completions are not persisted in the Processor's systems (forwarded in memory, not persisted); account and license data at rest is AES-256 encrypted; the audit-log retention policy is determined by your operations team.

Billing layer: crash-safe billing (pre-deduct → settle → refund), stays correct across process crashes via an in-flight ledger and per-request audit.
### CISO Concern Mapping
Excessive AI access concerns: GateLLM addresses this with fully self-hosted deployment + BYOK — keys and prompts never leave your network boundary; you fully control which models to use and which provider to route to, with no shadow AI and no hidden sub-processors (see the Sub-processor List).

Data used for training: the Processor does not come into contact with prompt data; whether a downstream model provider trains is determined by its policy, which you can review in the data-use matrix on the Sub-processor List before onboarding — entirely opt-in.

Cross-border compliance: Processor account data is transferred cross-border via SCCs / IDTA; cross-border transfers to downstream providers are engaged directly by you with appropriate safeguards (DPA Section 11).

Key leakage: keys live in memory only, are never persisted or transmitted; SSO delegates MFA and session management to your existing IdP, so credentials are not fragmented.
### Penetration Testing & Vulnerability Governance
Independent third-party penetration testing of GateLLM is in preparation (scope and rules of engagement are ready), covering the gateway process, authentication & authorization, Edge Functions, API gateway, and key-handling paths; a summary will be published in Section 7 of the Vulnerability Disclosure Policy once completed.

Responsible vulnerability disclosure policy: report via security@gatellm.io (PGP supported), acknowledged within 24 hours, remediated by CVSS severity (Critical 7 days / High 30 days / Medium 60 days / Low 90 days).

A Software Bill of Materials (SBOM) is provided; dependencies are regularly scanned for known vulnerabilities, and security patches are annotated with CVE IDs in the changelog.
- GDPR
- CCPA
- DPA
- SOC 2 controls aligned
- ISO 27001 controls aligned
## Trust & Compliance Documents
### Data Processing Agreement (DPA)
GDPR Art 28(3) mapping, SCC/IDTA cross-border, sub-processor change notification, LLM gateway data-flow specifics
### Sub-processor List
Data-use matrix for 100+ downstream model providers, no shadow AI, change subscription
### Security Questionnaire Library
CAIQ / SIG / VSA pre-answered, compressing questionnaire response from days to hours
### SLA & Incident Response
P1-P4 incident response process, support service tiers, license service maintenance, gateway HA deployment guidance
### Vulnerability Disclosure Policy
Responsible disclosure, response SLA, PGP communication, penetration test summary
### Open Source License Notice
Open-source components & licenses in the distribution, SBOM, BYOK SDK license boundary, attribution
### Version Support & Lifecycle
N-1/LTS support windows, security-patch backports, upgrade path, EOL notification

## Related
- [Home](https://www.gatellm.io/index.md)
- [Pricing](https://www.gatellm.io/pricing.md)
- [Cost Calculator](https://www.gatellm.io/calculator.md)
- [About](https://www.gatellm.io/about.md)
- [Book a Demo](https://www.gatellm.io/demo.md)
- [FAQ](https://www.gatellm.io/faq.md)
- [Compare AI Gateways](https://www.gatellm.io/compare.md)
- [Compare LiteLLM](https://www.gatellm.io/compare/litellm.md)
- [Compare OpenRouter](https://www.gatellm.io/compare/openrouter.md)
- [Compare Alibaba Cloud AI Gateway](https://www.gatellm.io/compare/alibaba-cloud.md)
- [Compare Azure API Management](https://www.gatellm.io/compare/azure-apim.md)
- [Compare Apigee](https://www.gatellm.io/compare/apigee.md)
- [Compare Cloudflare AI Gateway](https://www.gatellm.io/compare/cloudflare.md)
- [Compare Kong AI Gateway](https://www.gatellm.io/compare/kong.md)
- [Compare Portkey](https://www.gatellm.io/compare/portkey.md)
- [LiteLLM vs Kong AI Gateway](https://www.gatellm.io/compare/litellm-vs-kong.md)
- [LiteLLM vs OpenRouter](https://www.gatellm.io/compare/litellm-vs-openrouter.md)
- [LiteLLM vs Portkey](https://www.gatellm.io/compare/litellm-vs-portkey.md)
- [Use Cases](https://www.gatellm.io/use-cases.md)
- [Reduce LLM Cost](https://www.gatellm.io/use-cases/reduce-cost.md)
- [High Availability](https://www.gatellm.io/use-cases/high-availability.md)
- [Multi-Tenant Isolation](https://www.gatellm.io/use-cases/multi-tenant.md)
- [Compliance & Audit](https://www.gatellm.io/use-cases/compliance-audit.md)
- [Troubleshooting by Symptom](https://www.gatellm.io/use-cases/troubleshooting.md)
- [Mixed Multi-Vendor Model Stack](https://www.gatellm.io/use-cases/mixed-model-stack.md)
- [Self-Host AI Inside Office](https://www.gatellm.io/use-cases/self-hosted-office-ai.md)
- [Token Usage Visibility & Attribution](https://www.gatellm.io/use-cases/token-ops.md)
- [Token FinOps: AI Cost Allocation & Control](https://www.gatellm.io/use-cases/token-finops.md)
- [MCP Tool Governance](https://www.gatellm.io/use-cases/mcp-tool-governance.md)
- [Web Search for Every Model](https://www.gatellm.io/use-cases/web-search-grounding.md)
- [Multi-Key Rotation & Standby](https://www.gatellm.io/use-cases/multi-key-pooling.md)
- [Admission Control for Connected Clients](https://www.gatellm.io/use-cases/client-admission-control.md)
- [Enforce Which Model Agents Actually Run](https://www.gatellm.io/use-cases/enforce-model-policy.md)
- [No Model Choice on the Client](https://www.gatellm.io/use-cases/automatic-model-tiering.md)
- [One Protocol, Any Model](https://www.gatellm.io/use-cases/one-protocol-any-model.md)
- [Office / Microsoft 365 Add-in](https://www.gatellm.io/office-addin.md)
- [Glossary](https://www.gatellm.io/glossary.md)
- [Model Catalog](https://www.gatellm.io/models.md)
- [SDK & Framework Integrations](https://www.gatellm.io/integrations.md)
- [AI Coding Agents & Harnesses](https://www.gatellm.io/coding-agents.md)
- [Privacy Policy](https://www.gatellm.io/privacy-policy.md)
- [Terms of Service](https://www.gatellm.io/terms.md)
- [Cookie Policy](https://www.gatellm.io/cookies.md)
- [Data Processing Agreement (DPA)](https://www.gatellm.io/dpa.md)
- [Sub-processor List](https://www.gatellm.io/subprocessors.md)
- [Security Questionnaire (CAIQ/SIG/VSA)](https://www.gatellm.io/trust.md)
- [Incident Response & Support](https://www.gatellm.io/sla.md)
- [Vulnerability Disclosure Policy](https://www.gatellm.io/vulnerability-disclosure.md)
- [Open Source License Notice](https://www.gatellm.io/open-source-licenses.md)
- [Version Support & Lifecycle (EOL)](https://www.gatellm.io/lifecycle.md)
- [Engineering Blog](https://www.gatellm.io/blog.md)
- [Your Agents Have More Permissions Than Your Employees: Governing MCP Tools at the Gateway](https://www.gatellm.io/blog/mcp-tool-governance.md)
- [The $10k Invoice Problem: Five Ways to Cut LLM Spend Without Dumbing Down Your App](https://www.gatellm.io/blog/reduce-cost.md)
- [Your Vendor's List Price Is Not Your Cost: Applying Real FinOps to Token Spend](https://www.gatellm.io/blog/token-finops.md)
- [llms.txt](https://www.gatellm.io/llms.txt)