Marvell, Microsoft and Oracle Launch OCP Integrated HSM Standard for Cloud Servers

The three companies announced a collaborative effort aligned with the OCP. It aims to standardize a NIST FIPS 140-3 Level 3 integrated HSM for cloud and hyperscale data center infrastructure. It matters to Azure customers and enterprise IT admins because it targets where cryptographic keys live and how a workload proves it is trustworthy.

What was announced​

The working group sits under OCP's Security Track. Its charter is to define open specifications for an integrated HSM that handles secure key caching and cryptographic key lifecycle management directly at the server level.

The companies' reasoning is that most cloud and enterprise servers rely on network-attached HSMs or software-only key management. That means keys either cross the network or sit in memory that isn't FIPS 140-3 Level 3 protected. The proposed fix is an open specification for embedding a hardware security boundary, key vault and attestation chain directly in the server.

TipRanks' plain-language summary says the aim is for a server to avoid fetching keys from a distant security system every time. It also says the server should be able to verify that the security chip and key are genuine and untampered. That matches the companies' description.

Timeline​

An open technical specification draft is planned for the OCP Global Summit in October 2026. Per the announcement, the summit runs October 12–15 in San Jose, and version 1.0 follows later with no date given. The companies plan booth demonstrations and Security Track presentations. A Marvell event listing names an October 15 session on bringing silicon-level key security to the server tray. That listing shows planned activity. It is not proof that a draft has been published or a demo completed.

What the executives said​

These are projected benefits, not measured results. The announcement gives no benchmarks.

• Marvell's Cary Ussery: An integrated HSM would let key operations run where the workload runs. He said it would satisfy regulatory compliance and zero-trust requirements without compromising performance.
• Microsoft Azure's Mark Russinovich: He described industry leaders coming together around a fully open-source integrated HSM. He said it would advance interoperability and accelerate adoption of post-quantum cryptography.
• Oracle's Pradeep Vincent: He called an open specification an important step toward a common foundation for industry adoption.

What "FIPS 140-3 Level 3" does and doesn't mean​

NIST says FIPS 140-3 is a standard for cryptographic modules. It sets four increasing, qualitative security levels meant for a range of applications and environments. Its requirement areas include physical security, sensitive security parameter management, self-tests and life-cycle assurance.

The announcement describes a target, not a validation:

• Validation applies to a specific module and tested configuration.
• The announcement names no module, certificate, test lab or security policy for this effort.
• Level 3 is not a certification of a whole server, cloud service or workload.
• NIST's Cryptographic Module Validation Program keeps lists of modules in process and validated. Future claims should be checked there.

For context, NIST's modules-in-process list, last updated October 13, 2026, includes Marvell entries such as an "LS2 HSM Family" module. I can't tell from the list whether those relate to this working group, so treat any link as unestablished.

Existing Microsoft and Marvell context​

Neither Microsoft nor Marvell is starting from zero here, but the announcement doesn't say how this effort relates to their existing products.

Azure Integrated HSM. Microsoft Learn describes this as a hardware security module cache and crypto offload for virtual machines. That quote isn't from the announcement, so I'm paraphrasing the Learn page: on new AMD D-series v7 and E-series v7 servers, Microsoft-designed HSM chips are embedded in the hosts and meet FIPS 140-3 Level 3. The page's documented limits show how much deployment detail matters:

• It is supported on specific AMD v7 VM families, at 8 vCores and above, with Trusted Launch only.
• General availability is Windows-guest only, with Windows Server 2025 or 2022 images. Linux is listed as coming soon.
• It requires customer opt-in for supported SKUs.
• It is a local key cache for ephemeral operations, so keys don't persist across VM reboot or deallocation.

Those are limits of today's Azure service. They are not stated limits of the OCP specification. The OCP announcement doesn't say the new spec is the same technology as Azure Integrated HSM.

Azure Cloud HSM. Microsoft's documentation says this separate service uses Marvell LiquidSecurity HSMs validated to FIPS 140-3 Level 3. That shows an existing Microsoft–Marvell HSM relationship. It says nothing about the design or commercial status of the new in-server effort.

Why OCP​

The OCP Security Project says it creates designs and specifications for hardware-based security across IT gear. It aims to give other OCP projects a common foundation instead of each building its own. Its listed focus areas include boot code integrity, secure boot and recovery, firmware provisioning and attestation work. An integrated HSM spec fits that mission. But the new group's output hasn't been shown to be an approved OCP specification, and nobody beyond the three founding members has publicly joined. The announcement invites other organizations to participate through OCP.

Open questions​

My read, from general industry knowledge rather than the announcement, is that the hard parts sit in the details the press release doesn't cover. An HSM is a protected cryptographic module. It is not a complete key-management policy or a workload identity system. Watch for the following when the draft appears:

1. Threat model and interfaces: what the module defends against, and how software talks to it.
2. Attestation: how evidence is generated and who verifies it.
3. Key lifecycle: provisioning, rotation, backup, recovery and what happens on server failure. A local cache that loses keys on reboot, as Azure Integrated HSM's does, behaves very differently from durable storage.
4. Validation scope: which module and configuration actually earn a CMVP certificate.
5. Compatibility and availability: which server platforms, operating systems and clouds will support it, and when independent vendors can test hardware.

Practical impact​

For most Windows admins, nothing changes today. The announcement identifies no operating systems, server vendors, regions, pricing or customer availability, and it isn't a feature you can switch on. The audience is mainly hyperscale operators, server and silicon designers, and organizations that depend on validated modules.

If you run workloads on Azure, Azure Integrated HSM is the nearest concrete service to read up on. Be careful about assuming it implements the future spec. The real test will be whether the draft is detailed enough for rival vendors to build interoperable hardware, and whether independent validation follows. Until then, the announcement is a statement of intent from three big players.