detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Discord Keyword

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

'Triggers when monitored keywords or risky content appear in Discord channels. Useful for detecting data leakage, impersonation, abuse or reputational threats originating from social platforms.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1598 Phishing for Information
Initial AccessT1664 Exploitation for Initial Access

Rule body kusto

id: 601a5859-0dc2-452d-8d1e-66dc651c16d5
name: Cyble Vision Alerts Discord Keyword
description: |
  'Triggers when monitored keywords or risky content appear in Discord channels. Useful for detecting data leakage, impersonation, abuse or reputational threats originating from social platforms.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
  dataTypes:
  - CybleVisionAlerts_CL
enabled: true
queryfrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
eventGroupingSettings:
  aggregationKind: AlertPerResult
tactics:
- Reconnaissance
- InitialAccess
relevantTechniques:
- T1598
- T1664
query: |
  Alerts_discord  
  | where Service == "discord" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
  alertDetailsOverride:
  alertDisplayNameFormat: Discord Alert Risky Content by {{DC_AuthorUsername}}
  alertDescriptionFormat: |
    A monitored keyword or harmful content was detected in Discord.
    **Server:** {{DC_ServerName}}
    **Channel:** {{DC_ChannelName}}
    **Message:** {{DC_Content}}
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  DC_MessageID: DC_MessageID
  DC_Content: DC_Content
  DC_ChannelName: DC_ChannelName
  DC_ServerName: DC_ServerName
  DC_AuthorUsername: DC_AuthorUsername
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: AadUserId
    columnName: DC_AuthorID
  - identifier: Name
    columnName: DC_AuthorUsername
- entityType: CloudApplication
  fieldMappings:
  - identifier: Name
    columnName: DC_ServerName
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_discord

Stage 2: where

| where Service == "discord"

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
  • discord 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