MEDIUM

Ensure Lambda functions do not share execution roles

Each Lambda function should have its own execution role with function-specific permissions.

Security Impact

Shared roles make it difficult to enforce least privilege and audit access.

How to Remediate

Create unique IAM roles for each Lambda function or group of related functions with identical permission needs.

Affected Resources

AWS::Lambda::FunctionAWS::IAM::Role

Compliance Frameworks

SOC 2NIST 800-53

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, 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-13
Service
AWS Lambda
Category
Identity Management
Severity
MEDIUM

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related AWS Lambda Checks

View all checks
aws-lambda-1critical

Ensure Lambda functions are not publicly accessible

aws-lambda-2medium

Ensure Lambda functions use latest runtime versions

aws-lambda-3low

Ensure Lambda functions have tracing enabled

aws-lambda-4low

Ensure Lambda functions have dead letter queues configured

aws-lambda-5high

Ensure Lambda functions use least privilege IAM roles