Security
Built with tenant boundaries and auditability first
Envene is security software, so the product itself is designed around scoped access, encrypted credentials, clear permissions, and transparent records.
Team isolation
Tenant records are scoped by team and route access is protected by membership middleware and policies.
Encrypted integration tokens
OAuth token material lives in encrypted integration account storage and is excluded from activity logs.
Audit trails
Security-relevant actions are recorded for integration changes, scans, findings, apps, agents, tasks, and reports.
Metadata-first scans
The product focuses on inventory and access metadata rather than ingesting raw customer document content.
Local MCP caution
MCP tools should run only in trusted environments with appropriate database and transport controls.
Data handling posture
Scans use customer-approved, read-only OAuth access and inventory access metadata — apps, scopes, and sharing — never raw document contents. Provider clients are validated against credentials and API behavior before they are enabled for a workspace.
- Team-scoped models and policies guard tenant data.
- Read-only Google scopes are used for live Workspace metadata.
- Generated reports should be stored on protected object storage.
- Security contact configuration is available through SECURITY_SECURITY_EMAIL.