↳ GitHub sourceAnalytics ruleMedium

Vaikora - Quarantine rate spike

Description

Identifies an abnormal spike in Vaikora for O365 quarantine volume for a tenant. Fires when the hourly count exceeds three times the rolling 7-day baseline, signaling a targeted campaign or model surge worth admin review.
Rule type
Scheduled
Version
1.0.0
Declared status
Available
Query frequency
1h
Query period
7d
Trigger
gt 0

Declared MITRE coverage

Declared sources

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

Connectors

Data types

KQL query

Original query, unchanged.

let baseline = VaikoraO365_Quarantine_CL
  | where TimeGenerated between (ago(7d) .. ago(1h))
  | summarize HourlyCount = count() by bin(TimeGenerated, 1h), TenantId_s
  | summarize AvgHourlyCount = avg(HourlyCount) by TenantId_s;
VaikoraO365_Quarantine_CL
| where TimeGenerated >= ago(1h)
| summarize RecentCount = count() by TenantId_s
| join kind=inner baseline on TenantId_s
| where RecentCount > (AvgHourlyCount * 3.0)
| where RecentCount >= 10
| project TimeGenerated = now(), TenantId = TenantId_s, RecentCount, AvgHourlyCount, RatioOverBaseline = (RecentCount / AvgHourlyCount)

Declared entities

CloudApplication

Related content

Links established from declared identifiers and solution manifests.

Source provenance

GitHub

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

Source identifier
3b3eb1cd-578d-4198-9b7a-bd7253b0dc9f
Additional source files 2Solutions/Vaikora-O365/Analytic Rules/Vaikora - Quarantine rate spike.yamlsource ↗Solutions/Vaikora-O365/Data/Solution_VaikoraO365.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.