Consider support for "ignored" processes in FAA rules #491
Description
There are occasions when an admin may want to have a process be blocked from performing some operations via an FAA rule, but in order to reduce user friction, the admin may not want the user to be notified of the violation. This would work similarly to the EnableSilentMode key, but at a more granular, per-process exception level.
This would allow admins to deploy policies that generate fewer popups while also continuing to minimize the number of allowed processes.
The trade off is that when a user explicitly runs some operation with a binary that is silently blocked, they may not know it is part of some ignore list and will likely be very confused as to why the action doesn't work.
Users today have the ability to suspend future notifications for up to a month. But this still requires user interaction / training.