Skip to content

Commit d80360b

Browse files
Merge pull request #224643 from yelevin/yelevin/auto-disable-scenario
New auto-disable scenario
2 parents 7347090 + da08799 commit d80360b

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/sentinel/detect-threats-custom.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -308,6 +308,17 @@ You can easily determine the presence of any auto-disabled rules, by sorting the
308308
309309
SOC managers should be sure to check the rule list regularly for the presence of auto-disabled rules.
310310
311+
#### Permanent failure due to resource drain
312+
313+
Another kind of permanent failure occurs due to an **improperly built query** that causes the rule to consume **excessive computing resources** and risks being a performance drain on your systems. When Microsoft Sentinel identifies such a rule, it takes the same three steps mentioned above for the other permanent failures—disables the rule, prepends **"AUTO DISABLED"** to the rule name, and adds the reason for the failure to the description.
314+
315+
To re-enable the rule, you must address the issues in the query that cause it to use too many resources. See the following articles for best practices to optimize your Kusto queries:
316+
317+
- [Query best practices - Azure Data Explorer](/azure/data-explorer/kusto/query/best-practices)
318+
- [Optimize log queries in Azure Monitor](../azure-monitor/logs/query-optimization.md)
319+
320+
Also see [Useful resources for working with Kusto Query Language in Microsoft Sentinel](kusto-resources.md) for further assistance.
321+
311322
## Next steps
312323
313324
When using analytics rules to detect threats from Microsoft Sentinel, make sure that you enable all rules associated with your connected data sources in order to ensure full security coverage for your environment. The most efficient way to enable analytics rules is directly from the data connector page, which lists any related rules. For more information, see [Connect data sources](connect-data-sources.md).
@@ -317,6 +328,7 @@ You can also push rules to Microsoft Sentinel via [API](/rest/api/securityinsigh
317328
For more information, see:
318329
319330
- [Tutorial: Investigate incidents with Microsoft Sentinel](investigate-cases.md)
331+
- [Navigate and investigate incidents in Microsoft Sentinel - Preview](investigate-incidents.md)
320332
- [Classify and analyze data using entities in Microsoft Sentinel](entities.md)
321333
- [Tutorial: Use playbooks with automation rules in Microsoft Sentinel](tutorial-respond-threats-playbook.md)
322334

0 commit comments

Comments
 (0)