Skip to content

Commit f5dc8a1

Browse files
authored
Merge pull request #54051 from staleycyn/patch-1
Content drift storage security
2 parents 348add3 + adc33de commit f5dc8a1

6 files changed

Lines changed: 25 additions & 16 deletions

File tree

learn-pr/wwl-azure/configure-storage-security/includes/1-introduction.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,7 @@ In this module, you learn how to:
1313

1414
## Skills measured
1515

16-
The content in the module helps you prepare for [Exam AZ-104: Microsoft Azure Administrator](/credentials/certifications/resources/study-guides/az-104). The module concepts are covered in:
17-
18-
Implement and manage storage (15–20%)
19-
20-
- Secure storage
21-
- Generate shared access signature (SAS) tokens.
22-
- Manage access keys.
23-
- Configure stored access policies.
16+
The content in the module helps you prepare for [Exam AZ-104: Microsoft Azure Administrator](/credentials/certifications/resources/study-guides/az-104).
2417

2518
## Prerequisites
2619

learn-pr/wwl-azure/configure-storage-security/includes/2-review-strategies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Let's look at some characteristics of Azure Storage security. As you go through
1313

1414
- **Encryption at rest**. Storage Service Encryption (SSE) with a 256-bit Advanced Encryption Standard (AES) cipher encrypts all data written to Azure Storage. When you read data from Azure Storage, Azure Storage decrypts the data before returning it. This process incurs no extra charges and doesn't degrade performance. Encryption at rest includes encrypting virtual hard disks (VHDs) with Azure Disk Encryption. This encryption uses BitLocker for Windows images, and uses dm-crypt for Linux.
1515

16-
- **Encryption in transit**. Keep your data secure by enabling transport-level security between Azure and the client. Always use HTTPS to secure communication over the public internet. When you call the REST APIs to access objects in storage accounts, you can enforce the use of HTTPS by requiring *secure transfer* for the storage account. After you enable secure transfer, connections that use HTTP will be refused. This flag will also enforce secure transfer over SMB by requiring SMB 3.0 for all file share mounts.
16+
- **Encryption in transit**. You can configure your storage account to only accept requests from secure connections by setting the **Secure transfer required** property for the storage account. Existing accounts should explicitly disallow TLS 1.0 and 1.1, which are deprecated.
1717

1818
- **Encryption models**. Azure supports various encryption models, including server-side encryption that uses service-managed keys, customer-managed keys in Key Vault, or customer-managed keys on customer-controlled hardware. With client-side encryption, you can manage and store keys on-premises or in another secure location.
1919

@@ -33,6 +33,6 @@ Review the following strategies for authorizing requests to Azure Storage. Think
3333
| Authorization strategy | Description |
3434
| --- | --- |
3535
| **Microsoft Entra ID** | Microsoft Entra ID is Microsoft's cloud-based identity and access management service. With Microsoft Entra ID, you can assign fine-grained access to users, groups, or applications by using role-based access control. |
36-
| **Shared Key** | Shared Key authorization relies on your Azure storage account access keys and other parameters to produce an encrypted signature string. The string is passed on the request in the Authorization header. |
36+
| **Shared Key** | Access is authorized with an account access key. The key can be the primary or secondary access key. To enforce Entra ID authorization, disable the Shared Key at the storage account level. |
3737
| **Shared access signatures** | A SAS delegates access to a particular resource in your Azure storage account with specified permissions and for a specified time interval. |
38-
| **Anonymous access to containers and blobs** | You can optionally make blob resources public at the container or blob level. A public container or blob is accessible to any user for anonymous read access. Read requests to public containers and blobs don't require authorization.
38+
| **Anonymous access to containers and blobs** | Anonymous public access is disabled by default on new storage accounts. Microsoft recommends keeping anonymous access disabled for accounts containing sensitive data. |

learn-pr/wwl-azure/configure-storage-security/includes/5-determine-storage-service-encryption.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ Azure Storage encryption for data at rest protects your data by ensuring your or
22

33
When you create a storage account, Azure generates two 512-bit storage account access keys for that account. These keys can be used to authorize access to data in your storage account via Shared Key authorization, or via SAS tokens that are signed with the shared key.
44

5-
Microsoft recommends that you use Azure Key Vault to manage your access keys, and that you regularly rotate and regenerate your keys. Using Azure Key Vault makes it easy to rotate your keys without interruption to your applications. You can also manually rotate your keys.
5+
Microsoft recommends that you use Azure Key Vault to manage your access keys, and that you regularly rotate and regenerate your keys. Azure Key Vault supports automatic key rotation policies, allowing you to define rotation schedules (for example, every 90 days) that rotate keys automatically. You can also manually rotate your keys when needed.
66

77
### Things to know about Azure Storage encryption
88

learn-pr/wwl-azure/configure-storage-security/includes/6-create-customer-managed-keys.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ Consider the following characteristics of customer-managed keys.
1212

1313
- Customer-managed keys can be used with Azure Storage encryption. You can use a new key or an existing key vault and key. The Azure storage account and the key vault must be in the same region, but they can be in different subscriptions.
1414

15+
- Customer-managed keys are stored in a customer-owned Azure Key Vault or Azure Key Vault Managed HSM. Managed HSM provides FIPS 140-2 Level 3 validation for organizations with the highest compliance requirements.
16+
1517
## Configure customer-managed keys
1618

1719
In the Azure portal, you can configure customer-managed encryption keys. You can create your own keys, or you can have the keys managed by Microsoft. Consider how you might use Azure Key Vault to create your own customer-managed encryption keys.
@@ -24,4 +26,4 @@ In the Azure portal, you can configure customer-managed encryption keys. You can
2426

2527

2628
> [!TIP]
27-
> Expand your understanding of storage security in the [*Plan and implement security for storage*](/training/modules/security-storage/) training module.
29+
> Expand your understanding of storage security in the [*Plan and implement security for storage*](/training/modules/security-storage/) training module.

learn-pr/wwl-azure/configure-storage-security/includes/7-apply-best-practices.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,33 @@
44

55
### What are the benefits of Storage insights?
66

7-
- **Detailed Metrics and Logs**. Azure Storage Insights offers detailed metrics, logs, and diagnostic information that enhance visibility into storage operations. This helps in monitoring key performance indicators (KPIs) such as latency, throughput, capacity utilization, and transactions.
7+
- **Detailed Metrics and Logs**. Azure Storage Insights offers detailed metrics, logs, and diagnostic information that enhance visibility into storage operations. Insights helps in monitoring key performance indicators (KPIs) such as latency, throughput, capacity utilization, and transactions.
88

99
- **Enhanced Security and Compliance**. By using Azure Storage Insights, you can ensure enhanced security and compliance. It provides actionable insights and alerts that help in swiftly identifying and resolving security issues.
1010

1111
- **Role-Based Access Control (RBAC)**. Azure Storage Insights integrates with Azure's security features, including role-based access control (RBAC), Microsoft Entra ID, connection strings, and access control list (ACL) permissions. RBAC ensures secure access to your data and resources.
1212

1313
- **Unified View**. It delivers a unified view of your Azure Storage services' performance, capacity, and availability, which is crucial for maintaining the security and efficiency of your storage accounts.
1414

15-
### Security uses for Storage Insights
15+
### When to use Storage Insights
1616

1717
- **Real-Time Monitoring**. Azure Storage Insights enables real-time monitoring of storage accounts, allowing you to track usage trends, monitor performance, and set up alerts for any anomalies.
1818

1919
- **Security Auditing**. It aids in security auditing by providing comprehensive monitoring and detailed logs, which are essential for ensuring compliance and identifying any security issues.
2020

2121
- **Health Analysis and Optimization**. The tool helps in health analysis and optimization of storage accounts, ensuring security and optimal performance.
2222

23+
### When to use Microsoft Defender for Storage
24+
25+
While Storage Insights provides passive monitoring and historical analysis, Microsoft Defender for Storage offers proactive threat detection for active security threats.
26+
27+
**Key capabilities**
28+
29+
- **Malware scanning**. Automatically scans blob uploads for malware and viruses.
30+
31+
- **Sensitive data threat detection**. Identifies when personally identifiable information (PII) or credentials are stored inappropriately.
32+
33+
- **Activity-based threat detection**. Monitors for unusual access patterns, suspicious download volumes, and hash reputation analysis.
34+
35+
Microsoft Defender for Storage complements Storage Insights by providing active threat detection rather than reactive monitoring and historical reporting.
36+

learn-pr/wwl-azure/configure-storage-security/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
prefetch-feature-rollout: true
66
title: Configure Azure Storage Security
77
description: "Learn how to configure common Azure Storage security features like storage access signatures."
8-
ms.date: 02/24/2026
8+
ms.date: 03/23/2026
99
author: wwlpublish
1010
ms.author: cynthist
1111
ms.topic: module

0 commit comments

Comments
 (0)