Difference between revisions of "Native App Security"

From MgmtWiki
Jump to: navigation, search
(Context)
(Context)
Line 9: Line 9:
 
* For the case where the user is not forced to allow an application to run on their personal device, see the page [[Web Site Security]].
 
* For the case where the user is not forced to allow an application to run on their personal device, see the page [[Web Site Security]].
 
* Android App list of [[Data Category|Data Categories]] that require [[User Consent]]. https://support.google.com/googleplay/answer/6270602?hl=en
 
* Android App list of [[Data Category|Data Categories]] that require [[User Consent]]. https://support.google.com/googleplay/answer/6270602?hl=en
 +
* Apple CKContainer managers all attempts to access user data on the device or in iCloud. https://developer.apple.com/documentation/cloudkit/ckcontainer
  
 
==Problems==
 
==Problems==

Revision as of 10:33, 6 August 2018

Full Title and Meme

An application that is installed on a user's computing device with full power to act as the user.

Context

Problems

Solutions

  • The Native App exposes its name and the web site that backs it in a manner that allows the user to make a meaningful trust decision.
  • Joint use Native Apps are provide to some industries for all to use. It makes the trust decision by the user much more difficult.

References

Organizational Support

  • Rules for apps installed on Apple devices
  • Rules for apps installed on Android devices
  • Rules for apps installed on Windows devices are of two types, but it is not clear how the user could possibly distinguish, so the concept has not been helpful.

Other References

  1. The Open Web Application Security Project (OWASP) is a 501(c)(3) worldwide not-for-profit charitable organization focused on improving the security of web site software.
  2. ISACs are member-driven organizations, delivering all-hazards threat and mitigation information to asset owners and operators.