Support

I assume this extension installs a component. I also assume that the Target URL you see always has the same option and view. This means you can add a WAF Exception for this component and your problem will be solved.

Please note that it is generally an EXTREMELY BAD IDEA™ allowing file uploads in the front-end by a solution which throws DFIShield exceptions. It means that this solution communicates the internal, absolute server path of the uploaded file to the browser. This is called information leak and it's considered a security issue (albeit on the lowest of the three severity levels). By adding a WAF Exception you will give it free reign to do whatever it wants without being subject to Admin Tools checks. Be warned that if this solution contains other security vulnerabilities your site will be hacked and Admin Tools will not prevent it because you'll have told it not to.

IMHO, you don't need this component at all. You just need to teach your users how to use the media manager in the back-end of their site. You may have to adjust the Options of the media manager to allow EXE and MSI uploads (I suppose that's their software delivery format) and maybe change the maximum post and upload sizes in the server's php.ini.

Any uploader in the front-end of the site will trigger the DFIShield protection if it's written in an insecure manner. Considering that all the third party uploaders I've seen use the same libraries for staggered uploads I am pretty sure they will trigger it. If you are using an uploader in the back-end of the site the DFIShield won't be triggered.

All that said, I am against using an uploader altogether. No matter how well you code it you still have user-facing code modifying files on your server. That's a security incident waiting to happen. What's wrong with using SFTP?

SFTP is the much better way to handle uploads. Especially when you give each user their own certificate or their own username/password pair.