detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Darkweb Data Breaches

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 darkweb credential leakage and data breach records from CybleVision. Extracts leaked username, email, password hashes, registration dates, and metadata using the Alerts_DarkwebDataBreaches parser. Incidents grouped per service.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1589 Gather Victim Identity Information
Initial AccessT1078 Valid Accounts
CollectionT1530 Data from Cloud Storage
ExfiltrationT1048 Exfiltration Over Alternative Protocol

Rule body kusto

id: 588a2ee5-978a-43f7-9c10-6d76d82026ef
name: "Cyble Vision Alerts Darkweb Data Breaches"
description: |
  'Detects darkweb credential leakage and data breach records from CybleVision. Extracts leaked username, email, password hashes, registration dates, and metadata using the Alerts_DarkwebDataBreaches parser. Incidents grouped per service.'
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
- InitialAccess
- Exfiltration
- Collection
relevantTechniques:
- T1589
- T1078
- T1048
- T1530
subTechniques: []
query: |
  Alerts_darkweb_data_breaches 
  | where Service == "darkweb_data_breaches" 
  | extend  MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: CybleVision Darkweb Breach for {{DB_Email}}
  alertDescriptionFormat: |
    Username {{DB_Username}} Registration date {{DB_RegistrationDate}} Breach source {{Breach_Source}}
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  LeakedEmail: DB_Email
  UserName: DB_Username
  PasswordHash: DB_PasswordHash
  DisplayName: DB_DisplayName
  RegistrationDate: DB_RegistrationDate
  BreachDate: DB_Date
  BreachSource: Breach_Source
  S3Key: DB_S3Key
  Structured: DB_Structured
  Tags: DB_Tags
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: DB_Username
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: Domain
- entityType: IP
  fieldMappings:
  - identifier: Address
    columnName: IP
- entityType: Mailbox
  fieldMappings:
  - identifier: MailboxPrimaryAddress
    columnName: DB_Email
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_darkweb_data_breaches

Stage 2: where

| where Service == "darkweb_data_breaches"

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_data_breaches 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