WO2024007096A1

WO2024007096A1 - Privacy data protection method for android system

Info

Publication number: WO2024007096A1
Application number: PCT/CN2022/103577
Authority: WO
Inventors: 王晓东
Original assignee: 嘉兴尚坤科技有限公司
Priority date: 2022-07-04
Filing date: 2022-07-04
Publication date: 2024-01-11
Also published as: CN116982044A

Abstract

The present invention relates to a privacy data protection method for an Android system. The privacy data protection method is characterized by comprising the following steps: S1, setting a security domain, a trusted application domain and a suspicious application domain in an application layer of an Android system, wherein the security domain is used for storing privacy data, trusted application programs are run in the trusted application domain, and untrusted application programs are run in the suspicious application domain; and S2, configuring a monitoring module in the Android system for monitoring and capturing a privacy data request, which is sent by each application program in the Android system, and determining whether the application program is run in the trusted application domain or in the suspicious application domain; if the application program is run in the trusted application domain, executing steps S3-S5, and if the application program is run in the suspicious application domain, executing steps S6-S8. Compared with the prior art, the present invention has the advantages of effectively increasing the security of user's privacy data, preventing a malicious application program from stealing the privacy data, etc.

Description

A privacy data protection method for Android systems

Technical field

The present invention relates to the field of privacy data security, and in particular, to a privacy data protection method for Android systems.

Background technique

With the rapid development of network technology, smart devices are no longer limited to providing users with services such as calls and text messages, but also provide application services with various functions such as location positioning and payment. While users enjoy convenient services, they also face problems such as privacy data leakage. Taking the Android system as an example, some service applications apply for permission to access private data and obtain user private data for commercial purposes. For example, reading the user's call records, text message content, location information, etc. The current method to ensure the security of personal privacy data is to try to avoid browsing sensitive websites and install various anti-virus and anti-virus software. But this can only guarantee that the mobile phone system is safe within a certain range.

At the same time, although Android has a relatively strict user rights management mechanism, to break through the rights restrictions, the system rights need to be raised to the highest level, that is, ROOT authorization. However, even if the security software obtains ROOT authorization, there will still be the following problems: Android devices There are many manufacturers, and each of them will make some modifications to the system itself, so the existing technical methods may have incompatibility issues, causing ROOT authorization to be unstable on some models; ordinary users do not have professional knowledge about ROOT authorization. ROOT authorization cannot be performed on smart devices; while ROOT authorization opens up higher permissions to security software, it also gives malicious programs an opportunity to take advantage.

Contents of the invention

The purpose of the present invention is to provide a privacy data protection method for Android systems in order to overcome the shortcomings of the above-mentioned existing technologies.

The object of the present invention can be achieved through the following technical solutions:

A privacy data protection method for Android systems, including the following steps:

S1: Set a security domain, a trusted application domain and a suspicious application domain in the application layer of the Android system. The security domain is used to store private data. The trusted application runs in the trusted application domain. Untrusted applications run in suspicious application domains;

S2: Configure a monitoring module in the Android system to monitor and capture private data requests sent by each application in the Android system, and determine whether the application is running in a trusted application domain or a suspicious application domain. If it is running in a trusted application If it is running in the suspicious application domain, perform steps S3-S5. If it is running in the suspicious application domain, perform steps S6-S8;

S3: According to the access control policy of the security domain, send the private data request to the security domain to obtain authorization options for private data access;

S4: If the authorization selection result is "Allow", allow the application to access the private data this time, and perform step S5, otherwise deny the application the current access to the private data;

S5: The corresponding application directly accesses private data;

S6: The monitoring module intercepts the private data request and re-sends the private data request to the security domain to obtain the authorization selection for private data access;

S7: If the authorization selection result is "Allow", send fake private data or real private data to the monitoring module according to the user's choice, and execute step S8, otherwise the application's access to the private data will be denied;

S8: The monitoring module sends the received fake privacy data or real privacy data to the application that sends the privacy data request.

Further, a privacy policy execution module and a privacy policy management module are provided in the security domain to control applications' direct access to private data, and the privacy policy management module stores a privacy policy table.

Further, step S5 specifically includes:

S51: The package management service module in the Android system receives the privacy data request;

S52: The package management service module performs a permission check on the corresponding application according to the privacy policy table, determines the range of private data that the application can access, and transfers the private data according to the hook function set in the package management service module. The request is sent to the privacy policy management module;

S53: The privacy policy management module determines the content of the private data requested to be accessed by the application this time, and determines whether the content is within the range of private data that the application has permission to access. If so, the user is asked about the privacy data requested by the application this time. Whether it is possible to obtain the private data requested and send the query results to the privacy policy execution module;

S54: The privacy policy execution module receives the query results and sends them to the package management service module;

S55: The package management service module agrees or denies the application to access the private data requested based on the received query results.

Further, in step S2, the configuration monitoring module specifically includes:

Obtain a copy of the installation package of each application in the trusted application domain and the suspicious application domain, parse the copy of the installation package of each application, and obtain the binary executable code file corresponding to each application;

Modify or replace binary executable code files and inject loading modules to configure each application installation package;

Run the configured application installation package, start the loading module to load the monitoring module, and hook the monitoring module to the privacy data request of each application.

Furthermore, the monitoring module monitors and captures privacy data requests sent by various applications in the Android system, including:

The monitoring module is used to obtain the hook plug-in corresponding to the privacy data request of each application from the hook plug-in framework of the background sandbox, and the hook plug-in is used to capture the corresponding privacy data request.

Furthermore, the privacy policy table includes an application identification hash value and a user-set access scope flag. After receiving the query request, the privacy policy management module extracts the application identification from the request message and performs hash calculation, and then uses the privacy policy to The application identification hash value in the policy table can quickly query the corresponding entry. The user-set access range flag is used to record the private data range information that the application set by the user can access.

Compared with the prior art, the present invention has the following advantages:

The present invention sets a security domain, a trusted application domain and a suspicious application domain in the application layer of the Android system. The security domain is used to store private data; a monitoring module is configured in the Android system to monitor and capture the messages sent by each application in the Android system. private data request, and determine whether the application is running in a trusted application domain or a suspicious application domain. Depending on the judgment results, different methods are used to manage private data access. If it is a trusted application, the authorization selection result is " "Allow", the corresponding application can directly access the private data. If it is an untrusted application, the monitoring module intercepts the private data request and re-sends the private data request to the security domain. At the same time, if the authorization selection result is After "allowing", it is still necessary to send fake private data or real private data according to the user's choice, and rely on the monitoring module to relay and then send private data requests to distinguish between trustworthy applications and untrustworthy applications. When controlling trustworthy applications On the basis of accessing private data, increasing the control over untrusted applications obtaining private data can effectively protect users' private data.

Description of the drawings

Figure 1 is a schematic flow chart of the method of the present invention;

Figure 2 is a schematic flow chart of step S5 of the present invention.

Detailed ways

The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of the present invention.

As shown in Figures 1 and 2, the present invention provides a privacy data protection method for Android systems, which includes the following steps:

S1: Set up a security domain, a trusted application domain and a suspicious application domain in the application layer of the Android system. The security domain is used to store private data. Trusted applications run in the trusted application domain, and untrusted applications run in the suspicious applications. In the domain, a privacy policy execution module and a privacy policy management module are set up in the security domain to control applications' direct access to private data. The privacy policy table is stored in the privacy policy management module.

S2: Configure a monitoring module in the Android system to monitor and capture private data requests sent by each application in the Android system, and determine whether the application is running in a trusted application domain or a suspicious application domain. If it is running in a trusted application In the domain, perform steps S3-S5. If running in the suspicious application domain, perform steps S6-S8. The configuration monitoring module specifically includes: obtaining a copy of the installation package of each application in the trusted application domain and the suspicious application domain, And parse the copy of each application installation package to obtain the binary executable code file corresponding to each application; modify or replace the binary executable code file, inject the loading module to configure each application installation package; run each configured application Install the package, start the loading module, load the monitoring module, and hook the monitoring module to the privacy data requests of each application.

Set up a security domain, trusted application domain and suspicious application domain in the application layer of the Android system. The security domain is used to store private data; configure a monitoring module in the Android system to monitor and capture the privacy sent by each application in the Android system. data request, and determine whether the application is running in a trusted application domain or a suspicious application domain. Based on the different judgment results, different methods are used to manage private data access, which can effectively distinguish between trusted applications and untrusted applications. Protect users' private data.

If it is a trusted application, after the authorization selection result is "Allow", the corresponding application can directly access the private data. However, for direct access by trusted applications, private data access control is also required to improve privacy data. safety:

S3: According to the access control policy of the security domain, send the private data request to the security domain to obtain authorization options for private data access.

S4: If the authorization selection result is "Allow", the application is allowed to access the private data this time, and step S5 is executed. Otherwise, the application is denied this access to the private data.

S5: The corresponding application directly accesses private data, including:

S52: The package management service module checks the permissions of the corresponding application according to the privacy policy table, determines the range of private data that the application can access, and sends the private data request to Privacy policy management module;

S53: The privacy policy management module determines the content of the private data that the application requests to access this time, and determines whether the content is within the range of private data that the application has permission to access. If so, the user is asked whether the application can obtain it this time. It requests access to the private data and sends the query results to the privacy policy execution module;

If it is an untrusted application, the monitoring module intercepts the private data request and resends the private data request to the security domain. At the same time, if the authorization selection result is "Allow", it still needs to send fake private data or real private data according to the user's choice. , and rely on the monitoring module to relay and then send private data requests to applications, and increase the control over untrusted applications obtaining private data:

S6: The monitoring module intercepts the private data request and resends the private data request to the security domain to obtain authorization options for private data access.

S7: If the authorization selection result is "Allow", send fake private data or real private data to the monitoring module according to the user's choice, and execute step S8, otherwise the application will be denied this access to the private data.

S8: The monitoring module sends the received fake private data or real private data to the application that sent the private data request.

Among them, the monitoring module monitors and captures the privacy data requests sent by each application in the Android system, including: using the monitoring module to obtain the hook plug-in corresponding to the privacy data request of each application from the hook plug-in framework of the background sandbox, using the hook The plug-in captures the corresponding private data request. Specifically, the privacy policy table contains the application identification hash value and the user-set access scope flag. After receiving the query request, the privacy policy management module extracts the application identification from the request message and performs hash calculation, and then passes the application in the privacy policy table Identifies the hash value to quickly query the corresponding entry. The user-set access scope flag is used to record the private data scope information that the user-set application can access.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any worker familiar with the technical field can easily think of various equivalent methods within the technical scope disclosed in the present invention. Modifications or substitutions shall be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

A privacy data protection method for Android systems, which is characterized by including the following steps:

S1: Set a security domain, a trusted application domain and a suspicious application domain in the application layer of the Android system. The security domain is used to store private data. The trusted application runs in the trusted application domain. Untrusted applications run in suspicious application domains;

S2: Configure a monitoring module in the Android system to monitor and capture private data requests sent by each application in the Android system, and determine whether the application is running in a trusted application domain or a suspicious application domain. If it is running in a trusted application If it is running in the suspicious application domain, perform steps S3-S5. If it is running in the suspicious application domain, perform steps S6-S8;

S3: According to the access control policy of the security domain, send the private data request to the security domain to obtain authorization options for private data access;

S4: If the authorization selection result is "Allow", allow the application to access the private data this time, and perform step S5, otherwise deny the application the current access to the private data;

S5: The corresponding application directly accesses private data;

S6: The monitoring module intercepts the private data request and re-sends the private data request to the security domain to obtain the authorization selection for private data access;

S7: If the authorization selection result is "Allow", send fake private data or real private data to the monitoring module according to the user's choice, and execute step S8, otherwise the application's access to the private data will be denied;

S8: The monitoring module sends the received fake privacy data or real privacy data to the application that sends the privacy data request.
A privacy data protection method for Android systems according to claim 1, characterized in that a privacy policy execution module and a privacy policy management module are provided in the security domain to control applications' direct access to private data, The privacy policy management module stores a privacy policy table.
A privacy data protection method for Android systems according to claim 2, characterized in that step S5 specifically includes:

S51: The package management service module in the Android system receives the privacy data request;

S52: The package management service module performs a permission check on the corresponding application according to the privacy policy table, determines the range of private data that the application can access, and transfers the private data according to the hook function set in the package management service module. The request is sent to the privacy policy management module;

S53: The privacy policy management module determines the content of the private data requested to be accessed by the application this time, and determines whether the content is within the range of private data that the application has permission to access. If so, the user is asked about the privacy data requested by the application this time. Whether it is possible to obtain the private data requested and send the query results to the privacy policy execution module;

S54: The privacy policy execution module receives the query results and sends them to the package management service module;

S55: The package management service module agrees or denies the application to access the private data requested based on the received query results.
A privacy data protection method for Android systems according to claim 1, characterized in that in step S2, the configuration monitoring module specifically includes:

Obtain a copy of the installation package of each application in the trusted application domain and the suspicious application domain, parse the copy of the installation package of each application, and obtain the binary executable code file corresponding to each application;

Modify or replace binary executable code files and inject loading modules to configure each application installation package;

Run the configured application installation package, start the loading module to load the monitoring module, and hook the monitoring module to the privacy data request of each application.
A privacy data protection method for Android systems according to claim 4, characterized in that the monitoring module monitors and captures privacy data requests sent by each application in the Android system specifically includes:

The monitoring module is used to obtain the hook plug-in corresponding to the privacy data request of each application from the hook plug-in framework of the background sandbox, and the hook plug-in is used to capture the corresponding privacy data request.
A privacy data protection method for Android systems according to claim 3, characterized in that the privacy policy table includes an application identification hash value and a user-set access scope flag, and the privacy policy management module receives a query After the request, the application identifier is extracted from the request message and hashed, and then the corresponding entry is quickly queried through the application identifier hash value in the privacy policy table. The user-set access scope flag is used to record the application set by the user. Information about the scope of private data that can be accessed.