Marvell, Microsoft and Oracle are forming a new Open Compute Project working group to standardize server-level hardware security for cloud and hyperscale data centers.

Marvell announced the effort on October 13. The group is targeting a silicon-based, attested hardware security module, or HSM, designed around NIST FIPS 140-3 Level 3 requirements. The companies say an initial draft specification is being released through OCP so other vendors and operators can participate.

The core idea is to move more cryptographic trust directly into the server. HSMs protect sensitive keys and perform cryptographic operations inside dedicated hardware rather than exposing those keys to ordinary host software. NIST’s FIPS 140-3 standard defines four increasing security levels for cryptographic modules and covers physical security, authentication, sensitive parameter management, self-tests and life-cycle assurance.

Posts by MarvellTech

Marvell’s public engineering feed covers the company’s current data-center silicon and open-infrastructure work.

According to Marvell, the proposed design is intended to handle secure key caching, attestation and cryptographic key life-cycle management at the server level. The company argues that bringing those functions closer to compute can reduce latency and improve scalability compared with sending every cryptographic operation to a separate appliance.

Thales explains how hardware security modules protect cryptographic keys and act as trust anchors for cloud and enterprise systems.

This is not simply another security chip announcement. The important part is the attempt to define a common hardware interface through OCP. BitcoinVersus.Tech recently covered OSPA’s effort to standardize switch-platform management. The new HSM working group applies a similar open-specification approach to trust and key management inside servers.

The move also fits a broader shift toward hardware-enforced infrastructure controls. BitcoinVersus.Tech has examined specialized security processors inside Fortinet hardware and Lattice’s open control-plane approach for AI racks. In each case, more management and security logic is moving into dedicated silicon close to the hardware it protects.

The new OCP group still has to turn the proposal into a specification vendors will actually implement. FIPS 140-3 validation is also a formal testing process, so an open specification does not automatically make a product compliant. But a shared server-level HSM design could reduce duplicated engineering across cloud platforms and make hardware trust easier to integrate consistently across large fleets.

For data-center operators, the practical question is whether a common standard can make key protection, attestation and server identity more portable without weakening the isolation that gives HSMs their value. That is the problem Marvell, Microsoft and Oracle are now trying to solve through OCP.

BitcoinVersus.Tech Editor’s Note:
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiatives, please donate using the QR code provided

For best QR-code scanning results, please scan this donation code from a desktop or larger screen. Mobile screens may prevent camera recognition.