Skip to content

Commit b605f58

Browse files
updating
1 parent 0f011f7 commit b605f58

9 files changed

+77
-58
lines changed

articles/defender-for-cloud/TOC.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -268,6 +268,9 @@
268268
href: copilot-security-in-defender-for-cloud.md
269269
- name: Security recommendations
270270
items:
271+
- name: AI recommendations
272+
displayName: AI, recommendations
273+
href: recommendations-reference-ai.md
271274
- name: API recommendations
272275
displayName: API, recommendations
273276
href: recommendations-reference-api.md

articles/defender-for-cloud/recommendations-reference-app-services.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ On Azure, managed identities eliminate the need for developers to have to manage
141141
**Description**: Microsoft Defender for App Service leverages the scale of the cloud, and the visibility that Azure has as a cloud provider, to monitor for common web app attacks.
142142
Microsoft Defender for App Service can discover attacks on your applications and identify emerging attacks.
143143

144-
Important: Remediating this recommendation will result in charges for protecting your App Service plans. If you don't have any App Service plans in this subscription, no charges will be incurred.
144+
Remediating this recommendation will result in charges for protecting your App Service plans. If you don't have any App Service plans in this subscription, no charges will be incurred.
145145
If you create any App Service plans on this subscription in the future, they will automatically be protected and charges will begin at that time.
146146
Learn more in [Protect your web apps and APIs](defender-for-app-service-introduction.md).
147147
(Related policy: [Azure Defender for App Service should be enabled](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fmicrosoft.authorization%2fpolicyDefinitions%2f2913021d-f2fd-4f3d-b958-22354e2bdbcb)).

articles/defender-for-cloud/recommendations-reference-compute.md

Lines changed: 32 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ When you restore from a recovery point, you can restore the whole VM or specific
136136

137137
### [EDR configuration issues should be resolved on virtual machines](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dc5357d0-3858-4d17-a1a3-072840bff5be)
138138

139-
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. <br> Note: Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
139+
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
140140

141141
This agentless endpoint recommendation is available if you have Defender for Servers Plan 2 or the Defender CSPM plan. [Learn more](endpoint-detection-response.md) about agentless endpoint protection recommendations.
142142

@@ -188,9 +188,9 @@ When the file integrity monitoring solution is enabled, create data collection r
188188

189189
**Description**: Install Guest Attestation extension on supported Linux virtual machine scale sets to allow Microsoft Defender for Cloud to proactively attest and monitor the boot integrity. Once installed, boot integrity will be attested via Remote Attestation. This assessment only applies to trusted launch enabled Linux virtual machine scale sets.
190190

191-
Important:
192-
Trusted launch requires the creation of new virtual machines.
193-
You can't enable trusted launch on existing virtual machines that were initially created without it.
191+
- Trusted launch requires the creation of new virtual machines.
192+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
193+
194194
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
195195
(No related policy)
196196

@@ -200,9 +200,9 @@ Learn more about [Trusted launch for Azure virtual machines](../virtual-machines
200200

201201
**Description**: Install Guest Attestation extension on supported Linux virtual machines to allow Microsoft Defender for Cloud to proactively attest and monitor the boot integrity. Once installed, boot integrity will be attested via Remote Attestation. This assessment only applies to trusted launch enabled Linux virtual machines.
202202

203-
Important:
204-
Trusted launch requires the creation of new virtual machines.
205-
You can't enable trusted launch on existing virtual machines that were initially created without it.
203+
- Trusted launch requires the creation of new virtual machines.
204+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
205+
206206
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
207207
(No related policy)
208208

@@ -212,9 +212,9 @@ Learn more about [Trusted launch for Azure virtual machines](../virtual-machines
212212

213213
**Description**: Install Guest Attestation extension on supported virtual machine scale sets to allow Microsoft Defender for Cloud to proactively attest and monitor the boot integrity. Once installed, boot integrity will be attested via Remote Attestation. This assessment only applies to trusted launch enabled virtual machine scale sets.
214214

215-
Important:
216-
Trusted launch requires the creation of new virtual machines.
217-
You can't enable trusted launch on existing virtual machines that were initially created without it.
215+
- Trusted launch requires the creation of new virtual machines.
216+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
217+
218218
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
219219
(No related policy)
220220

@@ -224,9 +224,9 @@ Learn more about [Trusted launch for Azure virtual machines](../virtual-machines
224224

225225
**Description**: Install Guest Attestation extension on supported virtual machines to allow Microsoft Defender for Cloud to proactively attest and monitor the boot integrity. Once installed, boot integrity will be attested via Remote Attestation. This assessment only applies to trusted launch enabled virtual machines.
226226

227-
Important:
228-
Trusted launch requires the creation of new virtual machines.
229-
You can't enable trusted launch on existing virtual machines that were initially created without it.
227+
- Trusted launch requires the creation of new virtual machines.
228+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
229+
230230
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
231231
(No related policy)
232232

@@ -373,7 +373,7 @@ This recommendation helps you to improve server security posture. Defender for C
373373
**Description**: Microsoft Defender for servers provides real-time threat protection for your server workloads and generates hardening recommendations as well as alerts about suspicious activities.
374374
You can use this information to quickly remediate security issues and improve the security of your servers.
375375

376-
Important: Remediating this recommendation will result in charges for protecting your servers. If you don't have any servers in this subscription, no charges will be incurred.
376+
Remediating this recommendation will result in charges for protecting your servers. If you don't have any servers in this subscription, no charges will be incurred.
377377
If you create any servers on this subscription in the future, they will automatically be protected and charges will begin at that time.
378378
Learn more in [Introduction to Microsoft Defender for servers](defender-for-servers-introduction.md).
379379
(Related policy: [Azure Defender for servers should be enabled](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fmicrosoft.authorization%2fpolicyDefinitions%2f4da35fc9-c9e7-4960-aec9-797fe7d9051d)).
@@ -394,9 +394,10 @@ Learn more in [Introduction to Microsoft Defender for servers](defender-for-serv
394394

395395
**Description**: Enable Secure Boot on supported Windows virtual machines to mitigate against malicious and unauthorized changes to the boot chain. Once enabled, only trusted bootloaders, kernel, and kernel drivers will be allowed to run. This assessment only applies to trusted launch enabled Windows virtual machines.
396396

397-
Important:
398-
Trusted launch requires the creation of new virtual machines.
399-
You can't enable trusted launch on existing virtual machines that were initially created without it.
397+
398+
- Trusted launch requires the creation of new virtual machines.
399+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
400+
400401
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
401402
(No related policy)
402403

@@ -501,8 +502,8 @@ For a comparison of different disk encryption technologies in Azure, see <https:
501502
Use Azure Disk Encryption to encrypt all this data.
502503
Disregard this recommendation if:
503504

504-
1. You're using the encryption-at-host feature, or 2. Server-side encryption on Managed Disks meets your security requirements.
505-
Learn more in [Server-side encryption of Azure Disk Storage](https://aka.ms/disksse).
505+
You're using the encryption-at-host feature, or server-side encryption on Managed Disks meets your security requirements. Learn more in [server-side encryption of Azure Disk Storage](https://aka.ms/disksse).
506+
506507
(Related policy: [Disk encryption should be applied on virtual machines](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f0961003e-5a0a-4549-abde-af6a37f2724d))
507508

508509
**Severity**: High
@@ -511,9 +512,10 @@ Learn more in [Server-side encryption of Azure Disk Storage](https://aka.ms/disk
511512

512513
**Description**: Enable virtual TPM device on supported virtual machines to facilitate Measured Boot and other OS security features that require a TPM. Once enabled, vTPM can be used to attest boot integrity. This assessment only applies to trusted launch enabled virtual machines.
513514

514-
Important:
515-
Trusted launch requires the creation of new virtual machines.
516-
You can't enable trusted launch on existing virtual machines that were initially created without it.
515+
516+
- Trusted launch requires the creation of new virtual machines.
517+
- You can't enable trusted launch on existing virtual machines that were initially created without it.
518+
517519
Learn more about [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
518520
(No related policy)
519521

@@ -660,7 +662,7 @@ Authentication credentials `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` shoul
660662

661663
### [EDR configuration issues should be resolved on EC2s](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/695abd03-82bd-4d7f-a94c-140e8a17666c)
662664

663-
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. <br> Note: Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
665+
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
664666

665667
This agentless endpoint recommendation is available if you have Defender for Servers Plan 2 or the Defender CSPM plan. [Learn more](endpoint-detection-response.md) about agentless endpoint protection recommendations.
666668
- These new agentless endpoint recommendations support Azure and multicloud machines. On-premises servers aren't supported.
@@ -733,7 +735,7 @@ To learn more about the supported runtimes that this control checks for the supp
733735

734736
### [EDR configuration issues should be resolved on GCP virtual machines](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/f36a15fb-61a6-428c-b719-6319538ecfbc)
735737

736-
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. <br> Note: Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
738+
**Description**: To protect virtual machines from the latest threats and vulnerabilities, resolve all identified configuration issues with the installed Endpoint Detection and Response (EDR) solution. Currently, this recommendation only applies to resources with Microsoft Defender for Endpoint enabled.
737739

738740
This agentless endpoint recommendation is available if you have Defender for Servers Plan 2 or the Defender CSPM plan. [Learn more](endpoint-detection-response.md) about agentless endpoint protection recommendations.
739741

@@ -880,14 +882,17 @@ VMs created by GKE should be excluded. These VMs have names that start with ```g
880882

881883
**Description**: To support principle of least privileges and prevent potential privilege escalation, it's recommended that instances aren't assigned to default service account "Compute Engine default service account" with Scope "Allow full access to all Cloud APIs."
882884
Along with ability to optionally create, manage, and use user managed custom service accounts, Google Compute Engine provides default service account "Compute Engine default service account" for an instance to access necessary cloud services.
885+
883886
"Project Editor" role is assigned to "Compute Engine default service account" hence, This service account has almost all capabilities over all cloud services except billing.
884887
However, when "Compute Engine default service account" assigned to an instance it can operate in three scopes.
885888

886-
1. Allow default access: Allows only minimum access required to run an Instance (Least Privileges).
887-
1. Allow full access to all Cloud APIs: Allow full access to all the cloud APIs/Services (Too much access).
888-
1. Set access for each API: Allows Instance administrator to choose only those APIs that are needed to perform specific business functionality expected by instance
889+
- Allow default access: Allows only minimum access required to run an Instance (Least Privileges).
890+
- Allow full access to all Cloud APIs: Allow full access to all the cloud APIs/Services (Too much access).
891+
- Set access for each API: Allows Instance administrator to choose only those APIs that are needed to perform specific business functionality expected by instance.
892+
889893
When an instance is configured with "Compute Engine default service account" with Scope "Allow full access to all Cloud APIs," based on IAM roles assigned to the user(s) accessing Instance,
890894
it might allow user to perform cloud operations/API calls that user isn't supposed to perform leading to successful privilege escalation.
895+
891896
VMs created by GKE should be excluded. These VMs have names that start with ```gke-``` and are labeled ```goog-gke-node```.
892897

893898
**Severity**: Medium

articles/defender-for-cloud/recommendations-reference-container.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -296,7 +296,7 @@ The AllowPrivilegeEscalation attribute controls whether a process can gain more
296296
**Description**: Microsoft Defender for Containers provides hardening, vulnerability assessment and run-time protections for your Azure, hybrid, and multicloud Kubernetes environments.
297297
You can use this information to quickly remediate security issues and improve the security of your containers.
298298

299-
Important: Remediating this recommendation will result in charges for protecting your Kubernetes clusters. If you don't have any Kubernetes clusters in this subscription, no charges will be incurred.
299+
Remediating this recommendation will result in charges for protecting your Kubernetes clusters. If you don't have any Kubernetes clusters in this subscription, no charges will be incurred.
300300
If you create any Kubernetes clusters on this subscription in the future, they'll automatically be protected and charges will begin at that time.
301301
Learn more in [Introduction to Microsoft Defender for Containers](container-security.md).
302302
(No related policy)
@@ -411,7 +411,7 @@ Learn more about [Microsoft Defender for Cloud's security features for container
411411
**Description**: Microsoft Defender for Containers provides real-time threat protection for containerized environments and generates alerts about suspicious activities.
412412
Use this information to harden the security of Kubernetes clusters and remediate security issues.
413413

414-
Important: When you enabled Microsoft Defender for Containers and deployed Azure Arc to your EKS clusters, the protections - and charges - will begin. If you don't deploy Azure Arc on a cluster, Defender for Containers won't protect it, and no charges are incurred for this Microsoft Defender plan for that cluster.
414+
When you enable Microsoft Defender for Containers and deploy Azure Arc to your EKS clusters, the protections - and charges - will begin. If you don't deploy Azure Arc on a cluster, Defender for Containers won't protect it, and no charges are incurred for this Microsoft Defender plan for that cluster.
415415

416416
**Severity**: High
417417

0 commit comments

Comments
 (0)