Skip to content

Commit dfe4415

Browse files
authored
Update security-domain.md
small grammatical clarity fix in documentation
1 parent 21718e8 commit dfe4415

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/key-vault/managed-hsm/security-domain.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: managed-hsm
66
ms.topic: concept-article
77
author: msmbaldwin
88
ms.author: mbaldwin
9-
ms.date: 03/28/2022
9+
ms.date: 12/18/2023
1010
---
1111

1212
# Security domain in Managed HSM overview
@@ -15,7 +15,7 @@ A managed HSM is a single-tenant, [Federal Information Processing Standards (FIP
1515

1616
To operate, a managed HSM must have a security domain. The security domain is an encrypted blob file that contains artifacts like the HSM backup, user credentials, the signing key, and the data encryption key that's unique to the managed HSM.
1717

18-
A managed HSM serves the following purposes:
18+
A managed HSM security domain serves the following purposes:
1919

2020
- Establishes "ownership" by cryptographically tying each managed HSM to a root of trust keys under your sole control. This ensures that Microsoft doesn't have access to your cryptographic key material on the managed HSM.
2121
- Sets the cryptographic boundary for key material in a managed HSM instance.

0 commit comments

Comments
 (0)