Detection rules › Kusto
Cyble Advisory Alerts Advisory
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 Microsoft Sentinel incidents from Cyble Advisory service alerts. Advisory alerts provide intelligence and context related to monitored keywords.Severity is normalized using MappedSeverity for downstream automation.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Reconnaissance | T1595 Active Scanning, T1596 Search Open Technical Databases |
| Resource Development | T1587 Develop Capabilities |
Rule body kusto
id: 1932DCFD-A32E-49F9-A212-5BCD084FBD78
name: Cyble Advisory Alerts Advisory
description: |
'Generates Microsoft Sentinel incidents from Cyble Advisory service alerts. Advisory alerts provide intelligence and context related to monitored keywords.Severity is normalized using MappedSeverity for downstream automation.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
dataTypes:
- CybleVisionAlerts_CL
enabled: true
queryfrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
eventGroupingSettings:
aggregationKind: AlertPerResult
suppressionEnabled: false
tactics:
- Reconnaissance
- ResourceDevelopment
relevantTechniques:
- T1595
- T1596
- T1587
entityMappings: null
query: |
Alerts_advisory
| where Service == "advisory"
| extend MappedSeverity = Severity
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
reopenClosedIncident: false
lookbackDuration: PT5H
matchingMethod: AllEntities
alertDetailsOverride:
alertDisplayNameFormat: Cyble Vision Advisory {{ADV_Value}} detected
alertDescriptionFormat: |
Vision Alert for AdvisoryId {{ADV_Value}}
customDetails:
MappedSeverity: Severity
Status: Status
AlertID: AlertID
Service: Service
Keyword: KeywordName
BucketName: BucketName
AdvisoryId: ADV_Value
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
Alerts_advisory
Stage 2: where
| where Service == "advisory"
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 |