detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Suspicious Domain

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

'This Rule generates Cyble Vision Alerts for Service - Suspicious Domain severity LOW'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1595 Active Scanning

Rule body kusto

id: c56fcb78-b708-4a92-bad4-d50b1e15c42c
name: Cyble Vision Alerts Suspicious Domain
description: |
  'This Rule generates Cyble Vision Alerts for Service - Suspicious Domain severity LOW'
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
relevantTechniques:
- T1595
subTechniques: []
query: |
  Alerts_suspicious_domains 
  | where Service == "suspicious_domain" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: Suspicious Domain Detected {{Domain}}  {{Status}}
  alertDescriptionFormat: |
    Suspicious Domain detected for {{Domain}} with {{Status}}
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  Domain: Domain
  Keyword: KeywordName
  Score: SD_Score
  LiveStatus: SD_IsLive
  RegistrationDate: SD_RegistrationDate
  LastLiveCheck: SD_LastLiveCheck
  Screenshot: SD_ScreenshotURL
  A_Records: A_Records
  NS_Records: NS_Records
  MX_Records: MX_Records
entityMappings:
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: Domain
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_suspicious_domains

Stage 2: where

| where Service == "suspicious_domain"

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