Detection: Detect DNS Data Exfiltration using pretrained model in DSDL

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detection is deprecated as these do not work with the latest Splunk AI Toolkit(5.7.0) and Python for Scientific Computing for Linux 64-bit(4.3.0).

Removed in version: 5.26.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Description

The following analytic identifies potential DNS data exfiltration using a pre-trained deep learning model. It leverages DNS request data from the Network Resolution datamodel and computes features from past events between the same source and domain. The model generates a probability score (pred_is_exfiltration_proba) indicating the likelihood of data exfiltration. This activity is significant as DNS tunneling can be used by attackers to covertly exfiltrate sensitive data. If confirmed malicious, this could lead to unauthorized data access and potential data breaches, compromising the organization's security posture.

 1
 2| tstats `security_content_summariesonly` count FROM datamodel=Network_Resolution
 3  BY DNS.src _time DNS.query
 4
 5| `drop_dm_object_name("DNS")`
 6
 7| sort - _time,src, query
 8
 9| streamstats count as rank
10  BY src query
11
12| where rank < 10
13
14| table src,query,rank,_time
15
16| apply detect_dns_data_exfiltration_using_pretrained_model_in_dsdl
17
18| table src,_time,query,rank,pred_is_dns_data_exfiltration_proba,pred_is_dns_data_exfiltration
19
20| where rank == 1
21
22| rename pred_is_dns_data_exfiltration_proba as is_exfiltration_score
23
24| rename pred_is_dns_data_exfiltration as is_exfiltration
25
26| where is_exfiltration_score > 0.5
27
28| `security_content_ctime(_time)`
29
30| table src, _time,query,is_exfiltration_score,is_exfiltration
31
32| `detect_dns_data_exfiltration_using_pretrained_model_in_dsdl_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name Value
security_content_summariesonly summariesonly=summariesonly_config allow_old_summaries=oldsummaries_config fillnull_value=fillnull_config``
detect_dns_data_exfiltration_using_pretrained_model_in_dsdl_filter ``
detect_dns_data_exfiltration_using_pretrained_model_in_dsdl_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1048.003 Exfiltration Over Unencrypted Non-C2 Protocol Exfiltration

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting Value
Disabled true
Cron Schedule N/A
Earliest Time N/A
Latest Time N/A
Schedule Window N/A
Creates Finding (Notable) No
Creates Intermediate Finding (Risk Event) No
Anomaly detections generate Intermediate Findings (Risk Events). They do not generate a Finding (Notable) directly.

Implementation

Steps to deploy detect DNS data exfiltration model into Splunk App DSDL. This detection depends on the Splunk app for Data Science and Deep Learning which can be found here - https://splunkbase.splunk.com/app/4607/ and the Network Resolution datamodel which can be found here - https://splunkbase.splunk.com/app/1621/. The detection uses a pre-trained deep learning model that needs to be deployed in DSDL app. Follow the steps for deployment here - https://github.com/splunk/security_content/wiki/How-to-deploy-pre-trained-Deep-Learning-models-for-ESCU.

  • Download the artifacts .tar.gz file from the link - https://seal.splunkresearch.com/detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.tar.gz Download the detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.ipynb Jupyter notebook from https://github.com/splunk/security_content/notebooks
  • Login to the Jupyter Lab assigned for detect_dns_data_exfiltration_using_pretrained_model_in_dsdl container. This container should be listed on Containers page for DSDL app.
  • Below steps need to be followed inside Jupyter lab
  • Upload the detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.tar.gz file into app/model/data path using the upload option in the jupyter notebook.
  • Untar the artifact detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.tar.gz using tar -xf app/model/data/detect_suspicious_dns_txt_records_using_pretrained_model_in_dsdl.tar.gz -C app/model/data
  • Upload detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.pynb into Jupyter lab notebooks folder using the upload option in Jupyter lab
  • Save the notebook using the save option in jupyter notebook.
  • Upload detect_dns_data_exfiltration_using_pretrained_model_in_dsdl.json into notebooks/data folder.

Known False Positives

False positives may be present if DNS data exfiltration request look very similar to benign DNS requests.

Associated Analytic Story

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Not Applicable N/A N/A N/A
Unit Not Applicable N/A N/A N/A
Integration Not Applicable N/A N/A N/A

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: 8