Alpha notice: Aegis has not undergone an independent security audit. The security practices described here reflect our design intent. We plan to commission a third-party audit before general availability. Do not rely on Aegis for threat models requiring certified security assurances.

Security

Last updated: May 2026

Encryption at Rest

All PII fields (names, emails, phone numbers, account descriptions, location notes, executor notes) are encrypted at rest using AES-256-GCM. Each sensitive field has its own encrypted envelope. Category and title fields remain plaintext for filtering purposes.

Passwords are hashed with Argon2id (memory-hard, timing-safe). Password hashes are never exposed in API responses or logs.

Encryption in Transit

All communications use HTTPS/TLS. Cookies are set with HttpOnly, Secure (in production), and SameSite=Lax flags. API keys and session tokens are never passed in URL query strings.

CSRF and Session Security

All state-changing requests require a CSRF token (X-CSRF-Token header). Sessions use cryptographically random identifiers stored in HttpOnly cookies. Sessions expire after 7 days. Rate limiting is applied to authentication endpoints.

Trust Models

Aegis Core (Self-Hosted)

Your data stays on your infrastructure. You control the encryption keys. No data leaves your host unless you enable Relay services. Trust model: you trust yourself and your hosting environment.

Aegis Relay Monitoring

Aegis monitors your heartbeat and alerts your contacts if you go offline. No estate release material is held by Aegis. Trust model: you trust Aegis to accurately detect offline status and notify contacts.

Aegis Relay Escrow

Aegis holds encrypted release material. In an offline/incapacity scenario, Aegis can execute the release on your behalf. Trust model: you trust Aegis to hold and release material responsibly. Explicit acknowledgement required before enabling.

Aegis Hosted

Fully managed. Aegis stores your encrypted estate data and manages the release process. Trust model: you trust Aegis as a service provider, similar to trusting a cloud storage provider.

Audit Logging

Security-relevant events are logged with redacted payloads. Audit logs never contain plaintext PII, contact names, emails, phone numbers, or estate item content. Logs are structured and retained for operational security review.

Alpha Limitations

No independent third-party security audit has been performed
No Shamir Secret Sharing or multi-party key management
No "zero knowledge" architecture — Aegis can decrypt hosted data with server-managed keys
No formal penetration testing

Vulnerability Reporting

Report security issues to security@aegisdms.life.