Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
ecr_repositories_scan_images_on_push_enabledProvider: AWS
Service:
ecrSeverity: MEDIUM
Categories:
container-securityResource type:
AwsEcrRepositoryWhat this check verifies
[DEPRECATED] Amazon ECR repositories are evaluated for image scanning on push; when configured, new image uploads automatically trigger a vulnerability scan (scan_on_push).
Risk
Without scan on push, images with known CVEs can enter registries and reach runtime unnoticed, undermining integrity and confidentiality through exploitable packages. Attackers may achieve code execution and lateral movement. Delayed detection increases operational risk and extends remediation timelines.Recommendation
Enable image scanning on push (scan_on_push) for all repositories and use findings as promotion gates. Prefer continuous/enhanced scanning for defense in depth, set severity thresholds, and block or quarantine noncompliant images. Integrate results with CI/CD and adopt shift-left vulnerability management.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/ECR/scan-on-push.html
- https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning-basic-enabling.html
- https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ecr_repositories_scan_images_on_push_enabled. 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 AWS checks