Detection rules › Kusto
High Urgency IONIX Action Items
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.
'This query creates an alert for active IONIX Action Items with high urgency (9-10). Urgency can be altered using the "min_urgency" variable in the query.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1190 Exploit Public-Facing Application, T1195 Supply Chain Compromise |
Rule body kusto
id: 8e0403b1-07f8-4865-b2e9-74d1e83200a4
name: High Urgency IONIX Action Items
description: |
'This query creates an alert for active IONIX Action Items with high urgency (9-10).
Urgency can be altered using the "min_urgency" variable in the query.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: CyberpionSecurityLogs
dataTypes:
- CyberpionActionItems_CL
queryFrequency: 1d
queryPeriod: 14d
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1190
- T1195
query: |
let timeframe = 14d;
let min_urgency = 9;
CyberpionActionItems_CL
| where TimeGenerated > ago(timeframe)
| summarize arg_max(TimeGenerated, *) by id_s
| where is_open_b == true
| where urgency_d >= min_urgency
| extend timestamp = opening_datetime_t
| extend DNSCustomEntity = host_s
entityMappings:
- entityType: DNS
fieldMappings:
- identifier: DomainName
columnName: DNSCustomEntity
version: 1.0.2
kind: Scheduled
Stages and Predicates
Parameters
let timeframe = 14d;
let min_urgency = 9;
Stage 1: source
CyberpionActionItems_CL
Stage 2: where
| where TimeGenerated > ago(timeframe)
Stage 3: summarize
| summarize arg_max(TimeGenerated, *) by id_s
Stage 4: where
| where is_open_b == true
Stage 5: where
| where urgency_d >= min_urgency
Stage 6: extend
| extend timestamp = opening_datetime_t
Stage 7: extend
| extend DNSCustomEntity = host_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.
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 |
|---|---|
id_s | summarize |
timestamp | extend |
DNSCustomEntity | extend |