Use of watchlist to create an analytic rule in Sentinel

Open
#218 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
security

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.

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

log_query watchlist
Dominant language
PowerShell
Stars
1.2k
Forks
493
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/AzureMonitorCommunity

All issues in microsoft/AzureMonitorCommunity

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.