detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Darkweb Ransomware Leak

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

'A ransomware threat actor has posted victim data on the dark web. This alert includes leaked documents, threat actor name, victim organization, timestamps, and extracted text content for SOC triage.'

MITRE ATT&CK coverage

TacticTechniques
ImpactT1486 Data Encrypted for Impact, T1657 Financial Theft

Rule body kusto

id: 6deaf986-a25b-47b4-afbe-667901aa313b
name: Cyble Vision Alerts Darkweb Ransomware Leak
description: |
  'A ransomware threat actor has posted victim data on the dark web. This alert includes leaked documents, threat actor name, victim organization, timestamps, and extracted text content for SOC triage.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
  dataTypes:
  - CybleVisionAlerts_CL
enabled: true
queryfrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
eventGroupingSettings:
  aggregationKind: AlertPerResult
tactics:
- Impact
- Exfiltration
- Reconnaissance
relevantTechniques:
- T1486
- T1657
query: |
  Alerts_darkweb_ransomware
  | where Service == "darkweb_ransomware"
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: Darkweb Ransomware Leak {{Victim}} by {{ThreatActor}}
  alertDescriptionFormat: |
    A ransomware group has posted data belonging on the dark web. A document leak has been detected, including text extracted from the file.
    **Victim:** {{Victim}}
    **Threat Actor:** {{ThreatActor}}
    **Leaked File:** {{FileName}}
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  Victim: DW_Victim_Nested
  ThreatActor: DW_ThreatActor_Nested
  CompanyLeak: DW_CompanyLeak
  DocumentYear: DW_DocumentYear
  FileName: DW_FileName
  OriginalFileName: DW_OriginalFileName
  ContentText: DW_Text
  UpdatedDate: DW_UpdatedDate_Nested
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: DW_Victim_Nested
  - identifier: FullName
    columnName: DW_ThreatActor_Nested
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_darkweb_ransomware

Stage 2: where

| where Service == "darkweb_ransomware"

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