↳ GitHub sourceAnalytics ruleMedium

BitSight - new breach found

View on GitHub ↗Original file ↗

Description

'Rule helps to detect a new breach generated in BitSight.'

Rule type: Scheduled
Version: 1.0.1
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

BitSight

Data types

BitSightBreaches

KQL query

Original query, unchanged.

let timeframe = 24h;
BitSightBreaches
| where ingestion_time() > ago(timeframe)
| extend Severity = toreal(Severity)
| extend Severity = case( Severity == 1, "Low",
                          Severity == 2, "Medium",
                          Severity == 3, "High",
                          "Informational")
| project DateCreated, Companyname, Severity, PreviwURL, GUID

Declared entities

URL

Source provenance

GitHub

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

File: Solutions/BitSight/Analytic Rules/BitSightNewBreachFound.yaml ↗
Commit: 9800e51 ↗
Source identifier: a5526ba9-5997-47c6-bf2e-60a08b681e9b

Additional source files 2

Solutions/BitSight/Analytic Rules/BitSightNewBreachFound.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.