Forum Discussion
Reduce noisy alerts
gsingh_ When you setup the Watchlist, make sure that it contains a field that you can match on (maybe email address or internal GUID) so that you can then use that field to perform the match in a join command.
However, are you sure that is the correct way to go? I would think, based on the queries for these rules, that these rules find new activity in the last 14 days so they alerts would not show up after that time. Are the alerts being return actually correct, even if they are from valid users? If you modify the query to avoid these users you could be missing valid alerts.
You could see about combining the alerts into a single incident to avoid having all the incidents that would normally be generated (under the Incidents settings tab if you were not aware)
Hi GaryBushey thanks for the response. The use of internal GUID is a great idea, I will check it out.
I am not sure if this is an ideal way of tuning these use cases as we are running most of the rules once a day (With a lookup from the last 1 day). The alerts are picking up the right activity but it's from our legitimate internal tech users.
The reason I was keen to add the MFA login condition is because of the safety reasons, considering if an intruder is able to get access to our internal tech user's account somehow and use the credentials to perform any of these operations, we should definitely get alerted via these rules. I mean if the events indicate Logins from Internal (Tech User + Internal GUID + MFA Succeed) then it's safe to ignore these alerts.
Also, we are already combining these in a single incident. 🙂 Thanks