For the complete documentation index, see llms.txt. This page is also available as Markdown.

Azure DevOps

Integrate Cortex Cloud Application Security with your Azure DevOps version control system (VCS) to enable comprehensive security scans for exposed secrets, infrastructure-as-code (IaC) misconfigurations, vulnerabilities, package operational risks, and license compliance issues in your repositories. By scanning these repositories, Cortex Cloud builds a code-to-cloud lineage graph that powers Urgency classification, allowing you to efficiently analyze, prioritize, and remediate your most critical risks.

Architectural models and authentication options

Cortex Cloud supports the following Azure DevOps authentication methods.

Service Principal

An autonomous application identity in Microsoft Entra ID. Cortex Cloud manages its credentials centrally.

Use when: Security policies require application identities. It also suits CI automation and staff turnover.

Microsoft Entra ID user authentication

Cortex Cloud calls Azure DevOps APIs for the authenticated user. Azure DevOps audit logs show that user.

Use when: You need to discover and onboard several organizations in one Entra ID tenant.

Personal Access Token (PAT)

A static token belongs to one user and one Azure DevOps organization.

Use when: Microsoft Entra ID integration is not possible. Each organization requires a separate PAT.

Microsoft is deprecating legacy OAuth methods. Use Microsoft Entra ID for long-term support.

Learn more

Last updated

Was this helpful?