Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
awslambda_function_invoke_api_operations_cloudtrail_logging_enabledProvider: AWS
Service:
awslambdaSeverity: LOW
Categories:
loggingResource type:
AwsLambdaFunctionWhat this check verifies
AWS Lambda function invocations are recorded as CloudTrail data events when trails includeAWS::Lambda::Function resources.
The finding reflects whether a function’s Invoke activity is being logged by an eligible trail.
Risk
Without LambdaInvoke data events, per-invocation accountability is lost. Adversaries or misused automation can run code without an audit trail, obscuring actor, time, and source. This hinders forensics and enables covert exfiltration or unauthorized changes, impacting confidentiality and integrity.
Recommendation
Enable CloudTrail data event logging forAWS::Lambda::Function to capture Invoke calls across required Regions and accounts. Apply least privilege selectors to scope events, centralize logs with strong retention, and integrate alerts for anomalous invokes as part of defense in depth.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/lambda/latest/dg/logging-using-cloudtrail.html
- https://support.icompaas.com/support/solutions/articles/62000127055-ensure-lambda-functions-invoke-api-operations-are-being-recorded-by-cloudtrail
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = awslambda_function_invoke_api_operations_cloudtrail_logging_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks