Detection rules › Kusto

Zscaler - Forbidden countries

Status
available
Severity
high
Time window
1h
Source
github.com/Azure/Azure-Sentinel

'Detects suspicious ZPA connections from forbidden countries.'

MITRE ATT&CK coverage

Rule body kusto

id: b3d112b4-3e1e-11ec-9bbc-0242ac130002
name: Zscaler - Forbidden countries
description: |
  'Detects suspicious ZPA connections from forbidden countries.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CustomLogsAma
    datatypes:
      - ZPA_CL
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  let bl_countries = dynamic(['CH', 'RU']);       //List of countries from which you do not expect connections
  ZPAEvent 
  | where DvcAction == 'open'
  | where SrcGeoCountry in~ (bl_countries)
  | extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
version: 1.0.2
kind: Scheduled

Stages and Predicates

Parameters

let bl_countries = dynamic(['CH', 'RU']);

Stage 1: source

ZPAEvent

Stage 2: where

| where DvcAction == 'open'

Stage 3: where

| where SrcGeoCountry in~ (bl_countries)

Stage 4: extend

| extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUserName

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
DvcActioneq
  • open transforms: cased
SrcGeoCountryin
  • CH
  • RU

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
AccountCustomEntityextend
IPCustomEntityextend