AZDO.1014 - Anonymous access to pipeline badges.
Overview
Status badges in Azure DevOps should be disabled.
Rationale: Even in a private project, anonymous badge access is enabled by default. With anonymous badge access enabled, users outside your organization might be able to query information such as project names, branch names, job names, and build status through the badge status API.
Remediation action
Enable the restriction to prevent anonymous access to status badges.
- Sign in to your organization.
- Choose Organization settings.
- Select Settings under Pipelines.
- Enable the policy "Disable anonymous access to badges"
Results: Users outside of your organization cannot query information regarding your project names, branch names, job names, and build statuses through the badge status API.
Related links
Test Metadata
| Field | Value |
|---|---|
| Test ID | AZDO.1014 |
| Severity | Medium |
| Suite | Maester |
| Product | Azure DevOps |
| Feature | Pipelines |
| Area | External access and sharing |
| Resource type | Tenant |
| User impact | Low |
| Implementation cost | Low |
| MITRE ATT&CK | T1593.003 Code Repositories |
| PowerShell test | Test-AzdoOrganizationBadgesArePrivate |
| Services | AzureDevOps |
| Learn more | https://learn.microsoft.com/azure/devops/pipelines/create-first-pipeline?view=azure-devops&tabs=net%2Cbrowser#add-a-status-badge-to-your-repository |