Name:Monitor DNS For Brand Abuse id:24dd17b1-e2fb-4c31-878c-d4f746595bfa version:3 date:2024-10-17 author:David Dorsey, Splunk status:deprecated type:TTP Description:This search looks for DNS requests for faux domains similar to the domains that you want to have monitored for abuse. Data_source:
search:| tstats `security_content_summariesonly` values(DNS.answer) as IPs min(_time) as firstTime from datamodel=Network_Resolution by DNS.src, DNS.query | `drop_dm_object_name("DNS")` | `security_content_ctime(firstTime)`| `brand_abuse_dns` | `monitor_dns_for_brand_abuse_filter`
how_to_implement:You need to ingest data from your DNS logs. Specifically you must ingest the domain that is being queried and the IP of the host originating the request. Ideally, you should also be ingesting the answer to the query and the query type. This approach allows you to also create your own localized passive DNS capability which can aid you in future investigations. You also need to have run the search "ESCU - DNSTwist Domain Names", which creates the permutations of the domain that will be checked for. You also need the [`dnstwist`](https://gist.github.com/d1vious/c4c2aae7fa7d5cbb1f24adc5f6303ac1) custom command. known_false_positives:None at this time References: drilldown_searches:
: tags: analytic_story: - 'Brand Monitoring' asset_type:Endpoint confidence:50 impact:50 message:tbd observable: name:'query' type:'Other' - role: - 'Victim' name:'IPs' type:'IP Address' - role: - 'Attacker' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - '_time' risk_score:25 security_domain:network
