AZDO.1014: Anonymous access to pipeline badges.
| ID | AZDO.1014 |
| Severity | Medium |
| Suite | Mito |
| Product | Azure DevOps |
| Feature | Pipelines |
| Security area | External access and sharing |
| Resource type | Tenant |
| User impact of fixing | Low |
| Effort to fix | Low |
| MITRE ATT&CK | T1593.003 |
| Reads from | Azure DevOps |
| Further reading | https://learn.microsoft.com/azure/devops/pipelines/create-first-pipeline?view=azure-devops&tabs=net%2Cbrowser#add-a-status-badge-to-your-repository |
What this checks and how to fix it
Section titled “What this checks and how to fix it”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
Section titled “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
Section titled “Related links”Mito check. Author: SebastianClaesson. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.