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
| Communication Services |[ACSCallAutomationIncomingOperations](/azure/azure-monitor/reference/tables/ACSCallAutomationIncomingOperations)<br>[ACSCallAutomationMediaSummary](/azure/azure-monitor/reference/tables/ACSCallAutomationMediaSummary)<br>[ACSCallRecordingIncomingOperations](/azure/azure-monitor/reference/tables/ACSCallRecordingIncomingOperations)<br>[ACSCallRecordingSummary](/azure/azure-monitor/reference/tables/ACSCallRecordingSummary)<br>[ACSCallSummary](/azure/azure-monitor/reference/tables/ACSCallSummary)<br>[ACSJobRouterIncomingOperations](/azure/azure-monitor/reference/tables/ACSJobRouterIncomingOperations)<br>[ACSRoomsIncomingOperations](/azure/azure-monitor/reference/tables/acsroomsincomingoperations)|
194
+
| Communication Services |[ACSCallAutomationIncomingOperations](/azure/azure-monitor/reference/tables/ACSCallAutomationIncomingOperations)<br>[ACSCallAutomationMediaSummary](/azure/azure-monitor/reference/tables/ACSCallAutomationMediaSummary)<br>[ACSCallClientOperations](/azure/azure-monitor/reference/tables/ACSCallClientOperations)<br>[ACSCallRecordingIncomingOperations](/azure/azure-monitor/reference/tables/ACSCallRecordingIncomingOperations)<br>[ACSCallRecordingSummary](/azure/azure-monitor/reference/tables/ACSCallRecordingSummary)<br>[ACSCallSummary](/azure/azure-monitor/reference/tables/ACSCallSummary)<br>[ACSJobRouterIncomingOperations](/azure/azure-monitor/reference/tables/ACSJobRouterIncomingOperations)<br>[ACSRoomsIncomingOperations](/azure/azure-monitor/reference/tables/acsroomsincomingoperations)|
| Media Services |[AMSLiveEventOperations](/azure/azure-monitor/reference/tables/AMSLiveEventOperations)<br>[AMSKeyDeliveryRequests](/azure/azure-monitor/reference/tables/AMSKeyDeliveryRequests)<br>[AMSMediaAccountHealth](/azure/azure-monitor/reference/tables/AMSMediaAccountHealth)<br>[AMSStreamingEndpointRequests](/azure/azure-monitor/reference/tables/AMSStreamingEndpointRequests)|
@@ -203,24 +203,24 @@ The managed identity service generates the *principalId* GUID when you create th
203
203
204
204
## Link a workspace to a cluster
205
205
206
-
When a Log Analytics workspace is linked to a dedicated cluster, the workspace billing plan in workspace is changed to cluster plan, new data ingested to the workspace is routed to your dedicated cluster, and existing data remains in Log Analytics cluster. Linking a workspace has no effect on data ingestion and query experiences. Log Analytics query engine stitches data from old and new clusters automatically, and the results of queries are complete and accurate.
207
-
208
-
When dedicated cluster is configured with customer-managed key (CMK), new ingested data is encrypted with your key, while older data remains encrypted with Microsoft-managed key (MMK). The key configuration is abstracted by Log Analytics and the query across old and new data encryptions is performed seamlessly.
209
-
210
-
A cluster can be linked to up to 1,000 workspaces located in the same region as the cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
211
-
212
-
Other than the billing aspects that is governed by the cluster plan, all workspace configurations and query aspects remain unchanged after the link.
213
-
214
-
The workspace and the cluster can be in different subscriptions. It's possible for the workspace and cluster to be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
206
+
> [!NOTE]
207
+
> Linking a workspace can be performed only after the completion of the Log Analytics cluster provisioning.
208
+
> Linking a workspace to a cluster involves syncing multiple backend components and cache hydration, which can take up to two hours.
209
+
> When linking a Log Analytics workspace workspace, the workspace billing plan in changed to *LACluster*, and you should remove sku in workspace template to prevent conflict during workspace deployment.
210
+
> Other than the billing aspects that is governed by the cluster plan, all workspace configurations and query aspects remain unchanged during and after the link.
215
211
216
212
You need 'write' permissions to both the workspace and the cluster resource for workspace link operation:
217
213
218
214
- In the workspace: *Microsoft.OperationalInsights/workspaces/write*
219
215
- In the cluster resource: *Microsoft.OperationalInsights/clusters/write*
220
216
221
-
> [!NOTE]
222
-
> Linking a workspace can be performed only after the completion of the Log Analytics cluster provisioning.
223
-
> Linking a workspace to a cluster involves syncing multiple backend components and cache hydration, which can take up to two hours.
217
+
Once Log Analytics workspace linked to a dedicated cluster, new data sent to workspace is ingested to your dedicated cluster, while previously ingested data remains in Log Analytics cluster. Linking a workspace has no effect on workspace operation, including ingestion and query experiences. Log Analytics query engine stitches data from old and new clusters automatically, and the results of queries are complete.
218
+
219
+
When dedicated cluster is configured with customer-managed key (CMK), new ingested data is encrypted with your key, while older data remains encrypted with Microsoft-managed key (MMK). The key configuration is abstracted by Log Analytics and the query across old and new data encryptions is performed seamlessly.
220
+
221
+
A cluster can be linked to up to 1,000 workspaces located in the same region with cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
222
+
223
+
The workspace and the cluster can be in different subscriptions. It's possible for the workspace and cluster to be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
224
224
225
225
Use the following steps to link a workspace to a cluster. You can automated for linking multiple workspaces:
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/agentless-vulnerability-assessment-azure.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,13 +3,13 @@ title: Vulnerability assessments for Azure with Microsoft Defender Vulnerability
3
3
description: Learn about vulnerability assessments for Azure with Microsoft Defender Vulnerability Management.
4
4
author: dcurwin
5
5
ms.author: dacurwin
6
-
ms.date: 12/12/2023
6
+
ms.date: 12/14/2023
7
7
ms.topic: how-to
8
8
---
9
9
10
10
# Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management
11
11
12
-
Vulnerability assessment for Azure, powered by Microsoft Defender Vulnerability Management, is an out-of-box solution that empowers security teams to easily discover and remediate vulnerabilities in Linux container images, with zero configuration for onboarding, and without deployment of any agents.
12
+
Vulnerability assessment for Azure, powered by Microsoft Defender Vulnerability Management, is an out-of-box solution that empowers security teams to easily discover and remediate vulnerabilities in container images, with zero configuration for onboarding, and without deployment of any agents.
13
13
14
14
> [!NOTE]
15
15
> This feature supports scanning of images in the Azure Container Registry (ACR) only. Images that are stored in other container registries should be imported into ACR for coverage. Learn how to [import container images to a container registry](/azure/container-registry/container-registry-import-images).
@@ -18,8 +18,8 @@ In every subscription where this capability is enabled, all images stored in ACR
18
18
19
19
Container vulnerability assessment powered by Microsoft Defender Vulnerability Management has the following capabilities:
20
20
21
-
-**Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
22
-
-**Language specific packages** – support for language specific packages and files, and their dependencies installed or copied without the OS package manager. See the [complete list of supported languages](support-matrix-defender-for-containers.md#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
21
+
-**Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux and Windows OS. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
22
+
-**Language specific packages** – **Linux only** - support for language specific packages and files, and their dependencies installed or copied without the OS package manager. See the [complete list of supported languages](support-matrix-defender-for-containers.md#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
23
23
-**Image scanning in Azure Private Link** - Azure container vulnerability assessment provides the ability to scan images in container registries that are accessible via Azure Private Links. This capability requires access to trusted services and authentication with the registry. Learn how to [allow access by trusted services](/azure/container-registry/allow-access-trusted-services).
24
24
-**Exploitability information** - Each vulnerability report is searched through exploitability databases to assist our customers with determining actual risk associated with each reported vulnerability.
25
25
-**Reporting** - Container Vulnerability Assessment for Azure powered by Microsoft Defender Vulnerability Management provides vulnerability reports using following recommendations:
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/enable-vulnerability-assessment.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@ title: Enable vulnerability assessment powered by Microsoft Defender Vulnerabili
3
3
description: Learn how to enable vulnerability assessment powered by Microsoft Defender Vulnerability Management
4
4
ms.service: defender-for-cloud
5
5
ms.topic: how-to
6
-
ms.date: 07/20/2023
6
+
ms.date: 12/14/2023
7
7
---
8
8
9
9
# Enable vulnerability assessment powered by Microsoft Defender Vulnerability Management
10
10
11
-
Vulnerability assessment powered by Microsoft Defender Vulnerability Management, is an out-of-box solution that empowers security teams to easily discover and remediate vulnerabilities in Linux container images, with zero configuration for onboarding, and without deployment of any agents.
11
+
Vulnerability assessment powered by Microsoft Defender Vulnerability Management, is an out-of-box solution that empowers security teams to easily discover and remediate vulnerabilities in container images, with zero configuration for onboarding, and without deployment of any agents.
12
12
13
13
## How to enable vulnerability assessment powered by Microsoft Defender Vulnerability Management
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/includes/registries-images-mdvm.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
ms.service: defender-for-cloud
3
3
ms.custom: ignite-2022
4
4
ms.topic: include
5
-
ms.date: 07/25/2023
5
+
ms.date: 12/12/2023
6
6
ms.author: dacurwin
7
7
author: dcurwin
8
8
---
9
9
10
10
| Aspect | Details |
11
11
|--|--|
12
-
| Registries and images |**Supported**<br> • ACR registries <br> • [ACR registries protected with Azure Private Link](/azure/container-registry/container-registry-private-link) (Private registries requires access to Trusted Services) <br> • Container images in Docker V2 format <br> **Unsupported**<br> • Super-minimalist images such as [Docker scratch](https://hub.docker.com/_/scratch/) images<br> • Images with [Open Container Initiative (OCI)](https://github.com/opencontainers/image-spec/blob/main/spec.md) image format specification <br> • Windows images<br>|
13
-
|OS Packages|**Supported** <br> • Alpine Linux 3.12-3.16 <br> • Red Hat Enterprise Linux 6-9 <br> • CentOS 6-9<br> • Oracle Linux 6-9 <br> • Amazon Linux 1, 2 <br> • openSUSE Leap, openSUSE Tumbleweed <br> • SUSE Enterprise Linux 11-15 <br> • Debian GNU/Linux 7-12 <br> • Google Distroless (based on Debian Linux 7-12) <br>• Ubuntu 12.04-22.04 <br> • Fedora 31-37<br> • Mariner 1-2|
14
-
| Language specific packages <br><br> |**Supported** <br> • Python <br> • Node.js <br> • .NET <br> • JAVA <br> • Go |
12
+
| Registries and images |**Supported**<br> • ACR registries <br> • [ACR registries protected with Azure Private Link](/azure/container-registry/container-registry-private-link) (Private registries requires access to Trusted Services) <br> • Container images in Docker V2 format <br> • Windows images <br> **Unsupported**<br> • Super-minimalist images such as [Docker scratch](https://hub.docker.com/_/scratch/) images<br> • "Distroless" images that only contain an application and its runtime dependencies without a package manager, shell, or OS<br> is currently unsupported <br> • Images with [Open Container Initiative (OCI)](https://github.com/opencontainers/image-spec/blob/main/spec.md) image format specification <br>|
13
+
|Operating system|**Supported** <br> • Alpine Linux 3.12-3.16 <br> • Red Hat Enterprise Linux 6-9 <br> • CentOS 6-9<br> • Oracle Linux 6-9 <br> • Amazon Linux 1, 2 <br> • openSUSE Leap, openSUSE Tumbleweed <br> • SUSE Enterprise Linux 11-15 <br> • Debian GNU/Linux 7-12 <br> • Google Distroless (based on Debian Linux 7-12) <br>• Ubuntu 12.04-22.04 <br> • Fedora 31-37<br> • Mariner 1-2<br> • Windows Server 2016, 2019 and 2022 |
14
+
| Language specific packages **(Linux only)**<br><br> |**Supported** <br> • Python <br> • Node.js <br> • .NET <br> • JAVA <br> • Go |
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/support-matrix-defender-for-containers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Review support requirements for container capabilities in Microsoft
4
4
ms.topic: limits-and-quotas
5
5
author: dcurwin
6
6
ms.author: dacurwin
7
-
ms.date: 09/06/2023
7
+
ms.date: 12/14/2023
8
8
ms.custom: references_regions, ignite-2022
9
9
---
10
10
@@ -29,7 +29,7 @@ This article summarizes support information for Container capabilities in Micros
29
29
|[Vulnerability assessment](defender-for-containers-vulnerability-assessment-azure.md)| Agentless registry scan (powered by Qualys) <BR> [Supported OS packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-qualys)| ACR, Private ACR | GA | Preview | Agentless | Defender for Containers | Commercial clouds<br><br> National clouds: Azure Government, Azure operated by 21Vianet |
30
30
|[Vulnerability assessment](defender-for-containers-vulnerability-assessment-azure.md)| Agentless registry scan (powered by Qualys) <BR> [Supported language packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-qualys)| ACR, Private ACR | Preview | - | Agentless | Defender for Containers | Commercial clouds<br><br> National clouds: Azure Government, Azure operated by 21Vianet |
31
31
|[Vulnerability assessment](defender-for-containers-vulnerability-assessment-azure.md)| Agentless/agent-based runtime scan(powered by Qualys) [OS packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-qualys)| AKS | GA | Preview | Defender agent | Defender for Containers | Commercial clouds |
32
-
|[Vulnerability assessment](agentless-vulnerability-assessment-azure.md)| Agentless registry scan (powered by Microsoft Defender Vulnerability Management) [supported packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management)| ACR, Private ACR | GA |-| Agentless | Defender for Containers or Defender CSPM | Commercial clouds<br/><br/> National clouds: Azure Government, Azure operated by 21Vianet |
32
+
|[Vulnerability assessment](agentless-vulnerability-assessment-azure.md)| Agentless registry scan (powered by Microsoft Defender Vulnerability Management) [supported packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management)| ACR, Private ACR | GA |Preview| Agentless | Defender for Containers or Defender CSPM | Commercial clouds<br/><br/> National clouds: Azure Government, Azure operated by 21Vianet |
33
33
|[Vulnerability assessment](agentless-vulnerability-assessment-azure.md)| Agentless/agent-based runtime (powered by Microsoft Defender Vulnerability Management) [supported packages](#registries-and-images-support-for-azure---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management)| AKS | GA | - | Defender agent | Defender for Containers or Defender CSPM | Commercial clouds<br/><br/> National clouds: Azure Government, Azure operated by 21Vianet |
34
34
| Runtime threat protection |[Control plane](defender-for-containers-introduction.md#run-time-protection-for-kubernetes-nodes-and-clusters)| AKS | GA | GA | Agentless | Defender for Containers | Commercial clouds<br><br> National clouds: Azure Government, Azure operated by 21Vianet |
35
35
| Runtime threat protection | Workload | AKS | GA | - | Defender agent | Defender for Containers | Commercial clouds |
0 commit comments