In the versions of Android prior to Marshmallow, apps used to declare the permissions (install time permissions)<\/strong> they will require to the application manifest and then post installation, they were able to make use of these permissions without any need for user’s explicit permission. But now, a secondary notification has been added to the user. This will mandate the user’s permission when an application would look to access data (run time permissions)<\/strong> or functionality even if the application is a Google application. This will create an added layer of security for Android and will be helpful in stopping applications that invade our privacy. <\/p>\n The settings will have an option to “turn on” and “turn off” individual application permissions inside the \u2018Apps\u2019 menu or from the \u2018App Info\u2019 screen. This will enable us to use an app, even if we are \u00a0concerned about the application having access to certain permissions, we can easily grant or revoke the permission by the use of the slider\u00a0button in settings. <\/p>\n Encryption will be enabled on Android devices by default. The new devices that come with Marshmallow will have encryption enabled by default with a necessary condition being: The devices which fulfil the above-mentioned criteria will be enabled with encryption of the private user data partition\u00a0and the public data partition which resides in \/data<\/span> and \/sdcard<\/span>\u00a0respectively.<\/p>\n More details can be found in\u00a0Android 6.0 Compatibility Definition Document (CDD)<\/a>.<\/p>\n A new field \u2018Android security patch level\u2019 is added in the latest version of Android. It can\u00a0be found in the \u2018About Phone\u2019 settings. This would be a better indicator for users so as to understand what is the up-to-date level of their device. In the earlier versions, there was some build number, but with the introduction of this field the patch level is represented in a much more meaningful month\/day\/year format. <\/p>\n “It should make it really simple for users to understand the state of the device. The feature is part of Android’s attempt at making sure that security information and patch level information is available to users”<\/em><\/p><\/blockquote>\n –\u00a0Adrian Ludwig, the lead security engineer for Android<\/p>\n It will be interesting to see how these security features pan out once devices start getting Marshmallow update.<\/p>\n
\nHence, the replacement of the existing install time permissions<\/span>\u00a0approach with the run time permissions<\/span> approach will make sure that the user is prompted for permission each time the application accesses some data.
\n![\"howtogeek\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/11\/howtogeek.png\")
<\/p>\nSource:\u00a0howtogeek.com<\/h6>\n
Setting the individual application permissions<\/span><\/h3>\n
\n![\"pcworld.com\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/11\/pcworld.com_.jpg\")
<\/p>\nSource: computerworld.com<\/h6>\n
Encryption enabled Device<\/span><\/h3>\n
\n– AES crypto performance above 50MiB-per-second<\/p>\n![\"engadget.com\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/11\/engadget.com_.jpg\")
\nSource:\u00a0engadget.com<\/h6>\nAndroid security patch level<\/span><\/h3>\n
![\"\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/11\/rsz_arstechnicacom.jpg\")
<\/p>\nSource: arstechnica.com<\/h6>\n
\n![\"\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/11\/patch3.png\")
<\/p>\nSource:\u00a0Android 6.0 Compatibility Definition Document (CDD)<\/a><\/h6>\n