Name:Excessive DNS Failures id:104658f4-afdc-499e-9719-17243f9826f1 version:5 date:2024-10-17 author:bowesmana, Bhavin Patel, Splunk status:experimental type:Anomaly Description:The following analytic identifies excessive DNS query failures by counting DNS responses that do not indicate success, triggering when there are more than 50 occurrences. It leverages the Network_Resolution data model, focusing on DNS reply codes that signify errors. This activity is significant because a high number of DNS failures can indicate potential network misconfigurations, DNS poisoning attempts, or malware communication issues. If confirmed malicious, this activity could lead to disrupted network services, hindered communication, or data exfiltration attempts by attackers. Data_source:
search:| tstats `security_content_summariesonly` count from datamodel=Network_Resolution where nodename=DNS "DNS.reply_code"!="No Error" "DNS.reply_code"!="NoError" DNS.reply_code!="unknown" NOT "DNS.query"="*.arpa" "DNS.query"="*.*" by "DNS.src" "DNS.query" "DNS.reply_code" | `drop_dm_object_name("DNS")` | lookup cim_corporate_web_domain_lookup domain as query OUTPUT domain | where isnull(domain) | lookup update=true alexa_lookup_by_str domain as query OUTPUT rank | where isnull(rank) | eventstats max(count) as mc by src reply_code | eval mode_query=if(count=mc, query, null()) | stats sum(count) as count values(mode_query) as query values(mc) as max_query_count by src reply_code | where count>50 | `get_asset(src)` | `excessive_dns_failures_filter`
how_to_implement:To successfully implement this search you must ensure that DNS data is populating the Network_Resolution data model. known_false_positives:It is possible legitimate traffic can trigger this rule. Please investigate as appropriate. The threshold for generating an event can also be customized to better suit your environment. References: drilldown_searches:
: tags: analytic_story: - 'Suspicious DNS Traffic' - 'Command And Control' asset_type:Endpoint confidence:50 impact:50 message:Excessive DNS failures detected on $src$ mitre_attack_id: - 'T1071.004' - 'T1071' observable: name:'src' type:'Hostname' - role: - 'Victim' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - '_time' - 'DNS.query' - 'DNS.reply_code' - 'DNS.src' risk_score:25 security_domain:network
