CoreWeave Inc. introduced Remote Key Encryption on Tuesday, a service that encrypts customer data on its AI cloud using keys the company never possesses. The offering targets the key-custody problem that stalls enterprise AI projects in security review, because auditors demand a named list of everyone able to decrypt sensitive material and most cloud providers appear on that list. Model weights and training checkpoints fall under the same regulated-data rules as other corporate information, CoreWeave noted.
Under the service, encryption runs client-side inside the customer's own compute boundary, using keys generated and stored in the secrets manager, key management system or hardware security module the customer already operates. No key is imported into a CoreWeave-side key store, leaving the company holding only ciphertext. Access to the nodes remains gated behind CoreWeave's Support Access Management controls, and support engineers cannot reach those nodes without the customer's express permission.
Key rotation, expiration and revocation follow the customer's existing schedule and tooling. CoreWeave said the service drives rotation and deletion through that infrastructure instead of standing up a parallel set of controls, and that the key lifecycle management approach is patent pending. The underlying encryption algorithms are standard ones. Andy Manoske, CoreWeave's product lead for enterprise and security, and Paul Friedman, head of security foundations, wrote in a blog post that the fastest route to production is not a new security model but making the company's security layer speak fluently to the one customers already built.
That same principle shapes CoreWeave's earlier identity work. CoreWeave IAM handles authentication and authorization across the cloud and federates with enterprise identity providers including Microsoft Corp.'s Entra and Okta Inc., leaving the customer's provider as the source of truth. Automated User Provisioning, introduced last November, syncs users and groups continuously so a hire, role change or termination propagates across CoreWeave Kubernetes Service, AI Object Storage and the console without a ticket.
Training clusters present a harder case. CoreWeave's SUNK packages the open-source job scheduler Slurm for Kubernetes, and Slurm keeps its own notion of identity built on POSIX users, groups and accounts, which traditionally required manual reconciliation with a corporate directory. SUNK User Provisioning creates the POSIX user and groups, syncs SSH keys and sets up the Slurm account as soon as a federated user appears in CoreWeave IAM. Adding a researcher to a group in Entra or Okta lets that person log in to a cluster node within a minute with permissions already set, according to the company.
Remote Key Encryption enters limited availability later this year with IBM Corp. as launch partner. The first release protects data on CoreWeave AI Object Storage using keys held in HashiCorp Vault, HashiCorp Vault Enterprise or any key management or hardware security product supporting the Key Management Interoperability Protocol. IBM acquired HashiCorp Inc. in February 2025. CoreWeave's Fully Connected conference runs in San Francisco from Sept. 30 to Oct. 1.
More cybersecurity news from TechManNews.
