Detection rules › Kusto
Alarming number of anomalies generated in NetBackup
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.
This rule generates an incident when an alarming number of anomalies are generated in the last 15 minutes.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Credential Access | No specific technique |
| Discovery | No specific technique |
Rule body kusto
id: 2e0efcd4-56d2-41df-9098-d6898a58c62b
name: Alarming number of anomalies generated in NetBackup
description: This rule generates an incident when an alarming number of anomalies are generated in the last 15 minutes.
severity: Medium
status: Available
requiredDataConnectors: []
queryFrequency: 15m
queryPeriod: 15m
triggerOperator: gt
triggerThreshold: 0
tactics:
- Discovery
- CredentialAccess
techniques:
- T1110
- T1212
query: "NetBackupAlerts_CL\r\n| where Category contains \"ANOMALY_NEW\"\r\n| extend\
\ client = split(Message, \"client '\")[1]\r\n| extend clientName = split(client,\
\ \"'\")[0]\r\n| summarize Total=count() by tostring(clientName)\r\n| where\
\ Total >= 10"
entityMappings:
- entityType: Host
fieldMappings:
- identifier: HostName
columnName: clientName
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
lookbackDuration: PT5H
matchingMethod: AllEntities
reopenClosedIncident: false
suppressionDuration: PT5H
suppressionEnabled: false
eventGroupingSettings:
aggregationKind: SingleAlert
version: 1.0.1
kind: Scheduled
Stages and Predicates
Stage 1: source
NetBackupAlerts_CL
Stage 2: where
| where Category contains "ANOMALY_NEW"
Stage 3: extend
| extend client = split(Message, "client '")[1]
Stage 4: extend
| extend clientName = split(client, "'")[0]
Stage 5: summarize
| summarize Total=count() by tostring(clientName)
Stage 6: where
| where Total >= 10
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.
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.
| Field | Source |
|---|---|
Total | summarize |