Skip to main content

InfraSage Trust Center

Everything a procurement or security team needs to evaluate InfraSage, in one place. If something you need is missing, email [email protected]; we reply within 1 business day.

Deployment posture​

InfraSage supports three deployment models. In every one of them your telemetry and RCA outputs stay under your control, and we don't backhaul customer data to a shared analytics warehouse.

ModelWhere InfraSage runsWhere your telemetry livesWhere LLM calls go
BYOC (Bring Your Own Cloud)Your K8s clusterYour ClickHouse (never leaves your VPC)Your AWS Bedrock account (Anthropic Sonnet/Haiku)
Self-hostedYour infraYour ClickHouseYour Bedrock / Anthropic / Gemini / a model you host
Managed SaaS (not yet available)InfraSage-managed AWSInfraSage-managed ClickHouse (single-tenant DB per customer)Anthropic direct on your behalf

There is no cross-tenant data pooling by default. Contributing fault signatures across tenants is opt-in per tenant and governed by a separate DPA amendment.

Encryption​

  • In transit: TLS 1.3 for all external ingest (OTLP, webhooks, API); mTLS supported for gateway↔engine and engine↔ClickHouse
  • At rest: ClickHouse data on EBS gp3 / io2 with AWS-managed KMS encryption by default; customer-managed KMS supported
  • Secrets: helm chart supports ExternalSecrets operator pointing at AWS Secrets Manager or HashiCorp Vault; hardcoded credentials are not permitted in production deploys

PII handling​

InfraSage masks secrets and personal data before anything reaches an AI model:

  • What is masked: email addresses, card numbers, IBANs, phone numbers, US SSNs, JWTs, API keys and tokens, session cookies, Authorization: headers, and any attribute whose name says it holds a credential
  • How: matching values are replaced with typed placeholders such as [CARD], [EMAIL] or [SECRET] before the evidence is sent

The same masking can run at ingest, before anything is stored, and on alert evidence. See data redaction for every switch and its limits. For domain-specific values (customer IDs, order numbers, custom tokens), strip them at the source with the collector recipe on that page.

LLM data-handling​

  • Model providers: Anthropic Claude through AWS Bedrock in your own account (the BYOC default), Anthropic directly, Google Gemini, or a model you host, chosen with LLM_PROVIDER
  • Data retention at provider: AWS Bedrock does not train on customer data or retain it past the invocation window (per AWS Bedrock Data Privacy)
  • Prompt caching: short-lived provider-side caching only, isolated per tenant by account credentials
  • Cost containment: hard per-incident $ budget circuit-breaker (RCA_PER_INCIDENT_BUDGET_USD, default $2) prevents runaway-loop scenarios

Audit trail​

Every live-infrastructure action (kubectl-equivalent reads, cloud-API reads) is recorded in an append-only audit trail with a SHA-256 hash of its payload.

Planned: WORM (write-once-read-many) audit-log export to S3 Object Lock or Azure Immutable Blob for SOC-2 CC8.1 attestation.

Compliance​

  • SOC 2 Type II: In progress (observation window opening Q3 2026, target attestation Q1 2027). Auditor: TBD.
  • GDPR: DPA template available on request via [email protected]
  • HIPAA: Not currently certified. Reach out if you need a compliance roadmap.
  • ISO 27001: Not currently certified.

Sub-processors​

The full list of third-party services that process customer data is on the Sub-processors page.

Security disclosures + incident response​

  • Report a vulnerability: [email protected] or the InfraSage Security Vulnerability Disclosure Policy
  • Coordinated disclosure window: 90 days from initial report, negotiable for critical infrastructure severity
  • Incident notification SLA: For BYOC customers, security incidents affecting the InfraSage platform are notified within 24 hours of confirmation; for self-hosted deployments, we notify via the release-notes channel

RBAC + authentication​

  • RBAC: Backend-supported today; admin UI ships Q4 2026 (see Security → RBAC)
  • Authentication: SAML 2.0 + OIDC + local email/password + API keys with per-key scoping
  • Session management: JWT with configurable TTL; refresh-token rotation supported

Pages in this section: