Detection rules › Kusto
Known Malware Detected
'This creates an incident when a known Malware is detected on a endpoint managed by a Carbon Black.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Execution | T1204 User Execution |
Rule body kusto
id: 9f86885f-f31f-4e66-a39d-352771ee789e
name: Known Malware Detected
description: |
'This creates an incident when a known Malware is detected on a endpoint managed by a Carbon Black.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: VMwareCarbonBlack
dataTypes:
- CarbonBlackEvents_CL
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- Execution
relevantTechniques:
- T1204
query: |
CarbonBlackEvents_CL
| extend eventTime = datetime(1970-01-01) + tolong(eventTime_d/1000) * 1sec
| where targetApp_effectiveReputation_s =~ "KNOWN_MALWARE"
| summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated), count() by eventTime, deviceDetails_deviceName_s, deviceDetails_deviceIpAddress_s, processDetails_fullUserName_s, processDetails_targetName_s
entityMappings:
- entityType: Account
fieldMappings:
- identifier: FullName
columnName: processDetails_fullUserName_s
- entityType: Host
fieldMappings:
- identifier: FullName
columnName: deviceDetails_deviceName_s
- entityType: IP
fieldMappings:
- identifier: Address
columnName: deviceDetails_deviceIpAddress_s
version: 1.0.2
kind: Scheduled
Stages and Predicates
Stage 1: source
CarbonBlackEvents_CL
Stage 2: extend
| extend eventTime = datetime(1970-01-01) + tolong(eventTime_d/1000) * 1sec
Stage 3: where
| where targetApp_effectiveReputation_s =~ "KNOWN_MALWARE"
Stage 4: summarize
| summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated), count() by eventTime, deviceDetails_deviceName_s, deviceDetails_deviceIpAddress_s, processDetails_fullUserName_s, processDetails_targetName_s
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.
| Field | Kind | Values |
|---|---|---|
targetApp_effectiveReputation_s | eq |
|
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.
| Field | Source |
|---|---|
EndTime | summarize |
StartTime | summarize |
deviceDetails_deviceIpAddress_s | summarize |
deviceDetails_deviceName_s | summarize |
eventTime | summarize |
processDetails_fullUserName_s | summarize |
processDetails_targetName_s | summarize |