Detection rules › Kusto

Multiple failed attempts of NetBackup login

This is a third-party alert feed, not a detection over modeled telemetry. The vendor product raised the finding; this rule forwards it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.

Status
available
Severity
medium
Time window
15m
Source
github.com/Azure/Azure-Sentinel

This rule generates an incident when there are more than 5 failed login attemts for a given host in the last 15 minutes.

MITRE ATT&CK coverage

Rule body kusto

id: d39f0c47-2e85-49b9-a686-388c2eb7062c
name: Multiple failed attempts of NetBackup login
description: This rule generates an incident when there are more than 5 failed login attemts for a given host in the last 15 minutes.
severity: Medium
status: Available
requiredDataConnectors: []
queryFrequency: 15m
queryPeriod: 15m
triggerOperator: gt
triggerThreshold: 0
tactics:
    - CredentialAccess
    - Discovery
relevantTechniques:
    - T1110
    - T1212
query: "NetBackupAlerts_CL\r\n| where operation_s contains \"LOGIN\" and Message\
    \ contains \"authentication failed\" \r\n| extend userName =  split(userName_s,\
    \ \"@\")[0]\r\n| extend host = split(userName_s, \"@\")[1] \r\n| summarize Total=count()\
    \ by tostring(host)\r\n| where Total >= 5"
entityMappings:
  - entityType: Host
    fieldMappings:
      - identifier: HostName
        columnName: host
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    enabled: false
    reopenClosedIncident: false
    lookbackDuration: 5h
    matchingMethod: AllEntities
suppressionDuration: PT5H
suppressionEnabled: false
eventGroupingSettings:
  aggregationKind: SingleAlert
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

NetBackupAlerts_CL

Stage 2: where

| where operation_s contains "LOGIN" and Message contains "authentication failed"

Stage 3: extend

| extend userName =  split(userName_s, "@")[0]

Stage 4: extend

| extend host = split(userName_s, "@")[1]

Stage 5: summarize

| summarize Total=count() by tostring(host)
Threshold
ge 5

Stage 6: where

| where Total >= 5

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
Messagecontains
  • authentication failed
Totalge
  • 5 transforms: cased
operation_scontains
  • LOGIN

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
Totalsummarize