SECURITY
Enterprise-grade trust by default.
Security spans identity, access, encryption, auditability and operational controls across every request Olive governs. Data-specific boundaries and residency are covered separately in Data Security.
The short answer
Olive is built to meet the access, encryption and audit expectations enterprise security teams already require, before any question of what data can move where.
What matters in practice.
Enterprise AI decisions depend on context, not just the name of a model.
Identity
SSO with SAML or OIDC, role-based access
Encryption
In transit and at rest, customer-managed keys available
Auditability
Immutable record of decisions, approvals and policy changes
Least privilege
Read-only connectors for observe-mode deployments
IN PRACTICE
How the idea applies to enterprise work.
Access before execution
Requests are evaluated against identity, role and permission before any model or tool is reached.
Evidence after execution
Decisions, policy versions and approvals are preserved so security and compliance teams can review them later.
Operational controls
Tenant isolation, retention settings and SOC 2-aligned operational practices apply across deployment modes.
COMMON QUESTIONS
Security, explained.
How does Security differ from Data Security?
Security covers identity, access, encryption and audit controls overall. Data Security focuses specifically on data boundaries, sensitive content handling, retention and residency.
Can Olive integrate with our existing SSO?
Yes. Olive supports SAML and OIDC-based single sign-on with role-based access control.
Is there an audit trail for policy and routing decisions?
Yes. Approvals, policy versions and routing decisions are preserved in an auditable record.
Explore Model Fabric topics