Detect DNS Query to Decommissioned S3 Bucket

 Original Source: [splunk source]
Name:Detect DNS Query to Decommissioned S3 Bucket
id:2f1c5fd1-4b8a-4f5d-a0e9-7d6a8e2f5e1e
version:6
date:None
author:Jose Hernandez, Splunk
status:experimental
type:Anomaly
Description:This detection identifies DNS queries to domains that match previously decommissioned S3 buckets. This activity is significant because attackers may attempt to recreate deleted S3 buckets that were previously public to hijack them for malicious purposes. If successful, this could allow attackers to host malicious content or exfiltrate data through compromised bucket names that may still be referenced by legitimate applications.
Data_source:
  • -Sysmon EventID 22
search:| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Network_Resolution
WHERE DNS.message_type=QUERY
BY DNS.answer DNS.answer_count DNS.query
DNS.query_count DNS.reply_code_id DNS.src
DNS.vendor_product
| `drop_dm_object_name("DNS")`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| eval bucket_domain = lower(query)
| lookup decommissioned_buckets bucketName as bucket_domain OUTPUT bucketName as match
| where isnotnull(match)
| `detect_dns_query_to_decommissioned_s3_bucket_filter`


how_to_implement:To successfully implement this detection, you need to be ingesting DNS query logs and have them mapped to the Network_Resolution data model. Additionally, ensure that the baseline search "Baseline Of Open S3 Bucket Decommissioning" is running and populating the decommissioned_buckets KVstore lookup.
known_false_positives:Some applications or scripts may continue to reference old S3 bucket names after they have been decommissioned. These should be investigated and updated to prevent potential security risks.
References:
  -https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html
  -https://labs.watchtowr.com/8-million-requests-later-we-made-the-solarwinds-supply-chain-attack-look-amateur/
drilldown_searches:
 name:'DNS Activity for Host'
 search:'| from datamodel:Network_Resolution | search src="$src$"'
 earliest_offset:'-7d@d'
 latest_offset:'now'
analytic_story:['AWS S3 Bucket Security Monitoring', 'Data Destruction']

asset_type:Network

mitre_attack_id:['T1485']

product:['Splunk Enterprise', 'Splunk Enterprise Security', 'Splunk Cloud']

category:network

security_domain:network

tags:

tests:
 name:'Baseline Dataset Test'
 attack_data:
  data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1485/decommissioned_buckets/cloudtrail.json
  source: cloudtrail
  sourcetype: aws:cloudtrail
 test_type:'experimental'
 description:'This test is a legacy experimental test and may not be accurate.'
 name:'True Positive Test'
 attack_data:
  data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1485/decommissioned_buckets/dns.log
  source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
  sourcetype: XmlWinEventLog
 test_type:'experimental'
 description:'This test is a legacy experimental test and may not be accurate.'
manual_test:None