My company uses a set of user defined rules to prevent Office applications from launching or modifying exe's and dll's. These seem to work well to prevent zero day exploits, but they also prevent legitimate applications from running as well. Specifically, any Office add-in developed with Microsoft Visual Tools for Office (VSTO) will not load when these rules are enforced.
Is there a way to configure a user defined rule to detect a signed or otherwise registered application add-in and not block it?
Message was edited by: jay.ward on 11/19/10 10:51:29 AM CST