Cloudanix home page
Search...
⌘K
Ask AI
Community
Login
Login
Search...
Navigation
AWS Misconfigurations
Lambda Audit
Overview
AWS
Azure
GCP
GitHub
On-Demand Scan
Kubernetes
Integrations
AWS Introduction
Security of your AWS Account
AWS Pricing
AWS Services which determine your cost
AWS Threats
Getting Started with AWS Realtime Events
AWS Misconfigurations
Getting Started with AWS Audit
Permissions required for Misconfigurations Detection
API Gateway Audit
Cloudformation Audit
CloudFront Audit
CloudTrail Audit
Cloudwatch Audit
DynamoDB Audit
EC2 Audit
Elastic Search Audit
ELB Audit
IAM Audit
KMS Audit
Kubernetes Audit
Lambda Audit
RDS Audit
Redshift Audit
Route53 Audit
S3 Audit
Security Groups Audit
SES Audit
SNS Audit
IAM Deep Dive
App Sync Audit
Code Build Audit
Open Search Audit
Shield Audit
SQS Audit
On this page
Checks performed
AWS Misconfigurations
Lambda Audit
Checks performed
Lambda Functions Should Not Have Administrative Permissions
Lambda Functions Should Have Aliases
Lambda Functions Should Have Latest Runtime Version
CloudTrail Should Be Enabled For AWS Lambda
Lambda Functions Should Not Allow Cross Account Access
Lambda Should Have Access To VPC-only Resources
Lambda Functions Should Have Default Timeout Set
Lambda Functions Should Not Use Deprecated Versions
AWS Lambda Should Have DLQ Configured
AWS Lambda Functions Should Not Have Too Many Versions
Lambda Functions Should Have Tags
Lambda Functions Should Have Tracing Enabled
Lambda Should Have Concurrency Configured
Step Functions Should Have Logging Enabled
Multiple Functions Should Not Have The Same IAM Role
Lambda Functions Should Not Be Publicly Accessible
Kubernetes Audit
RDS Audit
Assistant
Responses are generated using AI and may contain mistakes.