LOW

Ensure Lambda functions are tagged appropriately

Lambda functions should have required tags for cost allocation, ownership, and environment identification.

Security Impact

Untagged functions are difficult to track for billing and security purposes.

How to Remediate

Implement tagging policies and apply required tags: Environment, Owner, Project, CostCenter.

Affected Resources

AWS::Lambda::Function

Compliance Frameworks

SOC 2

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 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-lambda-19
Service
AWS Lambda
Category
Governance
Severity
LOW

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