Ensure Lambda functions do not use wildcards in resource policies
Lambda resource policies should not use wildcards for principals or actions without proper conditions.
Security Impact
Wildcard policies can allow unintended access to invoke or manage Lambda functions.
How to Remediate
Replace wildcard principals with specific AWS account IDs, roles, or services. Add conditions like aws:SourceArn.
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 Lambda 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-lambda-18
- Service
- AWS Lambda
- Category
- Access Control
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Lambda Checks
View all checksEnsure Lambda functions are not publicly accessible
Ensure Lambda functions use latest runtime versions
Ensure Lambda functions have tracing enabled
Ensure Lambda functions have dead letter queues configured
Ensure Lambda functions use least privilege IAM roles