
In this article
A cloud provider can run the hardware that protects a payment key. Your team may still decide which application can use the key and who takes over when it needs replacing. To see what you’re buying, follow one payment key through those decisions.
In September 2026, the PCI Security Standards Council released version 1.0 of its Key Management and Operations Standard, or KMO. The Council says the standard covers payment key management from generation to destruction, initially focusing on keys for protecting personal identification numbers (PINs) and for point-to-point encryption (P2PE). The release also addresses cloud and remote hardware security modules.
What PCI KMO v1.0 covers
A hardware security module, or HSM, is a device designed to protect cryptographic keys and perform cryptographic operations. A payment HSM supports operations used in payments. An HSM may protect a key while an application is allowed to request a particular operation with that key. That’s why you need to ask who controls the application’s access as well as who protects the hardware.
The Council’s announcement covers the procedures and systems around the key as well as the hardware. Check the standard and programme rules when you need to know whether a particular service or listing covers your operation.
Two cloud services can divide the work differently
AWS describes its Payment Cryptography service as taking responsibility for the physical compliance of the HSMs it uses and enforcing the key attributes configured for the service. AWS says the customer is responsible for configuring the key’s attributes and access. That leaves the customer with real decisions about which applications and people should be able to request a payment operation.
Microsoft describes its Azure Payment HSM offering as a single-tenant service in which the customer gets administrative control and exclusive access to its allocated HSM. In that arrangement, ask who on your team will administer the device and plan for recovery. For either service, check what your programme will accept and what the provider can document for the operation you need.
Follow one payment key through a change
Suppose a small processor needs to replace a payment key that a partner also relies on. Before scheduling the change, the processor writes down what the key is for, which application uses it, which people can approve changes and which partner needs to be ready. The partner’s readiness matters: changing the key on the processor’s side alone could interrupt the payment flow.
In this example the provider protects the hardware and applies the configured limits on use. The processor controls which application identity can request the approved operation. It also coordinates the change with its partner, confirms that the application is using the replacement as intended, and keeps the relevant change and access records. The processor asks what record the provider supplies for its part of the work. Before retiring the old key, the processor checks with its partner whether anything still depends on it. The exact retirement plan depends on the payment operation, applicable rules and the service.
NIST describes distinct phases for preparing a key, operating it, handling it after active use and destroying it. That sequence is a useful planning aid. Ask who is responsible at each step, including who can tell you whether a key has been retired. Record who can confirm retirement before marking the change complete.
What to settle before choosing a provider
In a discussion among security practitioners, a commenter asked a small payments team to separate general cryptography from the specific operations it needed to perform. Take that distinction to your provider. A general-purpose HSM and a managed payment cryptography service are sold for different jobs. Ask your partner and the provider about your actual operation, and check any required validations with the organisation that manages the programme.
Take one representative key to the next provider call. Ask who decides its permitted use, who can change access, who handles replacement with the partner, and who supplies evidence for each step. Include what happens if the key is suspected to be compromised or you leave the service. Where the answers are shared, write down the part each side does. Use that list to compare providers before committing to a service.
Related 443 Labs guides
Ask 443 Labs to help map your payment cryptography services and the security responsibilities that sit around them.
Get in TouchSources
Related Services















