detection.wiki

Detection rules › Kusto

CybleVision Alerts Stealer Logs

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 credential theft and information-stealer malware logs. Extracts stolen credentials, URLs, device info, IPs, domains, and metadata using the Alerts_StealerLogs parser.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1589 Gather Victim Identity Information
Initial AccessT1189 Drive-by Compromise
Credential AccessT1555 Credentials from Password Stores
CollectionT1005 Data from Local System
ExfiltrationT1041 Exfiltration Over C2 Channel

Rule body kusto

id: e0bf55c2-35ef-47ab-8846-5087618ae805
name: CybleVision Alerts Stealer Logs
description: |
  'Detects credential theft and information-stealer malware logs. Extracts stolen credentials, URLs, device info, IPs, domains, and metadata using the Alerts_StealerLogs parser.'
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
- Collection
- Exfiltration
- Reconnaissance
- InitialAccess
relevantTechniques:
- T1555
- T1005
- T1041
- T1589
- T1189
subTechniques: []
query: |
  Alerts_stealer_logs 
  | where Service == "stealer_logs" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: CybleVision Stealer Log Credential Exposure {{SL_MainUsername}}
  alertDescriptionFormat: |
    Stolen credentials detected in stealer logs. Malware Family {{SL_MalwareFamily}} URL {{SL_MainURL}} IP {{SL_IP}}
  alertDynamicProperties: []
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  MalwareFamily: SL_MalwareFamily
  CompromisedDate: SL_CompromiseDate
  App: SL_App
  ContentURL: SL_URL_Content
  ContentUsername: SL_Username_Content
  Password: SL_Password
  HWID: SL_HWID
  IP: SL_IP
  Domain: SL_Domain
  Country: SL_Country
  FileName: SL_FileName
  FileSize: SL_FileSize
  FileCreated: SL_FileCreated
  FileModified: SL_FileModified
  Tags: SL_Tags
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: Name
    columnName: SL_MainUsername
- entityType: URL
  fieldMappings:
  - identifier: Url
    columnName: SL_MainURL
- entityType: IP
  fieldMappings:
  - identifier: Address
    columnName: SL_IP
- entityType: DNS
  fieldMappings:
  - identifier: DomainName
    columnName: SL_Domain
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_stealer_logs

Stage 2: where

| where Service == "stealer_logs"

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