Ensure Secrets Manager secrets are not publicly accessible
Secret resource policies should not allow public access with Principal:*.
Security Impact
Public secret access exposes credentials to anyone.
How to Remediate
Remove resource policy statements that allow Principal:* or Principal:AWS:* without conditions.
Affected Resources
Compliance Frameworks
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 AWS Secrets Manager 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-secretsmanager-4
- Service
- AWS Secrets Manager
- Category
- Public Access
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Secrets Manager Checks
View all checksEnsure Secrets Manager secrets have automatic rotation enabled
Ensure Secrets Manager secrets are encrypted with KMS CMK
Ensure Secrets Manager secrets have resource policies
Ensure Secrets Manager rotation is tested
Ensure Secrets Manager secrets have appropriate rotation schedules