Security, compliance, and data handling practices for Corveil.
Last updated
Preparing for SOC 2 Type I audit. Controls are being documented and validated.
Scheduling third-party penetration testing engagement.
Planned following Type I completion.
On roadmap for enterprise compliance requirements.
Security headers on all API responses follow FIPS 140-2 guidelines.
We complete SIG, CAIQ, and custom security questionnaires on request.
| Control | Implementation |
|---|---|
| Hosting | AWS (commercial and GovCloud regions). Self-hosted and managed SaaS options available. |
| Compute | ECS Fargate with auto-scaling. No persistent host access. Containers rebuilt on every deployment. |
| Tenant isolation | Separate database per customer. No shared data stores between tenants. |
| Network | Private subnets. Internal ALB with TLS termination. No public database endpoints. |
| Infrastructure as Code | Terraform modules. All infrastructure changes are version-controlled and auditable. |
| Air-gapped support | Supports fully disconnected environments with no external network dependencies. |
| Practice | Details |
|---|---|
| Model training | Customer data is never used to train models. Corveil is a proxy — data passes through to the provider selected by the customer. |
| Data residency | Self-hosted customers control data location entirely. Managed SaaS data resides in the region agreed upon at onboarding. |
| Encryption in transit | TLS 1.2+ enforced on all connections. |
| Encryption at rest | AES-256 for stored data. API keys are SHA-256 hashed — plaintext keys are not persisted. |
| Logging | Configurable audit logging. Organizations control retention duration and level of detail captured. |
| Data retention | Configurable per deployment. Self-hosted customers have full control. Managed SaaS follows contractual retention schedules. |
| PII handling | Built-in detection and redaction for SSN, credit cards, email addresses, phone numbers, and IP addresses. Can strip PII before provider call and restore in response. |
| Secret detection | Automatic detection and blocking of API keys, tokens, and credentials in outbound requests. |
| Control | Implementation |
|---|---|
| Authentication | Virtual API keys, OIDC/OAuth 2.0 SSO (Okta, Azure AD, Google), and JWT session management. |
| Key management | Virtual API keys shield provider credentials. Users never have access to underlying provider keys. Keys support expiration, budgets, and rate limits. |
| Authorization | Role-based access control at organization, team, and individual levels. Extends to model access, MCP tools, and individual tool parameters. |
| Session management | JWT-based sessions with configurable expiration. Admin impersonation is tracked with full audit trail. |
| Control | Implementation |
|---|---|
| Language | Go 1.24+. Compiled, statically typed, memory-safe. Single binary with no runtime dependencies. |
| Security headers | HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options on all responses. |
| Input validation | All API inputs validated and sanitized. Parameterized database queries. Strict content-type enforcement. |
| SSRF protection | DNS rebinding defense, private IP blocking, and cloud metadata endpoint protection on all outbound connections. |
| Dependencies | Minimal dependency footprint. Standard library preferred. All dependencies pinned via go.sum. |
| Content filtering | Pre-call and post-call guardrails with configurable PII redaction, keyword blocking, regex filtering, and content moderation. Full decision audit trail. |
Third-party services that may process customer data when using Corveil.
| Service | Purpose | Data Processed |
|---|---|---|
| AWS | Infrastructure hosting (managed SaaS) | All application data |
| OpenRouter | LLM provider routing | Request/response content (after guardrail filtering) |
| Anthropic | Direct LLM provider | Request/response content (after guardrail filtering) |
| Google Cloud (Vertex AI) | Direct LLM provider | Request/response content (after guardrail filtering) |
| AWS Bedrock | Direct LLM provider (including GovCloud) | Request/response content (after guardrail filtering) |
| PostHog | Product analytics | Usage events, feature adoption metrics |
Self-hosted deployments do not route data through Corveil infrastructure. LLM provider subprocessors depend on customer configuration.
Architecture review, data flow diagrams, or completed security questionnaire available on request.