Detection rules › Kusto

Digital Guardian - Exfiltration to online fileshare

Status
available
Severity
high
Time window
30m
Group by
SrcUserName
Source
github.com/Azure/Azure-Sentinel

'Detects exfiltration to online fileshare.'

MITRE ATT&CK coverage

Rule body kusto

id: f7b6ddef-c1e9-46f0-8539-dbba7fb8a5b8
name: Digital Guardian - Exfiltration to online fileshare
description: |
  'Detects exfiltration to online fileshare.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: SyslogAma
    datatypes:
      - Syslog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Exfiltration
relevantTechniques:
  - T1048
query: |
  let threshold = 10;
  DigitalGuardianDLPEvent
  | where isnotempty(inspected_document)
  | where http_url contains 'dropbox' or http_url contains 'mega.nz'
  | summarize f = dcount(inspected_document) by SrcUserName, bin(TimeGenerated, 30m)
  | where f >= threshold
  | extend AccountCustomEntity = SrcUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.2
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 10;

Stage 1: source

DigitalGuardianDLPEvent

Stage 2: where

| where isnotempty(inspected_document)

Stage 3: where

| where http_url contains 'dropbox' or http_url contains 'mega.nz'

Stage 4: summarize

| summarize f = dcount(inspected_document) by SrcUserName, bin(TimeGenerated, 30m)
Threshold
ge 10

Stage 5: where

| where f >= threshold

Stage 6: extend

| extend AccountCustomEntity = SrcUserName

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
fge
  • 10 transforms: cased
http_urlcontains
  • dropbox
  • mega.nz
inspected_documentis_not_null
  • (no value, null check)

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
SrcUserNamesummarize
fsummarize
AccountCustomEntityextend