ID | Technique | Tactic |
---|---|---|
T1562 | Impair Defenses | Defense Evasion |
T1562.008 | Disable or Modify Cloud Logs | Defense Evasion |
Detection: ASL AWS Defense Evasion Update Cloudtrail
Description
The following analytic detects UpdateTrail
events within AWS CloudTrail logs, aiming to identify attempts by attackers to evade detection by altering logging configurations. By updating CloudTrail settings with incorrect parameters, such as changing multi-regional logging to a single region, attackers can impair the logging of their activities across other regions. This behavior is crucial for Security Operations Centers (SOCs) to identify, as it indicates an adversary's intent to operate undetected within a compromised AWS environment. The impact of such evasion tactics is significant, potentially allowing malicious activities to proceed without being logged, thereby hindering incident response and forensic investigations.
Search
1`amazon_security_lake` api.operation=UpdateTrail
2| fillnull
3| stats count min(_time) as firstTime max(_time) as lastTime by api.operation actor.user.account_uid actor.user.uid http_request.user_agent src_endpoint.ip cloud.region
4| rename actor.user.uid as user, src_endpoint.ip as src_ip, cloud.region as region, http_request.user_agent as user_agent, actor.user.account_uid as aws_account_id
5| `security_content_ctime(firstTime)`
6| `security_content_ctime(lastTime)`
7| `asl_aws_defense_evasion_update_cloudtrail_filter`
Data Source
No data sources specified for this detection.
Macros Used
Name | Value |
---|---|
amazon_security_lake | sourcetype=aws:cloudtrail:lake |
asl_aws_defense_evasion_update_cloudtrail_filter | search * |
asl_aws_defense_evasion_update_cloudtrail_filter
is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
Setting | Value |
---|---|
Disabled | true |
Cron Schedule | 0 * * * * |
Earliest Time | -70m@m |
Latest Time | -10m@m |
Schedule Window | auto |
Creates Notable | Yes |
Rule Title | %name% |
Rule Description | %description% |
Notable Event Fields | user, dest |
Creates Risk Event | True |
Implementation
The detection is based on Amazon Security Lake events from Amazon Web Services (AWS), which is a centralized data lake that provides security-related data from AWS services. To use this detection, you must ingest CloudTrail logs from Amazon Security Lake into Splunk. To run this search, ensure that you ingest events using the latest version of Splunk Add-on for Amazon Web Services (https://splunkbase.splunk.com/app/1876) or the Federated Analytics App.
Known False Positives
While this search has no known false positives, it is possible that an AWS admin has updated cloudtrail logging. Please investigate this activity.
Associated Analytic Story
Risk Based Analytics (RBA)
Risk Message | Risk Score | Impact | Confidence |
---|---|---|---|
User $user$ has updated a cloudtrail logging for account id $aws_account_id$ from IP $src_ip$ | 90 | 100 | 90 |
References
Detection Testing
Test Type | Status | Dataset | Source | Sourcetype |
---|---|---|---|---|
Validation | ✅ Passing | N/A | N/A | N/A |
Unit | ✅ Passing | Dataset | aws_asl |
aws:cloudtrail:lake |
Integration | ✅ Passing | Dataset | aws_asl |
aws:cloudtrail:lake |
Replay any dataset to Splunk Enterprise by using our replay.py
tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub | Version: 3