Skip to content

Security

Overview · Updated May 2026

Coming from another cloud?

▸AWS·Security Pillar

This Quake AI feature maps to AWS’s Security Pillar.

▸DigitalOcean·Security

This Quake AI feature maps to DigitalOcean’s Security.

Security

Quake AI follows a shared responsibility model: the platform secures the underlying infrastructure, and you configure and protect your workloads, data, and access within your projects.

Shared responsibility at a glance#

AreaPlatform responsibilityYour responsibility
Physical infrastructureDatacenter security, hardware, power, coolingN/A
Hypervisor and host OSIsolation between tenants, patchingN/A
Network backboneBackbone integrity, DDoS mitigationSecurity groups, firewall rules, and TLS on public endpoints
API authenticationKeystone identity, token issuanceCredential rotation, app credential scope, MFA
Compute instancesVM placement, host securityOS patching, SSH key management, user data scripts
Block storageVolume encryption at rest (infrastructure layer)Access control, snapshot policies, backup strategy
Object storageStorage infrastructure availabilityBucket policies, SSE-C/SSE-OMK encryption, access control
KubernetesControl plane provisioning (via Magnum)RBAC, network policies, image scanning, secrets
Service availabilityAPI uptime, regional redundancyWorkload redundancy, health checks, auto-scaling

For the full breakdown, see Shared responsibility model.

Start here#

Work through the Security hardening checklist on a new project. It covers the credentials, security groups, and instance settings worth fixing before you put real traffic on the project.

Concepts#

How-to#

Reference and operations#

When a token or an application credential stops authenticating, start with Auth token diagnostics. Access and credentials covers how to rotate keys and scope application credentials.

Network documents security groups, Compute covers SSH keys and instance access, and Object storage covers bucket policies and encryption options.

Was this page helpful?