detection.wiki

Detection rules › Kusto

Bitglass - Multiple failed logins

Status
available
Severity
high
Time window
10m
Group by
User
Source
github.com/Azure/Azure-Sentinel

'Detects multiple failed logins.'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110 Brute Force

Rule body kusto

id: 7c570bfc-9f20-490e-80e8-b898c7ce4bda
name: Bitglass - Multiple failed logins
description: |
  'Detects multiple failed logins.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: Bitglass
    dataTypes:
      - Bitglass
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - CredentialAccess
relevantTechniques:
  - T1110
query: |
  let threshold = 10;
  Bitglass
  | where EventType =~ 'access'
  | where EventResultDetails =~ 'Failed login attempt.'
  | summarize count() by User, bin(TimeGenerated, 10m)
  | where count_ >= threshold
  | extend AccountCustomEntity = User
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 10;

Stage 1: source

Bitglass

Stage 2: where

| where EventType =~ 'access'

Stage 3: where

| where EventResultDetails =~ 'Failed login attempt.'

Stage 4: summarize

| summarize count() by User, bin(TimeGenerated, 10m)

Stage 5: where

| where count_ >= threshold

Stage 6: extend

| extend AccountCustomEntity = User

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
EventResultDetailseq
  • Failed login attempt.
EventTypeeq
  • access
count_ge
  • 10 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
Usersummarize
AccountCustomEntityextend