Skip to content

Commit c0f5528

Browse files
authored
Merge pull request #107118 from amitbapat/vabyok-fortanix
Added Fortanix to the supported HSMs tables.
2 parents 759b75a + 74d7a78 commit c0f5528

File tree

2 files changed

+18
-7
lines changed

2 files changed

+18
-7
lines changed

articles/key-vault/hsm-protected-keys-vendor-agnostic-byok.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,11 @@ The following table lists prerequisites for using BYOK in Azure Key Vault:
5555

5656
## Supported HSMs
5757

58-
|HSM vendor name|Supported HSM models|More information|
59-
|---|---|---|
60-
|Thales|SafeNet Luna HSM 7 family with firmware version 7.3 or later| [SafeNet Luna BYOK tool and documentation](https://supportportal.thalesgroup.com/csm?id=kb_article_view&sys_kb_id=3892db6ddb8fc45005c9143b0b961987&sysparm_article=KB0021016)|
58+
|Vendor name|Vendor Type|Supported HSM models|More information|
59+
|---|---|---|---|
60+
|Thales|Manufacturer|SafeNet Luna HSM 7 family with firmware version 7.3 or later| [SafeNet Luna BYOK tool and documentation](https://supportportal.thalesgroup.com/csm?id=kb_article_view&sys_kb_id=3892db6ddb8fc45005c9143b0b961987&sysparm_article=KB0021016)|
61+
|Fortanix|HSM as a Service|Self-Defending Key Management Service (SDKMS)|[Exporting SDKMS keys to Cloud Providers for BYOK - Azure Key Vault](https://support.fortanix.com/hc/en-us/articles/360040071192-Exporting-SDKMS-keys-to-Cloud-Providers-for-BYOK-Azure-Key-Vault)|
62+
6163

6264
> [!NOTE]
6365
> To import HSM-protected keys from the nCipher nShield family of HSMs, use the [legacy BYOK procedure](hsm-protected-keys-legacy.md).

articles/key-vault/key-vault-hsm-protected-keys.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,19 @@ This functionality is not available for Azure China 21Vianet.
2828

2929
Transferring HSM-protected keys to Key Vault is supported via two different methods depending on the HSMs you use. Use the table below to determine which method should be used for your HSMs to generate, and then transfer your own HSM-protected keys to use with Azure Key Vault.
3030

31-
|HSM Vendor Name|Supported HSM models|Supported HSM-key transfer method|
32-
|---|---|---|
33-
|Thales|<ul><li>SafeNet Luna HSM 7 family with firmware version 7.3 or newer</li></ul>| [Use new BYOK method (preview)](hsm-protected-keys-vendor-agnostic-byok.md)|
34-
|nCipher|<ul><li>nShield family of HSMs</li></ul>|[Use legacy BYOK method](hsm-protected-keys-legacy.md)|
31+
|Vendor Name|Vendor Type|Supported HSM models|Supported HSM-key transfer method|
32+
|---|---|---|---|
33+
|nCipher|Manufacturer|<ul><li>nShield family of HSMs</li></ul>|[Use legacy BYOK method](hsm-protected-keys-legacy.md)|
34+
|Thales|Manufacturer|<ul><li>SafeNet Luna HSM 7 family with firmware version 7.3 or newer</li></ul>| [Use new BYOK method (preview)](hsm-protected-keys-vendor-agnostic-byok.md)|
35+
|Fortanix|HSM as a Service|<ul><li>Self-Defending Key Management Service (SDKMS)</li></ul>|[Use new BYOK method (preview)](hsm-protected-keys-vendor-agnostic-byok.md)|
36+
37+
38+
39+
40+
41+
42+
43+
3544

3645

3746
## Next steps

0 commit comments

Comments
 (0)