Detection rules › Kusto
Lookout - New Threat events found.
This is a third-party alert feed, not a detection over modeled telemetry. The vendor product raised the finding; this rule forwards it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.
'Created to detect new Threat events from the data which is recently synced by Lookout Solution.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Discovery | T1057 Process Discovery |
Rule body kusto
id: 7593cc60-e294-402d-9202-279fb3c7d55f
name: Lookout - New Threat events found.
description: |
'Created to detect new Threat events from the data which is recently synced by Lookout Solution.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: LookoutAPI
dataTypes:
- Lookout_CL
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- Discovery
relevantTechniques:
- T1057
query: |
Lookout_CL
| where details_action_s == 'DETECTED' and type_s == 'THREAT'
| extend DetailsPackageName = details_packageName_s
| extend TargetPlatform = target_platform_s
| extend TargetOsVersion = target_osVersion_s
| extend Type = type_s
| extend Severity = details_severity_s
| extend Classifications = details_classifications_s
| extend Platform = target_platform_s
entityMappings:
- entityType: Host
fieldMappings:
- identifier: FullName
columnName: DetailsPackageName
- identifier: OSFamily
columnName: TargetPlatform
- identifier: OSVersion
columnName: TargetOsVersion
customDetails:
Type: Type
Severity: Severity
Classification: Classifications
Platform: Platform
version: 1.0.1
kind: Scheduled
Stages and Predicates
Stage 1: source
Lookout_CL
Stage 2: where
| where details_action_s == 'DETECTED' and type_s == 'THREAT'
Stage 3: extend (7 consecutive steps)
| extend DetailsPackageName = details_packageName_s
| extend TargetPlatform = target_platform_s
| extend TargetOsVersion = target_osVersion_s
| extend Type = type_s
| extend Severity = details_severity_s
| extend Classifications = details_classifications_s
| extend Platform = target_platform_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 |
|---|---|---|
details_action_s | eq |
|
type_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 |
|---|---|
DetailsPackageName | extend |
TargetPlatform | extend |
TargetOsVersion | extend |
Type | extend |
Severity | extend |
Classifications | extend |
Platform | extend |