domains / families / security / securing-serverless-functions

securing-serverless-functions

separate

'Hardens serverless compute platforms (AWS Lambda, Azure Functions, Google

When to use

• When deploying Lambda functions or Azure Functions with access to sensitive data or cloud APIs
• When auditing existing serverless workloads for overly permissive IAM roles
• When integrating serverless functions into a DevSecOps pipeline with automated security scanning
• When hardcoded secrets or vulnerable dependencies are discovered in function code
• When establishing runtime monitoring for serverless workloads to detect injection or credential theft

When not to use

• container-based compute security
• API Gateway configuration
• serverless architecture design decisions

Skill page

Source