Alerting

Alert on group membership changes under OU

pgw_jdog
New Member

Hi all.

First of all I have inherited our Splunk implementation and only have limited experience. Be gentle....

We currently have an alert configured that is monitoring forwarded events for group membership changes.
The query for the alert has the group names to be monitored hard coded. This most definitely does not scale.
What we would ideally like is to monitor any membership changes of all groups under one or more AD organisational units (recursive). By looking over Splunk documentation and this forum I suspect this would mean setting up one or more and AD Monitors and pointing them to the targeted OU's.

1.) Am I on the right track looking at an AD monitor.
2.) If so can someone point me in the general direction for how to set up an alert using the AD Monitor information.

Thanks in advance.

Jason.

0 Karma
1 Solution

DalJeanis
Legend

We're going to address your question about scalability first.

It's probably best for that kind of use case to create a lookup table for the groups you want to monitor. In that way, you can update the lookup using any desired method, and the alert will be updated (or, more accurately, will comply with the new list) automatically.

https://docs.splunk.com/Documentation/Splunk/7.1.1/SearchReference/Lookup

https://answers.splunk.com/answers/588630/understanding-the-lookup-command.html

In terms of building your lookup table, you would set up a search that reads your AD tables and does whatever recursive processing you want to build the full list. We can't speak to the hierarchy in your organization, but if you'd like to post a new question that shows the format of the records, with non-confidential example data, then we can help you write the search.

View solution in original post

0 Karma

pgw_jdog
New Member

Hello DalJeanis.
Thanks for the reply. I will investigate setting up and Active Directory lookup table and see how I go.

0 Karma

DalJeanis
Legend

We're going to address your question about scalability first.

It's probably best for that kind of use case to create a lookup table for the groups you want to monitor. In that way, you can update the lookup using any desired method, and the alert will be updated (or, more accurately, will comply with the new list) automatically.

https://docs.splunk.com/Documentation/Splunk/7.1.1/SearchReference/Lookup

https://answers.splunk.com/answers/588630/understanding-the-lookup-command.html

In terms of building your lookup table, you would set up a search that reads your AD tables and does whatever recursive processing you want to build the full list. We can't speak to the hierarchy in your organization, but if you'd like to post a new question that shows the format of the records, with non-confidential example data, then we can help you write the search.

0 Karma

DalJeanis
Legend

Welcome! This is not stack overflow. We are always gentle here, or at least we aspire to be.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...