Skip to content

Commit 5ca4f7b

Browse files
refresh pages 1 and 2
1 parent c1cbc15 commit 5ca4f7b

File tree

2 files changed

+13
-15
lines changed

2 files changed

+13
-15
lines changed

articles/defender-for-cloud/defender-for-devops-introduction.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
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
55
ms.topic: overview
66
ms.custom: references_regions
77
---
88

9-
# Overview of Microsoft Defender for Cloud DevOps Security
9+
# Overview of Microsoft Defender for Cloud DevOps security
1010

1111
Microsoft Defender for Cloud enables comprehensive visibility, posture management, and threat protection across multicloud environments including Azure, AWS, GCP, and on-premises resources.
1212

@@ -40,7 +40,7 @@ Here, you can add [Azure DevOps](quickstart-onboard-devops.md), [GitHub](quickst
4040

4141
The DevOps inventory table allows you to review onboarded DevOps resources and the security information related to them.
4242

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":::
4444

4545
On this part of the screen you see:
4646

@@ -67,7 +67,7 @@ On this part of the screen you see:
6767
6868
- **Findings** - Shows the total number of code, secrets, dependency, and infrastructure-as-code findings identified in the DevOps resource.
6969

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.
7171

7272
## Learn more
7373

@@ -77,12 +77,10 @@ This table can be viewed as a flat view at the DevOps resource level (repositori
7777

7878
- You can learn about [securing Azure Pipelines](/azure/devops/pipelines/security/overview).
7979

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).
8181

8282
## Next steps
8383

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).

articles/defender-for-cloud/monitoring-components.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
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.
44
author: dcurwin
55
ms.author: dacurwin
66
ms.topic: conceptual
7-
ms.date: 11/27/2022
7+
ms.date: 03/11/2024
88
---
99

1010
# How does Defender for Cloud collect data?
@@ -13,7 +13,7 @@ Defender for Cloud collects data from your Azure virtual machines (VMs), Virtual
1313

1414
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.
1515

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.
1717

1818
Data is collected using:
1919

@@ -96,7 +96,7 @@ The following use cases explain how deployment of the Log Analytics agent works
9696

9797
- **A pre-existing VM extension is present**:
9898
- 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.
100100
- 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.
101101

102102
Learn more about [working with the Log Analytics agent](working-with-log-analytics-agent.md).

0 commit comments

Comments
 (0)