Skip to content

Commit 4828f54

Browse files
authored
Merge pull request #3267 from HeidiSteen/heidist-feb
[azure search] HSM for encryption
2 parents 9a7a391 + ebe095e commit 4828f54

File tree

7 files changed

+163
-129
lines changed

7 files changed

+163
-129
lines changed
12.6 KB
Loading
-698 Bytes
Loading
24.3 KB
Loading
12.2 KB
Loading

articles/search/search-security-manage-encryption-keys.md

Lines changed: 134 additions & 122 deletions
Large diffs are not rendered by default.

articles/search/search-security-overview.md

Lines changed: 22 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: azure-ai-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: conceptual
13-
ms.date: 01/15/2025
13+
ms.date: 02/28/2025
1414
---
1515

1616
# Security overview for Azure AI Search
@@ -207,9 +207,11 @@ For data handled internally by the search service, the following table describes
207207

208208
| Model | Keys      | Requirements      | Restrictions | Applies to |
209209
|------------------|-------|-------------|--------------|------------|
210-
| server-side encryption | Microsoft-managed keys | None (built-in) | None, available on all tiers, in all regions, for content created after January 24, 2018. | Content (indexes and synonym maps) and definitions (indexers, data sources, skillsets), on data disks and temporary disks |
211-
| server-side encryption | customer-managed keys | Azure Key Vault | Available on billable tiers, in specific regions, for content created after August 1, 2020. | Content (indexes and synonym maps) on data disks |
212-
| server-side full encryption | customer-managed keys | Azure Key Vault | Available on billable tiers, in all regions, on search services after May 13, 2021. | Content (indexes and synonym maps) on data disks and temporary disks |
210+
| server-side encryption | Microsoft-managed keys | None (built-in) | None, available on all tiers, in all regions, for content created after January 24, 2018. | Content (indexes and synonym maps) and definitions (indexers, data sources, skillsets) on data disks and temporary disks |
211+
| server-side encryption | customer-managed keys | Azure Key Vault | Available on billable tiers, in specific regions, for content created after August 1, 2020. | Content (indexes and synonym maps) and definitions (indexers, data sources, skillsets) on data disks |
212+
| server-side full encryption | customer-managed keys | Azure Key Vault | Available on billable tiers, in all regions, on search services after May 13, 2021. | Content (indexes and synonym maps) and definitions (indexers, data sources, skillsets) on data disks and temporary disks |
213+
214+
When you introduce CMK encryption, you're encrypting content twice. For the objects and fields noted in the previous section, content is first encrypted with your CMK, and secondly with the Microsoft-managed key. Content is doubly encrypted on data disks for long-term storage, and on temporary disks used for short-term storage.
213215

214216
#### Service-managed keys
215217

@@ -219,9 +221,23 @@ Service-managed encryption applies to all content on long-term and short-term st
219221

220222
#### Customer-managed keys (CMK)
221223

222-
Customer-managed keys require another billable service, Azure Key Vault, which can be in a different region, but under the same subscription, as Azure AI Search.
224+
Customers use CMK for two reasons: extra protection, and the ability to revoke keys, preventing access to content.
225+
226+
Customer-managed keys require another billable service, Azure Key Vault, which can be in a different region, but under the same Azure tenant, as Azure AI Search.
227+
228+
CMK support was rolled out in two phases. If you created your search service during the first phase, CMK encryption was restricted to long-term storage and specific regions. Services created in the second phase can use CMK encryption in any region. As part of the second wave rollout, content is CMK-encrypted on both long-term and short-term storage.
229+
230+
+ The first rollout was on August 1, 2020 and included the following five regions. Search services created in the following regions supported CMK for data disks, but not temporary disks:
231+
232+
+ West US 2
233+
+ East US
234+
+ South Central US
235+
+ US Gov Virginia
236+
+ US Gov Arizona
237+
238+
+ The second rollout on May 13, 2021 added encryption for temporary disks and extended CMK encryption to [all supported regions](search-region-support.md).
223239

224-
CMK support was rolled out in two phases. If you created your search service during the first phase, CMK encryption was restricted to long-term storage and specific regions. Services created in the second phase, after May 2021, can use CMK encryption in any region. As part of the second wave rollout, content is CMK-encrypted on both long-term and short-term storage. For more information about CMK support, see [full double encryption](search-security-manage-encryption-keys.md#full-double-encryption).
240+
If you're using CMK from a service created during the first rollout and you also want CMK encryption over temporary disks, you need to create a new search service in your region of choice and redeploy your content. To determine your service creation date, see [How to check service creation date](vector-search-index-size.md#how-to-check-service-creation-date).
225241

226242
Enabling CMK encryption will increase index size and degrade query performance. Based on observations to date, you can expect to see an increase of 30-60 percent in query times, although actual performance will vary depending on the index definition and types of queries. Because of the negative performance impact, we recommend that you only enable this feature on indexes that really require it. For more information, see [Configure customer-managed encryption keys in Azure AI Search](search-security-manage-encryption-keys.md).
227243

articles/search/whats-new.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: HeidiSteen
77
ms.author: heidist
88
ms.service: azure-ai-search
99
ms.topic: overview
10-
ms.date: 12/11/2024
10+
ms.date: 02/28/2025
1111
ms.custom:
1212
- references_regions
1313
- ignite-2024
@@ -20,6 +20,12 @@ ms.custom:
2020
> [!NOTE]
2121
> Preview features are announced here, but we also maintain a [preview features list](search-api-preview.md) so you can find them in one place.
2222
23+
## February 2025
24+
25+
| Item                         | Type | Description |
26+
|-----------------------------|------|--------------|
27+
| [**Customer-managed keys support for Managed HSM**](search-security-manage-encryption-keys.md) | Security | Use either Azure Key Vault or Azure Key Vault Managed HSM (Hardware Security Module) to store customer-managed keys for extra encryption of sensitive content. |
28+
2329
## December 2024
2430

2531
| Item                         | Type | Description |

0 commit comments

Comments
 (0)