detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Phishing Domain Detected

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

'Cyble detected a phishing website impersonating a monitored brand. This alert provides landing page, host, screenshot, status and configured keyword for SOC triage.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1598.003 Phishing for Information: Spearphishing Link

Rule body kusto

id: eb1d45fe-1b19-4b54-b146-971f282a6fd9
name: Cyble Vision Alerts Phishing Domain Detected
description: |
  'Cyble detected a phishing website impersonating a monitored brand. This alert provides landing page, host, screenshot, status and configured keyword 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:
- Reconnaissance
relevantTechniques:
- T1598.003
query: |
  Alerts_phishing 
  | where Service == "phishing"
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
  alertDetailsOverride:
  alertDisplayNameFormat: Phishing Detected {{PH_PhishingKeyword}} on {{PH_DomainName}}
  alertDescriptionFormat: |
    A phishing landing page impersonating {{PH_Brand}}.
    Host {{PH_HostName}}
    Live {{PH_IsLive}}
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  PH_DomainName: PH_DomainName
  PH_Top_Domain: PH_Top_Domain
  PH_PhishingKeyword: PH_PhishingKeyword
  PH_PhishingStatus: PH_PhishingStatus
  PH_HostName: PH_HostName
  PH_Title: PH_Title
  PH_ScreenshotURL: PH_ScreenshotURL
  PH_IsLive: PH_IsLive
  PH_DetectedAt: PH_DetectedAt
  PH_LastLiveOn: PH_LastLiveOn
  PH_AWSObjectName: PH_AWSObjectName
  PH_Score: PH_Score
entityMappings:
- entityType: Url
  fieldMappings:
  - identifier: Url
    columnName: PH_DomainName
- entityType: Host
  fieldMappings:
  - identifier: HostName
    columnName: PH_HostName
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_phishing

Stage 2: where

| where Service == "phishing"

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