Secret resource policy allows public access

What's the problem

The secret's resource policy grants Principal "*" without limiting the account. 6WAF reads only the policy, never the secret value. Use --block-public-policy so Secrets Manager rejects such policies

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.