detection.wiki

Detection rules › Kusto

Cisco SE - Malware outbreak

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

'Detects possible malware outbreak.'

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1133 External Remote Services, T1190 Exploit Public-Facing Application

Rule body kusto

id: 225053c7-085b-4fca-a18f-c367f9228bf3
name: Cisco SE - Malware outbreak
description: |
  'Detects possible malware outbreak.'
severity: High
requiredDataConnectors:
  - connectorId: CiscoSecureEndpoint
    dataTypes:
      - CiscoSecureEndpoint
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
status: Available
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  let threshold = 2;
  CiscoSecureEndpoint
  | where isnotempty(ThreatName)
  | summarize infected = makeset(DstHostname) by ThreatName, bin(TimeGenerated, 10m)
  | where array_length(infected) >= threshold
  | extend MalwareCustomEntity = ThreatName
entityMappings:
  - entityType: Malware
    fieldMappings:
      - identifier: Name
        columnName: MalwareCustomEntity
version: 1.0.0
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 2;

Stage 1: source

CiscoSecureEndpoint

Stage 2: where

| where isnotempty(ThreatName)

Stage 3: summarize

| summarize infected = makeset(DstHostname) by ThreatName, bin(TimeGenerated, 10m)

Stage 4: where

| where array_length(infected) >= threshold

Stage 5: extend

| extend MalwareCustomEntity = ThreatName

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
ThreatNameis_not_null
  • (no value, null check)
infectedge
  • 2 transforms: array_length corpus 2 (kusto 2)

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
ThreatNamesummarize
infectedsummarize
MalwareCustomEntityextend