You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/3-design-integrated-posture-management-workload-protection.yml
title: Design integrated posture management and workload protection with Microsoft Defender for Cloud
3
+
title: Design integrated posture management solutions with Microsoft Defender for Cloud in hybrid and multicloud environments
4
4
metadata:
5
-
title: Design integrated posture management and workload protection with Microsoft Defender for Cloud
6
-
description: "SC-100 preparatory unit on the topic: design integrated posture management and workload protection with Microsoft Defender for Cloud."
5
+
title: Design integrated posture management solutions with Microsoft Defender for Cloud in hybrid and multicloud environments
6
+
description: "SC-100 preparatory unit on the topic: design integrated posture management solutions with Microsoft Defender for Cloud in hybrid and multicloud environments."
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/4-evaluate-security-posture-microsoft-defender-cloud.yml
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/7-integrate-hybrid-multi-cloud-environments-azure-arc.yml
Evaluating your organization's security posture requires a consistent framework that can be applied across Azure, AWS, GCP, and on-premises environments. The Microsoft Cloud Security Benchmark (MCSB) v2 serves as this evaluation framework, providing defined security controls you can measure your environment against.
1
+
Designing and evaluating the security posture of hybrid and multicloud environments starts with selecting the right security framework. The Microsoft Cloud Security Benchmark (MCSB) provides a foundation for both designing your security architecture and evaluating your current posture against industry best practices.
2
2
3
-
## Using MCSB to evaluate security posture
3
+
## Designing with MCSB as your security framework
4
4
5
-
MCSB enables you to evaluate security posture by comparing your current configurations and practices against defined security controls. This evaluation process helps you:
5
+
MCSB serves as more than an evaluation checklist—it's a design framework that guides your security architecture decisions. When designing your posture management solution, consider how MCSB fits into your overall approach.
6
6
7
-
-**Identify gaps**: Compare your current security configurations against MCSB control requirements to find areas that need improvement.
8
-
-**Prioritize improvements**: Use MCSB's risk-based guidance to focus on controls that address your highest risks.
9
-
-**Measure progress**: Track compliance against MCSB controls over time to demonstrate security posture improvement.
10
-
-**Benchmark across clouds**: Apply the same evaluation criteria across Azure, AWS, and GCP since MCSB provides implementation guidance for each platform.
7
+
**When to use MCSB as your primary baseline**: MCSB is appropriate as your primary security standard when:
8
+
-Your organization operates across Azure, AWS, and GCP (MCSB provides implementation guidance for all three)
9
+
-You need a comprehensive framework covering network, identity, data, and application security
10
+
-You want alignment with industry frameworks without maintaining separate mappings
11
11
12
-
For security posture management specifically, MCSB provides the Posture and Vulnerability Management (PV) domain. These controls define what a mature security posture looks like and give you the criteria to evaluate against.
12
+
**Mapping to regulatory requirements**: MCSB maps to common regulatory frameworks including PCI-DSS, ISO 27001, NIST SP 800-53, and CIS Controls. Design your compliance strategy by:
13
+
- Using MCSB as the operational baseline
14
+
- Mapping MCSB controls to your specific regulatory requirements
15
+
- Identifying gaps where regulations require controls beyond MCSB
13
16
14
-
## MCSB controls for security posture evaluation
17
+
**Designing exception management**: Not all MCSB controls apply to every workload. Design an exception process that documents:
18
+
- Which controls don't apply and why
19
+
- Compensating controls in place
20
+
- Review cadence for exceptions
15
21
16
-
The PV domain contains seven controls that serve as evaluation criteria for your security posture. Use the following table to assess your environment's alignment with each control:
22
+
## Evaluating posture against MCSB
17
23
18
-
| Control | What to evaluate | Questions to ask |
19
-
|---------|------------------|------------------|
20
-
| PV-1: Define and establish secure configurations | Whether security configuration baselines exist for each resource type and are applied during deployment. | Do you have documented baselines? Are configurations enforced at deployment time? |
21
-
| PV-2: Audit and enforce secure configurations | Whether you continuously monitor for configuration drift and can enforce compliance across environments. | Can you detect when configurations change? Do you have remediation policies in place? |
22
-
| PV-3: Define secure configurations for compute | Whether VMs and containers are deployed from hardened images with defined security baselines. | Are you using hardened images? Are OS security baselines defined and documented? |
23
-
| PV-4: Audit and enforce compute configurations | Whether compute resources are monitored for configuration deviations with automated remediation. | Do you have visibility into compute configuration drift across all cloud providers? |
24
-
| PV-5: Perform vulnerability assessments | Whether regular vulnerability scans cover all resource types with tracked remediation. | Are scans scheduled regularly? Do you have a centralized view of findings across clouds? |
25
-
| PV-6: Remediate vulnerabilities automatically | Whether patches and updates are deployed automatically using risk-based prioritization. | Is patching automated? Are critical vulnerabilities prioritized appropriately? |
26
-
| PV-7: Conduct red team operations | Whether penetration testing and red team exercises validate your security controls. | Do you conduct regular security testing? Are findings tracked to remediation? |
24
+
With your design in place, use MCSB to evaluate your current security posture. The Posture and Vulnerability Management (PV) domain defines what mature posture management looks like:
25
+
26
+
| Control | Evaluation criteria | Design questions |
| PV-1: Define secure configurations | Security baselines exist for each resource type | Do you have documented baselines enforced at deployment? |
29
+
| PV-2: Audit and enforce configurations | Continuous monitoring detects drift | Can you detect configuration changes with automated remediation? |
30
+
| PV-3: Define compute configurations | VMs and containers deploy from hardened images | Are OS security baselines defined and documented? |
31
+
| PV-4: Audit compute configurations | Compute resources monitored for deviations | Do you have visibility across all cloud providers? |
32
+
| PV-5: Perform vulnerability assessments | Regular scans cover all resource types | Do you have centralized findings across clouds? |
33
+
| PV-6: Remediate vulnerabilities | Patches deploy using risk-based prioritization | Is patching automated with critical vulnerabilities prioritized? |
34
+
| PV-7: Conduct red team operations | Penetration testing validates controls | Are findings tracked to remediation? |
27
35
28
36
## Conducting an MCSB-based evaluation
29
37
@@ -35,4 +43,4 @@ To evaluate your security posture using MCSB:
35
43
36
44
3.**Plan remediation**: Prioritize gaps based on risk and create a roadmap to address them, using MCSB's implementation guidance for your specific cloud platforms.
37
45
38
-
For detailed control requirements and platform-specific guidance, see [Posture and vulnerability management](/security/benchmark/azure/mcsb-posture-vulnerability-management) in the official MCSB documentation.
46
+
For detailed control requirements and platform-specific guidance, see [Posture and vulnerability management](/security/benchmark/azure/mcsb-posture-vulnerability-management) in the MCSB documentation.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/includes/4-evaluate-security-posture-microsoft-defender-cloud.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Secure score is Defender for Cloud's primary metric for evaluating security post
34
34
35
35
The Cloud Secure Score ranges from 0 to 100, with 100 indicating an optimal security posture. This model provides more accurate prioritization by factoring in contextual risk.
36
36
37
-
:::image type="content" source="../media/cloud-secure-score.png" alt-text="Screenshot of a the Cloud Secure Score and the Defender CSPM plan." lightbox="../media/cloud-secure-score.png":::
37
+
:::image type="content" source="../media/cloud-secure-score.png" alt-text="Screenshot of the Cloud Secure Score and the Defender CSPM plan." lightbox="../media/cloud-secure-score.png":::
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/includes/7-integrate-hybrid-multi-cloud-environments-azure-arc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Design your resource hierarchy to support security governance:
81
81
82
82
## Addressing common design challenges
83
83
84
-
**Disconnected scenarios**: Arc-enabled servers require periodic connectivity to Azure (at least every 30 days by default). For occasionally-connected scenarios, plan for this requirement. Arc-enabled Kubernetes clusters support GitOps for configuration even during disconnection.
84
+
**Disconnected scenarios**: Arc-enabled servers require periodic connectivity to Azure (at least every 30 days by default). For occasionallyconnected scenarios, plan for this requirement. Arc-enabled Kubernetes clusters support GitOps for configuration even during disconnection.
85
85
86
86
**Network segmentation**: If Arc resources exist in restricted network segments, aggregate traffic through proxies or deploy Arc gateway to minimize firewall openings.
0 commit comments