Detection rules › Kusto

Cisco SE - Multiple malware on host

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

'This rule triggers when multiple malware where detected on host.'

MITRE ATT&CK coverage

Rule body kusto

id: b13489d7-feb1-4ad3-9a4c-09f6d64448fd
name: Cisco SE - Multiple malware on host
description: |
  'This rule triggers when multiple malware where detected on host.'
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(ThreatName) by DstHostname, bin(TimeGenerated, 10m)
  | where array_length(infected) >= threshold
  | extend HostCustomEntity = DstHostname
entityMappings:
  - entityType: Host
    fieldMappings:
      - identifier: HostName
        columnName: HostCustomEntity
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(ThreatName) by DstHostname, bin(TimeGenerated, 10m)

Stage 4: where

| where array_length(infected) >= threshold

Stage 5: extend

| extend HostCustomEntity = DstHostname

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
DstHostnamesummarize
infectedsummarize
HostCustomEntityextend