Potential DGA Activity

Setup

The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.

DGA Detection Setup

The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.

Prerequisite Requirements:

The following steps should be executed to install assets associated with the DGA Detection integration:

Ingest Pipeline Setup

Before you can enable this rule, you’ll need to enrich DNS events with predictions from the Supervised DGA Detection model. This is done via the ingest pipeline named <package_version>-ml_dga_ingest_pipeline installed with the DGA Detection package. - If using an Elastic Beat such as Packetbeat, add the DGA ingest pipeline to it by adding a simple configuration setting to packetbeat.yml. - If adding the DGA ingest pipeline to an existing pipeline, use a pipeline processor.

Adding Custom Mappings

{
  "properties": {
    "ml_is_dga": {
      "properties": {
        "malicious_prediction": {
          "type": "long"
        },
        "malicious_probability": {
          "type": "float"
        }
      }
    }
  }
}

Anomaly Detection Setup

Before you can enable this rule, you’ll need to enable the corresponding Anomaly Detection job. - Go to the Kibana homepage. Under Analytics, click Machine Learning. - Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched DNS events. For example, this would be logs-endpoint.events.* if you used Elastic Defend to collect events, or logs-network_traffic.* if you used Network Packet Capture. - If the selected Data View contains events that match the query in this configuration file, you will see a card for DGA under "Use preconfigured jobs". - Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.

Framework: MITRE ATT&CK^TM