detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Leaked Credentials

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 leaked credentials identified by CybleVision ingestion and triggers an incident with mapped entities, severity, and details.'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1552 Unsecured Credentials
DiscoveryT1082 System Information Discovery

Rule body kusto

id: 224a63ae-e278-4a11-b7c2-02ec3e17b56c
name: Cyble Vision Alerts Leaked Credentials
description: |
  'Detects leaked credentials identified by CybleVision ingestion and triggers an incident with mapped entities, severity, and details.'
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:
- CredentialAccess
- Discovery
- Reconnaissance
relevantTechniques:
- T1552
- T1082
subTechniques: []
query: |
  Alerts_leaked_credentials
  | where Service == "leaked_credentials"
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: Leaked Credentials Detected {{LC_Username}}
  alertDescriptionFormat: |
    A leaked set of credentials associated with {{LC_Username}} was detected. Domain {{LC_Domain}} Source URL {{LC_URL}}
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  MappedSeveritry: MappedSeverity
  Leak_Username: LC_Username
  Leak_Url: LC_URL
  Leak_Date: LC_Date
  Leak_Tags: LC_Tags
  Leak_Data: LC_Data
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: LC_Username
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: LC_URL
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: LC_Domain
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_leaked_credentials

Stage 2: where

| where Service == "leaked_credentials"

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