detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Bitbucket

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 exposed secrets in Bitbucket repositories using the Alerts_bit_bucket parser. Creates one incident per matched secret. Includes decoder, detector, commit, file, and repository context for SOC triage.'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1552 Unsecured Credentials
DiscoveryT1083 File and Directory Discovery
ExfiltrationT1537 Transfer Data to Cloud Account

Rule body kusto

id: f3c25011-4509-41c8-be27-35d891531c39
name: Cyble Vision Alerts Bitbucket
description: |
  'Detects exposed secrets in Bitbucket repositories using the Alerts_bit_bucket parser. Creates one incident per matched secret. Includes decoder, detector, commit, file, and repository context for SOC triage.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
  dataTypes:
  - CybleVisionAlerts_CL
enabled: true
queryFrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
eventGroupingSettings:
  aggregationKind: AlertPerResult
tactics:
- CredentialAccess
- Exfiltration
- Discovery
relevantTechniques:
- T1552
- T1537
- T1083
query: |
  Alerts_bit_bucket 
  | where Service == "bit_bucket" 
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
alertDetailsOverride:
  alertDisplayNameFormat: Secret Exposure in Bitbucket {{BB_File}} ({{BB_DetectorName}})
  alertDescriptionFormat: |
    A sensitive secret was detected in Bitbucket repository {{BB_Repository}}. File {{BB_File}}:{{BB_Line}}. Investigator should verify exposure, rotate credentials and remediate impacted systems.
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  BB_DetectorName: BB_DetectorName
  BB_Raw: BB_Raw
  BB_File: BB_File
  BB_Line: BB_Line
  BB_Commit: BB_Commit
  BB_Email: BB_Email
  BB_Repository: BB_Repository
  BB_Link: BB_Link
  BB_Verified: BB_Verified
  BB_RotationGuide: BB_RotationGuide
entityMappings:
- entityType: Url
  fieldMappings:
  - identifier: Url
    columnName: BB_Repository
- entityType: Url
  fieldMappings:
  - identifier: Url
    columnName: BB_Link
- entityType: File
  fieldMappings:
  - identifier: Name
    columnName: BB_File
  - identifier: Directory
    columnName: KeywordName
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_bit_bucket

Stage 2: where

| where Service == "bit_bucket"

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