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/includes/7-integrate-hybrid-multi-cloud-environments-azure-arc.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Azure Arc supports several resource types critical to security posture:
**Design consideration**: Azure Arc is a prerequisite for Defender for Cloud protection on non-Azure resources. Plan Arc deployment as step one of your hybrid security strategy.
17
+
**Design consideration**: Azure Arc is a prerequisite for Defender for Cloud protection on non-Azure resources. Plan Arc deployment as step 1 of your hybrid security strategy.
18
18
19
19
## Designing network connectivity for Arc
20
20
@@ -40,8 +40,8 @@ Individual agent installation doesn't scale for enterprise deployments. Design y
| VMware vSphere | Arc-enabled VMware with guest management |
43
-
| AWS EC2 instances | Multicloud connector with auto-provisioning|
44
-
| GCP VMs | OS Configuration agent with auto-provisioning|
43
+
| AWS EC2 instances | Multicloud connector with autoprovisioning|
44
+
| GCP VMs | OS Configuration agent with autoprovisioning|
45
45
46
46
For at-scale deployment, use a service principal rather than interactive authentication. Create a dedicated service principal with the Azure Connected Machine Onboarding role and limit its scope to specific resource groups.
47
47
@@ -51,9 +51,9 @@ For at-scale deployment, use a service principal rather than interactive authent
51
51
52
52
The Connected Machine agent supports several security configurations to limit functionality based on your requirements:
53
53
54
-
**Extension allowlist**: Restrict which extensions can deploy on Arc-enabled servers. Create an allowlist of approved extensions to prevent unauthorized software installation.
54
+
**Extension allowlist**: Restrict which extensions can deploy on Arc-enabled servers. Create an allow list of approved extensions to prevent unauthorized software installation.
55
55
56
-
**Monitor mode**: Configure agents for monitoring only by restricting to a Microsoft-managed extension allowlist, disabling remote connectivity, and disabling the machine configuration agent. Use when Arc's purpose is purely observability.
56
+
**Monitor mode**: Configure agents for monitoring only by restricting to a Microsoft-managed extension allow list, disabling remote connectivity, and disabling the machine configuration agent. Use when Arc's purpose is purely observability.
57
57
58
58
**Local agent controls**: The `azcmagent` command-line tool allows local administrators to configure agent behavior, lock down connectivity options, and manage extensions.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/design-solutions-security-posture-management-hybrid-multicloud-environments/includes/8-design-solution-external-attack-surface-management.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Defender EASM discovers and catalogs:
11
11
| Domains | Primary domains, subdomains, acquired company domains |
12
12
| Hosts | Web servers, mail servers, DNS servers |
13
13
| IP addresses and blocks | Public IP ranges, cloud-hosted IPs |
14
-
| Web pages |Login portals, APIs, forgotten applications |
14
+
| Web pages |Sign-in portals, APIs, forgotten applications |
15
15
| SSL certificates | Certificate chains, expiration status |
16
16
| ASNs and WHOIS data | Network ownership, registration contacts |
17
17
@@ -49,7 +49,7 @@ Only **Approved Inventory** assets appear in dashboard metrics by default and re
49
49
50
50
## Designing integration with Defender for Cloud
51
51
52
-
Defender for Cloud's CSPM plan includes EASM integration at no additional cost. This integration enables internet-exposure validation by combining outside-in discovery with inside-out configuration assessment.
52
+
Defender for Cloud's CSPM plan includes EASM integration at no extra cost. This integration enables internet-exposure validation by combining outside-in discovery with inside-out configuration assessment.
53
53
54
54
The integration provides:
55
55
- Correlation between externally discovered assets and internal cloud resources
@@ -79,15 +79,18 @@ Defender EASM data becomes more valuable when integrated with your security oper
79
79
80
80
## Using dashboards for prioritization
81
81
82
-
Defender EASM provides specialized dashboards to prioritize security efforts:
82
+
Defender EASM provides eight dashboards to prioritize security efforts:
83
83
84
84
| Dashboard | Purpose |
85
85
|-----------|---------|
86
-
| Attack Surface Summary | High-level view of risks by severity (high, medium, low) |
| Inventory Changes | New, modified, and removed assets over time |
88
+
| Attack Surface Summary | High-level view of risks by severity (high, medium, low), cloud hosting, IP reputation |
89
+
| Security Posture | CVE exposure, domain configuration, open ports, SSL certificate status |
90
+
| Data Protection Compliance | Compliance risks for data protection requirements on EU-accessible infrastructure |
91
+
| OWASP Top 10 | Critical web application security risks based on OWASP list |
92
+
| CWE Top 25 | Common software weaknesses based on annual MITRE list |
93
+
| CISA Known Exploits | Vulnerabilities with confirmed exploitation by threat actors |
91
94
92
95
Use the Attack Surface Summary to identify high-severity findings—critical CVEs, compromised infrastructure associations, deprecated technology, or compliance issues. Each insight includes suggested remediation actions.
93
96
@@ -108,6 +111,6 @@ Defender EASM pricing is based on billable assets—the Approved Inventory asset
108
111
109
112
**Third-party risk**: Use the Dependency state for assets owned by third parties that support your operations. Track these assets separately from your owned infrastructure while maintaining visibility into their security posture.
110
113
111
-
**False positives**: Some discovered assets might not belong to your organization despite apparent connections. Use exclusions to prevent these from appearing in future discoveries, and mark observations as non-applicable when CVEs don't affect your specific configuration.
114
+
**False positives**: Some discovered assets might not belong to your organization despite apparent connections. Use exclusions to prevent these from appearing in future discoveries, and mark observations as nonapplicable when CVEs don't affect your specific configuration.
112
115
113
116
Your external attack surface represents what adversaries see when they scan your organization. Defender EASM provides that attacker's perspective, enabling you to identify and remediate exposures before they become entry points.
0 commit comments