WO2016037496A1 - 一种数据访问控制方法、装置以及终端 - Google Patents
一种数据访问控制方法、装置以及终端 Download PDFInfo
- Publication number
- WO2016037496A1 WO2016037496A1 PCT/CN2015/079817 CN2015079817W WO2016037496A1 WO 2016037496 A1 WO2016037496 A1 WO 2016037496A1 CN 2015079817 W CN2015079817 W CN 2015079817W WO 2016037496 A1 WO2016037496 A1 WO 2016037496A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- app
- data
- level
- privacy
- trusted
- 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
Links
Images
Classifications
-
- 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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- 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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
Definitions
- the present invention relates to the field of data access security management, and in particular, to a data access control method, apparatus, and terminal.
- the personal terminal stores a lot of personal data, including address book, short message, call record, photo, video, etc., which constitutes an important personal information asset of the user.
- Each type of personal data (such as a directory) usually contains many data items (such as multiple contacts, multiple text messages, multiple pictures, etc.), all of which are protected by the same system permissions. Permissions is a resource restriction mechanism provided by the operating system.
- Applications APPs
- APPs must obtain appropriate permissions to access specific protected data (such as address books) or perform certain business functions (such as accessing the network). If the APP has the appropriate permissions, it accesses all data entries in a certain type of data.
- all data items under the same APP, such as contacts have different sensitivity levels. It is easy to cause according to the existing permission control method, and another APP with a low security level reads all the data items under the APP. Including high-sensitivity data entries, which can easily lead to the leakage of highly sensitive data of end users or malicious theft.
- the embodiments of the present invention provide a data access control method, apparatus, and terminal that effectively prevent a high-sensitivity data entry from being leaked or stolen under an application.
- a first aspect of the embodiments of the present invention provides a data access control method, apparatus, and terminal, including acquiring a data access request of a first application APP to a second application APP, where the data of the second APP includes multiple data items.
- Each of the plurality of data entries has a respective privacy level; determining a trusted level of the first APP and the first APP to access a privacy level of each data item under the second APP data; determining, according to the trusted level of the first APP and the privacy level of each data item, for each of the plurality of data items
- the response of the data request of the second APP and the processing manner, the response and the processing manner include returning the data entry requested by the first APP, not returning the data entry requested by the first APP, and returning the modified data entry And auditing and recording one or more of the returned results.
- the multiple data entries of the second APP data are divided into one or more data types, where the data type refers to the description object is the same data.
- the obtaining, by the first application, the data access request of the second application APP includes acquiring the first application
- the program APP requests access to the same type of data of the second application APP.
- the determining the trusted level of the first APP includes: according to the foregoing The source of an APP and whether or not it has networking rights determines the trust level of the first APP.
- the APP source comprises pre-installed system software, trusted by a user App Market and other sources, where the level of trust is reduced by pre-installed system software, the application market trusted by users (APP Market) to other sources.
- the determining the second The privacy level of each data item under the APP data includes: manually setting a privacy level of each data item or determining a privacy level according to an association relationship between different APP data, wherein the association relationship includes data items with the same data generation location or time and from The data entry for the same contact.
- the trusted level according to the first APP and Determining, by the privacy level of each data entry, a response of the first APP to the data request of the second APP and processing manners for each of the multiple data entries:
- the response and the processing manner are returning the data entry that the first APP requests to access;
- the modified data entry includes false data or obfuscated data.
- the second APP includes a first address book and a second The first address book or the second address book includes a plurality of data items, each data item corresponding to a contact information, wherein the first address book stores contact information with a higher privacy level than the second address The privacy level of the contact information stored in the address book.
- the trusted level according to the first APP and Determining the privacy level of each data item, determining a response to the data request of the second APP, and processing manners include:
- the response and the processing manner are returning contact information of the first address book or returning the first and second communications All contact information recorded;
- the response and the processing manner are only returning the contact information of the second address book or not returning the contact information.
- the second aspect of the embodiments of the present invention provides an intelligent terminal, including an access control module and a privacy control module, where the access control module is configured to obtain a data access request of the first application APP to the second application APP.
- the data of the second APP includes a plurality of data items, Each of the plurality of data entries has a respective privacy level;
- the privacy control module is configured to determine a trusted level of the first APP and data under the second APP data to be accessed by the first APP a privacy level of the entry;
- the access control module is further configured to determine, according to the trusted level of the first APP and the privacy level of each data entry, for each data entry of the multiple data entries
- the response of the APP to the data request of the second APP and the processing manner, the response and the processing manner include returning a data entry requested by the first APP, not returning a data entry requested by the first APP, Returns one or more ways to modify the data entry and to audit and record the returned results.
- a third aspect of the embodiments of the present invention provides a smart terminal, including a processor and a memory, wherein the memory stores a plurality of data entries under data of the second APP, and each of the plurality of data entries a privacy level and a trusted level of the first APP; the processor obtaining a data access request of the first application APP to the second application APP, and according to the trusted level of the first APP and the each a privacy level of the data entry, determining, for each of the plurality of data entries, a response of the first APP to a data request of the second APP and a processing manner, the response and processing manner including returning the The first APP requests access to the data entry, does not return the data entry accessed by the first APP request, returns the modified data entry, and audits and records one or more of the returned results.
- the solution provides a privacy classification and protection for different data items in the personal data protected by the same authority in the APP on the smart terminal according to their respective sensitivity to the user, and solves the problem that the existing permission mechanism is too coarse.
- the problem of certain sensitive items in personal data cannot be effectively protected, and third-party APPs are effectively prevented from collecting and leaking such sensitive data without affecting the normal business functions of the APP.
- FIG. 1 is a schematic diagram of application program APP trust level and data item privacy level management according to Embodiment 1 of the present invention.
- FIG. 2 is a schematic flowchart of a data access control method according to Embodiment 1 of the present invention.
- FIG. 3 is a schematic diagram of an association relationship between data items in Embodiment 1 of the present invention.
- FIG. 4 is a second schematic diagram showing the relationship between data entries in the first embodiment of the present invention.
- FIG. 5 is a third schematic diagram of the relationship between data entries in the first embodiment of the present invention.
- FIG. 6 is a schematic diagram of a module of an intelligent terminal according to Embodiment 2 of the present invention.
- FIG. 7 is a schematic structural diagram of hardware of an intelligent terminal according to Embodiment 3 of the present invention.
- an APP running on a terminal needs to read some information items (such as partial contacts, partial short messages, and partial photos) of a certain type or types of personal data in the terminal to perform normal business functions, such as WeChat. Need to read the user's mobile phone address to search for friends for users, many social applications need to read some pictures in the user terminal for sharing. Currently The APP on the terminal will apply for various access rights (such as the right to read the address book) when installing. If the user wants to use the APP, he/she must agree to grant the access permission applied by the APP. Once the APP obtains the corresponding permission, the APP may not Restricted reading of all entries in a certain class or categories of personal data.
- the APP can read all the contacts and all the call records at will, or the APP can be read as soon as it is granted the android.permission.READ_SMS permission. All SMS records, or APP if you have com.android.browser.permission.READ_HISTORY_BOOKMARKS permission can access the browser history.
- APP does not need to read all personal data items.
- the APP runs on the user terminal in the form of compiled code. It is often difficult for the user to know the internal program logic, such as how the APP processes the user's personal data, whether some personal data is sent to the network, and the like. According to the current research and analysis, APP generally has excessive collection of user personal data. For example, in February 2014, MetaIntell tested 500 of the most popular Android apps and found that 92% of the programs had user data leakage behavior; in December 2013, HP released a test report, and one user used an average of 26 apps. An average of 97% of programs have privacy issues. These APPs may over-collect contacts, text messages, call records, photos, etc. in the user's smart terminal, especially some sensitive data items, which pose a serious threat to the user's personal privacy.
- each type of user personal data is protected by a corresponding authority, and the different data items in the same type of data protected by the same authority in the smart terminal APP are according to their respective users.
- the sensitivity of the speech is categorized by privacy, so that the data items have corresponding privacy sensitivity levels to reflect their sensitivity to the user.
- each data item needs to have corresponding privacy level information, but the information may not be directly stored with the corresponding data item, and the privacy level may be derived from other information, such as different storage locations.
- the privacy sensitivity level of the data item can be automatically deduced and determined according to the derivation rules provided by the system and adjusted by the user.
- APPs in the system are ranked according to their privacy credibility, and their privacy levels are evaluated based on their rights and their sources.
- each data item in the personal data is checked for its privacy sensitivity level and the privacy trust level of the APP.
- the relationship determines the visibility and presentation of the current data item in the application access result set based on the two levels of difference.
- the strategies that can be used here are: no return, return of false data, return of obfuscated data, access auditing, no restrictions, etc. This is called a privacy restriction policy.
- an embodiment of the present invention provides a data access control method, where the method includes the following steps:
- Step 101 Obtain a data access request of the first application APP to the second application APP, where the data of the second APP includes multiple data items, and each of the plurality of data items has a respective privacy level;
- Step 102 Determine a trusted level of the first APP and a first APP to access The privacy level of each data item under the second APP data;
- Step 103 Determine, according to the trusted level of the first APP and the privacy level of each data entry, a data request of the first APP to the second APP for each data entry in the multiple data entries.
- the response and the processing manner, the response and the processing manner include returning the data entry requested by the first APP, not returning the data entry requested by the first APP, returning the modified data entry, and without limitation Directly returning one or more of the data entries whose privacy level is lower than the first APP trust level and auditing and recording the returned results.
- the first APP includes installation software of various sources, such as software from system software, an application market (APP Market), and other sources.
- the second APP may be an application having a plurality of data entries such as short messages, contacts, albums, and the like.
- the first APP usually needs to invoke an access request initiated by the data of other APPs when installing or starting up.
- the plurality of data entries of the second APP data are classified into one or more data types, and the data types refer to data describing the same object, such as a contact, a short message, a call record, and a photo. Different types of data.
- the obtaining the data access request of the first application APP to the second application APP comprises acquiring an access request of the first application APP to the same type of data of the second application APP.
- determining the trusted level of the first APP includes: determining a trusted level of the first APP according to a source of the first APP and whether the network has the network access authority, where the APP source includes pre-installed system software
- the APP Trust Level reflects the user's conviction that the APP does not reveal the user's personal data. It can be measured by objective criteria or subjectively specified by the user.
- An objective credibility level evaluation method is used in the embodiment of the present invention, and the method is mainly based on the source of the APP and whether the APP has the networking authority to classify and specify the trusted level. do not.
- the privacy credibility rating of the APP can be executed in the cloud and delivered to the terminal.
- APP network access authority
- the network access authority is an important factor affecting the privacy level of APP privacy
- an APP without network access rights is impossible to disclose user privacy.
- APP has network access rights, it has the basic ability to disclose user privacy.
- the set of all APPs is defined as ALL
- the set of all APPs without networking rights is PLAIN
- the source of the APP reflects where the app was obtained, which is the provider of the app. Apps provided by trusted providers are usually relatively trustworthy. APPs can be divided into the following categories according to their sources:
- Pre-installed system software (defined as SYS), these are the non-unloadable system software pre-installed by the equipment manufacturer at the factory. These softwares form part of the terminal system, with clear software responsibility and best. Source credibility.
- determining a privacy level of each data item in the second APP data to be accessed by the first APP includes: manually setting a privacy level of each data item or determining a privacy level according to an association relationship between different APP data, where The association relationship includes data entries with the same data generation location or time and data entries from the same contact.
- Relationship for example, as shown in FIG. 3, if a communication record or a communication subject of a short message record happens to be a contact in the address book, the call record or the short message record is associated with the contact; if a photo is If you are shooting in a geographic location, this photo is associated with the geographic location.
- This association is used in this patent to automatically derive the privacy sensitivity level of certain data items, avoiding the user's privacy sensitivity of setting all personal data items one by one, and reducing the user management cost.
- the system can naturally calculate that a certain SMS record with A or a privacy record of a certain call record can be automatically set to H, and the email of the contact A is also Can be automatically marked as H.
- the user has ultimate control over the privacy sensitivity level of the personal data items automatically derived by the system and can be manually adjusted based on the results of the automatic derivation.
- photos, recordings, recorded videos, and the like on the smart terminal are generated in a geographical location, and the geographical location defines the external environment and possible content range generated by the digital content. If a geographic location is sensitive, photos, recordings, and recorded videos generated on that geographic location are potentially sensitive. Thereby, the sensitivity level of photos, sound recordings, recorded videos, etc. generated on the location area can be automatically derived from the sensitivity level of the geographical location area.
- users need to specify the corresponding privacy sensitivity level.
- most of the contacts and geographic locations in the terminal system are insensitive, and they can be automatically assigned a default level, which is defined in the system's privacy policy database.
- Individually sensitive contacts or geographic locations can be managed by the user through the management module. After the user specifies the sensitivity level of the address book contacts and the sensitivity level of each geographic location (which can be specified by the map), most of the personal data items in the smart terminal can be automatically derived.
- another possible association relationship is based on time correlation. If the user defines a certain period of time as sensitive (for example, to participate in a confidential conference), then the terminal is generated during the time period. All electronic documents, emails, and browser access records are automatically marked as privacy sensitive.
- step 103 determining, according to the trusted level of the first APP and the privacy level of the multiple data entries, a response to the data request of the second APP for each data entry in the multiple data entries, and The processing method determines the access response mode of the data entry for each data item.
- the granularity of the privacy control is that each data item is determined by each data item, and the privacy level is determined instead of the entire APP. The data, thereby improving the granularity of data access privacy controls.
- the privacy restriction policy database records the various differences between the privacy trust level of the APP accessing the personal data and the privacy sensitivity of the data entry, and the representation of the data entry in the APP access data result return set. The possible outcomes are:
- the access result set contains a fake data entry in place of the entry
- the access result set contains the data entry, but part of the field or content of the data entry is obfuscated;
- Unrestricted The data entry is included in the access result set.
- a contact is highly privacy sensitive
- a general APP such as WeChat
- WeChat a general APP
- This is expected by most users in most cases, because users generally do not have various social connections and sharing with such contacts.
- the user wants to add this contact as a WeChat friend, he needs to manually enter the contact's number to add.
- the APP since the APP only gets one number and cannot obtain any other information (such as a name) of the contact, the method maximizes the privacy of the user.
- the response manner and the result of the access are determined according to the trust level of the first APP and the privacy level of the second APP data item that needs to be accessed.
- the trusted level of the first APP is higher than or equal to the privacy level of the data item that it needs to access, such as when the trusted level of the first APP is H
- the second APP is to access the second
- the privacy level of the data entry of the APP whether H, M or L
- the response and the processing manner are all returning the data entry requested by the first APP; when the trusted level of the first APP is lower than the data that needs to be accessed
- the privacy level of the entry is M
- the privacy level of the data entry of the second APP to be accessed by the first APP is H
- the response and the processing manner are not returned.
- the first APP requests access to the data entry or returns the modified data entry, wherein the modified data entry includes false data or obfuscated data; wherein the return and processing manner may include auditing and recording the returned result, as may be set when the privacy level is When H's data entry is accessed, the audit is logged and the result is returned.
- the second APP includes a first address book and a second address book
- the first address book or the second address book includes a plurality of data entries, each data entry corresponding to a contact Information, wherein the privacy information of the contact information stored in the first address book is higher than the privacy level of the contact information stored in the second address book, for example, some important contact information is placed in the first address book, some Ordinary or unimportant contact information is placed in the second address book.
- Determining the response to the data request of the second APP and processing manner includes:
- the response and processing manner is returning contact information of the first address book or returning all contacts of the two address books information;
- the response and the processing manner are only returning the contact information of the second address book or not returning the contact information.
- the solution provides a privacy classification and protection for different data items in the same type or the same APP personal data covered by the rights of each user protection data on the intelligent terminal according to their respective sensitivity to the user.
- the management, control and protection methods of the personal data are more refined, and the original data storage and presentation mode is not changed, and the original terminal use experience of the user is maintained.
- another embodiment of the present invention is directed to an intelligent terminal, where the smart terminal includes an access obtaining module, a privacy control module, and an access control module, where:
- the access obtaining module is configured to obtain a data access request of the first application APP to the second application APP, where the data of the second APP includes a plurality of data items, each of the plurality of data items has a respective Privacy level;
- the privacy control module is configured to determine a trusted level of the first APP and a privacy level of each data entry under the second APP data that the first APP is to access;
- the access control module is further configured to determine, according to the trusted level of the first APP and the privacy level of each data entry, the first APP to the first data for each data entry in the multiple data entries.
- the response of the data request of the second APP and the processing manner, the response and the processing manner include returning the data entry requested by the first APP, and not returning to the first APP One or more ways of requesting access to a data entry, returning a modified data entry, and auditing and recording the returned result.
- the privacy control module is configured to determine a trusted level of the first APP according to a source of the first APP and whether the networking authority is available.
- the APP source includes pre-installed system software, an application market trusted by the user (APP Market), and other sources, wherein the trusted level is sequentially reduced by the pre-installed system software, the application market trusted by the user (APP Market), and other sources.
- the privacy control module is configured to manually set a privacy level of each data item or determine a privacy level according to an association relationship between different APP data, where the association relationship includes data items with the same data generation location or time and from the same contact Human data entry.
- the access control module is further configured to: when the trusted level of the first APP is higher than or equal to a privacy level of a data item that needs to be accessed, the response and the processing manner are returned to the first APP to request access Data entry
- the modified data entry includes false data or obfuscated data.
- the smart terminal in the embodiment of the present invention further includes a privacy restriction policy database, an application information level data table (library), and personal data (address book, photo) with sensitive level tags.
- the access control module is a default permission checking module of the smart terminal operating system, and is used to check whether an application has the right to access certain types of personal data.
- H is used here to represent a high level of privacy sensitivity
- M is a medium sensitivity level
- L is not sensitive.
- H stands for high privacy credibility
- M stands for medium privacy credibility
- L stands for general credibility.
- the application trust level table (library) records the privacy trust level of each APP in the system, as detailed in section 2.2.2 on how to calculate the privacy trust level of each APP.
- the privacy restriction policy database records the visibility of data entries and their privacy restrictions in various differences between the privacy trust level of the APP accessing the personal data and the privacy sensitivity of the data entry.
- the privacy sensitivity level of the data entry (the address book entry and the photo, etc.) can be associated by the association method described in Embodiment 1. System rules are automatically derived and adjusted by the user.
- the data item privacy sensitivity level may be recorded in a file attribute or in a redundant field of the data table, or a new database may be used in the system to store the information, which is only an implementation example.
- the privacy level of the application's privacy can be logged through a dedicated database or dynamically evaluated each time it is run.
- the privacy control module performs privacy protection control according to the privacy trust level of the current APP, the privacy sensitivity level of the data entry to be accessed, and the system access policy.
- the user manages the privacy sensitivity level of the personal data item and the privacy trust level of the APP through the management module, and specifies the privacy restriction policy of the system.
- the user first manages the privacy sensitivity level of the personal data item, the privacy trust level of the APP, and the privacy restriction policy of the system through the management module;
- the privacy control module initializes, reads the privacy trust level of all applications, and loads the system's privacy restriction policy
- the APP initiates access to a certain personal data through a user program interface (API).
- API user program interface
- the system default access control module intercepts the access request and checks whether it has the right to access the personal data (permission P). If not, the system Denied access; if so, the process continues;
- the access control module modifies the execution process of the API or intercepts the data result set returned by the API, compares the sensitivity level of the data item with the privacy trust level of the current APP one by one, and processes the data items in the result set according to the privacy restriction policy;
- the smart terminal in another embodiment of the present invention includes a processor and a memory, where the memory stores a plurality of data entries under data of the second APP, and each of the plurality of data entries a privacy level and a trusted level of the first APP;
- the processor acquires a data access request of the first application APP to the second application APP, and according to the trusted level of the first APP and the privacy level of each data item, Determining, by each of the plurality of data entries, a response of the first APP to a data request of the second APP and a processing manner, where the response and the processing manner include returning a data entry requested by the first APP to access Not returning the data entry requested by the first APP, returning the modified data entry, and auditing and recording one or more of the returned results.
- the data in the method step of the first embodiment and related policies are stored in the memory of the smart terminal in this embodiment, and all the method steps in the first embodiment can be executed.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Medical Informatics (AREA)
- Databases & Information Systems (AREA)
- Storage Device Security (AREA)
- Information Transfer Between Computers (AREA)
Abstract
一种数据访问控制方法、装置以及终端,包括获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;确定所述第一APP的可信级别以及所述第一APP要访问的第二APP数据下各数据条目的隐私级别;根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
Description
本发明涉及数据访问安全管理领域,特别是涉及一种数据访问控制方法、装置以及终端。
智能终端上存储了诸多个人数据,包括通信录、短信、通话记录、照片、视频等,这些个人数据构成了用户重要的个人信息资产。每类个人数据中(如通信录)通常都包含了很多数据条目(如多个联系人、多条短信、多张图片等),所有这些数据条目受到同一个系统权限的保护。系统权限(Permissions)是操作系统提供的一种资源限制机制,应用程序(APP)必须取得相应的权限才能访问特定受保护的数据(如通信录)或者执行某些业务功能(如访问网络)。如果APP拥有相应的权限,则访问到某类数据中的所有数据条目。然而,同一APP下的所有数据条目,例如联系人,具有不同的敏感级别,按照现有的权限控制方式就容易造成,安全级别不高的另一个APP读取到该APP下的所有数据条目,包括其中的高敏感级别的数据条目,这样容易造成终端用户高敏感数据的泄露或者被恶意窃取。
发明内容
有鉴于此,本发明实施例提供一种有效防止应用程序下的高敏感级别的数据条目泄露或被窃取的数据访问控制方法、装置以及终端。
本发明实施例第一方面提供一种数据访问控制方法、装置以及终端,包括获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;确定所述第一APP的可信级别以及所述第一APP要访问的
第二APP数据下各数据条目的隐私级别;根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中每一数据条目,确定对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
结合第一方面,在第一方面的第一种可能的实现方式中,所述第二APP数据的多个数据条目分为一种或多种数据类型,所述数据类型是指描述对象相同的数据。
结合第一方面或第一方面的第一种可能,在第一方面的第二可能的实现方式中,所述获取第一应用程式APP对第二应用程序APP的数据访问请求包括获取第一应用程式APP对第二应用程序APP的同一类型数据的访问请求。
结合第一方面或第一方面的第一种或第二种可能,在第一方面的第三种可能的实现方式中,所述确定所述第一APP的可信级别包括:根据所述第一APP的来源以及是否具有联网权限确定所述第一APP的可信级别。
结合第一方面或第一方面的第一至第三种可能中的任意一种可能,在第一方面的第四种可能的实现方式中,所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。
结合第一方面或第一方面的第一至第四种可能中的任意一种可能,在第一方面的第五种可能的实现方式中,所述确定所述第一APP要访问的第二APP数据下各数据条目的隐私级别包括:手动设置各个数据条目的隐私级别或者根据不同APP数据之间的关联关系确定隐私级别,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
结合第一方面或第一方面的第一至第五种可能中的任意一种可能,在第一方面的第六种可能的实现方式中,所述根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式包括:
当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,所述回应以及处理方式为返回所述第一APP请求访问的数据条目;
当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,所述回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据。
结合第一方面或第一方面的第一至第六种可能中的任意一种可能,在第一方面的第七种可能的实现方式中,所述第二APP包括第一通信录以及第二通信录,所述第一通信录或第二通信录包括多个数据条目,各数据条目对应为一联系人信息,其中所述第一通信录存储的联系信息的隐私级别高于所述第二通信录存储的联系人信息的隐私级别。
结合第一方面或第一方面的第一至第七种可能中的任意一种可能,在第一方面的第八种可能的实现方式中,所述根据所述第一APP的可信级别以及所述各数据条目的隐私级别,确定对所述第二APP的数据请求的回应以及处理方式包括:
确定所述第一APP的可信级别,如果所述第一APP属于高可信级别,则所述回应以及处理方式为返回第一通信录的联系人信息或者返回所述第一、第二通信录的所有联系人信息;
如果所述第一APP属于中或低可信级别,则所述回应以及处理方式为仅返回第二通信录的联系人信息或者不返回联系人信息。
本发明实施例第二方面提供一种智能终端,包括一访问控制模块以及隐私控制模块,其中:所述访问控制模块用于获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,
所述多个数据条目中的各数据条目具有各自的隐私级别;所述隐私控制模块用于确定所述第一APP的可信级别以及所述第一APP要访问的第二APP数据下各数据条目的隐私级别;所述访问控制模块还用于根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中每一数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
本发明实施例第三方面提供一种智能终端,包括处理器以及存储器,其特征在于,所述存储器存储有第二APP的数据下的多个数据条目、所述多个数据条目中各数据条目的隐私级别以及所述第一APP的可信级别;所述处理器获取第一应用程式APP对第二应用程序APP的数据访问请求,并据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中每一数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
本方案提供了一种对智能终端上APP中受到相同权限保护的个人数据中的不同数据条目按照其各自对用户而言的敏感性进行隐私分级并进行保护,解决现有权限机制粒度过粗而不能有效保护个人数据中某些敏感条目的问题,有效防止第三方APP收集和泄露这些敏感数据,同时又不影响APP的正常业务功能。
本发明实施例的优点将会在下面的说明书中部分阐明,一部分根据说明书是显而易见的,或者可以通过本发明实施例的实施而获知。
图1为本发明实施例一中应用程式APP可信级别以及数据条目隐私级别管理的示意图。
图2为本发明实施例一中数据访问控制方法流程示意图。
图3为本发明实施例一中数据条目之间关联关系的示意图之一。
图4为本发明实施例一中数据条目之间关联关系的示意图之二。
图5为本发明实施例一中数据条目之间关联关系的示意图之三。
图6为本发明实施例二中智能终端的模块示意图。
图7为本发明实施例三中智能终端的硬件结构示意图。
以下所述是本发明实施例的优选实施方式,应当指出,对于本技术领域的普通技术人员来说,在不脱离本发明实施例原理的前提下,还可以做出若干改进和润饰,这些改进和润饰也视为本发明实施例的保护范围。
在当前的终端应用中,有些文件类型,如图片文件,在一些系统上没有明确的系统权限保护,但它们明显是同一类文件,此时可以认为他们受到同一个特殊的”读图片”(permissions.picture.read)权限保护,而所有应用程序(APP)都缺省具有此权限。通常情况下,某类个人数据中的大部分条目(例如大部分的联系人、大部分的照片)都不是特别敏感的(例如一般性联系人,一般性风景照片等),而有些数据条目可能是很敏感的,例如通信录中一些特殊的联系人记录如工作上司、生意伙伴、政界人士、其它公众人士朋友等,短信记录及通话记录中与上述特殊敏感联系人的短信和电话来往记录,照片中的家人照片等。
终端上运行的APP在很多情况下都需要读取终端中某一类或者某几类个人数据中的部分信息条目(如部分联系人、部分短信、部分照片)以便执行正常的业务功能,例如微信需要读取用户的手机通信录以便为用户搜索好友,很多社交应用都需要读取用户终端中的部分图片以便进行分享。目前
终端上的APP在安装时都会申请各种访问权限(例如读取通信录的权限),用户如果希望使用该APP,则必须同意授予APP所申请的访问权限,APP一旦获得对应的权限则可以不受限制的读取某一类或者几类个人数据中的所有条目。例如,APP一旦被授予了Android.permission.READ_CONTACTS权限,则它可以随意读取所有的通信录联系人以及所有的通话记录,或者APP一旦被授予了android.permission.READ_SMS权限,则可以随意读取所有的短信记录,或者APP如果取得了com.android.browser.permission.READ_HISTORY_BOOKMARKS权限则可以访问则可以读取浏览器历史记录。然而APP在一般情况下,并不需要读取所有的个人数据条目,例如大部分终端用户一般不会把自己通信录中的工作上司或者生意伙伴加为微信好友;很多基于地理位置的应用都支持基于通信录的地理位置分享功能,但用户一般不会跟通信录中的父母、工作上司等进行位置分享;淘宝需要读取来自指定平台的短信以获取验证码,而不需要读取其它的短信记录。
APP以编译代码的形式在用户终端上运行,用户通常难以得知其内部的程序逻辑,例如APP如何对用户个人数据进行处理,是否会把部分个人数据发送到网络上等。根据目前的研究分析,APP普遍存在过度收集用户个人数据的情况。例如2014年2月,MetaIntell公司对500个最流行的Android APP进行测试,发现92%的程序存在用户个人数据泄露行为;2013年12月HP公司发布测试报告,一个用户平均使用26个APP,其中平均97%程序存在隐私问题。这些APP可能过度收集用户智能终端中的联系人、短信、通话记录、照片等,特别是部分敏感的数据条目,这对用户的个人隐私构成了严重的威胁。
针对智能终端上系统权限过于粗略而难以针对个人信息中某些特别敏感的数据条目进行保护的现状,对智能终端上每个权限覆盖保护的同一类数据中的不同数据条目按照其各自对用户而言的敏感性进行隐私分级,使
每个数据条目都有相应的隐私敏感级别以标识其敏感性,通过隐私限制确保只有可信级别或程度高的APP才能读取到终端上的敏感个人数据条目,使得用户可以精确管理和控制第三方APP对部分用户敏感数据的访问和收集。
如图1所示,在智能终端上,每类用户个人数据都为对应的权限所保护,本方案对智能终端APP中受到相同权限保护的同一类数据中的不同数据条目按照其各自对用户而言的敏感性进行隐私分级,使得数据条目都有相应的隐私敏感级别以反映其对用户而言的敏感性。这里每个数据条目都需要有相应的隐私级别信息,但这些信息未必直接与对应的数据条目存储在一起,隐私级别可能从其它信息中推导出来,如不同的存储位置。为了降低用户的管理代价,数据条目的隐私敏感级别可以按照系统提供的推导规则进行自动推导确定并由用户进行自主调整。对系统中的APP按照其隐私可信性进行分级,基于其所拥有的权限及其来源对其评估并确定其隐私可信级别。当拥有对应访问权限的APP并试图读取某类个人数据时,在系统缺省的权限检查通过之后,对该类个人数据中的每个数据条目检查其隐私敏感级别与APP的隐私可信级别的关系,根据两个级别的差异关系决定当前数据条目在应用程序访问结果集中的可见性和呈现形式。这里可以采用的策略可以是:不予返回、返回虚假数据、返回混淆数据、访问审计、不加限制等。这称为隐私限制策略。
实施例一
如图2所示,本发明实施例提供一种数据访问控制方法,所述方法包括以下步骤:
步骤101、获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;
步骤102、确定所述第一APP的可信级别以及所述第一APP要访问的
第二APP数据下各数据条目的隐私级别;
步骤103、根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目、不加限制而直接返回隐私级别低于所述第一APP可信级别的数据条目以及审计并记录返回结果中的一种或多种方式。
步骤101中,所述第一APP包括各种来源的安装软件,如来自系统软件、应用市场(APP Market)以及其它来源等软件。所述第二APP可以是短信息、通信录、相册等等具有多个数据条目的应用程序。所述第一APP通常在安装或者启动的时候需要调用其它APP的数据的时候发起的访问请求。
在一些实施例中,所述第二APP数据的多个数据条目分为一种或多种数据类型,所述数据类型是指描述对象相同的数据,例如联系人、短信、通话记录、照片为不同类型的数据。所述获取第一应用程式APP对第二应用程序APP的数据访问请求包括获取第一应用程式APP对第二应用程序APP的同一类型数据的访问请求。
步骤102中,确定所述第一APP的可信级别包括:根据所述第一APP的来源以及是否具有联网权限确定所述第一APP的可信级别,其中所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。例如,APP可信级别反应了用户对于该APP不会泄露用户个人数据的确信程度,它可以通过客观的标准进行度量,也可以由用户主观指定。本发明实施方式中使用一种客观的可信级别评估方法,该方法主要基于APP的来源和APP是否具有联网权限进行分类并指定可信级
别。这种APP的隐私可信级别评定,可以在云端执行并下发到终端上。
其中,是否具有联网权限是影响APP隐私可信级别的重要因素,一款没有联网权限的APP自己是不可能泄露用户隐私的,APP如果具有了联网权限,就具有泄露用户隐私的基本能力。这里定义所有APP的集合为ALL,所有不具有联网权限的APP的集合为PLAIN,具有联网权限的APP的集合为NET,显然ALL=PLAIN+NET。
APP的来源反应了该APP是从何处获得的,也即APP的提供者。可信提供者提供的APP通常相对较为可信。APP按照其来源可以分为以下几类:
1)预装的系统软件(定义为SYS),这些APP是设备制造商在出厂时预装的不可卸载的系统软件,这些软件构成了终端系统的一部分,有明确的软件责任归属,具有最好的来源可信性。
2)来自用户信任的APP Market(如Google Play)或者网站(如Baidu.com)的APP,这里定义其集合为MARKETS。
3)其它来源的APP,定义为OTHERS。
对于一款APP(设为a),其隐私可信级别L(a)定义如下:
a)L(a)=H(高)当且仅当a∈PLAIN∪SYS,即系统软件或者无联网权限软件的隐私信任级别可以为H。
b)L(a)=M(普通)当且仅当a∈MARKETS,即用户从可信提供者处获得APP其隐私可信级别可以为M。
c)L(a)=L(低)当且仅当a∈OTHERS∩NET,上述两种情况之外的APP,其隐私可信级别都为L。
步骤102中,确定所述第一APP要访问的第二APP数据下各数据条目的隐私级别包括:手动设置各个数据条目的隐私级别或者根据根据不同APP数据之间的关联关系确定隐私级别,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
例如,智能终端中,不同类别的个人数据条目之间往往具有内在的关联
关系,例如图3所示,如果一条通话记录或者短信记录的通讯主体正好是通信录中的某个联系人,则该条通话记录或者短信记录与该联系人存在关联关系;如果一张照片是在某个地理位置上拍摄的,则这张照片与该地理位置存在关联关系。
本专利中使用这种关联关系来自动推导某些数据条目的隐私敏感级别,避免用户逐条设置所有个人数据条目的隐私敏感性,降低用户管理代价。假设用户已经指定联系人A的隐私敏感级别是H,系统可以自然地计算出与A的某条短信记录或者某条通话记录的隐私敏感级别可以自动设定为H,该联系人A的邮件也可以自动标记为H。当然用户对系统自动推导的个人数据条目的隐私敏感级别具有最终控制权,可以基于自动推导的结果进行手动调整。
例如图4所示,智能终端上的照片、录音、录制的视频等产生于某个地理位置上,地理位置界定了这些数字内容产生的外部环境和可能的内容范围。如果某个地理位置区域是敏感的,则该该地理位置上产生的照片、录音和录制的视频等都潜在是敏感的。由此可以从地理位置区域的敏感级别出发自动推导在该位置区域上产生的照片、录音、录制的视频等的敏感级别。
对于通信录联系人和地理位置,用户需要去指定对应的隐私敏感级别。一般情况下,终端系统中大部分的通信录联系人和地理位置都是不敏感的,其可以被自动分配一个缺省级别,该缺省级别在系统的隐私限制策略数据库中进行定义。个别敏感的联系人或者地理位置可以由用户通过管理模块进行管理指定。在用户指定了通信录联系人的敏感级别和各个地理位置的敏感级别(可以通过地图指定)后,智能终端中的大部分个人数据条目都可以自动推导出来。
例如图5所示,另外一种可能的关联关系是基于时间关联的,如用户把某一段时间定义成敏感的(例如参加机密会议),则在此时间段内终端上产生
的所有电子文档、邮件和浏览器访问记录等都会被自动标记成隐私敏感的。
步骤103中,根据所述第一APP的可信级别以及所述多条数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定对所述第二APP的数据请求的回应以及处理方式,针对每一条数据条目的隐私级别去判断对该条数据条目的访问回应方式,可见隐私控制的粒度是在每一条数据条目,逐一对每一个数据条目进行隐私级别确定,而不是整个APP的数据,从而提高数据访问隐私控制的精细度。例如,隐私限制策略数据库记录访问个人数据的APP的隐私可信级别与数据条目的隐私敏感性的各种不同差异关系下,数据条目在APP访问数据结果返回集中的表现形式。其可能的结果有:
a)不予返回,在访问结果集中不包含该数据条目;
b)虚假数据,访问结果集中包含一条虚假的数据条目来代替该条目;
c)混淆数据,访问结果集中包含该数据条目,但该数据条目的部分字段或者内容经过混淆处理;
d)访问审计:系统对此次访问进行审计记录;
e)不加限制:在访问结果集中包含该数据条目。
与传统的各种访问控制方法不同,本方案中根据当前APP隐私可信级别与待访问数据条目的隐私敏感级别的不同差异(这种差异可能有多种情况)采取不同的限制手段。这种不同差异反应了当前这种访问行为自身的敏感性,需要不同的控制手段,这可以进一步避免过度限制和降低了冗余信息(审计日志等)的生成。例如对于一条敏感级别为H(高度敏感)的联系人记录(一大公司高管),一个隐私可信级别为L(不可信)的APP来读取时,系统可能返回虚假数据条目并且进行审计,而一个可信级别为M(较为可信)的APP来读取同一条目时,可能只需要返回虚假条目而无需审计(甚至可能是返回混淆数据)。本专利中,根据当前APP隐私可信级别与待访问数据条目的隐私敏感级别的不同差异采用不同的限制手段,以帮助用户进一步
避免过度限制和降低了冗余信息(审计日志等)的产生。
按照本方法,如果一个联系人是高度隐私敏感的,则一般的APP(如微信)都无法读取到这样的联系人。这在绝大部多数情况下都是用户所预期的,因为用户一般不会与这样的联系人进行各种社交联系和分享。如果在极特殊的情况下,用户确实希望把这个联系人加为微信好友,则他需要手动输入联系人的号码进行添加。这种情况下,由于APP只得到一个号码而不能获得该联系人的任何其他信息(如姓名),本方法最大程度的保护了用户的隐私。
可见,根据第一APP的可信级别以及其需要访问的第二APP数据条目的隐私级别,确定所述访问的回应方式以及结果。例如,当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,如当所述第一APP的可信级别为H,则第一APP要访问的第二APP的数据条目的隐私级别无论是H、M或者L,回应以及处理方式都是返回所述第一APP请求访问的数据条目;当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,如当所述第一APP的可信级别为M,第一APP要访问的第二APP的数据条目的隐私级别为H,则所述回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据;其中返回以及处理方式可以包括审计以及记录返回结果,如可以设定当隐私级别为H的数据条目被访问时,审计并记录访问以及返回结果。
在本发明某些实施例中,所述第二APP包括第一通信录以及第二通信录,所述第一通信录或第二通信录包括多个数据条目,各数据条目对应为一联系人信息,其中所述第一通信录存储的联系信息的隐私级别高于所述第二通信录存储的联系人信息的隐私级别,例如,一些比较重要的联系人信息放在第一通信录,一些普通或者不重要的联系人信息放在第二通信录。其中所述根据所述第一APP的可信级别以及所述各数据条目的隐私级别,
确定对所述第二APP的数据请求的回应以及处理方式包括:
确定所述第一APP的可信级别,如果所述第一APP属于高可信级别,则所述回应以及处理方式为返回第一通信录的联系人信息或者返回两个通信录的所有联系人信息;
如果所述第一APP属于中或低可信级别,则所述回应以及处理方式为仅返回第二通信录的联系人信息或者不返回联系人信息。
本方案提供了一种对智能终端上每个保护用户个人数据的权限所覆盖的同一类或者同一APP个人数据中的不同数据条目按照其各自对用户而言的敏感性进行隐私分级并进行保护,解决现有权限机制粒度过粗而不能有效保护个人数据中某些敏感条目的问题,有效防止第三方APP收集和泄露这些敏感数据,同时又不影响APP的正常业务功能;另外还给予用户一种相对于终端系统自身的权限管理措施更为精细化的个人数据的管理、控制和保护方式,同时不改变原有的数据保存和展现模式,保持用户原有的终端使用体验。
实施例二
如图6所示,本发明另一实施例涉及一种智能终端,所述智能终端包括一访问获取模块、隐私控制模块以及访问控制模块,其中:
所述访问获取模块用于获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;
所述隐私控制模块用于确定所述第一APP的可信级别以及所述第一APP要访问的第二APP数据下各数据条目的隐私级别;
所述访问控制模块还用于根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP
请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
所述隐私控制模块用于根据所述第一APP的来源以及是否具有联网权限确定所述第一APP的可信级别。其中所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。
所述隐私控制模块用于手动设置各个数据条目的隐私级别或者根据根据不同APP数据之间的关联关系确定隐私级别,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
所述访问控制模块还用于:当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,所述回应以及处理方式为返回所述第一APP请求访问的数据条目;
当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,所述回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据。
本发明实施例中的智能终端还包括隐私限制策略数据库、应用信息级别数据表(库)以及带有敏感级别标记的个人数据(通信录、照片)。其中访问控制模块是智能终端操作系统缺省的权限检查模块,用来检查一款应用是否具有访问某类个人数据所具有的权限。对于个人数据条目,这里使用H代表高隐私敏感级别,M代表中等敏感级别,L代表不敏感。对于APP,这里H代表高隐私可信度,M代表中等隐私可信度,L代表一般可信度。
应用信任级别表(库)记录系统中的每个APP的隐私可信级别,关于如何计算每个APP的隐私可信级别章节2.2.2中详述。隐私限制策略数据库记录访问个人数据的APP的隐私可信级别与数据条目的隐私敏感性的各种不同差异关系下数据条目可见性以及其隐私限制。所述数据条目(通信录条目和照片上等)的隐私敏感级别可以通过实施例一所述的关联方式进行关联
系统规则自动推导并由用户负责调整。
所述数据条目隐私敏感级别可以记录在文件属性中或者数据表的冗余字段中,也可以在系统中使用新的数据库来存储这些信息,图中只是一种实现范例。应用的隐私可信级别可以通过专门的数据库记录或者每次运行时动态评估。隐私控制模块根据当前APP的隐私信任级别、待访问数据条目的隐私敏感级别、系统访问策略进行隐私保护控制。用户通过管理模块管理个人数据条目的隐私敏感级别和APP的隐私可信级别,并指定系统的隐私限制策略。
系统的执行流程如下:
1)用户首先通过管理模块对个人数据条目的隐私敏感级别、APP的隐私可信级别以及系统的隐私限制策略进行管理;
2)隐私控制模块进行初始化,读取所有应用的隐私信任级别,并加载系统的隐私限制策略;
3)APP通过用户程序接口(API)发起对某种个人数据的访问,系统缺省的访问控制模块拦截该访问请求,检查是否拥有访问该类个人数据的权限(权限P),如果没有则系统拒绝访问;如果有,流程继续执行;
4)访问控制模块修改API的执行过程或拦截API返回的数据结果集,逐条比对数据条目的敏感级别与当前APP的隐私可信级别,根据隐私限制策略对结果集中的数据条目进行处理;
5)API调用返回,应用取得经过隐私限制模块处理过的个人数据。
实施例三
如图7所示,本发明又一实施例中的智能终端包括处理器以及存储器,所述存储器存储有第二APP的数据下的多个数据条目、所述多个数据条目中各数据条目的隐私级别以及所述第一APP的可信级别;
所述处理器获取第一应用程式APP对第二应用程序APP的数据访问请求,并据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对
所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
本实施例中的智能终端的存储器中存储有执行实施例一的方法步骤中的数据以及相关策略,可以执行实施例一中的所有方法步骤。
本发明是参照根据本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和
修改。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。
Claims (23)
- 一种数据访问控制方法,其特征在于,包括获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;确定所述第一APP的可信级别以及所述第一APP要访问的第二APP数据下各数据条目的隐私级别;根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
- 如权利要求1所述的数据访问控制方法,其特征在于,所述第二APP数据的多个数据条目分为一种或多种数据类型,所述数据类型是指描述对象相同的数据。
- 如权利要求2所述的数据访问控制方法,其特征在于,所述获取第一应用程式APP对第二应用程序APP的数据访问请求包括获取第一应用程式APP对第二应用程序APP的同一类型数据的访问请求。
- 如权利要求1至3任一项所述的数据访问控制方法,其特征在于,所述确定所述第一APP的可信级别包括:根据所述第一APP的来源以及是否具有联网权限确定所述第一APP的可信级别。
- 如权利要求4所述的数据访问控制方法,其特征在于,所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。
- 如权利要求1至3任一项所述的数据访问控制方法,其特征在于, 所述确定所述第一APP要访问的第二APP数据下各数据条目的隐私级别包括:手动设置各个数据条目的隐私级别或者根据不同APP数据之间的关联关系确定隐私级别,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
- 如权利要求1至3任一项所述的数据访问控制方法,其特征在于,所述根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式包括:当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,所述回应以及处理方式为返回所述第一APP请求访问的数据条目;当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,所述回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据。
- 如权利要求1至3任一项所述的数据访问控制方法,其特征在于,所述第二APP包括第一通信录以及第二通信录,所述第一通信录或第二通信录包括多个数据条目,各数据条目对应为一联系人信息,其中所述第一通信录存储的联系信息的隐私级别高于所述第二通信录存储的联系人信息的隐私级别。
- 如权利要求8所述的数据访问控制方法,其特征在于,所述根据所述第一APP的可信级别以及所述各数据条目的隐私级别,确定对所述第二APP的数据请求的回应以及处理方式包括:确定所述第一APP的可信级别,如果所述第一APP属于高可信级别,则所述回应以及处理方式为返回第一通信录的联系人信息或者返回所述第一、第二通信录的所有联系人信息;如果所述第一APP属于中或低可信级别,则所述回应以及处理方式为仅返回第二通信录的联系人信息或者不返回联系人信息。
- 一种智能终端,其特征在于,包括访问获取模块、隐私控制模块以及访问控制模块,其中:所述访问获取模块用于获取第一应用程式APP对第二应用程序APP的数据访问请求,所述第二APP的数据包括多个数据条目,所述多个数据条目中的各数据条目具有各自的隐私级别;所述隐私控制模块用于确定所述第一APP的可信级别以及所述第一APP要访问的第二APP数据下各数据条目的隐私级别;所述访问控制模块用于根据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
- 如权利要求10所述的智能终端,其特征在于,所述第二APP数据的多个数据条目分为一种或多种数据类型,所述数据类型是指描述对象相同的数据。
- 如权利要求11所述的智能终端,其特征在于,所述访问获取模块具体用于获取第一应用程式APP对第二应用程序APP的同一类型数据的访问请求。
- 如权利要求10至12任一项所述的智能终端,其特征在于,所述隐私控制模块用于根据所述第一APP的来源以及是否具有联网权限确定所述第一APP的可信级别。
- 如权利要求13所述的智能终端,其特征在于,所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。
- 如权利要求10至12任一项所述的智能终端,其特征在于,所述隐私控制模块用于手动设置各个数据条目的隐私级别或者根据根据不同APP数据之间的关联关系确定隐私级别,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
- 如权利要求10至12任一项所述的智能终端,其特征在于,所述访问控制模块具体用于:当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,所述回应以及处理方式为返回所述第一APP请求访问的数据条目;当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,所述回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据。
- 如权利要求10至12任一项所述的数据访问控制方法,其特征在于,所述第二APP包括第一通信录以及第二通信录,所述第一通信录或第二通信录包括多个数据条目,各数据条目对应为一联系人信息,其中所述第一通信录存储的联系信息的隐私级别高于所述第二通信录存储的联系人信息的隐私级别。
- 如权利要求17所述的数据访问控制方法,其特征在于,所述访问控制模块还用于:确定所述第一APP的可信级别,如果所述第一APP属于高可信级别,则所述回应以及处理方式为返回第一通信录的联系人信息或者返回两个通信录的所有联系人信息;如果所述第一APP属于中或低可信级别,则所述回应以及处理方式为仅返回第二通信录的联系人信息或者不返回联系人信息。
- 一种智能终端,包括存储器以及处理器,其特征在于,所述存储器存储有第二APP的数据下的多个数据条目、所述多个数据条目中各数据条目的隐私级别以及所述第一APP的可信级;所述处理器用于获取第一应用程式APP对第二应用程序APP的数据访 问请求,并据所述第一APP的可信级别以及所述各数据条目的隐私级别,针对所述多个数据条目中各数据条目,确定所述第一APP对所述第二APP的数据请求的回应以及处理方式,所述回应以及处理方式包括返回所述第一APP请求访问的数据条目、不予返回所述第一APP请求访问的数据条目、返回修改后的数据条目以及审计并记录返回结果中的一种或多种方式。
- 如权利要求19所述的智能终端,其特征在于,所存储器存储的第一APP的可信级别可以根据所述第一APP的来源以及是否具有联网权限确定。
- 如权利要求20所述的智能终端,其特征在于,所述APP来源包括预装系统软件、用户信任的应用市场(APP Market)以及其它来源,其中可信级别由预装系统软件、用户信任的应用市场(APP Market)到其它来源依次降低。
- 如权利要求19所述的智能终端,其特征在于,所述存储器存储的第二APP数据下各数据条目的隐私级别通过手动设置或者根据不同APP数据之间的关联关系确定,其中所述关联关系包括数据产生地点或时间相同的数据条目以及来自同一个联系人的数据条目。
- 如权利要求19至22任一项所述的智能终端,其特征在于,所述处理器用于获取第一应用程式APP对第二应用程序APP的数据访问请求,当所述第一APP的可信级别高于或等于其需要访问的数据条目的隐私级别时,所述第一应用程式APP对第二应用程序APP的数据访问请求的回应以及处理方式为返回所述第一APP请求访问的数据条目;当所述第一APP的可信级别低于其需要访问的数据条目的隐私级别时,所述第一应用程式APP对第二应用程序APP的数据访问请求的回应以及处理方式不予返回所述第一APP请求访问的数据条目或者返回修改后的数据条目,其中修改后的数据条目包括虚假数据或者混淆数据。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP15840842.7A EP3101584A4 (en) | 2014-09-10 | 2015-05-26 | Data access control method, device and terminal |
| US15/355,585 US20170068812A1 (en) | 2014-09-10 | 2016-11-18 | Data Access Control Method and Apparatus, and Terminal |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410459570.7 | 2014-09-10 | ||
| CN201410459570.7A CN105404819A (zh) | 2014-09-10 | 2014-09-10 | 一种数据访问控制方法、装置以及终端 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US15/355,585 Continuation US20170068812A1 (en) | 2014-09-10 | 2016-11-18 | Data Access Control Method and Apparatus, and Terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016037496A1 true WO2016037496A1 (zh) | 2016-03-17 |
Family
ID=55458330
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/079817 Ceased WO2016037496A1 (zh) | 2014-09-10 | 2015-05-26 | 一种数据访问控制方法、装置以及终端 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US20170068812A1 (zh) |
| EP (1) | EP3101584A4 (zh) |
| CN (1) | CN105404819A (zh) |
| WO (1) | WO2016037496A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2569605A (en) * | 2017-12-21 | 2019-06-26 | Sita Inf Networking Computing Usa Inc | System, device and method for processing data |
| CN110610072A (zh) * | 2019-09-06 | 2019-12-24 | 武汉达梦数据库有限公司 | 一种数据鉴权方法及装置 |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10019582B1 (en) * | 2016-02-24 | 2018-07-10 | Symantec Corporation | Detecting application leaks |
| CN106022168B (zh) * | 2016-07-01 | 2020-12-08 | 安徽继远检验检测技术有限公司 | 一种信息显示方法及移动终端 |
| CN106506511B (zh) * | 2016-11-17 | 2019-08-23 | 京东方科技集团股份有限公司 | 一种通讯录信息处理方法、装置 |
| CN106789893A (zh) * | 2016-11-22 | 2017-05-31 | 北京奇虎科技有限公司 | 一种用于对信息项进行安全处理的系统及方法 |
| TWI617940B (zh) * | 2016-12-01 | 2018-03-11 | 財團法人資訊工業策進會 | 資料保護方法與資料保護系統 |
| CN107451488B (zh) * | 2017-07-21 | 2021-01-05 | 珠海格力电器股份有限公司 | 一种提供个人信息的方法、装置及移动终端 |
| CN109388963A (zh) * | 2017-08-08 | 2019-02-26 | 武汉安天信息技术有限责任公司 | 一种移动终端用户隐私数据防护方法和装置 |
| WO2019196721A1 (en) * | 2018-04-11 | 2019-10-17 | Beijing Didi Infinity Technology And Development Co., Ltd. | Methods and apparatuses for processing data requests and data protection |
| CN108875356B (zh) * | 2018-05-29 | 2020-12-01 | 杭州滚马网络有限公司 | 一种数据访问方法、终端及计算机可读存储介质 |
| US11301578B2 (en) * | 2019-04-05 | 2022-04-12 | International Business Machines Corporation | Protecting data based on a sensitivity level for the data |
| US11675915B2 (en) | 2019-04-05 | 2023-06-13 | International Business Machines Corporation | Protecting data based on a sensitivity level for the data |
| US11270009B2 (en) * | 2019-06-21 | 2022-03-08 | Salesforce.Com, Inc. | Determining consent for an action using a consent policy reflecting an interpretation of applicable data privacy laws |
| CN110837654A (zh) * | 2019-07-31 | 2020-02-25 | Oppo广东移动通信有限公司 | 隐私信息获取方法及相关设备 |
| CN110826081B (zh) * | 2019-09-27 | 2022-09-16 | 维沃移动通信有限公司 | 一种权限管理方法及终端设备 |
| CN110990798B (zh) * | 2019-12-02 | 2021-07-20 | 珠海格力电器股份有限公司 | 应用程序权限配置方法、装置、电子设备及存储介质 |
| KR102883668B1 (ko) | 2020-04-03 | 2025-11-10 | 삼성전자주식회사 | 전자 장치 및 전자 장치의 제어 방법 |
| CN111563252A (zh) * | 2020-04-30 | 2020-08-21 | 北京无限光场科技有限公司 | 权限管理的方法及装置、终端和存储介质 |
| CN112241552B (zh) * | 2020-10-15 | 2021-09-24 | 海南大学 | 面向本质计算与推理的跨dikw模态隐私资源保护方法 |
| US11537705B2 (en) * | 2020-10-27 | 2022-12-27 | Dell Products L.P. | Device access control system |
| US11496482B2 (en) * | 2021-03-04 | 2022-11-08 | Oracle International Corporation | Methods and systems for memory tracing in asset management systems |
| CN113157664B (zh) * | 2021-03-18 | 2023-08-25 | 中睿信数字技术有限公司 | 基于分级标识的数据分级与授权方法和系统 |
| CN114186276B (zh) * | 2021-12-14 | 2025-03-21 | 中国农业银行股份有限公司 | 一种数据交付方法及装置 |
| CN117407843B (zh) * | 2023-10-13 | 2024-04-19 | 成都安美勤信息技术股份有限公司 | 一种隐私信息访问检测管理方法 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917513A (zh) * | 2010-08-02 | 2010-12-15 | 中兴通讯股份有限公司 | 一种实现隐私信息分级显示的方法及装置 |
| CN102905016A (zh) * | 2012-09-17 | 2013-01-30 | 东莞宇龙通信科技有限公司 | 信息展示方法及通信终端 |
| US20140245461A1 (en) * | 2013-02-28 | 2014-08-28 | Edward Kenneth O'Neill | Techniques for in-app user data authorization |
Family Cites Families (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100359427C (zh) * | 2005-04-06 | 2008-01-02 | 杭州波导软件有限公司 | 一种移动终端用户使用权限分级管理实现方法 |
| US8312268B2 (en) * | 2008-12-12 | 2012-11-13 | International Business Machines Corporation | Virtual machine |
| US9407748B2 (en) * | 2009-01-29 | 2016-08-02 | Centurylink Intellectual Property Llc | System and method for providing broadband notification |
| US8973158B2 (en) * | 2011-07-20 | 2015-03-03 | Microsoft Technology Licensing Llc | Trust level activation |
| CN103891392A (zh) * | 2011-08-30 | 2014-06-25 | 诺基亚公司 | 用于基于电话簿的应用共享的方法和装置 |
| US9773102B2 (en) * | 2011-09-09 | 2017-09-26 | Microsoft Technology Licensing, Llc | Selective file access for applications |
| US8990561B2 (en) * | 2011-09-09 | 2015-03-24 | Microsoft Technology Licensing, Llc | Pervasive package identifiers |
| CN102404727B (zh) * | 2011-11-24 | 2017-12-05 | 中兴通讯股份有限公司 | 移动终端的安全控制方法及装置 |
| US9519782B2 (en) * | 2012-02-24 | 2016-12-13 | Fireeye, Inc. | Detecting malicious network content |
| US8948821B2 (en) * | 2012-05-27 | 2015-02-03 | Qualcomm Incorporated | Notification based on user context |
| EP2883184B1 (en) * | 2012-08-10 | 2019-10-09 | BlackBerry Limited | Accessing contact records in a device with multiple operation perimeters |
| US9864810B2 (en) * | 2012-08-24 | 2018-01-09 | International Business Machines Corporation | User-specified user application data sharing |
| CN103686722B (zh) * | 2012-09-13 | 2018-06-12 | 中兴通讯股份有限公司 | 访问控制方法及装置 |
| US9092642B2 (en) * | 2012-09-27 | 2015-07-28 | Intel Corporation | Managing personal privacy settings |
| US9515832B2 (en) * | 2013-06-24 | 2016-12-06 | Microsoft Technology Licensing, Llc | Process authentication and resource permissions |
| JP6266284B2 (ja) * | 2013-09-19 | 2018-01-24 | 東芝メディカルシステムズ株式会社 | X線診断装置 |
| CN103559437B (zh) * | 2013-11-12 | 2016-07-06 | 中国科学院信息工程研究所 | 用于Android操作系统的访问控制方法及系统 |
| US9817987B2 (en) * | 2013-12-23 | 2017-11-14 | Dropbox, Inc. | Restricting access to content |
| US9460210B2 (en) * | 2014-04-04 | 2016-10-04 | Dropbox, Inc. | Enriching contact data based on content sharing history in a content management system |
-
2014
- 2014-09-10 CN CN201410459570.7A patent/CN105404819A/zh active Pending
-
2015
- 2015-05-26 EP EP15840842.7A patent/EP3101584A4/en not_active Withdrawn
- 2015-05-26 WO PCT/CN2015/079817 patent/WO2016037496A1/zh not_active Ceased
-
2016
- 2016-11-18 US US15/355,585 patent/US20170068812A1/en not_active Abandoned
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917513A (zh) * | 2010-08-02 | 2010-12-15 | 中兴通讯股份有限公司 | 一种实现隐私信息分级显示的方法及装置 |
| CN102905016A (zh) * | 2012-09-17 | 2013-01-30 | 东莞宇龙通信科技有限公司 | 信息展示方法及通信终端 |
| US20140245461A1 (en) * | 2013-02-28 | 2014-08-28 | Edward Kenneth O'Neill | Techniques for in-app user data authorization |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP3101584A4 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2569605A (en) * | 2017-12-21 | 2019-06-26 | Sita Inf Networking Computing Usa Inc | System, device and method for processing data |
| US12282568B2 (en) | 2017-12-21 | 2025-04-22 | Sita Information Networking Computing Usa, Inc. | System, device and method for processing data |
| CN110610072A (zh) * | 2019-09-06 | 2019-12-24 | 武汉达梦数据库有限公司 | 一种数据鉴权方法及装置 |
| CN110610072B (zh) * | 2019-09-06 | 2021-10-01 | 武汉达梦数据库有限公司 | 一种数据鉴权方法及装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| EP3101584A4 (en) | 2017-03-29 |
| US20170068812A1 (en) | 2017-03-09 |
| CN105404819A (zh) | 2016-03-16 |
| EP3101584A1 (en) | 2016-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016037496A1 (zh) | 一种数据访问控制方法、装置以及终端 | |
| US10990696B2 (en) | Methods and systems for detecting attempts to access personal information on mobile communications devices | |
| US12299164B2 (en) | Data security compliance for mobile device applications | |
| US10454942B2 (en) | Managed clone applications | |
| US9930071B2 (en) | System and methods for secure utilization of attestation in policy-based decision making for mobile device management and security | |
| US8190636B2 (en) | Method, apparatus and computer program product for providing object privilege modification | |
| US20130333039A1 (en) | Evaluating Whether to Block or Allow Installation of a Software Application | |
| US12395842B2 (en) | Security management on a mobile device | |
| US10410004B2 (en) | Method of preventing access to sensitive data of a computing device | |
| US20230075237A1 (en) | Self-Management of Devices Using Personal Mobile Device Management | |
| CN104462997B (zh) | 一种保护移动终端上工作数据的方法、装置和系统 | |
| US11017109B1 (en) | Dynamic sandboxing of user data | |
| US20230259548A1 (en) | Virtual file library | |
| Lee et al. | Protecting data on android platform against privilege escalation attack | |
| Liu et al. | An empirical study on android for saving non-shared data on public storage | |
| US11531716B2 (en) | Resource distribution based upon search signals | |
| Rafferty et al. | Privacy requirements in toy computing | |
| Abdella et al. | CA‐ARBAC: privacy preserving using context‐aware role‐based access control on Android permission system | |
| Sokolova et al. | Respecting user privacy in mobiles: privacy by design permission system for mobile applications | |
| Polykalas | Assessing general data protection regulation for personal data privacy: is the end of ‘Take it or leave it’Approach for downloading apps? | |
| CN121413014A (zh) | 数据访问控制方法、装置、设备、存储介质及程序产品 | |
| Montgomery | A Privacy Risk Scoring Framework for Mobile | |
| Marsan | Android behind the scenes: revealing hidden malware with AndroMEDA | |
| CN118646546A (zh) | 应用行为处理方法、电子设备及计算机存储介质 | |
| Kim et al. | Quality of Private Information (QoPI) Model for Effective |
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: 15840842 Country of ref document: EP Kind code of ref document: A1 |
|
| REEP | Request for entry into the european phase |
Ref document number: 2015840842 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2015840842 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |