↳ GitHub sourceAnalytics ruleMedium

Infoblox - High Threat Level Query Not Blocked Detected

Description

'At least 1 high threat level query generated by single host in 1 hour that is not blocked or redirected. Customize query count, scheduling, responses and more. This rule depends on a parser based on a Kusto Function to work as expected called [**InfobloxCDC**](https://aka.ms/sentinel-InfobloxCloudDataConnector-parser).'
Rule type
Scheduled
Version
1.0.4
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

Data types

KQL query

Original query, unchanged.

let threshold = 1;
InfobloxCDC
| where DeviceEventClassID has_cs "RPZ"
| where ThreatLevel_Score >=80
| where InfobloxB1PolicyAction == "Log" or SimplifiedDeviceAction == "PASSTHRU"
| summarize count() by SourceIP
| where count_ > threshold
| join kind=inner (InfobloxCDC
  | where DeviceEventClassID has_cs "RPZ"
  | where ThreatLevel_Score >=80
  | where InfobloxB1PolicyAction == "Log" or SimplifiedDeviceAction == "PASSTHRU"
  ) on SourceIP

Declared entities

IPHostDNSMalware

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
dc7af829-d716-4774-9d6f-03d9aa7c27a4
Additional source files 2Solutions/Infoblox Cloud Data Connector/Analytic Rules/Infoblox-HighThreatLevelQueryNotBlockedDetected.yamlsource ↗Solutions/Infoblox Cloud Data Connector/Data/Solution_Infoblox.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.