Core security pillars
CoreWeave’s approach centers on three integrated pillars:- Data security
- Network security and isolation
- Identity and access management (IAM)
Data security
Data security protects sensitive assets, including proprietary models, regulated data, and confidential business logic. Encryption capabilities and customer responsibilities differ by storage product. CoreWeave AI Object Storage encrypts data at rest and lets customers manage their own encryption keys. On supported Nodes, CoreWeave uses NVIDIA BlueField DPUs to separate infrastructure processing from the host system. Software on the DPU can offload operations such as firewalling and encryption.Network security and isolation
CoreWeave combines hardware and software controls to enforce security and workload separation. CoreWeave’s GPU-accelerated cloud supports multiple tenants with resource-intensive workloads. In this environment, network segmentation and virtual private cloud (VPC) architectures provide tenant isolation. on supported Nodes enhance hardware-level isolation. The DPU runs its own software independently from the host operating system and can offload routing and firewall tasks. CKS clusters that use Cilium provide eBPF-based network policy enforcement. You can deploy Tetragon for additional observability. Hubble requires a per-cluster configuration change from CoreWeave Support. The platform uses overlays with and to provide Layer 3 multi-tenancy without relying on hypervisors. This enables each tenant or namespace to operate in a dedicated, isolated network segment (VRF/VNI).Identity and access management (IAM)
Identity and access management (IAM) governs platform access for users, services, and workloads using principles of least privilege and role-based access control (RBAC). CoreWeave IAM Access Policies manage access to platform resources. CoreWeave AI Object Storage also provides organization access policies, workload identity federation, and audit logging. CoreWeave AI Object Storage supports workload identity federation with OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). Workloads can exchange external identity tokens for temporary Object Storage credentials instead of storing long-lived access keys. For storage access, organization access policies are written in JSON and apply to every request. Bucket policies can further refine access. Object Storage evaluates these policy types in a defined order, with exceptions for specific actions.Summary of security features
The following table summarizes key security features of the CoreWeave platform.
Together, data security, network isolation, and IAM form the foundation of CoreWeave’s security model.
For more information, see CoreWeave Security.