HIGH

Ensure ECR repository policies are restrictive

ECR repository policies should restrict access to specific principals.

Security Impact

Overly permissive policies may allow unauthorized image access.

How to Remediate

Review repository policies. Restrict to specific AWS accounts and IAM principals.

Affected Resources

AWS::ECR::Repository

Compliance Frameworks

SOC 2PCI-DSSNIST 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, NIST 800-53 compliance

  • Drift Detection

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

Check Details

Check ID
aws-ecr-5
Service
Elastic Container Registry (ECR)
Category
Access Control
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-1high

Ensure ECR repositories have image scanning enabled

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-6critical

Ensure ECR repositories do not allow public access