Bitglass - New risky user

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

'Detects new risky user.'

MITRE ATT&CK coverage

Tactic	Techniques
Initial Access	`T1078` Valid Accounts

Rule body

id: a123668c-d907-41b9-bf3f-8cb4cd7b163a
name: Bitglass - New risky user
description: |
  'Detects new risky user.'
severity: High
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 has_all ('Added', 'Risky Users')
  | extend AccountCustomEntity = User
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Stage 1: `source`

Bitglass

Stage 2: `where`

| where EventType =~ 'access'

Stage 3: `where`

| where EventResultDetails has_all ('Added', 'Risky Users')

Stage 4: `extend`

| extend AccountCustomEntity = User

Indicators

These rows show field, operator, and value matches.

Field	Kind	Values	Search
`EventResultDetails`	match	`Added` transforms: `term` `Risky Users` transforms: `term`	`field:"EventResultDetails" kind:match`
`EventType`	eq	`access`	`field:"EventType" kind:eq value:"access"`

Output fields

These fields are emitted when the rule matches.

Field	Source
`AccountCustomEntity`	`extend`

Bitglass - New risky user

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`