Block Exchange Forwarding needs an exception mechanism
under review
B
Brian Camp
There is no way to satisfy "Block Exchange Forwarding" in ISPM while a single forwarded mail address exists in the organization. There are common and unavoidable business use cases for forwards though. For example, we have a support mail box (help@ourdomain.com) that forwards to an outside JIRA mailbox for ticketing. We should be able to enable the prevent-forwarding ISPM control in a way that allows this business process to continue to function.
Ideally, there would be an admin-approved exception mechanism for allowing specific mailboxes to be forwarded, while preserving and enforcing the "block accounts from setting up forwarding" behavior.
S
Scott Riley
updated the status to
under review
S
Scott Riley
Hey Brian Camp - so the best way to do this at the moment would be to hit "Accept Risk" on the control. This will allow us to basically say "Hey, this is fine". The good thing is that if we detect any changes that add/remove any more forwarders being added then we can drift detect and alert you to the change.
We are consider other refinements here which may include an "expected configuration" in other words you basically hit the button to say "Yes, this is how it should look" Then we detect drift AND auto-remediate.