Azure-Sentinel/Detections
timbMSFT 265a3294ed
Queryandplaybook (#685)
* query and playbook commit
2020-05-14 18:26:55 +01:00
..
AWSCloudTrail materialize and other PR review changes 2020-05-01 15:41:48 -07:00
AuditLogs Documentation links should not include locale - fix and add validations (#678) 2020-05-13 15:07:12 +03:00
AzureActivity Merge pull request #454 from jeffhoyo/patch-1 2020-01-27 06:20:41 -08:00
AzureDiagnostics changes per review and starttime function changes 2020-01-16 11:11:13 -08:00
CommonSecurityLog Update Wazuh-Large Number of Web errors from an IP 2020-05-07 16:53:11 -07:00
DnsEvents Fixing up syntax a bit and adding in parameters, other than that no other logic changes. 2020-01-10 12:19:48 -08:00
MultipleDataSources Merge pull request #564 from robMSFT/robMSFT-RareOfficeUserAgent 2020-04-09 08:05:50 -07:00
OfficeActivity Merge pull request #649 from duzlov/master 2020-05-14 08:33:54 -07:00
SecurityEvent Documentation links should not include locale - fix and add validations (#678) 2020-05-13 15:07:12 +03:00
SigninLogs Merge pull request #670 from Azure/AzurePortalDetectionFix_May2020 2020-05-14 08:32:10 -07:00
Syslog Syslog detections - Minor syntax changes, one improvement to aggreation for SSH Potential Brute force 2020-01-16 10:57:33 -08:00
ThreatIntelligenceIndicator Queryandplaybook (#685) 2020-05-14 18:26:55 +01:00
W3CIISLog Update RareClientFileAccess.yaml 2020-04-03 09:51:39 +01:00
ZoomLogs PR fixes and new query 2020-04-27 12:22:01 -07:00
readme.md Updating Detections Readme 2019-03-11 10:30:25 -07:00

readme.md

About

  • This folder contains Detections based on different types of data sources that you can leverage in order to create alerts and respond to threats in your environment.
  • These detections are written using KQL query langauge and will provide you a starting point to protect your environment and get familiar with the different data tables.
  • To create the detection in your environment -
    • go to the 'Analytics' section
    • copy the required query
    • update the alert rule parameters according to the detection parameters - copy the name, the description, lookback time, threshold and severity.
    • the query will be simulated and you will be able to immediately see if a you have hits based on the detection.
    • create the alert rule
  • The rule created will run the query on the scheduled time that was defined, and trigger an alert that will be seen both in the SecurityAlert table and in a case in the Cases page

For questions or feedback, please contact AzureSentinel@microsoft.com