detection.wiki

Detection rules › Kusto

CybleVision Alerts Telegram Mentions

This is a third-party alert feed, not a detection over modeled telemetry. The vendor product raised the finding; this rule forwards it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.

Status
available
Severity
low
Time window
30m
Source
github.com/Azure/Azure-Sentinel

'Detects mentions of monitored keywords across Telegram channels and groups. Extracts message content, URLs, chat metadata, user identity, and timestamps.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1598 Phishing for Information
Resource DevelopmentT1585 Establish Accounts
Command & ControlT1102 Web Service

Rule body kusto

id: 4238f545-8b6f-4f7c-80b5-14cca2cebc99
name: CybleVision Alerts Telegram Mentions
description: |
  'Detects mentions of monitored keywords across Telegram channels and groups. Extracts message content, URLs, chat metadata, user identity, and timestamps.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
  dataTypes:
  - CybleVisionAlerts_CL
enabled: true
queryFrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
suppressionDuration: PT5H
eventGroupingSettings:
  aggregationKind: AlertPerResult
tactics:
- Reconnaissance
- ResourceDevelopment
- InitialAccess
- CommandAndControl
relevantTechniques:
- T1598
- T1585
- T1102
subTechniques: []
query: |
  Alerts_telegram_mentions 
  | where Service == "telegram_mentions" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: CybleVision Telegram Mention in {{TG_ChatTitle}}
  alertDescriptionFormat: |
    A Telegram post mentioning monitored keywords was detected. User {{TG_Username2}}. Message {{TG_Message}} URL {{TG_Urls}}\n
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  ChatID: TG_ChatID
  ChatTitle: TG_ChatTitle
  Message: TG_Message
  User: TG_Username2
  CreatedDate: TG_CreatedDate
  UpdatedDate: TG_UpdatedDate
  URLs: TG_Urls
  Tags: TG_Tags
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: TG_Username2
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: TG_Urls
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_telegram_mentions

Stage 2: where

| where Service == "telegram_mentions"

Stage 3: extend

| extend MappedSeverity = Severity

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
Serviceeq
  • telegram_mentions 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
MappedSeverityextend