HIGH

Ensure ECR repositories have image scanning enabled

ECR repositories should have scan-on-push enabled to detect vulnerabilities in container images.

Security Impact

Without scanning, vulnerable container images may be deployed to production.

How to Remediate

Enable scan on push for ECR repositories. Configure enhanced scanning for deeper analysis.

Affected Resources

AWS::ECR::Repository

Compliance Frameworks

SOC 2PCI-DSSHIPAANIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Elastic Container Registry (ECR) resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-ecr-1
Service
Elastic Container Registry (ECR)
Category
Vulnerability Management
Severity
HIGH

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Elastic Container Registry (ECR) Checks

View all checks
aws-ecr-2medium

Ensure ECR repositories have image immutability enabled

aws-ecr-3medium

Ensure ECR repositories are encrypted with KMS CMK

aws-ecr-4low

Ensure ECR repositories have lifecycle policies

aws-ecr-5high

Ensure ECR repository policies are restrictive

aws-ecr-6critical

Ensure ECR repositories do not allow public access