Post your comments for Symantec Leapfrogs McAfee in Mobile Security here
Page 1 of 1
Symantec Leapfrogs Mcafee In Mobile Security
#2
Posted 09 May 2012 - 07:13 AM
Any examples on how this "wrapping of code" works operationally? What does it actually do?
Nosce te ipsum.
Balance, Choice, Responsibility, Power, Reality, Humanity.
Balance, Choice, Responsibility, Power, Reality, Humanity.
#3
Posted 09 May 2012 - 03:04 PM
Exactly, I'm stumped on this too. Assuming it 'wraps' mobile apps on the mobile devices... I'm guessing that the protection would be designed to eliminate the ability to copy/paste data from a 'protected' app to another outside app (e-mail, Facebook, etc.). But as far as I see, once the data actually leaves the physical premises, there's no stopping it from 'escaping'.
And how would this protection be deployed? Would employees go for having their mobile devices modified?
Yes, some more in-depth info would shed more light onto this.
And how would this protection be deployed? Would employees go for having their mobile devices modified?
Yes, some more in-depth info would shed more light onto this.
---
Abort, Retry, Epic Fail? _
Abort, Retry, Epic Fail? _
#4
Posted 09 May 2012 - 10:19 PM
I can answer that - app wrapping can encrypt the app data and add additional controls on it, like blocking clipboard copy, copy to iCloud, copy to other programs, etc. You can also configure authentication whenever the app is launched.
Deployment is pretty simple actually - admin creates an app store, tells the users the URL, then users browse to the site from their mobile device and download the app store agent. Apps are presented to them when they log in. The app wrapping is done transparently (other than stuff like authentication). The devices themselves are not modified (it's not MDM).
Hope that helps.
Deployment is pretty simple actually - admin creates an app store, tells the users the URL, then users browse to the site from their mobile device and download the app store agent. Apps are presented to them when they log in. The app wrapping is done transparently (other than stuff like authentication). The devices themselves are not modified (it's not MDM).
Hope that helps.
#5
Posted 10 May 2012 - 09:21 AM
Makes sense to me. Thanks.
Still though, you can't lockdown everything. This scheme should work fine for custom business apps, but how about mainstream apps?
Still though, you can't lockdown everything. This scheme should work fine for custom business apps, but how about mainstream apps?
---
Abort, Retry, Epic Fail? _
Abort, Retry, Epic Fail? _
#6
Posted 11 May 2012 - 12:13 AM
oldschoolh4ck3r, on 10 May 2012 - 09:21 AM, said:
Makes sense to me. Thanks.
Still though, you can't lockdown everything. This scheme should work fine for custom business apps, but how about mainstream apps?
Still though, you can't lockdown everything. This scheme should work fine for custom business apps, but how about mainstream apps?
Not by default because that's a violation of Apple's Terms of Service. But let's say there's an app your business uses that you really want to secure - you could contact the app vendor and ask for a version of it that's signed with your company's certificate (i.e. a modified version of the app). Then it can be secured all day long.
Share this topic:
Page 1 of 1
Help












