DevOps security requires the following permissions:
Feature
Permissions
Connect DevOps environments to Defender for Cloud
Azure: Subscription Contributor or Security Admin
Azure DevOps: Project Collection Administrator on target Organization
GitHub: Organization Owner
GitLab: Group Owner on target Group
Review security insights and findings
Security Reader
Configure pull request annotations
Subscription Contributor or Owner
Install the Microsoft Security DevOps extension in Azure DevOps
Azure DevOps Project Collection Administrator
Install the Microsoft Security DevOps action in GitHub
GitHub Write
Note
Security Reader role can be applied on the Resource Group or connector scope to avoid setting highly privileged permissions on a Subscription level for read access of DevOps security insights and findings.
Feature availability
DevOps security capabilities, such as code-to-cloud contextualization, security explorer, attack path analysis, and pull request annotations for Infrastructure-as-Code security findings, are available when you enable the paid Defender Cloud Security Posture Management (CSPM) plan.
The following tables summarize the availability and prerequisites for each feature within the supported DevOps platforms:
In this episode of Defender for Cloud in the Field, Sukhandeep Singh joins Yuri Diogenes to talk about Defender for DevOps. Sukhandeep explains how Defender for DevOps uses a central console to provide security teams DevOps insights across multi-pipeline environments, such as GitHub and Azure DevOps. Sukhandeep also covers the security recommendations created by Defender for DevOps and demonstrates how to configure a GitHub connector using Defender for Cloud dashboard. Chapters 01:16 - What is Defender for
Learn about the benefits and features of Microsoft Defender for Cloud DevOps security, including visibility, posture management, and threat protection.