Not only is it a security risk, but it has the potential to become a support nightmare.
At least with the implementation that I support, (1200+ and growing rapidly), allowing users to download their own applications, especially when they aren't technically savvy to begin with, is just asking for trouble.
In case of trouble, our users first contact is supposed to be with our Help Desk, which will attempt to resolve the problem, or route it to the appropriate department. If there are unknown, untested applications that reside on the BlackBerry handheld, these could complicate the support process, especially if the user has become "dependant" upon a particular unknown, untested, unsupported app.
As far as the security risk, Wired Magazine ran an article over the summer regarding an application known as BBProxy. This was a proof of concept created by a hacker that could be loaded on the BlackBerry handheld, and would exploit the trusted connection between the handheld and the BES to attack either the BES, or the network of the company that runs it.
A way around this is to use the BES to wirelessly load tested and approved handheld applications for your deployment. Look around on the RIM web site for information and a demonstration. This will override any security settings preventing third party downloads directly to the handheld.
I hope this provides some additional food for thought to your question.
|