| 引用本文: | 罗杨,张齐勋,沈晴霓,刘宏志,吴中海.多层次的Android系统权限控制方法.软件学报,2015,26(S2):263-271 |
| |
|
| |
|
|
| 本文已被:浏览 3519次 下载 6848次 |
 码上扫一扫! |
|
|
| 多层次的Android系统权限控制方法 |
|
罗杨1,2,3, 张齐勋1,2,3, 沈晴霓1,2,3, 刘宏志1,2,3, 吴中海1,2,3
|
|
1.北京大学软件与微电子学院, 北京 100871;2.网络与软件安全保障教育部重点实验室(北京大学), 北京 100871;3.北京大学服务计算与大数据技术研究室, 北京 100871
|
|
| 摘要: |
| 随着Android智能平台的普及,其安全问题日益受到人们关注.在底层安全方面,部分root工具已经实现了对最新版本Android的root提权,从而给恶意软件滥用权限造成可乘之机;在上层应用安全方面,目前还没有能够在应用权限进行有效管理的方法.基于安全策略的思想,提出了一种Android应用权限动态管理机制,利用安全策略对授权进行描述,在Android框架层设置权限检查点,并调用请求评估算法进行授权评估,从而实现对应用行为的监控.实验结果表明,该方法能够有效管理Android应用权限的正常调用,约束非法调用,并且系统开销较小. |
| 关键词: 权限管理 安全策略 SELinux 请求评估 权限检查 |
| DOI: |
| 分类号: |
| 基金项目:国家科技重大专项(2012ZX03002022);国家自然科学基金(61232005);国家高新技术研究发展计划(863)(2015AA016009) |
|
| Android Multi-Level System Permission Management Approach |
|
LUO Yang1,2,3, ZHANG Qi-Xun1,2,3, SHEN Qing-Ni1,2,3, LIU Hong-Zhi1,2,3, WU Zhong-Hai1,2,3
|
|
1.School of Software and Microelectronics, Peking University, Beijing 100871, China;2.MoE Key Laboratory of Network and Software Assurance(Peking University), Beijing 100871, China;3.Research Laboratory of Service Computing and Big Data Technology, Peking University, Beijing 100871, China
|
| Abstract: |
| With the expansion of the market share occupied by the Android platform, security issues (especially application security) have become attention focus of researchers. In fact, the existing methods lack the capabilities to manage application permissions without root privilege. This study proposes a dynamic management mechanism of Android application permissions based on security policies. The paper first describes the permissions by security policies, then implementes permission checking code and request evaluation algorithm in Android framework layer. Experimental results indicate that the presented approach succeeds in permission management of Android applications, and its system overhead is low, which makes it an effective method for Android permission management. |
| Key words: permission management security policy SELinux request evaluation permission check |
|
|
|
|