↳ GitHub sourceAnalytics ruleHigh

Claroty - Policy violation

Description

'Detects Claroty policy violation events from ClarotyEvent when EventOriginalType or EventType contains 'Policy Violation'. Use this rule to identify policy enforcement events that may indicate unauthorized discovery or prohibited network activity. This rule expects ClarotyEvent data to be available in the workspace.'

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

CefAma

Data types

CommonSecurityLog

KQL query

Original query, unchanged.

ClarotyEvent
  | where EventOriginalType has 'Policy Violation' or EventType has 'Policy Violation'
  | project TimeGenerated, DstIpAddr, EventOriginalType, EventType
  | extend IPCustomEntity = DstIpAddr

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/Claroty/Analytic Rules/ClarotyPolicyViolation.yaml ↗
Commit: 9800e51 ↗
Source identifier: 3b22ac47-e02c-4599-a37a-57f965de17be

Additional source files 2

Solutions/Claroty/Analytic Rules/ClarotyPolicyViolation.yamlsource ↗Solutions/Claroty/Data/Solution_Claroty.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.