Anomalous number of AWS Lambda functions deleted

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Goal

Detects anomalous deletion of AWS Lambda functions. This rule identifies when a user or role deletes an unusual number of Lambda functions within a short time period.

Strategy

This rule monitors AWS CloudTrail logs for DeleteFunction20150331 events. The detection uses anomaly detection to establish a baseline of normal deletion patterns over a 24-hour learning period and identifies deviations from this baseline. Lambda functions often contain critical business logic and their deletion can disrupt services or remove security controls.

Triage & Response

  1. Review the @userIdentity.arn to identify the account or role that performed the deletions.
  2. Check the @requestParameters.functionName to determine which specific Lambda functions were deleted.
  3. Verify if the deleted functions were part of a planned decommissioning or migration effort.
  4. Examine the CloudTrail logs for additional suspicious activity from the same identity around the time of the deletions.
  5. Review AWS CloudWatch logs for the deleted functions to check for any unusual activity prior to deletion.
  6. Check if the identity has the necessary permissions to perform these deletions through IAM policies.
  7. Restore the deleted functions from backups if available and implement stricter access controls for Lambda function deletion.
PREVIEWING: aliciascott/DOCS-10683-Cloudcraft-CCM