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: articles/defender-for-cloud/recommendations-reference-compute.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
@@ -4,7 +4,7 @@ description: This article lists all Microsoft Defender for Cloud compute securit
4
4
author: Elazark
5
5
ms.service: defender-for-cloud
6
6
ms.topic: reference
7
-
ms.date: 05/18/2025
7
+
ms.date: 03/30/2026
8
8
ms.author: elkrieger
9
9
ms.custom: generated
10
10
ai-usage: ai-assisted
@@ -45,10 +45,10 @@ To learn about actions that you can take in response to these recommendations, s
45
45
46
46
**Severity**: High
47
47
48
-
### Allowlist rules in your adaptive application control policy should be updated
48
+
### Allow list rules in your adaptive application control policy should be updated
49
49
50
50
**Description**: Monitor for changes in behavior on groups of machines configured for auditing by Defender for Cloud's adaptive application controls. Defender for Cloud uses machine learning to analyze the running processes on your machines and suggest a list of known-safe applications. These are presented as recommended apps to allow in adaptive application control policies.
51
-
(Related policy: [Allowlist rules in your adaptive application control policy should be updated](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f123a3936-f020-408a-ba0c-47873faf1534)).
51
+
(Related policy: [Allow list rules in your adaptive application control policy should be updated](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f123a3936-f020-408a-ba0c-47873faf1534)).
52
52
53
53
**Severity**: High
54
54
@@ -279,7 +279,7 @@ Replaces the older recommendation *Virtual machines should encrypt temp disks, c
279
279
280
280
### Linux virtual machines should use only signed and trusted boot components
281
281
282
-
**Description**: With Secure Boot enabled, all OS boot components (boot loader, kernel, kernel drivers) must be signed by trusted publishers. Defender for Cloud has identified untrusted OS boot components on one or more of your Linux machines. To protect your machines from potentially malicious components, add them to your allowlist or remove the identified components.
282
+
**Description**: With Secure Boot enabled, all OS boot components (boot loader, kernel, kernel drivers) must be signed by trusted publishers. Defender for Cloud has identified untrusted OS boot components on one or more of your Linux machines. To protect your machines from potentially malicious components, add them to your allow list or remove the identified components.
283
283
(No related policy)
284
284
285
285
**Severity**: Low
@@ -771,7 +771,7 @@ If you enable the interactive serial console on an instance, clients can attempt
771
771
A virtual machine instance has four virtual serial ports. Interacting with a serial port is similar to using a terminal window, in that input and output is entirely in text mode and there's no graphical interface or mouse support.
772
772
The instance's operating system, BIOS, and other system-level entities often write output to the serial ports, and can accept input such as commands or answers to prompts.
773
773
Typically, these system-level entities use the first serial port (port 1) and serial port 1 is often referred to as the serial console.
774
-
The interactive serial console doesn't support IP-based access restrictions such as IP allowlists. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address.
774
+
The interactive serial console doesn't support IP-based access restrictions such as IP allow lists. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address.
775
775
This allows anybody to connect to that instance if they know the correct SSH key, username, project ID, zone, and instance name.
776
776
Therefore interactive serial console support should be disabled.
0 commit comments