Detection rules › Kusto
Claroty - Suspicious activity
Detects suspicious behavior that is generally indicative of malware.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Discovery | T1018 Remote System Discovery |
Rule body kusto
id: 99ad9f3c-304c-44c5-a61f-3a17f8b58218
name: Claroty - Suspicious activity
description: 'Detects suspicious behavior that is generally indicative of malware.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- Discovery
relevantTechniques:
- T1018
query: |
ClarotyEvent
| where EventOriginalType has 'Suspicious Activity' or EventType has 'Suspicious Activity'
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType
| extend IPCustomEntity = DstIpAddr
entityMappings:
- entityType: IP
fieldMappings:
- identifier: Address
columnName: IPCustomEntity
alertDetailsOverride:
alertDisplayNameFormat: Claroty suspicious activity on {{IPCustomEntity}}
alertDescriptionFormat: 'Claroty reported suspicious activity for {{IPCustomEntity}}. Event type: {{EventType}}. Original
type: {{EventOriginalType}}.'
customDetails:
DestinationIP: DstIpAddr
EventOriginalType: EventOriginalType
EventType: EventType
version: 1.0.4
kind: Scheduled
Stages and Predicates
Stage 1: source
ClarotyEvent
Stage 2: where
| where EventOriginalType has 'Suspicious Activity' or EventType has 'Suspicious Activity'
Stage 3: project
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType
Stage 4: extend
| extend IPCustomEntity = DstIpAddr
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 |
|---|---|---|
EventOriginalType | match |
|
EventType | match |
|
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 |
|---|---|
DstIpAddr | project |
EventOriginalType | project |
EventType | project |
TimeGenerated | project |
IPCustomEntity | extend |