detection.wiki

Detection rules › Kusto

Cisco SDWAN - IPS Event Threshold

Status
available
Severity
high
Time window
3h
Group by
Classification
Source
github.com/Azure/Azure-Sentinel

'This analytic rule will monitor specific IPS event in the data.'

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1189 Drive-by Compromise, T1190 Exploit Public-Facing Application

Rule body kusto

id: dc3627c3-f9de-4f17-bfd3-ba99b64a0a67
name: Cisco SDWAN - IPS Event Threshold
description: |
  'This analytic rule will monitor specific IPS event in the data.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CiscoSDWAN
    dataTypes:
      - CiscoSyslogUTD
queryFrequency: 3h
queryPeriod: 3h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1189
query: |
  CiscoSyslogUTD 
  | where Classification == "Enter classification" 
  | summarize count() by Classification 
  | where count_ > 10
incidentConfiguration:
  createIncident: true
eventGroupingSettings:
    aggregationKind: AlertPerResult
customDetails:
  "classification": "Classification"
  "classification_count": "count_"
entityMappings:
  - entityType: Malware
    fieldMappings:
      - identifier: Name
        columnName: Classification
version: 1.0.1
kind: Scheduled

Stages and Predicates

Stage 1: source

CiscoSyslogUTD

Stage 2: where

| where Classification == "Enter classification"

Stage 3: summarize

| summarize count() by Classification

Stage 4: where

| where count_ > 10

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
Classificationeq
  • Enter classification transforms: cased
count_gt
  • 10 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
Classificationsummarize