Detection rules › Kusto
Mimecast Targeted Threat Protection - URL Protect
'Detects malicious scan results and actions which are not allowed.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T0865 Spearphishing Attachment |
Rule body kusto
id: 952faed4-c6a6-4873-aeb9-b348e9ce5aba
name: Mimecast Targeted Threat Protection - URL Protect
description: |
'Detects malicious scan results and actions which are not allowed.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: MimecastTTPAPI
dataTypes:
- MimecastTTPUrl
queryFrequency: 30m
queryPeriod: 30m
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
- Discovery
relevantTechniques:
- T0865
query: |
MimecastTTPUrl
| where ['Scan Result'] == "malicious" and Action != "allow"
| extend From_User_EmailAddress = ['From User Email Address'],MessageID = ['Message ID'] , User_EmailAddress = ['User Email Address'], SendingIP = ['Sending IP']
suppressionDuration: 5h
suppressionEnabled: false
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: true
reopenClosedIncident: false
lookbackDuration: P7D
matchingMethod: AllEntities
eventGroupingSettings:
aggregationKind: AlertPerResult
entityMappings:
- entityType: IP
fieldMappings:
- identifier: Address
columnName: SendingIP
- entityType: MailMessage
fieldMappings:
- identifier: Sender
columnName: From_User_EmailAddress
- identifier: InternetMessageId
columnName: MessageID
- identifier: Recipient
columnName: User_EmailAddress
- entityType: URL
fieldMappings:
- identifier: Url
columnName: Url
version: 1.0.1
kind: Scheduled
Stages and Predicates
Stage 1: source
MimecastTTPUrl
Stage 2: where
| where ['Scan Result'] == "malicious" and Action != "allow"
Stage 3: extend
| extend From_User_EmailAddress = ['From User Email Address'],MessageID = ['Message ID'] , User_EmailAddress = ['User Email Address'], SendingIP = ['Sending IP']
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 |
|---|---|---|
Action | ne |
|
Scan Result | 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 |
|---|---|
From_User_EmailAddress | extend |
MessageID | extend |
SendingIP | extend |
User_EmailAddress | extend |