> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to CoreWeave Security

> Introduction to CoreWeave's security approach across data protection, network isolation, and access management

CoreWeave uses product-specific controls to protect data, isolate network traffic, and manage identity for large-scale AI workloads. On supported Nodes, Data Processing Units (DPUs) provide a hardware-separated execution environment for infrastructure services.

## Which access controls apply to your work

CoreWeave Infrastructure and Forge (Weights & Biases) each have separate authorization and access control systems. The following table provides a comparative overview of each one:

| | CoreWeave Infrastructure | Forge |
| - | - | - |
| **What it governs** | CKS clusters, VPCs, Object Storage, observability, and billing | Projects, teams, organization membership, and which products a user can reach |
| **Principals** | Users and groups | Users, teams, and service accounts |
| **How access is granted** | [IAM Access Policies](https://docs.coreweave.com/security/iam/access-policies.md): a policy holds rules, and each rule assigns [roles](https://docs.coreweave.com/security/iam/access-policies/roles.md) to a principal. Default-deny, so access exists only where a policy grants it | [Organization and team roles](https://docs.coreweave.com/products/wandb/platform/hosting/iam/access-management-intro.md), plus per-project visibility scopes |
| **Where access is scoped** | The organization, evaluated per action across services | The [organization, team, and project](https://docs.coreweave.com/products/wandb/platform/hosting/iam/org_team_struct.md) hierarchy |
| **Provisioning from your IdP** | [Automated User Provisioning](https://docs.coreweave.com/security/automated-user-provisioning.md) over SCIM, with group memberships flowing into IAM | [SCIM provisioning](https://docs.coreweave.com/products/wandb/platform/hosting/iam/scim.md) |
| **Automated access** | [OIDC Workload Identity](https://docs.coreweave.com/products/cks/auth-access/workload-identity/introduction.md) for CKS workloads reaching external cloud services, and [workload identity federation](https://docs.coreweave.com/products/storage/object-storage/auth-access/workload-identity-federation/about.md) for Object Storage credentials | [Service accounts](https://docs.coreweave.com/products/wandb/platform/hosting/iam/service-accounts.md) and [API keys](https://docs.coreweave.com/products/wandb/platform/hosting/iam/api-keys.md) for workflows such as CI/CD pipelines |

If you administer both platforms, see [Forge and CoreWeave identity](https://docs.coreweave.com/security/forge-identity-and-access.md) for how the two identity systems relate and where each administrative task belongs.

The following sections describe how CoreWeave implements security across data protection, network isolation, and access management.

## 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](https://docs.coreweave.com/products/storage/object-storage/buckets/server-side-encryption/about-sse-c.md).

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.

Data Processing Units (DPUs) (A Data Processing Unit (DPU) is a specialized processor that provides network and other infrastructure functions separately from the host CPU.) on [supported Nodes](https://docs.coreweave.com/products/networking/nimbus.md) 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](https://docs.coreweave.com/products/networking/cilium-network-policy-cks-patterns.md). You can deploy [Tetragon](https://docs.coreweave.com/security/tutorials/ebpf-observability.md) for additional observability. Hubble requires a per-cluster configuration change from CoreWeave Support.

The platform uses Ethernet Virtual Private Network (EVPN) (An Ethernet Virtual Private Network (EVPN) interconnects Layer 2 networks and carries Layer 3 VPN services.) overlays with VXLAN encapsulation (Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) combines EVPN's Control Plane with VXLAN's Data Plane.) and Type 5 routes (A Type 5 EVPN deals exclusively with IP route advertisement.) 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](https://docs.coreweave.com/products/storage/object-storage/auth-access/organization-policies/about.md), [workload identity federation](https://docs.coreweave.com/products/storage/object-storage/auth-access/workload-identity-federation/about.md), and [audit logging](https://docs.coreweave.com/products/storage/object-storage/auth-access/audit-logging.md).

CoreWeave AI Object Storage supports [workload identity federation](https://docs.coreweave.com/products/storage/object-storage/auth-access/workload-identity-federation/about.md) 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.

| Component | Description |
| - | - |
| Data Processing Units (DPUs) | On supported Nodes, NVIDIA BlueField DPUs provide a hardware-separated environment that runs infrastructure software independently from the host operating system. |
| EVPN-VXLAN | Ethernet Virtual Private Network (EVPN) is used for efficient and scalable Layer 2 and Layer 3 VPN services. VXLAN (Virtual Extensible LAN) is used to encapsulate network traffic and create a virtualized network overlay. |
| Type 5 Routes in EVPN | Enable inter-tenant routing and traffic forwarding between isolated network segments. |
| Isolated networks for sensitive workloads | Networks are physically and virtually isolated to keep sensitive workloads secure and inaccessible to unauthorized systems. |

Together, data security, network isolation, and IAM form the foundation of CoreWeave's security model.

For more information, see [CoreWeave Security](https://www.coreweave.com/security).
