AWS Disable Bucket Versioning

Original Source: [splunk source]
Name:AWS Disable Bucket Versioning
id:657902a9-987d-4879-a1b2-e7a65512824b
version:3
date:2024-09-30
author:Bhavin Patel, Splunk
status:production
type:Anomaly
Description:The following analytic detects when AWS S3 bucket versioning is suspended by a user. It leverages AWS CloudTrail logs to identify `PutBucketVersioning` events with the `VersioningConfiguration.Status` set to `Suspended`. This activity is significant because disabling versioning can prevent recovery of deleted or modified data, which is a common tactic in ransomware attacks. If confirmed malicious, this action could lead to data loss and hinder recovery efforts, severely impacting data integrity and availability.
Data_source:
  • -AWS CloudTrail PutBucketVersioning
search:`cloudtrail` eventName= PutBucketVersioning "requestParameters.VersioningConfiguration.Status"=Suspended
| stats count values(requestParameters.bucketName) as bucket_name values(resources{}.ARN) as resource_arn by src_ip aws_account_id awsRegion eventName userAgent user_arn userIdentity.principalId errorCode
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`| `aws_disable_bucket_versioning_filter`


how_to_implement:You must install splunk AWS add on and Splunk App for AWS. This search works with AWS CloudTrail logs.
known_false_positives:It is possible that an AWS Administrator has legitimately disabled versioning on certain buckets to avoid costs.
References:
  -https://invictus-ir.medium.com/ransomware-in-the-cloud-7f14805bbe82
  -https://bleemb.medium.com/data-exfiltration-with-native-aws-s3-features-c94ae4d13436
drilldown_searches:
name:'View the detection results for - "$aws_account_id$"'
search:'%original_detection_search% | search aws_account_id = "$aws_account_id$"'
earliest_offset:'$info_min_time$'
latest_offset:'$info_max_time$'
name:'View risk events for the last 7 days for - "$aws_account_id$"'
search:'| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$aws_account_id$") starthoursago=168 | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
earliest_offset:'$info_min_time$'
latest_offset:'$info_max_time$'
tags:
  analytic_story:
    - 'Suspicious AWS S3 Activities'
    - 'Data Exfiltration'
  asset_type:AWS Account
  confidence:80
  impact:80
  message:Bucket Versioning is suspended for S3 buckets- $bucket_name$ by user $user_arn$ from IP address $src_ip$
  mitre_attack_id:
    - 'T1490'
  observable:
    name:'user_arn'
    type:'User'
    - role:
      - 'Attacker'
    name:'src_ip'
    type:'IP Address'
    - role:
      - 'Attacker'
    name:'aws_account_id'
    type:'Other'
    - role:
      - 'Victim'
  product:
    - 'Splunk Enterprise'
    - 'Splunk Enterprise Security'
    - 'Splunk Cloud'
  required_fields:
    - '_time'
    - 'eventName'
    - 'user_arn'
    - 'src_ip'
    - 'aws_account_id'
    - 'destinationLocationArn'
    - 'sourceLocationArn'
    - 'userAgent'
    - 'userIdentity.principalId'
  risk_score:64
  security_domain:threat

tests:
name:'True Positive Test'
 attack_data:
  data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1490/aws_bucket_version/cloudtrail.json
  sourcetype: aws:cloudtrail
  source: aws_cloudtrail
  update_timestamp: True
manual_test:None