Detection rules › Kusto
Claroty - Suspicious file transfer
Detects Claroty events where EventOriginalType or EventType contains Suspicious File Transfer and maps the destination IP as the primary entity for triage.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Discovery | T1018 Remote System Discovery |
| Exfiltration | T1020 Automated Exfiltration |
Rule body kusto
id: 5cf35bad-677f-4c23-8927-1611e7ff6f28
name: Claroty - Suspicious file transfer
description: 'Detects Claroty events where EventOriginalType or EventType contains Suspicious File Transfer and maps the destination
IP as the primary entity for triage.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- Discovery
- Exfiltration
relevantTechniques:
- T1018
- T1020
query: |
ClarotyEvent
| where EventOriginalType has 'Suspicious File Transfer' or EventType has 'Suspicious File Transfer'
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType
| extend IPCustomEntity = DstIpAddr
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType, IPCustomEntity
entityMappings:
- entityType: IP
fieldMappings:
- identifier: Address
columnName: IPCustomEntity
alertDetailsOverride:
alertDisplayNameFormat: Claroty suspicious file transfer to {{DstIpAddr}}
alertDescriptionFormat: Claroty flagged suspicious file transfer activity to {{DstIpAddr}} using event type {{EventType}}
customDetails:
EventOriginalType: EventOriginalType
EventType: EventType
version: 1.0.4
kind: Scheduled
Stages and Predicates
Stage 1: source
ClarotyEvent
Stage 2: where
| where EventOriginalType has 'Suspicious File Transfer' or EventType has 'Suspicious File Transfer'
Stage 3: project
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType
Stage 4: extend
| extend IPCustomEntity = DstIpAddr
Stage 5: project
| project TimeGenerated, DstIpAddr, EventOriginalType, EventType, IPCustomEntity
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 |
IPCustomEntity | project |
TimeGenerated | project |