Detection rules › Kusto
Cyble Vision Alerts Malicious Ads 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.
'Generates an incident when Cyble Intelligence detects a malicious advertisement, malvertising activity, or redirect attempting to impersonate a legitimate brand.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1189 Drive-by Compromise, T1566 Phishing |
| Execution | T1059 Command and Scripting Interpreter |
Rule body kusto
id: cf0a9691-5716-42e0-bfa1-49b35d3a7892
name: Cyble Vision Alerts Malicious Ads Detected
description: |
'Generates an incident when Cyble Intelligence detects a malicious advertisement, malvertising activity, or redirect attempting to impersonate a legitimate brand.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
dataTypes:
- CybleVisionAlerts_CL
enabled: true
queryFrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
suppressionDuration: PT5M
eventGroupingSettings:
aggregationKind: AlertPerResult
tactics:
- InitialAccess
- Execution
relevantTechniques:
- T1189
- T1566
- T1059
query: |
Alerts_malicious_ads
| where Service == "malicious_ads"
| extend MappedSeverity = Severity
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
reopenClosedIncident: false
lookbackDuration: PT5H
matchingMethod: AllEntities
alertDetailsOverride:
alertDisplayNameFormat: Malicious Ad Detected {{MA_DomainName_Nested}}
alertDescriptionFormat: |
Cyble Intelligence detected a malicious advertisement or suspicious redirect.
Domain {{MA_Domain_URL}}
Brand/Keyword {{MA_Keyword_Nested}}
Status Code {{MA_StatusCode}}
customDetails:
MappedSeverity: Severity
Status: Status
AlertID: AlertID
Service: Service
Domain: MA_Domain_URL
Keyword: MA_Keyword_Nested
IsLive: MA_IsLive
entityMappings:
- entityType: URL
fieldMappings:
- identifier: Url
columnName: MA_Domain_URL
- entityType: DNS
fieldMappings:
- identifier: DomainName
columnName: MA_DomainName_Nested
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
Alerts_malicious_ads
Stage 2: where
| where Service == "malicious_ads"
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.
| Field | Kind | Values |
|---|---|---|
Service | eq |
|
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.
| Field | Source |
|---|---|
MappedSeverity | extend |