Skip to content

Commit c43269e

Browse files
committed
update
1 parent 10939ec commit c43269e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/security/fundamentals/secrets-best-practices.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,12 @@ See:
4141

4242
Leveraging secure key stores ensures that your secrets are stored in a secure, encrypted location. Services like [Azure Key Vault](/azure/key-vault) provide robust security features, including access control, logging, and automatic rotation. This approach centralizes the management of your secrets and reduces the risk of unauthorized access.
4343

44-
For even greater security, particularly for highly sensitive or critical secrets, consider using Hardware Security Modules (HSMs), which offer enhanced protection compared to software-based secret stores. [Azure Managed HSM](/azure/key-vault/managed-hsm) provides a fully managed, FIPS 140-2 Level 3 validated HSM service that can help protect your most sensitive secrets.
44+
For even greater security, particularly for highly sensitive or critical secrets, consider encrypting the secret with a key stores in a Hardward Security Model (HSM), which offer enhanced protection compared to software-based secret stores. For an overview of all the key management offering in Azure and guidance on which to choose, see [How to choose the right key management solution](key-management-choose.md).
4545

4646
See:
4747

4848
- [Key management in Azure](key-management.md)
49+
- [How to choose the right key management solution](key-management-choose.md)
4950
- [Azure Key Vault](/azure/key-vault/general/overview)
5051
- [Azure Managed HSM](/azure/key-vault/managed-hsm/overview)
5152

0 commit comments

Comments
 (0)