detection.wiki

Detection rules › Kusto

Snowflake - Abnormal query process time

Status
available
Severity
medium
Time window
1h
Source
github.com/Azure/Azure-Sentinel

'Detects query with abnormal proccess time.'

MITRE ATT&CK coverage

TacticTechniques
ImpactT1499 Endpoint Denial of Service

Rule body kusto

id: 1376f5e5-855a-4f88-8591-19eba4575a0f
name: Snowflake - Abnormal query process time
description: |
  'Detects query with abnormal proccess time.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: Snowflake
    dataTypes:
      - Snowflake
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Impact
relevantTechniques:
  - T1499
query: |
  let threshold = 10000;
  Snowflake
  | where QueryTotalElapsedTime > threshold
  | extend AccountCustomEntity = TargetUsername
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 10000;

Stage 1: source

Snowflake

Stage 2: where

| where QueryTotalElapsedTime > threshold

Stage 3: extend

| extend AccountCustomEntity = TargetUsername

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
QueryTotalElapsedTimegt
  • 10000 transforms: cased

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

FieldSource
AccountCustomEntityextend