Skip to main content

Secure Product Architecture

In addition to the security principles we adhere to and our secure development lifecycle, we provide a cohesive security architecture for Palette.

Secure Product Architecture​

Palette uses a microservices-based architecture, and we take steps to ensure each service is secured. Product functionality is broken down logically into isolated services within containers. Containers are deployed in a Kubernetes cluster, called a management cluster, which Palette hosts and manages in Software as a Service (SaaS) mode or that users can host and manage in a self-hosted environment.

Deployment Models​

Palette and Palette VerteX support three architecture models: multi-tenant SaaS, dedicated SaaS, and self-hosted, which includes support for airgapped environments. With these flexible deployment models, we can work within your existing requirements for responsibility separation and network restrictions. Model availability depends on the edition of Palette (Palette or Palette VerteX) and the location of the deployment (US or EU).

Deployment ModelDescription
Multi-Tenant SaaSThe management plane is hosted in AWS and managed by Spectro Cloud. Each customer operates as an isolated tenant with enforced data isolation and access controls. Spectro Cloud controls management plane upgrades.
Dedicated SaaSThe management plane is hosted as a dedicated instance in a customer-selected cloud and region within Spectro Cloud's cloud account. Spectro Cloud manages the instance, and the customer controls when to upgrade the management plane.
Self-HostedThe management plane is hosted in the customer's environment. This environment can be a public cloud, a data center, or bare metal devices. This model supports airgapped environments.

SaaS Region Availability​

Deployment ModelGeographyPalette RegionsPalette VerteX Regions
Multi-Tenant SaaSUSus-east-1, us-west-1, and us-west-2us-gov-west-1
Multi-Tenant SaaSEUeu-central-1 and eu-west-1Not available
Dedicated SaaSUSCustomer decidesNot available
Dedicated SaaSEUCustomer decidesNot available

A diagram of Palette deployment models

Palette’s robust security measures safeguard your data and ensure the integrity of our services. We adhere to industry-leading standards and continuously refine our practices to provide the highest level of security. Palette infrastructure safeguards data in your Kubernetes production environment with its zero-trust architecture, granular Role-Based Access Control (RBAC), immutable Linux distributions (Kairos), and hardened clusters and Kubernetes packs.

Palette's security controls ensure data protection in SaaS operation at the management platform level and the tenant cluster level. To learn more, refer to SaaS Operation. In self-hosted operation, you must ensure security controls in your environment. Find out more about self-hosted deployment in Self-Hosted Operation.

Multi-Tenancy​

Palette and Palette VerteX have multi-tenant SaaS platforms, where every tenant represents a customer. We ensure tenant isolation through the following design principles and techniques:

  • Network Isolation - Tenant clusters are created in the tenant’s public cloud accounts or in private data centers. Customers cannot intercept network traffic in other tenant clusters. Access to tenant cluster APIs through the cluster’s kubeconfig file is restricted to the tenant.

  • Data Isolation - Palette applies a tenant filter to every operation to ensure users' access is restricted to their own tenant.

  • Tenant Data Encryption - Tenant data is encrypted, and all message communication uses tenant-specific channels.

  • Audit Policies - We record all actions taken on the platform and provide a comprehensive report for tracking purposes.

  • Noisy Neighbor Prevention - In the SaaS deployment model, we use AWS Load Balancers and AWS CloudFront with a web application firewall (WAF) for all our public-facing services. These services benefit from the protections of AWS Shield Standard, which defends against the most common and frequently occurring network and transport layer Distributed Denial-of-Service (DDoS) attacks that target applications. This ensures that excessive calls from a tenant do not adversely affect other tenants' use of the platform.

Palette Authentication & Authorization​

Palette fully supports RBAC and two authentication modes:

  • Local Authentication and Password Policy - With local authentication, a user email serves as the ID, and a password is compared with the one-way hash stored in the database to authenticate users to a tenant. The platform administrator can set password policy to control the requirements for password length, rule, and expiration. Users who sign in with a password can also add a passkey as a second factor, and tenant administrators can require one. Refer to Manage Passkeys and Passkey Enforcement for more information.

  • Single Sign-On (SSO) and Multi-Factor Authentication (MFA) - In these modes, the tenant is configured to have Security Assertion Markup Language (SAML) 2.0 Identity Provider (IDP) integrations. If the IDP requires MFA, you are redirected to the IDP to authenticate. SSO can also automatically map a user to one or more user groups in the tenant.

API Security​

Palette uses JSON Web Token (JWT)-based authentication and authorization for Representational State Transfer (REST) API access over HTTPS.

The authentication token is valid for a limited time. If the token is about to expire, you can request a token refresh before making other API calls. Tokens are revoked when a user logs out or changes their password.

Palette has a common API gateway validation service that ensures there are no incorrect parameter values or potential vulnerabilities, such as Structured Query Language (SQL) injection or cross-site scripting.

You can use the gateway validation service log to trace APIs with a unique ID, Tenant UID, or Session UID. To avoid revealing unnecessary information, all UID values are 48-bit random hex strings.

Refer to the API Key Authentication guide for details.