WO2013185413A1 - 应用权限的控制方法及装置 - Google Patents

应用权限的控制方法及装置 Download PDF

Info

Publication number
WO2013185413A1
WO2013185413A1 PCT/CN2012/079659 CN2012079659W WO2013185413A1 WO 2013185413 A1 WO2013185413 A1 WO 2013185413A1 CN 2012079659 W CN2012079659 W CN 2012079659W WO 2013185413 A1 WO2013185413 A1 WO 2013185413A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
policy
permission
monitoring
trust level
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2012/079659
Other languages
English (en)
French (fr)
Inventor
鲁司运
张贞志
钟声
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to US14/415,650 priority Critical patent/US20150222641A1/en
Priority to EP12879120.9A priority patent/EP2861003A4/en
Publication of WO2013185413A1 publication Critical patent/WO2013185413A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/105—Multiple levels of security
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for controlling application rights.
  • BACKGROUND With mobile terminals entering the era of intelligence, on the free and open intelligent mobile terminal platform, due to the large number of developers of application software, the quality is also uneven, which makes it difficult to ensure security.
  • Application software can be easily implanted with malicious code that contains malicious deductions, stealing user privacy information, etc., posing a serious threat to security.
  • the security monitoring capability of the intelligent mobile terminal system is relatively weak, which can only ensure the stability of the downloading program and the data integrity, and cannot effectively verify the source of the mobile application software, lacking comprehensive testing and effective verification mechanism.
  • the present invention provides a method and apparatus for controlling application rights, so as to solve at least one security system for controlling application rights in a related art, in the process of downloading and running an application, a mobile terminal has rights It is not clear that the mobile terminal has a large security risk.
  • a method for controlling an application authority including: acquiring a trust level of an application according to signature information of an application, where the application includes at least one of the following: an application to be downloaded, an application to be installed The installed application controls the permissions of the application according to the trust level and the preset monitoring policy.
  • obtaining the trust level of the application according to the signature information of the application comprises: acquiring signature information of the application; matching the signature information with a certificate public key of one or more preset certificates in the mobile terminal, and according to different The matching result sets a different trust level for the application.
  • setting different trust levels of the application according to different matching results includes: recording a number of the signature information matching the certificate public key or a name of the certificate; according to the number of matching or the name of the certificate Set the trust level of the app.
  • controlling the rights of the application according to the trust level and the preset monitoring policy comprises: determining whether the rights currently used by the application are rights in the system default monitoring policy; if yes, in the system The policy corresponding to the trust level is searched for in the default monitoring policy, and the rights of the application are controlled according to the corresponding policy.
  • the searching for the policy corresponding to the trust level in the system default monitoring policy includes: determining whether there is an application monitoring policy corresponding to the currently used permission of the application, where the application monitoring policy is used to indicate the right The time period during which the usage is monitored; if yes, the policy corresponding to the trust level is searched for in the application monitoring policy.
  • the method further includes: saving and analyzing a control process of the rights currently used by the application to obtain a processing policy; The control process of applying the currently used permissions is synchronized to the cloud server to obtain a processing policy.
  • a control device for applying an application which is applied to a mobile terminal, includes: an obtaining module, configured to acquire a trust level of an application according to signature information of the application, where the application includes at least the following The application to be downloaded, the application to be installed, and the installed application; the control module is configured to control the authority of the application according to the trust level and the preset monitoring policy.
  • the obtaining module includes: an acquiring unit, configured to acquire signature information of the application; and a matching unit configured to match the signature information with a certificate public key of one or more preset certificates in the mobile terminal ; Set the unit, set to set different trust levels of the application according to different matching results.
  • the control module includes: a determining unit, configured to determine whether the currently used permission of the application is a right in a system default monitoring policy; and the searching unit is configured to be in the current default permission of the system default monitoring policy In the case of the system default monitoring policy, the policy corresponding to the trust level is searched; and the control unit is configured to control the rights of the application according to the corresponding policy.
  • the device further comprises: a saving module, configured to save and analyze a control process of the authority currently used by the application to obtain a processing policy; or set to synchronize the control process of the currently used permission of the application to Cloud server to get processing strategy.
  • the present invention adopts the following method:
  • the acquired trust level is added to the control process of the application authority, and the corresponding monitoring policy is preset for the trust level.
  • the security system for controlling the application authority is not solved in the related art.
  • the mobile terminal In the process of downloading and running the application, the mobile terminal has a large security risk due to the unclear authority of the application.
  • the problem in turn, provides a more secure and comprehensive monitoring method for application rights, which improves the performance of the mobile terminal.
  • FIG. 1 is a flowchart of a method for controlling application authority according to an embodiment of the present invention
  • FIG. 2 is a flowchart of an application trust level acquisition according to a preferred embodiment of the present invention
  • FIG. 3 is a preferred implementation according to the present invention.
  • FIG. 4 is a flowchart of an application control policy generation process according to a preferred embodiment of the present invention
  • FIG. 5 is a flow chart of application authority monitoring according to a preferred embodiment of the present invention
  • FIG. 6 is a flowchart of a system default monitoring policy generation process according to a preferred embodiment 2 of the present invention
  • FIG. 7 is a flowchart of a process for monitoring application usage rights according to a preferred embodiment of the present invention
  • FIG. 8 is a flowchart according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram 2 of a control device for applying rights according to an embodiment of the present invention
  • FIG. 10 is a structural block diagram 3 of a control device for applying rights according to an embodiment of the present invention
  • 11 is a structural block diagram of a control device for applying authority according to an embodiment of the present invention
  • FIG. 12 is a preferred implementation according to the present invention.
  • the mobile terminal has weak application monitoring capability, and its main performance is as follows: (1) There is no effective support and verification means for the trustworthiness level of the application software, and the trust level of the application is the basis for effective monitoring permission use. This also leads to the inability to effectively classify and monitor the use of application rights; (2) By default, the monitoring rights are relatively large and the monitoring is too cumbersome.
  • the user privacy information including message records, contact records, call records, etc.
  • mobile device local connection permissions including WIFI connection, Bluetooth connection, etc.
  • monitoring In view of the above problem, the embodiment of the present invention provides a method for controlling the application authority. The process of the method is as shown in FIG.
  • Step S102 obtaining a trust level of the application according to the signature information of the application, where The application includes at least one of the following: an application to be downloaded, an application to be installed, and an installed application; Step S104, controlling the permission of the application according to the trust level and the preset monitoring policy.
  • the obtained trust level is added to the control process of the application authority, and the corresponding monitoring policy is preset for the trust level, and the security system for controlling the application authority is not solved in the related technology, and the mobile terminal is in the During the process of downloading and running the application, the application has the privilege of being unclear, which causes the mobile terminal to have a large security risk.
  • obtaining the trust level of the application according to the signature information of the application may include: acquiring signature information of the application; matching the signature information with a certificate public key of one or more preset certificates in the mobile terminal, and matching according to different The result setting applies a different level of trust.
  • the setting of different trust levels according to different matching results may further include: recording the number of signature information matching the certificate public key or the name of the certificate; the trust level applied according to the number of matching settings or the name of the certificate.
  • the level of trust can be expressed in the form of trust and non-trust, or in the form of different levels of trust, such as first-level trust, second-level trust, and so on.
  • the trust level can be set by recording the name of the certificate, for example, "vendor trust level”, “operator trust level”, "third party partner trust level”, etc., through one of the certificates Obtain the trust level corresponding to a certificate; Second, the trust level can also be based on the number of different authentication certificates.
  • the level for example, by passing two authentication certificates, the level is set to one level, that is, "level one trust level", or the application is set to level two when two authentication certificates are set.
  • a matching threshold may be set, that is, when the number of matching information of the application and the certificate public key reaches a preset number, the application is determined.
  • the trust level is trust.
  • the matching threshold may also be set to pass a certain fixed certificate. For example, if the application matches the carrier certificate, the application is determined.
  • the trust level is trust, as long as it fails to pass the carrier certificate, it is considered to be untrusted.
  • the above trust levels can be set according to the different needs of different users.
  • the policy corresponding to the trust level is searched, and the privilege of the application is controlled according to the corresponding policy. If it is not the permission in the system default monitoring policy, you can not control the permission.
  • the privilege exists in the system default monitoring policy you need to find the policy corresponding to the application trust level in the system default monitoring policy.
  • the policy corresponding to the trust level may be searched in the application monitoring policy.
  • the player's trust level is level 3.
  • the contact database is The system defaults to monitor permissions in the policy. If yes, find the control policy of the player with the trust level of 3 in the system default monitoring policy. If the level 3 trust level and the level 3 trust level do not control when the sensitive authority is touched, the player access control database is not controlled; if the level 1 to 3 trust level application touches the permission, control is required. Then record the control process or alarm when the player accesses the contact database, or record and alarm at the same time.
  • the Internet access permission is a sensitive permission.
  • the use process of the Internet access right is recorded for subsequent processing.
  • the current privilege does not have a corresponding application monitoring policy record. Therefore, the system can pop up a prompt box to remind the user to wait for the receiving user to set the privilege monitoring policy. Then, the user's monitoring settings for the permission (full-time monitoring/full-time monitoring/intra-period monitoring) are converted into application monitoring policies used by the rights, and the monitoring policy record values recorded by the system are saved and updated.
  • the usage of the permission can be monitored according to the policy.
  • the control process of the currently used permission may be analyzed to obtain a processing policy, or the control process of the currently used permission of the application may be synchronized to the cloud server to obtain a processing policy. If you select the local process of analyzing the usage rights of the application, you can present the record of the process to the user, the user. If the process is synchronized to the cloud server to obtain a processing policy, the cloud server analyzes the process according to the synchronization process, and sends the analysis result to the mobile terminal, so that the user can perform the processing policy according to the analysis of the cloud server. deal with.
  • the preferred embodiment of the present invention provides a method for controlling the application rights.
  • the mobile terminal is used as an example for the mobile phone. FIG.
  • Step S202 performing application package information parsing processing during boot scan or application installation.
  • Step S204 Extract the signature information data of the application according to the result of the application packet parsing process, and record the data.
  • Step S206 performing authentication processing on the application signature information and the public key file of the mobile phone pre-made digital certificate, and determining whether the authentication is passed. If the authentication is performed by performing step S208, otherwise step S210 is performed.
  • Step S208 the trust level corresponding to the digital certificate passed the authentication is given, for example: "vendor trust level",
  • step S210 the application is given an "untrustable level”.
  • step S212 the application trust level obtained by the authentication is recorded in the attribute configuration file corresponding to the application, and is treated as a normal attribute of the application. As shown in FIG.
  • Step S302 loading a configuration file of a system default monitoring policy.
  • the preset system default monitoring policy configuration file is first loaded in the specified system directory.
  • Step S304 performing parsing processing of the system default monitoring policy configuration file, and obtaining a permission list that each application module needs to monitor.
  • Step S306 the parsed permission list of each application module obtained by the parsing is recorded into the memory data structure to generate a system default monitoring policy.
  • Step S402 when it is detected that the current application uses the sensitive authority in the system, the process proceeds to step 404.
  • the sensitive permissions may be customized according to the needs of the user, for example, the rights related to the user's payment class, or the user privacy information class rights.
  • Step S404 determining whether the permission belongs to a permission required to be controlled by the system default control policy. If it does not belong to the control required for the system default control policy, step S406 is performed, and if yes, step S408 is performed. In step S406, the usage of the permission required for monitoring by the non-system default monitoring policy is ignored.
  • Step S408 determining whether an application monitoring policy used by the permission already exists. If there is no application monitoring policy used by the permission, step S410 is performed, and if yes, step S412 is performed. Step S410, the application monitoring policy without the permission does not perform monitoring processing. Step S412, monitoring according to an application monitoring policy. Step S414, recording the permission usage of the application.
  • FIG. 5 shows the overall flow of monitoring application rights. The entire monitoring process will be described below with reference to FIG. 5. The process includes steps S502 to S518: Step S502, when it is detected that the application system sensitive authority is accessed, the process proceeds to step S504. Step S504, determining whether the privilege belongs to a privilege defined in the system default control policy.
  • step S506 is performed. If yes, step S508 is performed. Step S506, since the permission is a permission required for the non-system default control policy, the use of the permission is not monitored. For example, when the sensitive permission accessed by the user involves the local connection class permission of the mobile device, if it is not in the system default control policy, the permission is not controlled.
  • Step S508 determining whether an application monitoring policy of the authority already exists. If yes, step S510 is performed, and if not, step 512 is performed. Step S510: Obtain an application monitoring policy record of the privilege, and monitor usage of the privilege according to the application monitoring policy.
  • Step S512 Since the current permission does not have a record of the corresponding permission monitoring policy, the pop-up prompt box prompts the user that the current system sensitive permission is being used, and does not monitor the permission, and waits for the receiving user to further set the permission monitoring.
  • Step S514 receiving a setting of a monitoring policy of the user for the authority.
  • Step S516, converting the monitoring setting of the authority to the application monitoring policy used by the authority, and saving and updating the monitoring policy record value recorded by the system, wherein the monitoring setting may be full time monitoring, full time monitoring, time monitoring, etc. Settings.
  • the implementation of the preferred implementation can effectively classify the mobile terminal application based on the trust level, and perform classification management of the key authority usage according to the application trust level classification.
  • This embodiment can target the mobile phone for different control requirements of the manufacturer or the user.
  • Key access control is customizable and dynamically tunable.
  • the user can easily realize the management and control of the key sensitive permission group of the mobile phone terminal, and can effectively manage and control the security threat behavior that may exist in the mobile phone application, thereby effectively ensuring the security of the mobile phone.
  • Preferred Embodiment 2 The embodiment of the present invention can implement monitoring of a sensitive privilege group on a smart phone that is most vulnerable to malicious intrusion and most needs to be protected by software.
  • the monitored privilege group can include: sending a message, calling, and network traffic access.
  • the monitoring using the permission of the "non-trusted application” is taken as an example.
  • the monitoring principle and processing flow of the application permission under other trust levels are similar.
  • the system default monitoring policy is set, and the sending of the message, the call, the network traffic access, and the like to the "untrusted application trust level" need to be controlled, the configuration file is defined in the xml file format, and the defined configuration file is defined.
  • the content is as follows:
  • sysControlPermission tag represents this is the system default control permission
  • trustLevel tag represents the permission trust level
  • "unApproved” means the permission is not trusted to be monitored
  • permission tag represents The authority to be monitored under the trust level
  • D_SMS represents the sending of the message permission
  • CALL_PHO E represents the call permission
  • ACCES S_INTERNET represents the network traffic access
  • ACCES S_MES S AGE represents the access message record permission
  • ACCESS_CONTACTS represents the access contact record permission
  • ACCES S MES SAGE stands for access message record permission
  • ACCES S CALLLOG stands for access call record permission
  • ACCESS_LOCATION stands for access to personal geographical location information (including GPS location and base station location)
  • the listed monitoring rights may be modified or decreased as needed, and the control principle and process are similar.
  • FIG. 6 the figure is a flowchart of a system default monitoring policy generation process of rights, and the process includes steps S602 to S606:
  • step S602 when the system is initialized at boot time, the preset system default monitoring policy configuration file is first loaded in the specified system directory.
  • step S604 performing parsing processing of the system default monitoring policy configuration file, and parsing the permission list required for monitoring the "untrusted monitoring permission”.
  • Step S606 Record the permission list that is parsed and required to be monitored into the memory data to form a system default monitoring policy.
  • Step S702 when it is detected that the application uses the rights, step S704 is performed. For example, if a playback application is recorded to its access contact database during use, then step S704 is performed. Step S704, obtaining the permission of the application, and comparing the permission with the system default permission list. Step S706, determining whether the permission belongs to the authority of the system default control. If it is not the authority of the system default control, step S708 is performed, and if it is, step S710 is performed. In step S708, since the permission is a non-system default control authority, the usage of the permission is not monitored. Step S710, determining whether an application monitoring policy used for the permission already exists.
  • step S712 Obtain an application monitoring policy record of the authority, and perform permission monitoring according to the monitoring policy.
  • step S714 Since the current permission does not have a corresponding application monitoring policy record, the system prompts a prompt box to remind the user, and waits for the receiving user to set the permission monitoring policy.
  • Step S718 Convert the user's monitoring settings (full-time monitoring/full-time non-monitoring/intra-period monitoring) to the application monitoring policy used by the authority, and save and update the monitoring policy record value recorded by the system.
  • Step S720 monitoring the permission usage according to the user's selection.
  • Step S722 saving or synchronizing the monitoring information to the cloud server.
  • Step S724 analyzing the saved data according to the analysis policy or feeding back the cloud processing policy to the user.
  • the preferred embodiment can perform the rights control according to different applications, and can separately monitor and manage the rights of the mobile application (sending a message, making a call, accessing network traffic, etc.), and can be flexibly adjusted according to the actual monitoring requirements and scenarios of the user.
  • Application monitoring policy for application permissions The preferred embodiment can realize the purpose of monitoring and managing the rights of the mobile phone terminal, and can effectively detect, promptly remind and prevent the security threat behavior that the mobile terminal authority is maliciously infringed, thereby effectively ensuring the security of the mobile terminal authority.
  • the embodiment of the present invention further provides a control device for applying rights, and the device can be applied to the detection of the security of the application rights in the mobile terminal.
  • the structural block diagram of the device can be as shown in FIG. 8 , and includes: acquiring module 10, setting
  • the application includes the following at least one of the following: an application to be downloaded, an application to be installed, an installed application, and a control module 20 coupled with the obtaining module 10 and configured to be trusted according to the trust information of the application. Levels and preset monitoring policies control the permissions of the application.
  • the 9 may further include: an obtaining unit 102 configured to acquire signature information of the application; a matching unit 104 coupled with the obtaining unit 102, configured to set the signature information and one or more of the mobile terminal The certificate public key of the preset certificate is matched; the setting unit 106 is coupled with the matching unit 104, and is set to apply different trust levels according to different matching result settings.
  • the obtaining module 10 may also be configured to record the number of matching signature information and the certificate public key; and set the trust level of the application according to the number of matching.
  • the control device for the application authority may also be as shown in FIG.
  • control module 20 may include: a determining unit 202, configured to determine whether the permission currently used by the application is a permission in the system default monitoring policy;
  • the unit 204 is coupled to the determining unit 202, and is configured to search for a policy corresponding to the trust level in the system default monitoring policy if the current right is the right in the system default monitoring policy;
  • the control unit 206 is coupled with the searching unit 204, and is configured to Control the permissions of the application according to the corresponding policy.
  • the control module 20 may also be configured to determine whether there is an application monitoring policy of the current authority; if yes, the policy corresponding to the trust level is searched in the application monitoring policy.
  • 11 further includes a saving module 30 coupled with the control module 20, configured to save and analyze the control process of the currently used authority to obtain a processing policy; or to apply the currently used permission.
  • the control process is synchronized to the cloud server for processing strategies.
  • the preferred embodiment provides a control device for applying rights, and the device implements an application trust level grading mechanism based on signature authentication, which can effectively classify pre-built/installed applications in the mobile phone based on trust levels; Privilege monitoring management strategy, and can realize the formulation of the monitoring strategy according to the user's needs, and can flexibly adjust the permission required for each application to be monitored; at the same time, it has the ability to use the monitoring policy based on the application as the monitoring unit, that is, The user can define the monitoring policy of the application to use the permission according to the actual needs. Under the support of the application trust level and the permission monitoring policy and the log analysis policy mechanism, the dynamic monitoring function of the key sensitive authority of the mobile phone system is realized.
  • the naming of each module is slightly different from the module naming of the device in the above embodiment, but the combination of the modules in the embodiment can achieve the same function as the device of the above embodiment.
  • This embodiment includes the following modules:
  • Authentication module Implements the application trust level authentication function. When scanning the mobile phone pre-production application/downloading and installing the application, the authentication module will parse the application signature information, and at the same time with the mobile phone pre-made certificate (including the pre-made "vendor signature certificate”, “Operator Signing Certificate”, “3rd Party Partner Signing Certificate”, etc. are authenticated, and different trust level attributes are applied according to the application signature information and the certificate public key authentication result.
  • Monitoring policy module Adopting the policy definition mechanism based on the configuration file mode, the application rights access monitoring strategy is divided into the "system default monitoring policy" and the "application monitoring strategy” level 2 management strategy system. Among them, the "system default monitoring policy” defines the sensitive permissions that need to be monitored by the application at all levels.
  • the "application monitoring policy” records the monitoring policies used by each specific application for each sensitive permission (full-time monitoring/full-time monitoring/time monitoring), and the specific policy is generated by dynamically recording the user's permission monitoring setting operation.
  • Permission use log module Realize the preservation of the monitoring process.
  • (2) extended application trust level and monitoring policy mechanism realize the sensitive permissions on the mobile phone that are most vulnerable to abuse and need to be protected. Dynamic monitoring of groups.
  • the permission monitoring module obtains the trust level attribute to which the application belongs; secondly, the specific monitoring policy of the right is determined by the monitoring policy module according to the application trust level; and the application is determined according to the confirmed monitoring policy.
  • the use of the permission is monitored.
  • the monitoring forms include: full-time monitoring, full-time monitoring, and time-of-day monitoring. When no monitoring form is found, the corresponding application control policy is dynamically saved/updated according to the user's settings.
  • Permission usage monitoring module Used to implement background monitoring operation.
  • the schematic diagram of the preferred embodiment may be as shown in FIG. 12.
  • the monitoring policy module is first invoked, the pre-made monitoring policy configuration file is loaded and parsed, and then the system default monitoring permission is generated according to the parsed result. Strategy.
  • the authentication module is called, and then the loading permission is monitored in the background using the monitoring module.
  • the foregoing embodiment implements at least one of the following technical effects:
  • the present invention adopts the following method: adding the acquired trust level to the control process of the application authority, and pre-determining the trust level The corresponding monitoring strategy is set.
  • the mobile terminal In the process of downloading and running the application, the mobile terminal has a large security risk due to the unclear authority of the application.
  • the problem provides a more secure and comprehensive monitoring method for application rights, which improves the performance of the mobile terminal.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Storage Device Security (AREA)

Abstract

本发明公开了一种应用权限的控制方法及装置，其中，该方法包括：根据应用的签名信息获取应用的信任等级，其中，应用包括以下至少之一：待下载的应用、待安装的应用、已经安装的应用；依据信任等级和预置的监控策略对应用的权限进行控制。通过运用本发明，解决了相关技术中没有一种对应用权限进行控制的安全体系，移动终端在下载、运行应用等过程中，由于应用具有的权限不明确，致使移动终端存在很大的安全隐患的问题，进而提供了一种较为安全且全面的应用权限的监控方法，提升了移动终端的性能。

Description

应用权限的控制方法及装置 技术领域 本发明涉及通信领域， 具体而言， 涉及一种应用权限的控制方法及装置。 背景技术 随着移动终端进入智能时代， 在自由、 开放的智能移动终端平台上， 由于应用软 件的开发者较多， 质量也参差不齐， 使其安全性难以得到保证。 应用软件容易被植入 含有恶意扣费、 窃取用户隐私信息等行为的恶意代码， 从而对安全造成严重威胁。 当前智能移动终端系统的安全监控能力相对薄弱， 其只能保证对下载程序的稳定 性、 数据完整性进行检测， 而无法有效的验证手机应用软件的来源， 缺乏全面的测试 及有效的验证机制， 也无法对安装后的应用程序可能存在安全威胁行为进行有效的监 控， 因而无法对移动终端的安全性进行有效的保证。 相关技术中没有一种对应用权限进行控制的安全体系， 移动终端在下载、 运行应 用等过程中， 由于应用具有的权限不明确， 致使移动终端存在很大的安全隐患。 发明内容 本发明提供了一种应用权限的控制方法及装置， 以至少解决相关技术中没有一种 对应用权限进行控制的安全体系， 移动终端在下载、 运行应用等过程中， 由于应用具 有的权限不明确， 致使移动终端存在很大的安全隐患的问题。 根据本发明的一个方面， 提供了一种应用权限的控制方法， 包括： 根据应用的签 名信息获取应用的信任等级， 其中， 所述应用包括以下至少之一： 待下载的应用、 待 安装的应用、 已经安装的应用； 依据所述信任等级和预置的监控策略对所述应用的权 限进行控制。 优选地， 根据应用的签名信息获取应用的信任等级包括： 获取所述应用的签名信 息； 将所述签名信息与移动终端内的一个或多个预置证书的证书公钥进行匹配， 并根 据不同匹配结果设置所述应用不同的信任等级。 优选地， 根据不同匹配结果设置所述应用不同的信任等级包括： 记录所述签名信 息与所述证书公钥匹配的个数或所述证书的名称； 依据匹配的个数或所述证书的名称 设置所述应用的信任等级。 优选地， 依据所述信任等级和预置的监控策略对所述应用的权限进行控制包括： 判断所述应用当前使用的权限是否为系统默认监控策略中的权限； 如果是， 则在所述 系统默认监控策略中查找所述信任等级对应的策略， 并根据所述对应的策略控制所述 应用的权限。 优选地， 在所述系统默认监控策略中查找所述信任等级对应的策略包括： 判断是 否存在与所述应用当前使用的权限对应的应用监控策略， 其中， 所述应用监控策略用 于指示对权限使用情况进行监控的时间段； 如果是， 则在所述应用监控策略中查找所 述信任等级对应的策略。 优选地， 依据所述信任等级和预置的监控策略对所述应用的权限进行控制之后， 还包括： 将所述应用当前使用的权限的控制过程进行保存和分析以获得处理策略； 或 将所述应用当前使用的权限的控制过程同步到云端服务器以获得处理策略。 根据本发明的另一方面， 提供了一种应用权限的控制装置， 应用于移动终端， 包 括： 获取模块， 设置为根据应用的签名信息获取应用的信任等级， 其中， 所述应用包 括以下至少之一： 待下载的应用、 待安装的应用、 已经安装的应用； 控制模块， 设置 为依据所述信任等级和预置的监控策略对所述应用的权限进行控制。 优选地， 所述获取模块包括： 获取单元， 设置为获取所述应用的签名信息； 匹配 单元， 设置为将所述签名信息与移动终端内的一个或多个预置证书的证书公钥进行匹 配； 设置单元， 设置为根据不同匹配结果设置所述应用不同的信任等级。 优选地， 所述控制模块包括： 判断单元， 设置为判断所述应用当前使用的权限是 否为系统默认监控策略中的权限； 查找单元， 设置为在所述当前权限为系统默认监控 策略中的权限的情况下， 在所述系统默认监控策略中查找所述信任等级对应的策略； 控制单元， 设置为根据所述对应的策略控制所述应用的权限。 优选地， 所述装置还包括： 保存模块， 设置为将所述应用当前使用的权限的控制 过程进行保存和分析以获得处理策略； 或设置为将所述应用当前使用的权限的控制过 程同步到云端服务器以获得处理策略。 本发明采用了如下方法： 将获取的信任等级加入到对应用权限的控制过程中， 并 为信任等级预置了相应的监控策略。 通过运用本发明， 解决了相关技术中没有一种对 应用权限进行控制的安全体系， 移动终端在下载、 运行应用等过程中， 由于应用具有 的权限不明确， 致使移动终端存在很大的安全隐患的问题， 进而提供了一种较为安全 且全面的应用权限的监控方法， 提升了移动终端的性能。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据本发明实施例的应用权限的控制方法的流程图； 图 2是根据本发明优选实施例一的应用信任等级获取的流程图； 图 3是根据本发明优选实施例一的系统默认监控策略生成方法的流程图； 图 4是根据本发明优选实施例一的应用控制策略生成过程的流程图； 图 5是根据本发明优选实施例一的应用权限进行监控的流程图； 图 6是根据本发明优选实施例二的系统默认监控策略生成过程的流程图； 图 7是根据本发明优选实施例二的监控应用使用权限的处理流程； 图 8是根据本发明实施例的应用权限的控制装置的结构框图一； 图 9是根据本发明实施例的应用权限的控制装置的结构框图二； 图 10是根据本发明实施例的应用权限的控制装置的结构框图三； 图 11是根据本发明实施例的应用权限的控制装置的结构框图四； 以及 图 12是根据本发明优选实施例三的应用权限的控制装置的结构示意图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 相关技术中移动终端对应用监控能力较为薄弱，其主要表现在以下几个方面： （1 ) 对应用软件的可信任等级缺乏有效的支持及验证手段， 而应用的信任等级是有效监控 权限使用的基础， 这也就导致无法很好的对应用权限使用进行有效分类监控； （2) 默 认需监控权限相对比较多和监控过于繁琐， 用户的实际需求可能只是对某些权限进行 监控； （3 ) 由于开发平台较为开放， 因此对移动终端应用的权限使用控制比较宽松， 绝大部分的权限应用开发者只需要声明即可获取， 例如， 手机设备上的敏感权限， 其 中， 涉及用户付费类的权限（包括发送消息、 拨打电话、 上网等）、 用户隐私信息类权 限（包括消息记录、联系人记录、通话记录等）、手机设备本地连接类权限（包括 WIFI 连接、 蓝牙连接等） 等使用未进行有效的监控。 鉴于上述问题， 本发明实施例提供了一种应用权限的控制方法， 该方法的流程如 图 1所示， 包括步骤 S102至步骤 S104: 步骤 S102, 根据应用的签名信息获取应用的信任等级， 其中， 应用包括以下至少 之一： 待下载的应用、 待安装的应用、 已经安装的应用； 步骤 S104, 依据信任等级和预置的监控策略对应用的权限进行控制。 本实施例将获取的信任等级加入到对应用权限的控制过程中， 并为信任等级预置 了相应的监控策略， 解决了相关技术中没有一种对应用权限进行控制的安全体系， 移 动终端在下载、 运行应用等过程中， 由于应用具有的权限不明确， 致使移动终端存在 很大的安全隐患的问题， 进而提供了一种较为安全且全面的应用权限的监控方法， 提 升了移动终端的性能。 在实施过程中， 根据应用的签名信息获取应用的信任等级可以包括： 获取应用的 签名信息； 将签名信息与移动终端内的一个或多个预置证书的证书公钥进行匹配， 并 根据不同匹配结果设置应用不同的信任等级。 其中， 根据不同匹配结果设置应用不同的信任等级还可以包括： 记录签名信息与 证书公钥匹配的个数或证书的名称； 依据匹配的个数设置或证书的名称应用的信任等 级。 在实施的过程中， 信任等级可以以信任和非信任的形式体现， 也可以以不同信任 等级的形式体现， 例如一级信任， 二级信任等。 在上述步骤实施的过程中， 当以不同信任等级的形式体现时， 还可以分为两种情 况。 第一种， 信任等级可以通过记录证书的名称来进行设置， 例如， "厂商信任级别"、 "运营商信任级别"、 "第 3方合作厂商信任级别"等， 则通过其中某个证书就可以获 得某个证书对应的信任级别； 第二种， 信任等级也可以根据通过不同认证证书的个数 对级别进行设置， 例如， 通过两个认证证书， 则级别设置为一级， 即"一级信任级别"， 或者设置通过两个认证证书的情况下该应用被设置为二级等。 当信任等级以信任和非信任的形式体现时， 则可以设定一个匹配阈值， 即当该应 用的签名信息与证书公钥匹配的个数达到一个预设的个数时， 则确定该应用的信任等 级为信任， 当该信任应用触及敏感权限时， 可以选择不对其操作权限进行控制； 上述 匹配阈值还可以设置为通过某一固定证书， 例如， 只要与运营商证书匹配后， 则确定 该应用的信任等级是信任， 只要无法通过运营商证书的， 都认为是非信任。 上述信任 等级可根据不同用户的不同需求进行相应的设定。 在步骤 S102 执行后， 判断应用当前使用的权限是否为系统默认监控策略中的权 限。 如果是， 说明该权限是用户重视的权限， 则在系统默认监控策略中查找信任等级 对应的策略， 并根据对应的策略控制应用的权限。 如果不是系统默认监控策略中的权 限， 则可以不对该权限进行控制。 在系统默认监控策略中存在该权限时， 需要在系统默认监控策略中查找该应用信 任等级对应的策略。 执行过程中， 需要判断是否存在当前使用的权限对应的应用监控 策略。 如果存在应用监控策略， 则可以在应用监控策略中查找信任等级对应的策略， 例如， 播放器的信任等级为 3级， 当检测到该播放器访问联系人数据库时， 则判断联 系人数据库是否为系统默认监控策略中的监控权限。 如果是， 则在系统默认监控策略 中查找信任等级为 3级的播放器的控制策略。 如果 3级信任等级及 3级以上的信任等 级触及该敏感权限时不进行控制， 则不对该播放器访问联系人数据库进行控制； 如果 1至 3级信任等级的应用触及该权限时需要进行控制， 则记录该控制过程或对该播放 器访问联系人数据库时进行报警， 或同时记录并报警。 在一个实施例中， 上网权限为敏感权限， 当移动终端检测一个游戏应用在凌晨 3 点钟使用了上网权限， 则将上网权限的使用过程进行记录， 以进行后续处理。 在不存在当前权限的应用监控策略时， 由于当前权限还没有对应的应用监控策略 记录， 因此， 系统可以弹出提示框提醒用户， 等待接收用户设置该权限监控策略。 然 后将用户对于该权限的监控设置（全时段监控 /全时段不监控 /时段内监控）转化为权限 使用的应用监控策略， 保存和更新系统记录的监控策略记录值。 此时， 系统具备了应 用监控策略， 则可以根据该策略对该权限使用进行监控。 在上述步骤结束后， 可以将应用当前使用的权限的控制过程进行分析以获得处理 策略， 或将应用当前使用的权限的控制过程同步到云端服务器以获得处理策略。 如果 选择本地对应用使用权限的过程进行分析， 则可以将该过程的记录呈现给用户， 用户 根据实际情况进行处理； 如果选择同步到云端服务器以获得处理策略的方式， 则云端 服务器根据同步的过程进行分析， 并将分析结果发送给移动终端， 以便用户根据云端 服务器的分析获得的处理策略进行处理。 优选实施例一 本优选实施例提供了一种应用权限的控制方法， 在本优选实施例中， 以移动终端 为手机为例， 进行说明。 图 2示出应用信任等级获取的流程， 包括步骤 S202至步骤 S212: 步骤 S202, 开机扫描或应用安装时进行应用包信息解析处理。 在开机进行应用扫 描或者是进行新应用的安装时， 首先进行对应用包进行解压操作， 并完成对应用包信 息的解析处理。 步骤 S204, 根据对应用包解析处理的结果， 提取出应用的签名信息数据， 并记录 下来。 步骤 S206, 将应用签名信息与手机预制数字证书的公钥文件进行认证处理， 判断 认证是否通过。 如果认证通过执行步骤 S208, 否则执行步骤 S210。 步骤 S208,赋予认证通过的数字证书所对应的信任级别，例如： "厂商信任级别"、
"运营商信任级别"、 "第 3方合作厂商信任级别"等； 或者也可以根据通过不同认证 证书的个数对级别进行设置， 例如， 通过一个认证证书， 则级别设置为一级， 即 "一 级信任级别"， 或者设置通过两个认证证书的情况下该应用被设置为一级。执行完该步 骤则进入步骤 S212。 步骤 S210， 赋予该应用 "不可信任级别"。 步骤 S212, 将认证得到的应用信任级别记录到应用对应的属性配置文件中， 作为 应用的一个常态属性对待。 如图 3所示， 该图为系统默认监控策略生成方法的流程图， 该流程包括步骤 S302 至步骤 S306: 步骤 S302, 加载系统默认监控策略的配置文件。 实施中， 系统开机时初始化时， 首先会在指定的系统目录加载预置好的系统默认监控策略配置文件。 步骤 S304， 进行系统默认监控策略配置文件的解析处理， 得到各应用模块所需监 控的权限列表。 步骤 S306, 将解析得到的各应用模块所需监控的权限列表记录到内存数据结构 中， 生成系统默认监控策略。 图 4是应用控制策略生成过程的流程图， 该流程包括步骤 S402至步骤 S414: 步骤 S402, 当监测到当前应用使用到系统中的敏感权限时， 进入步骤 404。其中， 在该步骤中， 敏感权限可以根据用户的需求进行自定义， 例如， 涉及用户付费类的权 限， 或用户隐私信息类权限等。 步骤 S404, 判断该权限是否属于系统默认控制策略所需控制的权限。 若不属于系 统默认控制策略所需控制的权限， 执行步骤 S406, 若属于， 则执行步骤 S408。 步骤 S406, 忽略非系统默认监控策略所需监控的权限使用。 步骤 S408, 判断是否已经存在该权限使用的应用监控策略。 若不存在该权限使用 的应用监控策略， 则执行步骤 S410, 若存在， 执行步骤 S412。 步骤 S410， 没有该权限的应用监控策略， 不做监控处理。 步骤 S412, 按应用监控策略进行监控。 步骤 S414, 记录应用的权限使用情况。 图 5示出了对应用权限进行监控的总体流程， 下面结合图 5对整个监控过程进行 说明。 该过程包括步骤 S502至步骤 S518: 步骤 S502, 当监测到应用系统敏感权限被访问时， 进入步骤 S504。 步骤 S504， 判断该权限是否属于系统默认控制策略中定义所需控制的权限。 在该 步骤实施的过程中， 需在系统默认控制策略中进行查找， 若不属于系统默认控制策略 中的权限， 则执行步骤 S506, 若属于， 则执行步骤 S508。 步骤 S506， 由于该权限为非系统默认控制策略所需控制的权限， 因此对该权限的 使用不进行监控。 例如， 当用户访问的敏感权限涉及手机设备本地连接类权限时， 其 不在系统默认控制策略中， 则不对该权限进行控制。 步骤 S508，判断是否已经存在该权限的应用监控策略。若存在，则执行步骤 S510, 若不存在则执行步骤 512。 步骤 S510, 获取该权限的应用监控策略记录， 并根据该应用监控策略对权限的使 用进行监控。 步骤 S512, 由于当前权限还没有对应的权限监控策略的记录， 因此， 弹出提示框 提醒用户当前系统敏感权限正在被使用， 并且没有对该权限进行监控， 等待接收用户 对于该权限监控的进一步设置。 步骤 S514, 接收到用户对于该权限的监控策略的设置。 步骤 S516, 将用户对于该权限的监控设置转化为权限使用的应用监控策略， 保存 和更新系统记录的监控策略记录值， 其中， 监控设置可以为全时段监控、 全时段不监 控、 时段内监控等设置。 步骤 S518, 根据用户的设置的应用监控策略进行监控。 该优选实施的实施， 能够有效的对手机终端应用进行基于信任等级的分类， 并根 据应用信任等级分类来进行关键权限使用的分类管理， 该实施例可以针对厂商或用户 的不同控制需求来对手机关键权限控制的可定制化及可动态调整化。 用户通过运用本 实施例， 可以很容易的实现对手机终端关键敏感权限组的管理和控制的目的， 能够有 效的对手机应用可能存在的安全威胁行为进行管理控制，有效的保证了手机的安全性。 优选实施例二 本发明实施例可以通过软件实现对智能手机上最易被恶意入侵和最需要重点保护 的敏感权限组的监控， 实现被监控的权限组可以包括： 发送消息、 呼叫、 网络流量访 问控制权限、 访问联系人记录， 消息记录、 手机设备信息、 地理位置信息、 wifi连接、 蓝牙连接。 在实施过程中， 均以 "非可信应用" 的权限使用的监控为例进行说明， 其 它信任等级下应用权限使用的监控原理及处理流程均相似。 在本优选实施例中， 设置系统默认监控策略， 将发送消息、 呼叫、 网络流量访问 等加入到 " 非可信应用信任等级"需要控制权限中， 配置文件以 xml文件格式定义， 定义的配置文件内容如下：
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<sysControlPermission> <trustLevel name="unApproved">
<permission name=" SEND—SMS" /> <permission name=" CALL—PHONE" /> <permission name="ACCESS_ INTERNET" /> <permission name=" ACCESS—MESSAGE" /> permission name=" ACCESS—CONTACTS" /> <permission name=" ACCESS CALLLOG" /> permission name=" ACCESS—LOCATION" /> <permission name=" ACCESS DEVICE INFO" /> <permission name="WIFI" />
<permission name=" BLUETOOTH" /> </trustLevel > </sysControlPermission> 其中， sysControlPermission标签代表这是系统默认控制权限； trustLevel标签代表 权限信任等级， "unApproved"代表权限不可信需要监控； permission标签代表了信任 等级下所需监控的权限 SE D_SMS 代表发送消息权限； CALL_PHO E代表拨打电 话权限； ACCES S_ INTERNET代表网路流量访问权限； ACCES S_MES S AGE代表访 问消息记录权限； ACCESS_CONTACTS 代表访 问联系人记录权限； ACCES S MES SAGE代表访问消息记录权限； ACCES S CALLLOG代表访问通话记录 权限； ACCESS_LOCATION代表访问个人地理位置信息 （包括 GPS定位以及基站定 位） 权限； ACCES S_DEVICE_INFO 代表访问手机设备信息权限 （包括 IMEI、 IMSI 以及本机号码等）； WIFI代表使用 wifi进行本地网络连接权限； BLUETOOTH代表 通过蓝牙建立本地连接权限。优选地，可以根据需要对列出的监控权限进行增减修改， 控制的原理和流程都是相似的。 如图 6所示， 该图是权限的系统默认监控策略生成过程的流程图， 该流程包括步 骤 S602至步骤 S606: 步骤 S602， 系统开机时初始化时， 首先会在指定的系统目录加载预置好的系统默 认监控策略配置文件。 步骤 S604, 进行系统默认监控策略配置文件的解析处理， 解析得到 "不可信需监 控权限"所需监控的权限列表。 步骤 S606, 将解析得到所需监控的权限列表记录到内存数据中， 形成系统默认监 控策略。 下面结合图 7对本优选实施例进行说明。 图 7中监控应用使用权限的处理流程包 括步骤 S702至步骤 S724: 步骤 S702, 当监测到应用使用到权限时， 执行步骤 S704。 例如， 一个播放应用 在使用的过程中， 被记录到其访问联系人数据库， 则此时执行步骤 S704。 步骤 S704， 获取应用的权限， 将该权限与系统默认权限列表进行比较。 步骤 S706, 判断该权限是否属于系统默认控制的权限。 若不属于系统默认控制的 权限， 则执行步骤 S708, 若属于， 执行步骤 S710。 步骤 S708，由于权限为非系统默认控制权限，因此对该权限的使用情况不做监控。 步骤 S710, 判断是否已经存在对该权限使用的应用监控策略。 若存在， 则执行步 骤 S712, 否则执行步骤 S714。 步骤 S712， 获取该权限的应用监控策略记录， 并根据监控策略进行权限的监控。 步骤 S714, 由于当前权限还没有对应的应用监控策略记录， 因此， 系统会弹出提 示框提醒用户， 等待接收用户设置该权限监控策略。 步骤 S716, 接收到用户对于该权限的监控策略。 步骤 S718, 将用户对于该权限的监控设置 （全时段监控 /全时段不监控 /时段内监 控） 转化为权限使用的应用监控策略， 保存和更新系统记录的监控策略记录值。 步骤 S720, 根据用户的选择对该权限使用进行监控。 步骤 S722, 把监控信息保存或同步到云服务端。 步骤 S724, 根据分析策略对保存的数据分析或将云端处理策略反馈至用户。 本优选实施例可以很好的根据应用的不同进行权限控制， 可以分别监控和管理手 机应用的权限（发送消息、 拨打电话、 网络流量访问等）， 可以根据用户的实际监控需 求和场景来灵活调整应用权限的应用监控策略。 本优选实施例可以实现对手机终端权 限监控管理的目的， 能够有效发现、 即时提醒和阻止对手机终端权限被恶意侵害的安 全威胁行为， 从而有效的保证了手机终端权限的安全性。 本发明实施例还提供了一种应用权限的控制装置， 该装置可以应用于移动终端中 对应用权限安全性的检测， 该装置的结构框图可以如图 8所示， 包括： 获取模块 10， 设置为根据应用的签名信息获取应用的信任等级， 其中， 应用包括以下至少之一： 待 下载的应用、 待安装的应用、 已经安装的应用； 控制模块 20， 与获取模块 10耦合， 设置为依据信任等级和预置的监控策略对应用的权限进行控制。 其中， 图 9所示装置的获取模块 10可以包括： 获取单元 102， 设置为获取应用的 签名信息； 匹配单元 104， 与获取单元 102耦合， 设置为将签名信息与移动终端内的 一个或多个预置证书的证书公钥进行匹配； 设置单元 106， 与匹配单元 104耦合， 设 置为根据不同匹配结果设置应用不同的信任等级。 在实施过程中， 获取模块 10还可以设置为记录签名信息与证书公钥匹配的个数； 依据匹配的个数设置应用的信任等级。 在一个优选实施例中， 应用权限的控制装置还可以如图 10所示， 其控制模块 20 可以包括： 判断单元 202， 设置为判断应用当前使用的权限是否为系统默认监控策略 中的权限； 查找单元 204， 与判断单元 202耦合， 设置为在当前权限为系统默认监控 策略中的权限的情况下， 在系统默认监控策略中查找信任等级对应的策略； 控制单元 206， 与查找单元 204耦合， 设置为根据对应的策略控制应用的权限。 在实施过程中， 控制模块 20 还可以设置为判断是否存在当前权限的应用监控策 略； 如果是， 则在应用监控策略中查找信任等级对应的策略。 图 11示出的应用权限的控制装置还包括保存模块 30， 与控制模块 20耦合， 设置 为将应用当前使用的权限的控制过程进行保存和分析以获得处理策略； 或将应用当前 使用的权限的控制过程同步到云端服务器以获得处理策略。 下面结合附图及优选实施例对上述实施例中的应用权限的控制装置进行说明。 优选实施例三 本优选实施例提供了一种应用权限的控制装置， 该装置的实现基于签名认证的应 用信任等级分级机制， 能够将手机中预制 /安装的应用进行基于信任等级的有效分类； 建立对需监控应用的权限的监控管理策略， 并且可以实现根据用户需求对监控策略的 可配制化， 即可灵活调整各应用所需监控的权限； 同时， 具有基于应用为监控单元的 权限使用监控策略设置能力， 即用户可以根据实际需要分别定义应用对权限使用的监 控策略； 在应用信任等级及权限监控策略和日志分析策略机制的支持下， 实现对手机 系统关键敏感权限的动态监控功能。 在本优选实施例中， 各模块的命名与上述实施例中装置的模块命名略有不同， 但 本实施例中各模块的组合能实现与上述实施例装置相同的功能。 本实施例包括如下模 块：
( 1 ) 认证模块： 实现应用信任等级认证功能， 在开机扫描手机预制应用 /下载安 装应用时，认证模块会解析应用的签名信息， 同时与手机预制的证书（包括预制的 "厂 商签名证书"、 " 运营商签名证书"、 "第 3方合作厂商签名证书"等）进行认证， 根据 应用的签名信息与证书公钥的认证结果， 赋予应用不同的信任等级属性。 (2)监控策略模块： 采用基于配置文件方式的策略定义机制， 应用权限访问监控 策略分为 "系统默认监控策略" 以及 "应用监控策略" 2级管理策略体系。 其中， "系 统默认监控策略"定义了各级任级别下应用所需要监控的敏感权限， 系统初始化时， 通过解析预制的策略配置文件得到。 "应用监控策略"记录了各具体应用本身对各敏感 权限使用的监控策略 （全时段监控 /全时间不监控 /时段监控）， 具体策略通过动态记录 用户的权限监控设置操作生成。
(3 ) 权限使用日志模块： 实现对监控流程的保存， 在 （1 ) (2) 扩展的应用信任 等级以及监控策略机制的支持下， 实现对手机上最易被滥用和需要重点保护的敏感权 限组的动态监控。 应用在使用到系统敏感权限时， 首先， 权限监控模块会获取应用所 属的信任等级属性； 其次， 依据应用信任等级通过监控策略模块来确定该权限的具体 监控策略； 并根据确认的监控策略对应用对该权限使用进行监控， 监控的形式包括： 全时段监控、 全时段不监控、 时段监控， 在没有查到监控形式的情况， 弹出提示后根 据用户的设置动态保存 /更新对应的 "应用控制策略"， 把监控的应用使用权限情况记 录到日志中， 保存在本地或更新到云端服务器； 最后根据本地的日志分析策略或云端 服务器返回的处理意见反馈给用户。 (4) 权限使用监控模块： 用于实现后台监控运行。 在具体实施过程中，本优选实施例的结构示意图可以如图 12所示，系统初始化时， 首先调用监控策略模块， 加载和解析预制的监控策略配置文件， 然后根据解析的结果 生成系统默认监控权限策略。 系统启动时， 调用认证模块， 随后加载权限使用监控模块在后台监控。 当监控到 应用使用手机关键敏感权限时， 会把权限使用情况数据传入权限使用日志模块进行记 录， 在记录后会进入分析权限使用策略模块的分析流程。 监控权限使用模块通过与日 志模块及监控策略模块协同工作， 最终完成对应用权限使用的监控及用户建议功能。 从以上的描述中， 可以看出， 上述实施例实现了如下技术效果的至少之一： 本发明采用了如下方法： 将获取的信任等级加入到对应用权限的控制过程中， 并 为信任等级预置了相应的监控策略。 通过运用本发明， 解决了相关技术中没有一种对 应用权限进行控制的安全体系， 移动终端在下载、 运行应用等过程中， 由于应用具有 的权限不明确， 致使移动终端存在很大的安全隐患的问题， 进而提供了一种较为安全 且全面的应用权限的监控方法， 提升了移动终端的性能。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种应用权限的控制方法， 包括：
根据应用的签名信息获取应用的信任等级， 其中， 所述应用包括以下至少 之一： 待下载的应用、 待安装的应用、 已经安装的应用；
依据所述信任等级和预置的监控策略对所述应用的权限进行控制。
2. 根据权利要求 1所述的方法， 其中， 根据应用的签名信息获取应用的信任等级 包括：
获取所述应用的签名信息；
将所述签名信息与移动终端内的一个或多个预置证书的证书公钥进行匹 配， 并根据不同匹配结果设置所述应用不同的信任等级。
3. 根据权利要求 2所述的方法， 其中， 根据不同匹配结果设置所述应用不同的信 任等级包括：
记录所述签名信息与所述证书公钥匹配的个数或所述证书的名称； 依据匹配的个数或所述证书的名称设置所述应用的信任等级。
4. 根据权利要求 1至 3中任一项所述的方法， 其中， 依据所述信任等级和预置的 监控策略对所述应用的权限进行控制包括：
判断所述应用当前使用的权限是否为系统默认监控策略中的权限； 如果是， 则在所述系统默认监控策略中查找所述信任等级对应的策略， 并 根据所述对应的策略控制所述应用的权限。
5. 根据权利要求 4所述的方法， 其中， 在所述系统默认监控策略中查找所述信任 等级对应的策略包括：
判断是否存在与所述应用当前使用的权限对应的应用监控策略， 其中， 所 述应用监控策略用于指示对权限使用情况进行监控的时间段；
如果是， 则在所述应用监控策略中查找所述信任等级对应的策略。 根据权利要求 1所述的方法， 其中， 依据所述信任等级和预置的监控策略对所 述应用的权限进行控制之后， 还包括：
将所述应用当前使用的权限的控制过程进行保存和分析以获得处理策略； 或将所述应用当前使用的权限的控制过程同步到云端服务器以获得处理策略。 一种应用权限的控制装置， 应设置为移动终端， 包括：
获取模块， 设置为根据应用的签名信息获取应用的信任等级， 其中， 所述 应用包括以下至少之一： 待下载的应用、 待安装的应用、 已经安装的应用； 控制模块， 设置为依据所述信任等级和预置的监控策略对所述应用的权限 进行控制。 根据权利要求 7所述的装置， 其中， 所述获取模块包括：
获取单元， 设置为获取所述应用的签名信息；
匹配单元， 设置为将所述签名信息与移动终端内的一个或多个预置证书的 证书公钥进行匹配；
设置单元， 设置为根据不同匹配结果设置所述应用不同的信任等级。 根据权利要求 7或 8所述的装置， 其中， 所述控制模块包括：
判断单元， 设置为判断所述应用当前使用的权限是否为系统默认监控策略 中的权限；
查找单元，设置为在所述当前权限为系统默认监控策略中的权限的情况下， 在所述系统默认监控策略中查找所述信任等级对应的策略；
控制单元， 设置为根据所述对应的策略控制所述应用的权限。 根据权利要求 7所述的装置， 其中， 所述装置还包括： 保存模块， 设置为将所述应用当前使用的权限的控制过程进行保存和分析 以获得处理策略； 或将所述应用当前使用的权限的控制过程同步到云端服务器 以获得处理策略。
PCT/CN2012/079659 2012-06-12 2012-08-03 应用权限的控制方法及装置 Ceased WO2013185413A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/415,650 US20150222641A1 (en) 2012-06-12 2012-08-03 Method and device for controlling permission of application
EP12879120.9A EP2861003A4 (en) 2012-06-12 2012-08-03 METHOD AND DEVICE FOR CONTROLLING APPLICATION RIGHTS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210192660.5A CN103491056B (zh) 2012-06-12 2012-06-12 应用权限的控制方法及装置
CN201210192660.5 2012-06-12

Publications (1)

Publication Number Publication Date
WO2013185413A1 true WO2013185413A1 (zh) 2013-12-19

Family

ID=49757463

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/079659 Ceased WO2013185413A1 (zh) 2012-06-12 2012-08-03 应用权限的控制方法及装置

Country Status (4)

Country Link
US (1) US20150222641A1 (zh)
EP (1) EP2861003A4 (zh)
CN (1) CN103491056B (zh)
WO (1) WO2013185413A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140066015A1 (en) * 2012-08-28 2014-03-06 Selim Aissi Secure device service enrollment
CN110334518A (zh) * 2019-07-05 2019-10-15 北京可信华泰信息技术有限公司 基于可信计算平台的度量策略的验证方法及装置

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140123300A1 (en) 2012-11-26 2014-05-01 Elwha Llc Methods and systems for managing services and device data
US9619497B2 (en) 2012-10-30 2017-04-11 Elwah LLC Methods and systems for managing one or more services and/or device data
US9749206B2 (en) 2012-10-30 2017-08-29 Elwha Llc Methods and systems for monitoring and/or managing device data
US20140123325A1 (en) 2012-11-26 2014-05-01 Elwha Llc Methods and systems for managing data and/or services for devices
US9088450B2 (en) 2012-10-31 2015-07-21 Elwha Llc Methods and systems for data services
US10091325B2 (en) 2012-10-30 2018-10-02 Elwha Llc Methods and systems for data services
US9635486B2 (en) * 2014-06-10 2017-04-25 Microsoft Technology Licensing, Llc Network selection for a given application or context
US9521153B2 (en) * 2014-08-18 2016-12-13 Dell Products L.P. Platform trust extension
CN104318180A (zh) * 2014-11-18 2015-01-28 上海斐讯数据通信技术有限公司 基于智能终端的系统安全权限处理状态机模型
CN105243311B (zh) 2015-10-19 2017-02-22 广东欧珀移动通信有限公司 一种指纹信息的安全调用方法、装置及移动终端
CN105468939B (zh) * 2015-11-24 2018-12-14 苏州铭冠软件科技有限公司 移动终端安全防护系统
US20170149828A1 (en) 2015-11-24 2017-05-25 International Business Machines Corporation Trust level modifier
CN105760751B (zh) * 2016-02-14 2019-02-05 联想(北京)有限公司 一种信息处理方法和电子设备
CN106650444B (zh) * 2016-11-25 2020-01-14 成都网安科技发展有限公司 一种基于软件签名和安装时间的Android系统应用检测方法
US20180183836A1 (en) * 2016-12-28 2018-06-28 Ca, Inc. Discovery driven web-based application resource protection
CN108268793A (zh) * 2016-12-30 2018-07-10 珠海金山办公软件有限公司 一种权限编辑方法及装置
CN107172646A (zh) * 2017-06-06 2017-09-15 苏州小雨伞网络科技有限公司 一种跨设备网络监控方法
US11222135B2 (en) 2018-05-28 2022-01-11 International Business Machines Corporation User device privacy protection
CN109195158B (zh) * 2018-07-04 2022-04-26 中国联合网络通信集团有限公司 一种出境安检方法及系统
CN108513300A (zh) * 2018-07-11 2018-09-07 北京奇安信科技有限公司 一种管控wifi连接的处理方法及终端
CN109711161B (zh) * 2018-12-03 2022-04-22 联想(北京)有限公司 一种监控方法及电子设备
CN109684825B (zh) * 2018-12-28 2023-07-07 维沃移动通信有限公司 一种权限管理方法及终端设备
CN110046494B (zh) * 2019-04-24 2019-11-19 天聚地合(苏州)数据股份有限公司 基于终端的大数据处理方法及系统
US11438325B2 (en) 2020-02-28 2022-09-06 EMC IP Holding Company LLC Trust establishment by escalation
CN113746690B (zh) * 2020-08-12 2023-01-31 西安京迅递供应链科技有限公司 监控流量数据的方法、装置及计算机可读存储介质
CN111683107A (zh) * 2020-08-14 2020-09-18 北京东方通软件有限公司 面向互联网的安全审计方法和系统
EP4287050A1 (de) * 2022-05-30 2023-12-06 Siemens Aktiengesellschaft Überwachung eines anwendungsprogramms in abhängigkeit dessen privilegs
EP4400964A1 (en) * 2023-01-12 2024-07-17 Giesecke+Devrient Mobile Security Germany GmbH Change and recovery of personalization data in a secure element

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101707652A (zh) * 2009-10-20 2010-05-12 李东声 能够实现数字证书应用的手机
US20100332848A1 (en) * 2005-09-29 2010-12-30 Research In Motion Limited System and method for code signing
CN102404727A (zh) * 2011-11-24 2012-04-04 中兴通讯股份有限公司 移动终端的安全控制方法及装置
CN102420902A (zh) * 2011-11-24 2012-04-18 中兴通讯股份有限公司 一种分类管理功能使用权限的方法及移动终端

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7099663B2 (en) * 2001-05-31 2006-08-29 Qualcomm Inc. Safe application distribution and execution in a wireless environment
EP1564957B1 (en) * 2004-02-11 2007-08-22 Sony Ericsson Mobile Communications AB Method and apparatus for providing dynamic security management
JP2005275839A (ja) * 2004-03-25 2005-10-06 Nec Corp ソフトウェア利用許可方法及びシステム
US7853793B2 (en) * 2004-05-03 2010-12-14 Piotr Cofta Trusted signature with key access permissions
US8020001B2 (en) * 2006-02-23 2011-09-13 Qualcomm Incorporated Trusted code groups
US8245031B2 (en) * 2006-07-07 2012-08-14 Sandisk Technologies Inc. Content control method using certificate revocation lists
CN101513008B (zh) * 2006-07-31 2012-09-19 意大利电信股份公司 在电信终端上实现安全性的系统
US9218200B2 (en) * 2008-08-21 2015-12-22 Vmware, Inc. Selective class hiding in open API component architecture system
CN101651697A (zh) * 2009-09-21 2010-02-17 杭州华三通信技术有限公司 一种网络访问权限的管理方法和设备
US8832447B2 (en) * 2011-08-10 2014-09-09 Sony Corporation System and method for using digital signatures to assign permissions
CN102413220B (zh) * 2011-11-24 2014-08-20 中兴通讯股份有限公司 一种控制连接功能的使用权限的方法及移动终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100332848A1 (en) * 2005-09-29 2010-12-30 Research In Motion Limited System and method for code signing
CN101707652A (zh) * 2009-10-20 2010-05-12 李东声 能够实现数字证书应用的手机
CN102404727A (zh) * 2011-11-24 2012-04-04 中兴通讯股份有限公司 移动终端的安全控制方法及装置
CN102420902A (zh) * 2011-11-24 2012-04-18 中兴通讯股份有限公司 一种分类管理功能使用权限的方法及移动终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2861003A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140066015A1 (en) * 2012-08-28 2014-03-06 Selim Aissi Secure device service enrollment
US9867043B2 (en) * 2012-08-28 2018-01-09 Visa International Service Association Secure device service enrollment
CN110334518A (zh) * 2019-07-05 2019-10-15 北京可信华泰信息技术有限公司 基于可信计算平台的度量策略的验证方法及装置

Also Published As

Publication number Publication date
EP2861003A1 (en) 2015-04-15
CN103491056A (zh) 2014-01-01
US20150222641A1 (en) 2015-08-06
EP2861003A4 (en) 2015-10-28
CN103491056B (zh) 2017-12-26

Similar Documents

Publication Publication Date Title
WO2013185413A1 (zh) 应用权限的控制方法及装置
US12026261B2 (en) Quarantine of software by an evaluation server based on authenticity analysis of user device data
US12120519B2 (en) Determining a security state based on communication with an authenticity server
EP3706022B1 (en) Permissions policy manager to configure permissions on computing devices
US20210258304A1 (en) Configuring access to a network service based on a security state of a mobile device
US9940454B2 (en) Determining source of side-loaded software using signature of authorship
EP2759956B1 (en) System for testing computer application
US20160226872A1 (en) System and method for verifying status of an authentication device
WO2013075412A1 (zh) 移动终端的安全控制方法及装置
WO2014040461A1 (zh) 访问控制方法及装置
CN103546436A (zh) 一种安全控制方法及终端、云服务器
US20190044950A1 (en) Detection of Compromised Access Points
WO2013075422A1 (zh) 一种保护隐私信息的方法及移动终端
US20220256349A1 (en) Provision of Application Level Identity
US20250392614A1 (en) Home Gateway Monitoring for Vulnerable Home Internet of Things Devices
CN116015695A (zh) 资源访问方法、系统、装置、终端及存储介质
WO2023216913A1 (zh) 通信方法及装置
WO2019037581A1 (zh) 一种用于对用户设备进行无线连接预授权的方法与设备
WO2018014555A1 (zh) 数据传输控制方法及装置
CN117896156A (zh) 数据的可信校验方法、信发设备、校验系统及相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12879120

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012879120

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14415650

Country of ref document: US