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.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...