detection.wiki

Detection rules › Kusto

Cyble Vision Alerts Postman API Exposure Detection

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 Postman requests, collections or endpoints referencing monitored entities. Alerts analysts to possible API enumeration, leaked endpoints, or unintended exposure.'

MITRE ATT&CK coverage

TacticTechniques
ReconnaissanceT1595 Active Scanning
Credential AccessT1552 Unsecured Credentials
ExfiltrationT1041 Exfiltration Over C2 Channel

Rule body kusto

id: 99ca8956-5aad-4542-9fbc-8254182b424d
name: Cyble Vision Alerts Postman API Exposure Detection
description: |
  'Detects exposed Postman requests, collections or endpoints referencing monitored entities. Alerts analysts to possible API enumeration, leaked endpoints, or unintended exposure.'
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
- CredentialAccess
- Exfiltration
relevantTechniques:
- T1595
- T1552
- T1041
query: |
  Alerts_postman  
  | where Service == "postman"
  | extend MappedSeverity = Severity
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: PT5H
    matchingMethod: AllEntities
  alertDetailsOverride:
  alertDisplayNameFormat: Exposed Postman API Request {{PM_Title}}
  alertDescriptionFormat: |
    A Postman API request referencing monitored entity {{KeywordName}} was discovered. Public Workspace {{PM_IsPublic}}. Developer {{PM_DevelopedBy}}. This may indicate exposed API endpoints, leaked request parameters or sensitive testing data.
customDetails:
  MappedSeverity: Severity
  Status: Status
  AlertID: AlertID
  Service: Service
  PM_Title: PM_Title
  PM_DevelopedBy: PM_DevelopedBy
  PM_DevelopedByUrl: PM_DevelopedByUrl
  PM_Category: PM_Category
  PM_PostmanKey: PM_PostmanKey
  PM_Url: PM_Url
entityMappings:
- entityType: Url
  fieldMappings:
  - identifier: Url
    columnName: PM_Url
- entityType: Host
  fieldMappings:
  - identifier: HostName
    columnName: KeywordName
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

Alerts_postman

Stage 2: where

| where Service == "postman"

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