Splunk Enterprise Security

Best Practice: Separating Dev/Test and Prod Notables in Incident Review

tfrederick74656
Explorer

I'm looking to provide two separate ES incident review views: one for rules that are live, and another for new rules that are still being tested. I already know I can pre-populate the search box on the incident review dashboard, and then add a new link in the ES navigation bar, but I'm wondering what the best practice is for how to actually filter the notables: Should I prefix all of my non-prod correlation searches with "Dev"? Should I eval in a "prod_status" field? Should I put in an automatic lookup that maps rule_title to dev/test/prod? What's the best approach for making searches easy to separate, and simple to graduate from dev to test to prod?

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.


Introducing Unified TDIR with the New Enterprise Security 8.2

Read the blog
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...