Bitglass - Impossible travel distance

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

'Detects logins from different geo locations.'

MITRE ATT&CK coverage

Tactic	Techniques
Initial Access	`T1078` Valid Accounts

Rule body

id: cdb6e4a4-b9bd-4c30-94b9-ecce5a72d528
name: Bitglass - Impossible travel distance
description: |
  'Detects logins from different geo locations.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: Bitglass
    dataTypes:
      - Bitglass
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1078
query: |
  Bitglass
  | where EventType =~ 'access'
  | where EventResultDetails startswith 'Simultaneous logins from geographically distant locations'
  | extend AccountCustomEntity = User
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: `source`

Bitglass

Stage 2: `where`

| where EventType =~ 'access'

Stage 3: `where`

| where EventResultDetails startswith 'Simultaneous logins from geographically distant locations'

Stage 4: `extend`

| extend AccountCustomEntity = User

Indicators

These rows show field, operator, and value matches.

Field	Kind	Values	Search
`EventResultDetails`	starts_with	`Simultaneous logins from geographically distant locations`	`field:"EventResultDetails" kind:starts_with value:"Simultaneous logins from geographically distant locations"`
`EventType`	eq	`access`	`field:"EventType" kind:eq value:"access"`

Output fields

These fields are emitted when the rule matches.

Field	Source
`AccountCustomEntity`	`extend`

Bitglass - Impossible travel distance

MITRE ATT&CK coverage

Rule body

Stages and Predicates

Stage 1: source

Stage 2: where

Stage 3: where

Stage 4: extend

Indicators

Output fields

Stage 1: `source`

Stage 2: `where`

Stage 3: `where`

Stage 4: `extend`