detection.wiki

Detection rules › Kusto

Cyble Vision Alerts OSINT Mention 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

'Triggers when Cyble detects an OSINT mention related to monitored keywords, entities, or brand identifiers. OSINT findings may indicate data leaks, expose content, targeting activity, impersonation, or discussions that may require investigation.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1589 Gather Victim Identity Information, T1592 Gather Victim Host Information

Rule body kusto

id: 9ff985d8-57a8-4302-a8e6-34fa96c3c505
name: Cyble Vision Alerts OSINT Mention Detected
description: |
  'Triggers when Cyble detects an OSINT mention related to monitored keywords, entities, or brand identifiers. OSINT findings may indicate data leaks, expose content, targeting activity, impersonation, or discussions that may require investigation.'
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
- ResourceDevelopment
relevantTechniques:
- T1592
- T1589
query: |
  Alerts_osint  
  | where Service == "osint" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
  alertDetailsOverride:
  alertDisplayNameFormat: OSINT Mention Identified for Monitored Keyword {{KeywordName}}
  alertDescriptionFormat: |
    A public OSINT mention referencing monitored keyword/entity {{KeywordName}} has been detected. Source {{OS_Source}}. Mention URL {{OS_MentionURL}}. This may indicate reputational impact, data exposure, or adversarial research targeting the organization.
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  AuthorName: OS_AuthorName
  AuthorUsername: OS_AuthorUsername
  Source: OS_Source
  MentionDate: OS_MentionDate
  MentionURL: OS_MentionURL
  PostSnippet: OS_PostSnippet
entityMappings:
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: MA_Domain
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: MA_DomainURL
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: KeywordName
- entityType: Host
  fieldMappings:
  - identifier: HostName
    columnName: Domain
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_osint

Stage 2: where

| where Service == "osint"

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