↳ GitHub sourceAnalytics ruleHigh

Device Alert Surge

Description

'Triggers an incident when a device generates 5 or more Medium or High severity alerts, indicating potential compromise.'

Rule type: Scheduled
Version: 1.0.0
Declared status: Available
Query frequency: 1h
Query period: 1h
Trigger: gt 0

Declared MITRE coverage

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Connectors

MorphisecCCF

Data types

Morphisec

KQL query

Original query, unchanged.

MorphisecAlerts_CL
| where threatMessageArrivalTime >= ago(1h)
| where attackSeverity in ("HIGH", "MEDIUM")
| summarize arg_max(threatMessageArrivalTime, *) by id
| summarize AlertCount = dcount(id) by hostname
| where AlertCount >= 5

Declared entities

Host

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

File: Solutions/Morphisec/Analytic Rules/MorphisecDeviceAlertSurge.yaml ↗
Commit: 9800e51 ↗
Source identifier: 5c8e1f2e-9d6b-4f4a-8f3e-123456789abc

Additional source files 2

Solutions/Morphisec/Analytic Rules/MorphisecDeviceAlertSurge.yamlsource ↗Solutions/Morphisec/Data/Solution_Morphisec.jsonsolution-membership ↗

GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.