Windows Mobile as secure as Blackberry - are you joking?
At TechEd US 2008 this year I'm presenting a session which is called - 'Windows Mobile as secure as Blackberry - are you joking'
I wanted to cover this topic as there is so much FUD out there on the Windows Mobile Security story.
Sorry - FUD - That's Fear Uncertainty and Doubt (off topic but I recently discovered that FUD means something very different in Scotland - please Live Search this off your Corporate Network - I take no responsibility for any offence caused)
I'm starting to collate my content for this session but I thought I'd ask those of you who read my blog what issues/topics you thought I should include?
Comments
Anonymous
April 29, 2008
Jason love your blog as you have a good pulse on things mobility and I'd love to see this presentation but you are not going 1-1 with BES. Windows Mobile against Exchange only is not as secure as Blackberry against BES. Your policies are limited, and there is NO reporting, assest management through exchange unless you want to phrase out IIS logs. Yes with System Center 2007 Device Manager you approach what BES does but at that point your TCO is double that of a BES CAL. Device manager should be PART of exchange and not SC2007 and an extra expense. If anyone would you might know this .. will SCDM support the Iphone?Anonymous
April 29, 2008
The comment has been removedAnonymous
April 29, 2008
Jason, sorry I'm going to miss your presentation, but believe that it is important to address the need to have a direct connection into the network is still better than relying on a 3rd party NOC ;)Anonymous
April 29, 2008
The comment has been removedAnonymous
April 29, 2008
The comment has been removedAnonymous
April 29, 2008
The comment has been removedAnonymous
April 29, 2008
The comment has been removedAnonymous
April 30, 2008
The lack of MDM for Iphone will be a dissappointment. I'm in the 2.0 beta and it's very basic security and not quite what Windows Mobile 5.0 MSFP offered. With BES 4.1 and later you pretty much have a policy via BES to control / lock down every aspect of the device if you choose. The code signing has nothing to do with 3rd party applications but more so with internally developed that you wish to put on the Blackberry. I believe the current cost is $25 per company to have a signed java key.Anonymous
April 30, 2008
The security can be tweaked. Are you using the mmc to change the policies on the device? (You must manually add the mobile templates to your mmc.) There is quite a lot of settings to play with there. BB of course will be easier to secure, but I'd attribute this to it being limited from the word go. It is much easier to play around with WM settings, as we pretty much have open access to the whole device. You can lock down pretty much any aspect of the WM device you choose, even without MDM its possible to create a completely secure SOE with only basic desktop tools. Notepad.exe being the key player. The underlying XML CSPs that were even in ppc2003 and WM5, allow for a massive amount of control even from a humble cab file.Anonymous
May 01, 2008
Can I suggest something NOT to mention - that's the 'number of policies' war that seems to be going on. You guys continually adding more, and my RIM contacts pointing out that they've still got more. It's getting silly, and no one cares about quantity - it's quality that's important. The NOC vs. direct argument is important, from a security POV. There are good arguments on both sides, but I doubt you're looking for ideas to present a balanced comparison! ;-) P.