Check ID:
Provider: Azure
Service:
Severity: HIGH
Categories:
Resource type:
containerregistry_admin_user_disabledProvider: Azure
Service:
containerregistrySeverity: HIGH
Categories:
identity-access, secretsResource type:
microsoft.containerregistry/registriesWhat this check verifies
Azure Container Registry admin account configuration, confirming the built-in admin user is disabled so access relies on Microsoft Entra-based RBAC identities and scoped roles.Risk
Using a shared, always-valid admin credential grants full push/pull and lacks attribution. Compromise enables unauthorized image pulls (confidentiality), malicious pushes or tag changes (integrity), and deletions or lockout (availability), enabling supply-chain attacks and lateral movement.Recommendation
Disable the admin account and require Microsoft Entra-backed RBAC. Assign least-privilege roles to users, service principals, or managed identities. Prefer short-lived credentials, rotate any residual secrets, and apply defense-in-depth with network restrictions and continuous auditing of registry access.Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
az acr update —name <RegistryName> —resource-group <ResourceGroupName> —admin-enabled false
References
Where this check fires
This check runs on every scheduled scan against your Azure account. Findings appear at Cloud Security → Findings filterable byCheck ID = containerregistry_admin_user_disabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Azure checks