2021-04-02 08:46 AM
Wondering if anyone has the naming convention for the nwxxxxxx app rules (screenshot) that are part of the decoder "apprule" process. These map to an "Alert" meta key in our environment. Seems like these might be a legacy pull in...
anyone else run into this? I know you can go through each one and put a custom name, but with like 100 of these, that could take a bit to go through and plus review the log to see if the naming makes sense. Did know if RSA had this in the hunting guide, I recall them discussing several meta keys there. Anyone have this top of mind?
2021-04-02 09:44 AM
2021-04-02 10:06 AM
I was wondering if they were remnants of the legacy deployments. I think those might have got loaded right when we went to 11.0....I have reviewed a few of them and I think they can be useful and renamed.
Thank you for the extra comment on DONT use alert.id for meta creation, we dont, we typically will use the "Alert" function for app rule creation and data truncating. But I had no knowledge of this.
Question: In 11.5.3 do the app rules still work top - down?
Thank you John!!!
2021-04-02 10:17 AM
2021-04-02 10:30 AM
No sir. We will keep them the same. We have not touched them. Glad I posted this on here.
Thanks John
2021-04-02 10:32 AM
I see what you are saying is they are a placeholder and going to the next meta. I will share this with my team as well.
So, thinking this through. Alert.id should not be in any of the search meta criteria is what you are saying so pivoting off them is not the intended use.
2021-04-02 10:34 AM
2021-04-02 10:36 AM
Awesome. I will do that.
Have a good weekend and holiday John!