Ensure Lambda functions are not publicly accessible
Lambda function resource policies should not allow public invocation. Public functions can be called by anyone.
Security Impact
Public Lambda functions can be invoked by anyone, leading to unauthorized access and potential cost abuse.
How to Remediate
Remove resource-based policies that allow Principal:* or Principal:AWS:* without conditions. Use API Gateway with authentication for public APIs.
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, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-lambda-1
- Service
- AWS Lambda
- 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 Lambda Checks
View all checksEnsure 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
Ensure Lambda functions do not have secrets in environment variables