ECR repository policy allows any AWS account

What's the problem

The policy allows Principal "*" with no condition tying the caller to an identity, network or Organization: anyone can pull the images (and read code, configuration or credentials left in layers); with write actions they can push a poisoned image into your workloads

How 6WAF detects it

• Deterministic checks through AWS API calls (IAM, S3, EC2/VPC, CloudTrail, KMS, Secrets Manager, ACM, detection services) — no LLM is used for detection; severity is the value the scanner assigns, shown above.
• Scanning uses an IAM Role you deploy yourself via CloudFormation; 6WAF stores no credentials and you revoke access any time by deleting the stack.
• Automated scoring covers only part of the scope of standards such as ISO 27001 — this is a technical assessment, not a certification.