Security

AEGIS by Hu is a multi-tenant compliance platform for regulated firms. The security model rests on six pillars. Where a control is built but not yet switched on in production, this page says so. The full answers are in our security questionnaire, which we send on request.

The six pillars

1.Tenant isolation

Every database row carries a verified tenantId; every query filters by it; verified middleware overwrites any client-supplied tenant header before a route handler sees the request. Postgres Row-Level Security policies are written for the tenant tables and tested in CI, but they are not yet enforced in production. Until that cutover, the application layer is the isolation control in production, and we do not claim the database would refuse a read that application code failed to filter.

2.Authentication

Identity is provided by Clerk (SOC 2 Type II): sign-in and organisation-scoped sessions. MFA is supported but not yet required for every user. Enterprise SSO (SAML) needs a paid Clerk plan, which is not in place yet. Edge middleware verifies sessions, so unauthenticated traffic reaches only the routes that are public on purpose, such as /api/health. Demo mode is rejected in production by an env-var fail-safe.

3.Encryption

In transit: TLS 1.2+ on every external surface, HSTS pre-load eligible, nonce-based Content Security Policy without 'unsafe-inline' on script-src. At rest: Supabase Postgres uses AES-256 disk encryption. PII fields (KYC profile data, identity details) are additionally protected by application-layer field-level encryption: AES-256-GCM with per-tenant keys derived via HKDF-SHA256 from a platform master key. Master-key rotation tooling is built; it has not yet been exercised on a live environment. A query that bypasses tenant isolation surfaces only opaque ciphertext to the wrong tenant.

4.Audit logging

Every regulatorily-significant action emits an entry to a hash-chained, append-only ledger. The published catalogue of auditable operations and tamper-detection properties is in the source repository (docs/AUDIT_TRAIL.md). The ledger’s public API exposes no mutation methods, so write-once is enforced in application code and pinned by automated regression tests. A database trigger that would also refuse updates and deletes is written but not yet applied in production.

5.Data residency

Every tenant’s data is stored in one EU region today, whatever region value the tenant record carries: region routing is a passthrough to a single database. The sub-processor register names the region and every other hosting location. Sign-in data (Clerk) and AI inference (Anthropic, and OpenAI for embeddings) are processed in the United States. Other regions (UK, DIFC, Singapore, Hong Kong, US) are designed for but none is live.

6.Continuous monitoring

/api/health for uptime, /api/metrics for operational counters, structured JSON logs for server-side events, held by the hosting platform. Errors flow to Sentry with PII scrubbed via beforeSend. Recovery targets are documented internally; no restore drill has been recorded yet.

One application, no internal services

Production runs as a single web application over a managed database. The source repository also holds a set of separate microservices, but they are not deployed and process no customer data, so no service-to-service traffic exists to secure.

Live status

Current platform health, subprocessor status pages, and our SLO commitments are at /status.

Vulnerability disclosure

Security researchers may report vulnerabilities to security@aegiscompliant.com. We commit to:

  • Acknowledging receipt within 2 business days.
  • Triaging and providing an initial assessment within 5 business days.
  • Acting in good faith: no legal action against researchers who report responsibly.

We are not currently running a paid bug bounty programme. Researchers who report valid vulnerabilities may be listed in the platform’s Hall of Fame on request.

Certifications & roadmap

AEGIS is bootstrap-stage. The following are in flight; we publish the plan rather than wait until the certificates are framed on the wall:

  • SOC 2 Type I: vendor selection in progress; target date set against first paying customer.
  • Independent penetration test: scoped, not yet booked.
  • Field-level encryption rollout: library landed and adopted on the highest-PII surface (KYC); other PII-bearing routes adopt incrementally.
  • Where sign-in data is held: Clerk hosts sign-in data in the United States and offers no regional hosting option on any plan. Before the first EU regulated customer goes live with real data, we will hold either a dated commitment from Clerk or a move to a provider that hosts in the EU.

More detail

Customers and prospective customers can request:

  • Our security questionnaire, answered control area by control area.
  • The platform-level DPIA.
  • The risk register, incident-response procedure, backup & restore runbook, subprocessor list (already public), and customer DPA template.
  • The most recent SOC 2 report (when available) and penetration-test summary (when available).

Reach security@aegiscompliant.com.

Last reviewed: 2026-11-14.

Security · AEGIS by Hu