Skip to content

Commit 0df2dec

Browse files
tylchanCopilot
andauthored
Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
1 parent 0c399ce commit 0df2dec

1 file changed

Lines changed: 0 additions & 8 deletions

File tree

  • src/react/docs/workshop-guidance/devsecops

src/react/docs/workshop-guidance/devsecops/DS_050.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,11 @@
11
# Connect DevOps environments to Defender for Cloud
22

3-
4-
53
**Implementation Effort:** Low – Authorizing the Defender for Cloud connectors and installing the app on each DevOps organization is a bounded onboarding task, though it needs subscription and organization owners to grant access.
6-
74
**User Impact:** Low – Connecting environments and running security assessments happens in the management plane, so developers keep working in their repositories and pipelines without interruption.
8-
95
**Lifecycle Stage:** Run
106

11-
12-
137
## Overview
148

15-
16-
179
Connect GitHub, Azure DevOps, and GitLab environments to Microsoft Defender for Cloud so repositories, pipelines, and service connections are assessed in one security management plane. Connecting the environments is the prerequisite, but most DevOps posture management recommendations and advanced capabilities — such as attack path analysis and code-to-cloud mapping — require Defender CSPM and any applicable Microsoft Defender for Cloud plans for the connected workloads.
1810

1911

0 commit comments

Comments
 (0)