detection.wiki

Detection rules › Kusto

ApexOne - Multiple deny or terminate actions on single IP

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

'Detects multiple deny or terminate actions on single IP.'

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1190 Exploit Public-Facing Application

Rule body kusto

id: cd94e078-67b7-11ec-90d6-0242ac120003
name: ApexOne - Multiple deny or terminate actions on single IP
description: |
  'Detects multiple deny or terminate actions on single IP.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CefAma
    dataTypes:
      - CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
query: |
  let threshold = 5;
  TMApexOneEvent
  | where EventMessage has "Behavior Monitoring"
  | where DvcAction == 2 or DvcAction == 3
  | summarize count() by SrcIpAddr, bin(TimeGenerated, 10m)
  | where count_ > threshold
  | extend IPCustomEntity = SrcIpAddr
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
version: 1.0.3
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 5;

Stage 1: source

TMApexOneEvent

Stage 2: where

| where EventMessage has "Behavior Monitoring"

Stage 3: where

| where DvcAction == 2 or DvcAction == 3

Stage 4: summarize

| summarize count() by SrcIpAddr, bin(TimeGenerated, 10m)

Stage 5: where

| where count_ > threshold

Stage 6: extend

| extend IPCustomEntity = SrcIpAddr

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
DvcActioneq
  • 2 transforms: cased
  • 3 transforms: cased
EventMessagematch
  • Behavior Monitoring transforms: term
count_gt
  • 5 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
SrcIpAddrsummarize
IPCustomEntityextend