microsoft / microsoft/AzureMonitorCommunity
Use of watchlist to create an analytic rule in Sentinel
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
This rule triggers when there is a DNS query for non-local domain.
//This is my log query and watchlist
Not able to figure it out why i am not seeing the domain listed in the watchlist to my table
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached log_query and watchlist screenshots to identify how the analytic rule references the watchlist. Confirm what field should contain the non-local domain and compare it with the field returned in the table. Done means the expected watchlist domain appears in the table when the rule query runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100