↳ GitHub sourceAnalytics ruleHigh

Imperva - Critical severity event not blocked

View on GitHub ↗Original file ↗

Description

'Detects when critical severity event was not blocked.'

Rule type: Scheduled
Version: 1.0.1
Declared status: Available
Query frequency: 10m
Query period: 10m
Trigger: gt 0

Declared MITRE coverage

Declared sources

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

Connectors

ImpervaWAFCloudAPI

Data types

ImpervaWAFCloud

KQL query

Original query, unchanged.

ImpervaWAFCloud
| where EventSeverity =~ 'CRITICAL'
| where DvcAction !startswith 'REQ_BLOCKED' or DvcAction !startswith 'REQ_BAD_'
| extend IPCustomEntity = SrcIpAddr

Declared entities

Source provenance

GitHub

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

File: Solutions/ImpervaCloudWAF/Analytic Rules/ImpervaAttackNotBlocked.yaml ↗
Commit: 629d1d3 ↗
Source identifier: 4d365217-f96a-437c-9c57-53594fa261c3

Additional source files 2

Solutions/ImpervaCloudWAF/Analytic Rules/ImpervaAttackNotBlocked.yamlsource ↗Solutions/ImpervaCloudWAF/Data/Solution_ImpervaCloudWAF.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.