Azure Managed HSM Overview - Azure Managed HSM (2024)

Azure Key Vault Managed HSM (Hardware Security Module) is a fully managed, highly available, single-tenant, standards-compliant cloud service that enables you to safeguard cryptographic keys for your cloud applications, using FIPS 140-2 Level 3 validated HSMs. It is one of several key management solutions in Azure.

For pricing information, please see Managed HSM Pools section on Azure Key Vault pricing page. For supported key types, see About keys.

The term "Managed HSM instance" is synonymous with "Managed HSM pool". To avoid confusion, we use "Managed HSM instance" throughout these articles.

Note

Zero Trust is a security strategy comprising three principles: "Verify explicitly", "Use least privilege access", and "Assume breach". Data protection, including key management, supports the "use least privilege access" principle. For more information, see What is Zero Trust?

Why use Managed HSM?

Fully managed, highly available, single-tenant HSM as a service

  • Fully managed: HSM provisioning, configuration, patching, and maintenance is handled by the service.
  • Highly available: Each HSM cluster consists of multiple HSM partitions. If the hardware fails, member partitions for your HSM cluster will be automatically migrated to healthy nodes. For more information, see Managed HSM Service Level Agreement
  • Single-tenant: Each Managed HSM instance is dedicated to a single customer and consists of a cluster of multiple HSM partitions. Each HSM cluster uses a separate customer-specific security domain that cryptographically isolates each customer's HSM cluster.

Access control, enhanced data protection & compliance

  • Centralized key management: Manage critical, high-value keys across your organization in one place. With granular per key permissions, control access to each key on the 'least privileged access' principle.
  • Isolated access control: Managed HSM "local RBAC" access control model allows designated HSM cluster administrators to have complete control over the HSMs that even management group, subscription, or resource group administrators cannot override.
  • Private endpoints: Use private endpoints to securely and privately connect to Managed HSM from your application running in a virtual network.
  • FIPS 140-2 Level 3 validated HSMs: Protect your data and meet compliance requirements with FIPS (Federal Information Protection Standard) 140-2 Level 3 validated HSMs. Managed HSMs use Marvell LiquidSecurity HSM adapters.
  • Monitor and audit: fully integrated with Azure monitor. Get complete logs of all activity via Azure Monitor. Use Azure Log Analytics for analytics and alerts.
  • Data residency: Managed HSM doesn't store/process customer data outside the region the customer deploys the HSM instance in.

Integrated with Azure and Microsoft PaaS/SaaS services

Uses same API and management interfaces as Key Vault

  • Easily migrate your existing applications that use a vault (a multi-tenant) to use Managed HSMs.
  • Use same application development and deployment patterns for all your applications irrespective of key management solution in use: multi-tenant vaults or single-tenant Managed HSMs.

Import keys from your on-premises HSMs

  • Generate HSM-protected keys in your on-premises HSM and import them securely into Managed HSM.

Next steps

Feedback

Submit and view feedback for

I am an expert with a deep understanding of Azure Key Vault Managed HSM and related concepts. My expertise is grounded in extensive hands-on experience, ongoing research, and a commitment to staying abreast of the latest developments in cloud security, key management, and cryptographic standards.

Now, let's delve into the key concepts covered in the provided article:

  1. Azure Key Vault Managed HSM (Hardware Security Module):

    • A fully managed, highly available, and single-tenant cloud service.
    • Utilizes FIPS 140-2 Level 3 validated HSMs for safeguarding cryptographic keys.
    • Part of Azure's key management solutions.
  2. Pricing Information:

    • Refer to the Managed HSM Pools section on the Azure Key Vault pricing page for details.
  3. Managed HSM Instance:

    • Synonymous with "Managed HSM pool" to avoid confusion.
  4. Zero Trust Security Strategy:

    • Comprises three principles: "Verify explicitly," "Use least privilege access," and "Assume breach."
    • Key management, including data protection, aligns with the "use least privilege access" principle.
  5. Why Use Managed HSM:

    • Fully managed service, handling provisioning, configuration, patching, and maintenance.
    • Highly available with automatic migration of HSM partitions in case of hardware failure.
    • Single-tenant architecture, providing dedicated HSM instances for each customer.
  6. Access Control, Enhanced Data Protection & Compliance:

    • Centralized key management with granular per-key permissions.
    • Managed HSM employs a "local RBAC" access control model.
    • Private endpoints for secure and private connections to Managed HSM from virtual networks.
    • FIPS 140-2 Level 3 validated HSMs for data protection and compliance.
  7. Monitoring and Audit:

    • Fully integrated with Azure Monitor for complete logs of all activity.
    • Utilizes Azure Log Analytics for analytics and alerts.
  8. Data Residency:

    • Managed HSM ensures customer data is not stored or processed outside the region of deployment.
  9. Integration with Azure and Microsoft PaaS/SaaS Services:

    • Generates or imports keys for data encryption in various Azure services.
    • Utilizes the same API and management interfaces as Key Vault.
    • Facilitates easy migration of applications from multi-tenant vaults to single-tenant Managed HSMs.
  10. Import Keys from On-Premises HSMs:

    • Allows the secure import of keys generated in on-premises HSMs into Managed HSM.
  11. Next Steps:

    • Provides links for technical details, quickstart guides, security baselines, best practices, and service-related information.

This article covers a comprehensive range of topics, including security strategies, key management principles, service features, integration capabilities, and practical guidance for using Azure Key Vault Managed HSM.

Azure Managed HSM Overview - Azure Managed HSM (2024)

FAQs

What is managed HSM in Azure? ›

Azure Key Vault Managed HSM is a cloud service that safeguards encryption keys. Because this data is sensitive and critical to your business, you need to secure your managed hardware security modules (HSMs) by allowing only authorized applications and users to access the data.

What is the difference between Azure managed HSM and key vault premium? ›

Vaults are low-cost, easy to deploy, zone-resilient, highly available, and multi-tenant, whereas Managed HSMs are single-tenant, zone-resilient (where available), highly available, and useful for applications that have stringent security requirements.

What are the key types in managed HSM? ›

HSM-protected keys
Key typeVaults (Premium SKU only)Managed HSMs
RSA-HSM: RSA keySupported (2048-bit, 3072-bit, 4096-bit)Supported (2048-bit, 3072-bit, 4096-bit)
oct-HSM: Symmetric keyNot supportedSupported (128-bit, 192-bit, 256-bit)
2 more rows
Feb 12, 2024

How many key vaults should you use? ›

Use separate key vaults

When you deploy Azure Key Vault, you must choose between single or multiple vaults. Microsoft recommends users keep one vault per application, per environment. For example, use one key vault each for development, pre-production and production within specific regions.

How does Azure HSM work? ›

With Azure Dedicated HSM, you manage who in your organization can access your HSMs and the scope and assignment of their roles. You have full administrative and cryptographic control over your HSMs. Microsoft has no access to or visibility into the keys stored in them.

How do I create an Azure managed HSM? ›

Deploy the template
  1. Subscription: Select an Azure subscription.
  2. Resource group: Select Create new, enter "myResourceGroup" as the name, and then select OK.
  3. Location: Select a location. ...
  4. managedHSMName: Enter a name for your Managed HSM.
Feb 20, 2024

What is the full form of HSM in Azure? ›

HSM (hardware security module) is a physical computing device used for safeguarding and managing cryptographic keys that can be used for cryptographic operations.

What is the difference between HSM key and software key? ›

Both types of key have the key stored in the HSM at rest. The difference is for a software-protected key when cryptographic operations are performed they are performed in software in compute VMs while for HSM-protected keys the cryptographic operations are performed within the HSM.

What is the difference between HSM and trusted execution environment? ›

HSM and TEE both play crucial roles in securing vehicles against cyber threats. HSMs excel in cryptographic operations and secure key storage, while TEEs create isolated execution environments within the main processor.

What are the basics of HSM? ›

Hardware security modules (HSMs) are hardened, tamper-resistant hardware devices that secure cryptographic processes by generating, protecting, and managing keys used for encrypting and decrypting data and creating digital signatures and certificates.

What are the disadvantages of HSM? ›

If a weakness is exposed in HSM's cryptographic algorithm, it will cost a huge amount to upgrade. Another drawback in using HSM is the lack of transparency in the model. Because most vendors do not allow independent review, there is a challenge in testing the effectiveness of random number generators in the hardware.

What is the overview of HSM? ›

The hardware security module protects cryptographic keys and handles the encryption and decryption processes. HSMs manage the entire lifecycle of cryptographic keys. HSMs also can create and verify digital signatures. All access transactions involving an HSM are logged to create an audit trail.

How do I see secrets in Azure key vault? ›

If you select on the current version, you can see the value you specified in the previous step. By clicking "Show Secret Value" button in the right pane, you can see the hidden value. You can also use Azure CLI, or Azure PowerShell to retrieve previously created secret.

What can be stored in Azure key vault? ›

Azure Key Vault is a cloud service for securely storing and accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, or cryptographic keys. Key Vault service supports two types of containers: vaults and managed hardware security module(HSM) pools.

How do I store keys in Azure key vault? ›

For more information on Key Vault, review the Overview.
  1. Prerequisites. To access Azure Key Vault, you'll need an Azure subscription. ...
  2. Sign in to Azure. Sign in to the Azure portal.
  3. Add a key to Key Vault. ...
  4. Retrieve a key from Key Vault. ...
  5. Clean up resources. ...
  6. Next steps.
Jan 30, 2024

What is the difference between managed and unmanaged Azure storage? ›

Managed disks: This is managed by Azure Resource Manager, which involves deploying and managing sources like virtual machines, storage accounts, and networks within Azure. Unmanaged disks: In Azure, you can keep your virtual hard disks (VHDs) as page blobs in your Storage accounts.

What does managed mean in Azure? ›

Azure Managed Services can help you streamline processes such as maintaining the functionality of the business architecture, resources, and application by having your managed services provider (MSP) always on top of your Azure cloud services–from uploading applications to monitoring the cloud environment.

What is managed and unmanaged in Azure? ›

The main difference between Managed and Unmanaged Disks in Azure lies in storage account management. Managed Disks are automatically managed by Azure, while Unmanaged Disks require manual storage account management.

What is a managed device in Azure? ›

https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/require-managed-devices#:.... In simple terms, managed devices are devices that are under some sort of organizational control.

Top Articles
Latest Posts
Article information

Author: Duncan Muller

Last Updated:

Views: 5946

Rating: 4.9 / 5 (79 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Duncan Muller

Birthday: 1997-01-13

Address: Apt. 505 914 Phillip Crossroad, O'Konborough, NV 62411

Phone: +8555305800947

Job: Construction Agent

Hobby: Shopping, Table tennis, Snowboarding, Rafting, Motor sports, Homebrewing, Taxidermy

Introduction: My name is Duncan Muller, I am a enchanting, good, gentle, modern, tasty, nice, elegant person who loves writing and wants to share my knowledge and understanding with you.