Detection rules › Kusto

Digital Guardian - Exfiltration to external domain

Status
available
Severity
medium
Time window
1h
Source
github.com/Azure/Azure-Sentinel

'Detects exfiltration to external domain.'

MITRE ATT&CK coverage

Rule body kusto

id: a19885c8-1e44-47e3-81df-d1d109f5c92d
name: Digital Guardian - Exfiltration to external domain
description: |
  'Detects exfiltration to external domain.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: SyslogAma
    datatypes:
      - Syslog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Exfiltration
relevantTechniques:
  - T1048
query: |
  let corp_domain = dynamic(['example.com']);     //add all corporate domains to this list
  DigitalGuardianDLPEvent
  | where NetworkApplicationProtocol =~ 'SMTP'
  | where isnotempty(inspected_document)
  | extend s_domain = extract(@'@(.*)', 1, SrcUserName)
  | extend d_domain = extract(@'@(.*)', 1, DstUserName)
  | where s_domain in~ (corp_domain)
  | where d_domain !in (corp_domain)
  | extend AccountCustomEntity = SrcUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.2
kind: Scheduled

Stages and Predicates

Parameters

let corp_domain = dynamic(['example.com']);

Stage 1: source

DigitalGuardianDLPEvent

Stage 2: where

| where NetworkApplicationProtocol =~ 'SMTP'

Stage 3: where

| where isnotempty(inspected_document)

Stage 4: extend

| extend s_domain = extract(@'@(.*)', 1, SrcUserName)

Stage 5: extend

| extend d_domain = extract(@'@(.*)', 1, DstUserName)

Stage 6: where

| where s_domain in~ (corp_domain)

Stage 7: where

| where d_domain !in (corp_domain)

Stage 8: extend

| extend AccountCustomEntity = SrcUserName

Exclusions

Top-level NOT(...) conjuncts: predicates this rule actively suppresses.

FieldKindExcluded values
d_domaineqcorp_domain

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
NetworkApplicationProtocoleq
  • SMTP
inspected_documentis_not_null
  • (no value, null check)
s_domainin
  • corp_domain

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

FieldSource
s_domainextend
d_domainextend
AccountCustomEntityextend