Security
Security Architecture You Can Verify
Aegis security controls are built around user-owned master keys, client-encrypted vault access, signed activity records, and explicit trust boundaries between users, devices, and services.
Master key ownershipClient-side encryptionSigned audit records
Core Sections
Credential Protection
Vault data is encrypted client-side before sync operations and remains protected by device and session context checks.
- Master key derivation and unlock happen locally on trusted user devices.
- Platform services process ciphertext and cannot read credential plaintext.
- Encrypted attachments and notes with scoped visibility.
- Deterministic unlock flow with policy and trust checks.
Session Trust Signals
Runtime signals detect abnormal access patterns and trigger monitoring or containment before credential disclosure.
- Geo and device anomaly detection hooks.
- Policy-aware autofill restrictions.
- Revocation and lock actions from a central console.
Audit and Forensics
Security-relevant events are available through exportable histories designed for incident and compliance workflows.
Security Console
Need operational controls? The Security Console provides risk views and response pathways for live environments.
- Open the console from Dashboard.
- Run simulation and alert workflows.
- Track posture trends over time.