detection.wiki

Detection rules › Kusto

CybleVision Alerts Cyber Crime Forum Alerts

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 discussions, marketplace posts, threat actor activity, and intelligence mentions from cybercrime forums. Extracts discussion metadata, topic details, URLs, emails, phone numbers, and content using Alerts_CyberCrimeForums parser.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1589 Gather Victim Identity Information, T1598 Phishing for Information
Resource DevelopmentT1585 Establish Accounts
ExfiltrationT1646 Exfiltration Over C2 Channel

Rule body kusto

id: b78c4641-cc16-48e0-9d05-c9b36a55d214
name: CybleVision Alerts Cyber Crime Forum Alerts
description: |
  'Detects discussions, marketplace posts, threat actor activity, and intelligence mentions from cybercrime forums. Extracts discussion metadata, topic details, URLs, emails, phone numbers, and content using Alerts_CyberCrimeForums parser.'
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
- Exfiltration
relevantTechniques:
- T1598
- T1585
- T1589
- T1646
subTechniques: []
query: |
  Alerts_cyber_crime_forums 
  | where Service == "cyber_crime_forums" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: CybleVision Forum Mention {{CF_TopicName}}
  alertDescriptionFormat: |
    A mention was detected on a cybercrime forum. Source {{CF_SourceName}} By {{CF_DiscussionBy}} Content {{CF_Content}}
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  TopicName: CF_TopicName
  DiscussionBy: CF_DiscussionBy
  DiscussionDate: CF_DiscussionDate
  Content: CF_Content
  Phones: CF_Phones
  TopicURL: CF_TopicURL
  TopicID: CF_TopicID
  TopicCreatedBy: CF_TopicCreatedBy
  Reputation: CF_Reputation
  Likes: CF_Likes
  Tags: CF_Tags
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: CF_Emails
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: CF_Urls
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: CF_SourceName
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_cyber_crime_forums

Stage 2: where

| where Service == "cyber_crime_forums"

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