detection.wiki

Detection rules › Kusto

Infoblox - Data Exfiltration Attack

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

'Data exfiltration attack detected by Infoblox Threat Insight. Customize query count, scheduling, responses and more. This rule depends on a parser based on a Kusto Function to work as expected called InfobloxCDC.'

MITRE ATT&CK coverage

TacticTechniques
ImpactT1498 Network Denial of Service, T1565 Data Manipulation

Rule body kusto

id: 8db2b374-0337-49bd-94c9-cfbf8e5d83ad
name: Infoblox - Data Exfiltration Attack
description: |
  'Data exfiltration attack detected by Infoblox Threat Insight. Customize query count, scheduling, responses and more. This rule depends on a parser based on a Kusto Function to work as expected called [**InfobloxCDC**](https://aka.ms/sentinel-InfobloxCloudDataConnector-parser).'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: CefAma
    dataTypes:
      - CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Impact
relevantTechniques:
  - T1498
  - T1565
query: |
  let threshold = 1;
  InfobloxCDC
  | where DeviceEventClassID has_cs "RPZ"
  | where InfobloxB1FeedName == "Threat Insight - Data Exfiltration"
  | summarize count() by SourceIP
  | where count_ > threshold
  | join kind=innerunique (InfobloxCDC
    | where DeviceEventClassID has_cs "RPZ"
    | where InfobloxB1FeedName == "Threat Insight - Data Exfiltration"
    ) on SourceIP
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: SourceIP
  - entityType: Host
    fieldMappings:
      - identifier: HostName
        columnName: DeviceName
      - identifier: OSVersion
        columnName: InfobloxB1SrcOSVersion
      - identifier: FullName
        columnName: SourceUserName
  - entityType: Malware
    fieldMappings:
      - identifier: Name
        columnName: InfobloxB1FeedName
      - identifier: Category
        columnName: InfobloxB1FeedName
customDetails:
  SourceMACAddress: SourceMACAddress
  InfobloxB1FeedName: InfobloxB1FeedName
  InfobloxB1Network: InfobloxB1Network
  InfobloxB1Action: InfobloxB1PolicyAction
  InfobloxB1PolicyName: InfobloxB1PolicyName
eventGroupingSettings:
  aggregationKind: SingleAlert
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: true
    reopenClosedIncident: true
    lookbackDuration: 7d
    matchingMethod: AllEntities
version: 1.0.3
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 1;

Stage 1: source

InfobloxCDC

Stage 2: where

| where DeviceEventClassID has_cs "RPZ"

Stage 3: where

| where InfobloxB1FeedName == "Threat Insight - Data Exfiltration"

Stage 4: summarize

| summarize count() by SourceIP

Stage 5: where

| where count_ > threshold

Stage 6: join

| join kind=innerunique (InfobloxCDC
  | where DeviceEventClassID has_cs "RPZ"
  | where InfobloxB1FeedName == "Threat Insight - Data Exfiltration"
  ) on SourceIP

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
DeviceEventClassIDmatch
  • RPZ transforms: cased, term
InfobloxB1FeedNameeq
  • Threat Insight - Data Exfiltration transforms: cased
count_gt
  • 1 transforms: cased

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
SourceIPsummarize