Detection rules › Kusto

GWorkspace - Possible brute force attack

Status
available
Severity
medium
Time window
5m
Group by
ActorEmail
Source
github.com/Azure/Azure-Sentinel

'Detects possible brute force attack.'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110 Brute Force

Rule body kusto

id: 8f6cd9a4-5e57-11ec-bf63-0242ac130002
name: GWorkspace - Possible brute force attack
description: |
  'Detects possible brute force attack.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: GoogleWorkspaceReportsAPI
    dataTypes:
      - GWorkspaceActivityReports
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - CredentialAccess
relevantTechniques:
  - T1110
query: |
  let threshold = 5;
  GWorkspaceActivityReports
  | where EventMessage has "login_failure"
  | summarize login_attempts = count() by ActorEmail, bin(TimeGenerated, 5m)
  | where login_attempts > threshold
  | extend AccountCustomEntity = ActorEmail
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 5;

Stage 1: source

GWorkspaceActivityReports

Stage 2: where

| where EventMessage has "login_failure"

Stage 3: summarize

| summarize login_attempts = count() by ActorEmail, bin(TimeGenerated, 5m)
Threshold
gt 5

Stage 4: where

| where login_attempts > threshold

Stage 5: extend

| extend AccountCustomEntity = ActorEmail

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
EventMessagematch
  • login_failure transforms: term
login_attemptsgt
  • 5 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
ActorEmailsummarize
login_attemptssummarize
AccountCustomEntityextend