Container registry security hardening
High
Cross-cloud
General
acr-container-registry-security-hardening
Applies to
Microsoft.ContainerRegistry/registriesAWS::ECR::Repository
What CGPulse checks
A resource passes this rule when adminUserEnabled must equal false OR imageScanOnPush must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Disable the admin user and use IAM/Azure AD identities for scoped, auditable access. In AWS Console: ECR > Repositories > configure IAM policies for access. See: https://docs.aws.amazon.com/AmazonECR/latest/userguide/security-iam.html
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening
- Kubernetes clusters must restrict public API access