Securing AWS Lambda function URLs

This article analyzes the risks of insecure AWS Lambda function URLs, showing how attackers can discover misconfigured public endpoints (e.g., via passive DNS or development artifacts) and abuse them for data access/manipulation, privilege escalation, vulnerability exploitation, denial of service, and “denial of wallet.” It recommends enforcing IAM authentication and tight resource policies, configuring restrictive CORS, and setting reserved concurrency to limit blast radius, while noting the broader trend of serverless-targeting threats (e.g., Denonia) and describing how Wiz can detect toxic exposure/privilege combinations and monitor serverless security posture.