Aeion Search Security
External search vendors create three security problems at once — a second access-control system to keep in sync, a second audit log to reconcile, and a second copy of your data sitting in someone else's infra. Aeion Search runs inside your Postgres. Every query automatically inherits the user's tenant, identity, and permissions. Every result respects that collection's access rules. Every search is captured to the audit trail with retention per your policy. PII redacted at index time. SOC 2 Type 2 + HIPAA BAA + GDPR covered.
Tenant Isolation by Construction
Zero cross-tenant leakage, enforced at every layer of the request.
PII Redaction at Index Time
Sensitive fields can be excluded from full-text vectors and embeddings.
Audit Trail
Every search captured. Retention per tenant policy.
Compliance Coverage
`
Prompt-Injection Defense for Agentic RAG
When LLM agents call search, the query text may itself be an attack vector.
FAQ
Impossible at the SQL layer. Every query has the tenant scope hardcoded into it automatically. The user cannot override it.
Postgres TDE (Transparent Data Encryption) + per-tenant CMK (Customer-Managed Keys) on Enterprise tier. Embeddings encrypted alongside source data.
TLS 1.3 enforced for all connections. mTLS available for service-to-service calls.
Per-tenant admin sees their own logs. Cross-tenant admin access (Aeion platform staff) is gated by SOC 2 break-glass procedure with auditable approval.
Cascade delete via collection foreign key. Embedding row removed atomically with source row. HNSW index re-builds incrementally.
Per-tenant configurable. Default for EU tenants: 30 days. Per-purpose annotation supports lawful basis tracking.
Per-query content scanning via configurable patterns. Suspicious queries flagged + optionally blocked.
Annual third-party pen test covers search endpoints. Reports available under NDA.
Per-tenant SIEM export to Splunk, Datadog, Elastic, Sumo Logic, custom webhook. Per-event format configurable.
Yes — per-tenant admin role has read access to search logs within their tenant. Read access itself logged.
Every search log entry records how the search was invoked, including MCP. Same RBAC scope as a human user, with agent-persona attribution.
Zero by construction. Embeddings and indexes live in your Postgres. Aeion staff has no access to tenant data outside SOC 2 break-glass.