Skip to main content

Security Architecture

Hystersis implements defense-in-depth security across authentication, authorization, data protection, and network layers.

Authentication

API Key Authentication

All API requests require an API key via the X-API-Key header:
API keys support:
  • Scoped permissions — Limit key access to specific operations
  • Rate limiting — Per-key rate limits
  • Expiration — Keys can be set to expire
  • Rotation — Seamless key rotation without service interruption

Session Authentication

Web dashboard users authenticate via JWT tokens:

Social OAuth

Supports Google and GitHub for user registration:

Encryption

Data at Rest

  • Neo4j — TLS for in-transit, disk encryption at rest
  • Qdrant — Encrypted vector storage
  • Redis — Encrypted persistence (AOF)
  • S3/GCS — Server-side encryption (AES-256)

Data in Transit

  • All API endpoints enforce TLS 1.2+
  • Internal service communication uses TLS
  • Database connections use encrypted protocols (Bolt, gRPC)

Multi-Tenant Isolation

Tenant Isolation

Each tenant’s data is isolated at the storage layer:
  • Neo4j — Data segregated by tenant_id node property
  • Qdrant — Per-tenant collections with payload filtering
  • Redis — Namespace-prefixed keys per tenant

API Key Scoping

Security Headers

All API responses include security headers:

Audit Logging

All operations emit audit events:

Compliance

  • SOC 2 Type II — Audit controls and monitoring
  • GDPR — Data subject rights, right to erasure
  • CCPA — Consumer data access and deletion
  • HIPAA — Available with BAA for healthcare use

Best Practices

  1. Rotate API keys every 90 days
  2. Use scoped keys with minimum necessary permissions
  3. Enable 2FA for all admin accounts
  4. Review audit logs regularly
  5. Keep dependencies updated
  6. Use VPC/private networks for database connectivity
  7. Enable encryption at rest and in transit

See Also