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/defender-for-devops-introduction.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
title: Microsoft Defender for Cloud DevOps security - the benefits and features
3
-
description: Learn about the benefits and features of Microsoft DevOps security
4
-
ms.date: 01/24/2023
3
+
description: Learn about the benefits and features of Microsoft DevOps security.
4
+
ms.date: 03/11/2024
5
5
ms.topic: overview
6
6
ms.custom: references_regions
7
7
---
8
8
9
-
# Overview of Microsoft Defender for Cloud DevOps Security
9
+
# Overview of Microsoft Defender for Cloud DevOps security
10
10
11
11
Microsoft Defender for Cloud enables comprehensive visibility, posture management, and threat protection across multicloud environments including Azure, AWS, GCP, and on-premises resources.
12
12
@@ -40,7 +40,7 @@ Here, you can add [Azure DevOps](quickstart-onboard-devops.md), [GitHub](quickst
40
40
41
41
The DevOps inventory table allows you to review onboarded DevOps resources and the security information related to them.
42
42
43
-
:::image type="content" source="media/defender-for-devops-introduction/inventory-grid.png" alt-text="Screenshot of the devops inventory table on the DevOps security overview page." lightbox="media/defender-for-devops-introduction/bottom-of-page.png":::
43
+
:::image type="content" source="media/defender-for-devops-introduction/inventory-grid.png" alt-text="Screenshot that shows the Devops inventory table on the DevOps security overview page." lightbox="media/defender-for-devops-introduction/bottom-of-page.png":::
44
44
45
45
On this part of the screen you see:
46
46
@@ -67,7 +67,7 @@ On this part of the screen you see:
67
67
68
68
-**Findings** - Shows the total number of code, secrets, dependency, and infrastructure-as-code findings identified in the DevOps resource.
69
69
70
-
This table can be viewed as a flat view at the DevOps resource level (repositories for Azure DevOps and GitHub, projects for GitLab) or in a grouping view showing organizations/projects/groups hierarchy. Also, the table can be filtered by subscription, resource type, finding type, or severity.
70
+
This table can be viewed as a flat view at the DevOps resource level (repositories for Azure DevOps and GitHub, projects for GitLab) or in a grouping view showing organizations/projects/groups hierarchy. Also, you can filter the table by subscription, resource type, finding type, or severity.
71
71
72
72
## Learn more
73
73
@@ -77,12 +77,10 @@ This table can be viewed as a flat view at the DevOps resource level (repositori
77
77
78
78
- You can learn about [securing Azure Pipelines](/azure/devops/pipelines/security/overview).
79
79
80
-
- Learn about [security hardening practices for GitHub Actions](https://docs.github.com/actions/security-guides/security-hardening-for-github-actions).
80
+
- Learn about [security hardening practices for GitHub actions](https://docs.github.com/actions/security-guides/security-hardening-for-github-actions).
81
81
82
82
## Next steps
83
83
84
-
[Connect your Azure DevOps organizations](quickstart-onboard-devops.md).
85
-
86
-
[Connect your GitHub organizations](quickstart-onboard-github.md).
87
-
88
-
[Connect your GitLab groups](quickstart-onboard-gitlab.md).
84
+
-[Connect your Azure DevOps organizations](quickstart-onboard-devops.md).
85
+
-[Connect your GitHub organizations](quickstart-onboard-github.md).
86
+
-[Connect your GitLab groups](quickstart-onboard-gitlab.md).
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/monitoring-components.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
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Overview of the extensions that collect data from your workloads
3
-
description: Learn about the extensions that collect data from your workloads to let you protect your workloads with Microsoft Defender for Cloud.
3
+
description: Protect your workloads with Microsoft Defender for Cloud by learning about the extensions that collect data from your workloads.
4
4
author: dcurwin
5
5
ms.author: dacurwin
6
6
ms.topic: conceptual
7
-
ms.date: 11/27/2022
7
+
ms.date: 03/11/2024
8
8
---
9
9
10
10
# How does Defender for Cloud collect data?
@@ -13,7 +13,7 @@ Defender for Cloud collects data from your Azure virtual machines (VMs), Virtual
13
13
14
14
Data collection is required to provide visibility into missing updates, misconfigured OS security settings, endpoint protection status, and health and threat protection. Data collection is only needed for compute resources such as VMs, Virtual Machine Scale Sets, IaaS containers, and non-Azure computers.
15
15
16
-
You can benefit from Microsoft Defender for Cloud even if you don’t provision agents. However, you'll have limited security and the capabilities listed above aren't supported.
16
+
You can benefit from Microsoft Defender for Cloud even if you don’t provision agents. However, you'll have limited security and the capabilities listed aren't supported.
17
17
18
18
Data is collected using:
19
19
@@ -96,7 +96,7 @@ The following use cases explain how deployment of the Log Analytics agent works
96
96
97
97
-**A pre-existing VM extension is present**:
98
98
- When the Monitoring Agent is installed as an extension, the extension configuration allows reporting to only a single workspace. Defender for Cloud doesn't override existing connections to user workspaces. Defender for Cloud will store security data from the VM in the workspace already connected, if the "Security" or "SecurityCenterFree" solution was installed on it. Defender for Cloud might upgrade the extension version to the latest version in this process.
99
-
- To see to which workspace the existing extension is sending data to, run the *TestCloudConnection.exe* tool to validate connectivity with Microsoft Defender for Cloud, as described in [Verify Log Analytics Agent connectivity](/services-hub/unified/health/assessments-troubleshooting#verify-log-analytics-agent-connectivity). Alternatively, you can open Log Analytics workspaces, select a workspace, select the VM, and look at the Log Analytics agent connection.
99
+
- To see to which workspace the existing extension is sending data to, run the *TestCloudConnection.exe* tool to validate connectivity with Microsoft Defender for Cloud, as described in [Verify Log Analytics agent connectivity](/services-hub/unified/health/assessments-troubleshooting#verify-log-analytics-agent-connectivity). Alternatively, you can open Log Analytics workspaces, select a workspace, select the VM, and look at the Log Analytics agent connection.
100
100
- If you have an environment where the Log Analytics agent is installed on client workstations and reporting to an existing Log Analytics workspace, review the list of [operating systems supported by Microsoft Defender for Cloud](security-center-os-coverage.md) to make sure your operating system is supported.
101
101
102
102
Learn more about [working with the Log Analytics agent](working-with-log-analytics-agent.md).
0 commit comments