detection.wiki

Detection rules › Kusto

CybleVision Alerts Mobile Apps

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

'Detects suspicious, unauthorized or impersonating mobile applications from 3rd-party marketplaces using CybleVision data. Extracts metadata, screenshots, developer, package name, and detailed app attributes.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1595 Active Scanning
Resource DevelopmentT1608 Stage Capabilities
Initial AccessT1195 Supply Chain Compromise

Rule body kusto

id: 6d55fefc-b334-4b79-b11c-667746b5bdde
name: CybleVision Alerts Mobile Apps
description: |
  'Detects suspicious, unauthorized or impersonating mobile applications from 3rd-party marketplaces using CybleVision data. Extracts metadata, screenshots, developer, package name, and detailed app attributes.'
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
- ResourceDevelopment
- InitialAccess
relevantTechniques:
- T1595
- T1608
- T1195
subTechniques: []
query: |
  Alerts_mobile_apps 
  | where Service == "mobile_apps" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: CybleVision Suspicious Mobile App {{MA_Title}}
  alertDescriptionFormat: |
    A potentially suspicious mobile application was detected. Developer {{MA_Developer}} Market {{MA_MarketSource}} Deep Link {{MA_DeepLink}}\n
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  AppName: AppName
  Developer: MA_Developer
  MarketSource: MA_MarketSource
  MarketURL: MA_MarketURL
  PackageName: MA_PackageName
  Description: MA_Description
  Downloads: MA_Downloads
  MarketStatus: MA_MarketStatus
  MarketUpdated: MA_MarketUpdated
  CreatedOn: MA_Created
  AppEmail: MA_Email
  IconURL: MA_MarketURL
  Website: MA_Website
  Version: MA_Version
  Screenshots: MA_Screenshots
  Tags: MA_Tags
entityMappings:
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: MA_DeepLink
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: Domain
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_mobile_apps

Stage 2: where

| where Service == "mobile_apps"

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