Changes

#Least Privilege: Applications must be granted the minimum privileges necessary to function

#Minimize Permissions: APIs should be designed in such a way to provide the most functionality without the need to be granted permissions

===Process for granting permissions===

Note: If sensitive permissions are requested, certain security requirements may be placed on the application.

===Management of Permissions===

#Users need to be guided on the consequence of changing permissions, and protected from making choices which are insecure or which could disable their device (e.g. removing the permissions setting capability from the permissions web app)

#Permissions can be modified either through a permission manager application, or set through contextual actions (e.g. response to security prompts including "remember me" checkboxes or through behavior in some cases, e.g. user ignores a prompt five times in a minute, don't prompt again for an hour)

===Default Permission Policy===

A user should be warned before they override the Default Permission Policy in an unsafe way.

===Permission Types===

##Allow

#List of Permissions: TBD

===Trust Model===

#The user is the root source of trust for permissions settings.

#The user can choose to override store permissions (either granting or revoking privileges), but the store permissions should be safe for the user, and represent the minimum permissions the application needs to run.

#The store can also entrust other stores with the power to grant permissions (possibly a subset of permissions, or not privileged permissions)

=== Security Requirements for Critical App Deployment ===

*Will there even be a separate set of requirements, or will threats be mitigated by App Store processes instead?