detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Physical Threat Alert

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

'Creates an incident for physical threats identified by Cyble Intelligence such as explosions, safety incidents, riots, or violence. Each alert generates a single incident for SOC evaluation.'

MITRE ATT&CK coverage

TacticTechniques
ImpactT1486 Data Encrypted for Impact

Rule body kusto

id: 88db8505-1889-46aa-a4e2-4e866262dcb9
name: Cyble Vision Alerts Physical Threat Alert
description: |
  'Creates an incident for physical threats identified by Cyble Intelligence such as explosions, safety incidents, riots, or violence. Each alert generates a single incident for SOC evaluation.'
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:
- Impact
relevantTechniques:
- T1486
query: |
  Alerts_physical_threats
  | where Service == "physical_threats"
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: Physical Threat Detected  {{PT_Title_Nested}}
  alertDescriptionFormat: |
    A physical threat incident was identified by Cyble Intelligence.
    Title {{PT_Title_Nested}}
    Threat Type {{PT_ThreatType}}
    Published At {{PT_PublishedAt}}
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  ThreatTitle: PT_Title_Nested
  ThreatType: PT_ThreatType
  Location: PT_LocationName
  LocationType: PT_LocationType
  Latitude: PT_Latitude
  Longitude: PT_Longitude
entityMappings:
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: PT_BaseSourceURL
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_physical_threats

Stage 2: where

| where Service == "physical_threats"

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