Built on Principles
Our principles form the solid foundation of Spice AI’s security, guiding every decision and action we make.
Certified compliance with industry standards.
All Spice AI systems are protected by Secure-Access-Controls including Authentication (AuthN), Authorization (AuthZ), and RBAC (Role-Based-Access-Control).
All secret and sensitive information is encrypted in-transit and at-rest.
All authentication systems require and enforce Multi-Factor-Authentication (MFA).
Least-Privilege-Access is employed so that users, employees, and contractors do not have greater access than necessary.
Multiple security controls in depth.
Access and usage are logged and auditable.
Code is scanned and tested for secrets and vulnerabilities.
Access is given only when it's required.
Security & Data Protection
Corporate and production secrets are encrypted at-rest and in-transit. Corporate secrets are stored and managed in an enterprise-grade password manager with SSO access. Service secrets are stored and managed in platform-specific secure key vaults and key stores. A minimum of TLS 1.2+ is employed for encrypted transmission.
Spice AI is in the process of being certified for SOC2-2017 Type II, which is expected to be complete by Jan 2024.
Secure Code & Patch Management
Code is scanned and tested for secrets and vulnerabilities during Continuous Integration (CI) systems, using GitHub Security features like Dependabot, CodeQL, and Secrets Scanner. Base-level operating systems and container images are monitored, upgraded, and updated on regular cycles.
Access is logged and auditable.
Secure Access Control
Spice AI corporate, development, and production systems are protected by Single-Sign-On (SSO) Secure-Access-Controls. This includes secure Authentication (AuthN) and role/group-based Authorization (AuthZ).
Spice AI employs multiple levels of security, including Firewalls and Bastions for access into private networks, user, service, and machine authentication and authorization.
Deployment Environments and Controls
Deployment environments, such as Development, Production, etc. are utilized and segregated. Controls including approvals for deploying to Production environments are used, enforced, and logged.
Multi-Factor Authentication (MFA)
All access requires and enforces Multi-Factor-Authentication (MFA) where possible.
Least-Privilege-Access is employed so that users and employees do not have greater access than necessary.
No-standing-access is enforced, with users only given access when required (JIT) and for a limited period of time.