Aeion CRM Security Architecture

CRM systems hold the most sensitive customer data your business has — contact PII, pipeline projections, customer financial information, communication history. Aeion's defense: per-tenant data isolation enforced at the database layer (cross-tenant queries impossible), AES-256 encryption at rest for sensitive fields, a full activity audit log, GDPR right-to-erase + right-to-export pipeline, SOC 2 + ISO 27001 + GDPR architecture mapping.

Defense-in-Depth Inventory

Per-tenant isolation

Enforced at the data layer — every query is auto-scoped to your tenant; cross-tenant queries return zero rows

RBAC at the data layer

Access rules are evaluated before every read/write — per-object, per-role

Encryption at rest

AES-256-GCM for sensitive PII fields (when enabled)

Email content encryption

Optional — encrypt email body + attachments in your engagement history

Activity audit log

Every CRM action is recorded (deal updates, contact changes, email opens, etc.)

API key scoping

Per-key permission scopes; sales reps can have read-only API keys for analytics tools

GDPR pipeline

Right-to-erase + right-to-export with 30-day SLA

PII redaction

Configurable per-tenant (e.g., redact SSN-like patterns in notes)

Backup integrity

Aegis pgBackRest WAL archiving + S3 Object Lock — tamper-evident at storage layer

Per-Tenant Isolation

Multi-tenant CRM deployments need rigorous data isolation — Customer A's pipeline must NEVER be visible to Customer B's session.

Role-Based Access at the Data Layer

CRM systems have rich role hierarchies — sales rep can see own deals, manager can see team's deals, admin sees all. Aeion enforces this at the database query layer, not just the UI.

Activity Audit Log

Every CRM action lands in the activity timeline — deal updates, contact and company changes, emails sent/opened/clicked, meetings scheduled and completed, notes, tasks, calls, pipeline and stage changes, lead-score changes, and churn-risk changes. Each entry records who performed the action, from where, and the before/after state for updates.