Prebuild Rule Installation - Best Practices

Hey everyone,

After I just upgraded our Stack to 9.5.6, I asked myself again what is the best way to handle pre-build rule installation in Elastic.

I finished the Elastic Security Training this year, and the trainer recommended that we only install the rules that we might enable, meaning rules that make sense in our environment. For example, if we have no AWS, I should not install those rules.

My colleague who manages the cluster with me has another philosphy - install all rules, then check which ones to enable.

My problem with the recommended approach: after the update, let's say there are 100 new rules to install. I check these rules, 20 make sense for us, the rest not. So I install those 20, the other 80 stay behind the "Install Elastic Rules" button. Now after the next update, there are again 100 rules that can be installed, which means that now the "Install Elastic Rules" button shows me 180 rules to install - I have to check them all, since there is no way to filter or sort by "arrived at" or something like this.

So after a few rounds of update where we did not install all rules, I have currently about 400 rules there, and it becomes impossible to recheck them all and decide which ones to install.

Even if we would install all rules, we still would have to use some "manual" way to track which ones are new, and which ones we should enabled after the installation.

It would be nice to have a field like "Install Date" in the rule view, or a "Added Date" in the "Install Elastic Rule" Window - like that you could more easily filter or sort the view and see which rules you need to check.

My question: how are you all handling the installation of new rules after a stack update? Do you have additional lists to manage the rules, which one are installed, which one should be enabled...?

I am happy about your input, and maybe there is an idea that could ease this in Elastic that can be added as a feature request...

I usually script the install via the API and keep a simple json list of rule ids I care about then run it after each upgrade (skip the rest). that way I only ever see the new ones I added to the list and I can tag them in kibana if needed (but api is easier). just remember to version control the list