This analytic identifies AWS
DeleteLogGroup events in CloudTrail logs. Attackers may evade the logging capability by deleting the log group in CloudWatch. This will stop sending the logs and metrics to CloudWatch. When the adversary has the right type of permissions within the compromised AWS environment, they may delete the CloudWatch log group that is logging activities in the environment.
- Type: TTP
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2022-07-17
- Author: Gowthamaraj Rajendran, Splunk
- ID: d308b0f1-edb7-4a62-a614-af321160710f
Kill Chain Phase
- CIS 10
1 2 3 4 5 `cloudtrail` eventName = DeleteLogGroup eventSource = logs.amazonaws.com userAgent !=console.amazonaws.com errorCode = success | stats count min(_time) as firstTime max(_time) as lastTime values(requestParameters.logGroupName) as log_group_name by src region eventName userAgent user_arn aws_account_id | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `aws_defense_evasion_delete_cloudwatch_log_group_filter`
The SPL above uses the following Macros:
aws_defense_evasion_delete_cloudwatch_log_group_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
You must install Splunk AWS Add on and enable CloudTrail logs in your AWS Environment.
Known False Positives
While this search has no known false positives, it is possible that an AWS admin has deleted CloudWatch logging. Please investigate this activity.
Associated Analytic Story
|90.0||100||90||User $user_arn$ has deleted a CloudWatch logging group for account id $aws_account_id$ from IP $src$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1