![]() ![]() We are 'grandfathered' as we started down the process officially before the recent updates. Not knowing where you are in the process, my answer may not be accurate for your situation, but here it is. Ken makes some good points and the gov's recommended approach. If all the mobile device is doing is MFA/2FA, it is NOT in scope. If you use an appendix, removes the need to rev the whole policy. List can (and should be) an appendix, but could be in the BYOD policy itself. The apps in scope are just the ones that handle business data. ![]() Should be relatively inclusive but does not need to be all inclusive. Name/username, Mfg, Model, OS version, and confirmation that the devices are auto-downloading and auto-updatingģ. An inventory list of the devices themselves. We also specify in our policy not to use the pre-installed apps like Mail and Calender so there is no mingling of personal and business data.Ģ. Our policy is written for mobile devices as a whole, not just iPhones, as ALL mobile devices are in scope regardless of type and who owns. A detailed BYOD policy (with signed ack from employees) that details how devices will be used including approved use or uses, no jailbreaking, no 'unsigned' apps etc. What is sufficient based on our assessors review is:ġ. We are finalizing this exact process and we do not use MDM. Ironically, while we have all been told how much more secure iPhone is than Android, Play Protect probably covers option 1 (if you squint hard enough). Again, as far as I know the iOS sandbox doesn't do this and no such sandbox is possible from a third party.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |