↳ GitHub sourceAnalytics ruleMedium

BitSight - diligence risk category detected

Description

'Rule helps to detect whenever there is a diligence risk category found in BitSight.'
Rule type
Scheduled
Version
1.0.2
Declared status
Available
Query frequency
1d
Query period
24h
Trigger
GreaterThan 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 timeframe = 24h;
BitSightFindingsData
| where ingestion_time() > ago(timeframe)
| where RiskCategory == "Diligence"
| extend Severity = toreal(Severity)
| extend Severity = case( Severity <= 6.9 and Severity >= 4.0, "Low",
                          Severity <= 8.9 and Severity >= 7.0, "Medium",
                          Severity <= 10.0 and Severity >= 9.0, "High",
                          "Informational")
| project FirstSeen, CompanyName, Severity, RiskCategory, TemporaryId, RiskVector

Declared entities

Malware

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
161ed3ac-b242-4b13-8c6b-58716e5e9972
Additional source files 2Solutions/BitSight/Analytic Rules/BitSightDiligenceRiskCategoryDetected.yamlsource ↗Solutions/BitSight/Data/Solution_BitSight.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.