Enterprise Security Architecture
Designed to support SOC 2-aligned security practices and HIPAA-ready workflows when configured.
Multi-Tenant Isolation
Every database query filters strictly by authenticated session tenant ID (`company_id`). Cross-tenant parameter spoofing is systematically blocked.
AES-256 & TLS 1.3
Sensitive secrets and SMTP app passwords are encrypted at rest with AES-256-CBC. All network transmissions are enforced via modern TLS.
Strict Knowledge Grounding
Cai answers exclusively from verified company documents. If facts are absent, Cai clarifies or escalates to Human Action instead of fabricating data.
Audit Trails & SSRF Defense
Knowledge URL scrapers validate IP ranges against private networks and metadata endpoints. Actions are recorded in tamper-evident audit logs.
1. Cryptographic Protection at Rest & Transit
All sensitive credentials—including third-party SMTP passwords, webhook secrets, and access tokens—are symmetrically encrypted in MySQL tables using openssl AES-256-CBC with SHA-256 key derivations. Plaintext passwords are never returned in dashboard configuration responses.
2. Multi-Tenant Query Validation
Tenant authorization is established exclusively through authenticated server sessions ($_SESSION['company_id']) or cryptographically verified widget tokens. User-modifiable request parameters (such as ?company_id= or ?tenant=) are ignored on protected endpoints.
3. Role-Based Access Control (RBAC)
Granular role permissions (Owner, Admin, Manager, Sales Agent, Support Agent) are verified on both the frontend UI and the underlying backend REST endpoints before permitting any mutation or export of company records.
4. Contact Security Team
For vulnerability disclosures, compliance questionnaire inquiries, or security whitepapers, please email: