Detection rules › Kusto
Rubrik Critical Anomaly
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.
'Rubrik Critical Anomaly rule matches Severity and if Critical severity found then generate the incident for each object.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1546 Event Triggered Execution |
Rule body kusto
id: 54c70d21-696f-4f03-9238-9d7118d079fe
name: Rubrik Critical Anomaly
version: 1.0.0
kind: Scheduled
description: |
'Rubrik Critical Anomaly rule matches Severity and if Critical severity found then generate the incident for each object.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: RubrikSecurityCloudAzureFunctions
dataTypes:
- RubrikAnomalyData
queryFrequency: 10m
queryPeriod: 10m
triggerOperator: gt
triggerThreshold: 0
tactics:
- Persistence
relevantTechniques:
- T1546
query: |
Rubrik_Anomaly_Data_CL
| where severity_s == "critical"
eventGroupingSettings:
aggregationKind: AlertPerResult
customDetails:
ClusterIdentifier: custom_details_clusterId_g
ObjectId: custom_details_objectId_g
ObjectName: custom_details_objectName_s
ObjectType: custom_details_objectType_s
ClusterName: custom_details_clusterName_s
incidentConfiguration:
createIncident: true
Stages and Predicates
Stage 1: source
Rubrik_Anomaly_Data_CL
Stage 2: where
| where severity_s == "critical"
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.
| Field | Kind | Values |
|---|---|---|
severity_s | eq |
|