From the source
Baseten has published a walkthrough of how it holds one security standard across a fleet of 20+ clouds and 100+ clusters, including more than a dozen neoclouds it uses for global scale.
- The company says it treats GPUs as fungible across providers, so every cluster is evaluated and hardened before it serves traffic, because neoclouds are often less hardened and less uniform than hyperscalers.
- Baseten describes a threat model with four trust boundaries: the infrastructure layer, operating partners, workloads, and internal access.
- At handover it closes every public port except those serving traffic, puts the Kubernetes API behind an allowlist, and sets SSH to key-only access with regularly rotated keys, with on-demand SSH behind multi-factor authentication and multi-party approval.
- Customer builds run in microVMs, tenants are isolated on the network, and RDMA transfers pass through a node agent that authorizes each one.
- Baseten says nobody there has standing administrative access to production clusters, and that it scopes credentials to one cluster at most so a compromised cluster cannot reach another.
- The post ends with a checklist readers can apply to their own fleet or use when evaluating a provider's security standards.






