A privacy rights management method and device based on IOS system

Abstract

The purpose of this application is to provide a privacy permission management method and device based on the IOS system. This application obtains the third-party SDK list of the mobile terminal, and the system installed in the mobile terminal is the IOS system; constructs a monitor for monitoring the calling objects that access the privacy permission in the mobile terminal; monitors the privacy permission accessing the mobile terminal through the monitor to detect the target calling object; determines whether the target calling object exists in the third-party SDK list; if not, collects the historical privacy information of the target calling object accessing the privacy permission of the mobile terminal and uploads it to the server, so that the server generates a corresponding permission management policy based on the historical privacy information; based on the received permission management policy, performs corresponding permission management on the target calling object that accesses the privacy permission of the mobile terminal, and obtains the permission management of the target calling object based on the statistical results analysis, forming a complete management system for detection, collection, and management restrictions.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a privacy authority management method and device based on an IOS system. Background Art

[0002] During the 2020 "315" Gala, the exposure of two companies providing third-party SDK (Software Development Kit) plug-ins caused heated discussion among users. It is reported that providing third-party SDK plug-ins can steal user privacy without the user's knowledge. The third-party SDKs of these two companies not only steal user privacy data without the user's knowledge, but also transmit the user privacy data to the designated server for storage after reading the user privacy data; more importantly, since the third-party SDK is a packaged closed-source file, it is difficult for developers who integrate third-party SDKs into their applications to fully understand which user privacy permissions the third-party SDK will access.

[0003] While third-party SDKs may pose a risk of user privacy data leakage, and CCTV's "315" Gala exposed the existence of unscrupulous companies exploiting third-party SDKs to illegally steal user privacy data, third-party SDKs have long formed a highly symbiotic relationship with application software. Today, application development is now inseparable from the technical support provided by third-party SDKs, making it unrealistic for many developers to avoid using third-party SDKs.

[0004] In existing technologies, to address the issue of iOS app privacy permissions being overused by third-party SDKs, some security vendors have proposed the following solutions. While these solutions offer some protection, they also have significant vulnerabilities and shortcomings:

[0005] (1) Third-party SDK positioning technology. Since locating third-party SDK permissions on the iOS side requires certain technical capabilities, some companies only provide third-party SDK permission management functions on the Android side, but not on the iOS side, or can only manage dynamic library privacy permissions that are easier to track.

[0006] (2) Third-party SDK technology that focuses only on collection and not management. Some companies provide functions that detect the compliance of third-party SDK permissions based on the application and usage of third-party SDK permissions. The disadvantage of this is obvious. It can only know which privacy permissions are open to third-party SDKs, but cannot control the usage permissions of third-party SDKs. Because, in the iOS system, as long as the user authorizes a certain privacy access permission to the application, any third-party SDK integrated in the application can use these privacy functions at any time, and some permissions are even used for a long time once authorized. Therefore, when privacy permissions are already open, it is more important to implement access permission control for certain third-party SDKs. At the same time, the lack of accuracy in permission management is also a major problem. For example, location permissions are subdivided into single location permissions, in-use permissions, and background location permissions on the iOS platform. The inability to accurately collect permission usage details will also have an adverse impact on permission management. Summary of the Invention

[0007] One purpose of this application is to provide a privacy permission management method and device based on the iOS system, which solves the problem of third-party SDK privacy permission abuse and theft of user privacy information in mobile devices installed with the iOS system, realizes the use of monitors to monitor the target calling objects that call privacy permissions in iOS system applications in real time, and also collects and analyzes historical privacy information of the target calling objects, thereby achieving the management and restriction of the target calling objects and forming a complete and three-dimensional privacy permission management system.

[0008] According to one aspect of the present application, a privacy rights management method based on an iOS system is provided, wherein the method includes:

[0009] Obtain a list of third-party SDKs for a mobile terminal, where the mobile terminal is installed with an iOS system;

[0010] Constructing a monitor for monitoring the calling objects that access privacy rights in the mobile terminal;

[0011] The privacy authority for accessing the mobile terminal is monitored by the monitor to detect the target calling object;

[0012] Determine whether the target calling object exists in the third-party SDK list;

[0013] If not, collecting historical privacy information of the target calling object's privacy rights to access the mobile terminal and uploading it to a server, so that the server generates a corresponding rights management policy based on the historical privacy information;

[0014] Based on the received permission management policy, corresponding permission management is performed on the target calling object that has the privacy permission to access the mobile terminal.

[0015] Furthermore, in the above method, obtaining the third-party SDK list of the mobile terminal includes:

[0016] Build a file analyzer for collecting third-party SDKs in applications;

[0017] The file analyzer is called to parse all applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, where the third-party SDK list includes at least two third-party SDKs.

[0018] Furthermore, in the above method, the file analyzer includes a dynamic file parser and a static analysis tool;

[0019] The calling of the file analyzer parses all applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, wherein the third-party SDK list includes at least two third-party SDKs, including:

[0020] Invoking the dynamic file parser to collect a dynamic third-party SDK list corresponding to each application installed in the mobile terminal, wherein the dynamic third-party SDK list includes at least one dynamic third-party SDK;

[0021] Invoking the static analysis tool to parse a static third-party SDK list corresponding to each application installed in the mobile terminal, the static third-party SDK list including at least one static third-party SDK;

[0022] A list of third-party SDKs of all applications installed in the mobile terminal is obtained according to the dynamic third-party SDK list and the static third-party SDK list.

[0023] Furthermore, in the above method, collecting historical privacy information of the target calling object's access to the privacy authority of the mobile terminal includes:

[0024] Collect at least one historical privacy behavior of the target calling object;

[0025] The at least one historical privacy behavior is classified according to sensitivity and / or collection frequency to obtain historical privacy information corresponding to the target calling object.

[0026] Furthermore, in the above method, if the permission management policy is a permission control policy, wherein, based on the received permission management policy, corresponding permission management is performed on the target calling object that has access to the privacy permission of the mobile terminal, including:

[0027] Based on the received permission management policy, the target calling object is allowed to call and access part of the privacy permissions of the mobile terminal, and no response is returned to the target calling object calling and accessing other permissions other than part of the privacy permissions of the mobile terminal.

[0028] Furthermore, in the above method, if the permission management policy is a blacklist control policy, performing corresponding permission management on the target calling object with access to the privacy permission of the mobile terminal based on the received permission management policy includes:

[0029] Based on the received blacklist management policy, the target calling object is directly prohibited from calling the privacy authority of the mobile terminal.

[0030] Furthermore, in the above method, the privacy rights management method based on the iOS system further includes:

[0031] If so, the target calling object is determined to be the application program itself in the mobile terminal, and the access corresponding to the target calling object is executed.

[0032] According to another aspect of the present application, a non-volatile storage medium is also provided, on which computer-readable instructions are stored. When the computer-readable instructions can be executed by a processor, the processor implements the above-mentioned privacy authority management method based on the IOS system.

[0033] According to another aspect of the present application, a privacy rights management device based on an iOS system is provided, wherein the device includes:

[0034] one or more processors;

[0035] a computer-readable medium for storing one or more computer-readable instructions,

[0036] When the one or more computer-readable instructions are executed by the one or more processors, the one or more processors implement the above-mentioned privacy authority management method based on the IOS system.

[0037] Compared with the prior art, the present application obtains a third-party SDK list for a mobile terminal installed with an iOS system; constructs a monitor for monitoring call objects accessing privacy permissions in the mobile terminal; monitors access to the privacy permissions of the mobile terminal through the monitor to detect a target call object; determines whether the target call object is on the third-party SDK list; if not, collects historical privacy information of the target call object accessing the privacy permissions of the mobile terminal and uploads it to a server, so that the server generates a corresponding permission management policy based on the historical privacy information; and performs corresponding permission management on the target call object accessing the privacy permissions of the mobile terminal based on the received permission management policy. This implements a system in which, after constructing a monitor for real-time monitoring of access to privacy permissions in a mobile terminal installed with an iOS system, judgment and analysis are performed on the monitored target call objects, and historical privacy information of target call objects not on the third-party SDK list is collected and counted. Permission management of the target call objects is determined based on the statistical analysis, forming a complete management system for detection, collection, management and restriction, effectively preventing any third-party SDK from accessing user privacy permissions in a mobile terminal installed with an iOS system. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0039] Figure 1 A flowchart illustrating a privacy rights management method based on an iOS system according to one aspect of the present application is shown;

[0040] Figure 2 A flowchart of a privacy rights management method based on an iOS system in accordance with one aspect of the present application is shown for managing the privacy rights of a third-party SDK in an actual application scenario.

[0041] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0042] The present application is described in further detail below with reference to the accompanying drawings.

[0043] In a typical configuration of the present application, the terminal, the device of the service network and the trusted party all include one or more processors (CPUs), input / output interfaces, network interfaces and memories.

[0044] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0045] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include non-transitory media such as modulated data signals and carrier waves.

[0046] like Figure 1 As shown, one aspect of the present application provides a flowchart of a privacy rights management method based on an iOS system, wherein the method includes steps S11, S12, S13, S14, S15, and S16, specifically including the following steps:

[0047] Step S11, obtaining a third-party SDK list of a mobile terminal, where the system installed on the mobile terminal is an IOS system; herein, the third-party SDK list of the mobile terminal refers to a list of third-party SDKs obtained when using a mobile terminal installed with an IOS system, because each application needs to access different privacy permissions in the mobile terminal according to its own functions. For example, when using a map application in a mobile terminal, the map application will simultaneously display a third-party SDK for positioning service permissions, a third-party SDK for navigation permissions, etc.

[0048] Step S12, construct a monitor for monitoring the calling object of accessing privacy rights in the mobile terminal; in actual application scenarios, the monitor can be implanted in the privacy permission acquisition function of each third-party SDK end, or in the privacy permission provision function of the mobile terminal, or in the privacy permission function acquired at different ports according to the needs of the specific application scenario, etc. In a preferred embodiment of the present application, the monitor is preferably implanted in the privacy permission acquisition function of the third-party SDK end, so as to realize real-time and accurate monitoring of each third-party SDK that accesses privacy rights in the mobile terminal, and effectively curb the arbitrary access of bad third-party SDKs to privacy rights in the mobile terminal.

[0049] In step S13, the privacy authority for accessing the mobile terminal is monitored by the monitor to detect the target calling object, thereby locating and locking the target calling object for accessing the privacy authority of the mobile terminal, making the target calling object clear and unambiguous, thereby making subsequent judgment and analysis of data more accurate and reducing the risk of malicious access to the mobile terminal.

[0050] Step S14, determining whether the target calling object exists in the third-party SDK list; in actual application scenarios, the determination method includes but is not limited to checking the calling thread in the privacy permission function corresponding to the target calling object. Specifically, checking whether the caller in the call stack of the calling thread in the privacy permission function exists in the third-party SDK list to determine whether the target calling object is the application software itself in the mobile terminal, or another third-party SDK.

[0051] For example, there are 4 pieces of information in the call stack, among which sequence 1 includes the caller system, and the called method initializes the page; sequence 2 includes the caller application software, and the called method pulls up the SDK; sequence 3 includes the caller third-party SDK, and the called method getlocation; sequence 4 includes the caller application software, and the called methods perform other operations. It can be seen that it is the third-party SDK that calls the privacy permission method, rather than the application software itself. By combining the obtained mobile terminal third-party SDK list to screen and check each target calling object, it is convenient to conduct subsequent analysis of third-party SDKs that are not the application software itself, thereby improving management efficiency.

[0052] Step S15: If not, historical privacy information of the target calling object's privacy rights to access the mobile terminal is collected and uploaded to the server, so that the server generates a corresponding rights management policy based on the historical privacy information.

[0053] It should be noted that after the server collects historical privacy information of the target calling object and uploads it to the server, the server will analyze whether there is any unauthorized collection information in each historical privacy information. Among them, unauthorized collection information refers to historical privacy information corresponding to abnormal behaviors such as the privacy permissions accessed by the target calling object do not match the functions of the target calling object; after analysis, the server generates a corresponding permission management policy for the target calling object based on the number, nature and other attributes of the unauthorized collection information, realizes the collection and statistics of historical privacy information of the target calling object, and analyzes the statistical results to obtain different permission management policies for different target calling objects.

[0054] Step S16: Based on the received permission management policy, corresponding permission management is performed on the target calling object with access to the privacy permission of the mobile terminal.

[0055] Through the above steps S11 to S16, the list of third-party SDKs of mobile terminals installed with the IOS system is obtained, and combined with the constructed monitor, the calling objects that access the privacy permissions in the mobile terminal are detected and analyzed, and the target calling objects of the application software itself in the non-mobile terminal are obtained. The historical privacy information of the target calling objects is collected and counted, and the statistical structure is analyzed to obtain the corresponding permission management strategy. Finally, permission management is performed according to the permission management strategy, forming a privacy permission management technology for detecting, collecting, analyzing, counting and controlling the privacy permissions of third-party SDKs on mobile terminals installed with the IOS system, preventing third-party SDKs from abusing permissions and stealing user privacy information.

[0056] In a preferred embodiment of the present application, a third-party SDK list A of a mobile terminal installed with an iOS system is preferably obtained, wherein the third-party SDK list A only contains a certain map application and the third-party SDK for location service permissions and navigation permissions corresponding to the map application; a monitor is constructed to monitor the calling object for accessing privacy permissions in the mobile terminal, and the monitor is embedded in the function for obtaining privacy permissions on the third-party SDK side; in response to the access of the privacy permission function on the third-party SDK side, the monitor detects the third-party SDK for album permissions, that is, the target calling object is the third-party SDK for album permissions; based on the third-party SDK list A, it is determined that the third-party SDK for album permissions does not exist in the third-party SDK list A; historical privacy information of the third-party SDK for album permissions is collected and uploaded to the server, the server determines whether there is any unauthorized collection of information in the historical privacy information of the third-party SDK for album permissions, determines that there is abnormal historical privacy information in the third-party SDK for album permissions, and generates a permission management policy for the third-party SDK for album permissions; finally, the mobile terminal receives the permission management policy and completes permission management of the third-party SDK for album permissions.

[0057] Following the above embodiment of the present application, the step S11 of obtaining the third-party SDK list of the mobile terminal specifically includes:

[0058] Build a file analyzer for collecting third-party SDKs in applications;

[0059] Call the file analyzer to parse all the applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, where the third-party SDK list includes at least two third-party SDKs, thereby acquiring the third-party SDK in each application in the mobile terminal and collecting the third-party SDKs that need to be accessed in each application.

[0060] In a preferred embodiment of the present application, it is preferred that only a certain map application exists in the mobile terminal, and a file analyzer is constructed to collect third-party SDKs in the application; the file analyzer is called to parse and obtain a third-party SDK for positioning service permissions and a third-party SDK for navigation permissions in a certain map application in the mobile terminal A, and obtain the third-party SDK list A of the mobile terminal.

[0061] Following the above embodiment of the present application, the file analyzer includes a dynamic file parser and a static analysis tool;

[0062] The file analyzer is called in step S11 to parse all applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, wherein the third-party SDK list includes at least two third-party SDKs, including:

[0063] The dynamic file parser is called to collect a dynamic third-party SDK list corresponding to each application installed in the mobile terminal, wherein the dynamic third-party SDK list includes at least one dynamic third-party SDK; in an actual application scenario, a MachO file parser is constructed to check the fields identified by the LC_LOAD_DYLIB loading instruction and the LC_LOAD_WEAK_DYLIB loading instruction in the IOS application installation package, and a dynamic third-party SDK loading list is collected, wherein the LC_LOAD_DYLIB loading instruction is a strong reference loading instruction, that is, it is used to indicate that if the current library cannot be loaded successfully, an error will be reported, resulting in startup failure; the LC_LOAD_WEAK_DYLIB loading instruction is a weak reference loading instruction, that is, it is used to indicate that if the library exists under the loading path, it will be introduced, otherwise it will not be introduced and will not affect the use.

[0064] The static analysis tool is called to parse a static third-party SDK list corresponding to each application installed in the mobile terminal, where the static third-party SDK list includes at least one static third-party SDK.

[0065] In actual application scenarios, static analysis tools can exist on mobile terminals or on servers. The acquisition and invocation of static analysis tools are determined based on actual application requirements. When the static analysis tool is on the server, it invokes the online static analysis tool on the server and then performs static analysis on the iOS installation package or manually inputs static library detection features to determine the list of third-party static libraries and the ownership of files within the static libraries. The static library analysis results are then sent to the third-party SDK privacy rights management tool on the mobile terminal.

[0066] A list of third-party SDKs of all applications installed in the mobile terminal is obtained according to the dynamic third-party SDK list and the static third-party SDK list.

[0067] It should be noted that based on the application functions of the application and the characteristics of some third-party SDKs, there are dynamic third-party SDKs and static third-party SDKs in the application. Among them, dynamic third-party SDK means that the application needs to dynamically load the calling logic when calling certain privacy permissions, and static third-party SDK means that the application needs to statically load the calling logic when calling certain privacy permissions. By simultaneously collecting dynamic third-party SDKs and static third-party SDKs in each application, the comprehensiveness and completeness of the third-party SDK list of mobile terminals can be improved.

[0068] In a preferred embodiment of the present application, it is preferred that only a certain map application exists in the mobile terminal, and a file analyzer for collecting third-party SDKs in the application is constructed, wherein the file analyzer includes a dynamic file parser and a static analysis tool; the static analysis tool is called to parse and obtain a static third-party SDK list of a certain map application in the mobile terminal, wherein the static third-party SDK list of the certain map application includes a third-party SDK with positioning service permissions; the dynamic file parser is called to collect a dynamic third-party SDK list of a certain map application installed in the mobile terminal, wherein the dynamic third-party SDK list of the certain map application includes a third-party SDK with navigation permissions, and the dynamic third-party SDK list and the static third-party SDK list are combined to form a complete third-party SDK list A of the mobile terminal.

[0069] Following the above embodiment of the present application, the step S15 of collecting historical privacy information of the target calling object's access to the privacy authority of the mobile terminal specifically includes:

[0070] Collect at least one historical privacy behavior of the target calling object;

[0071] The at least one historical privacy behavior is classified according to sensitivity and / or collection frequency to obtain historical privacy information corresponding to the target calling object.

[0072] Here, at least one historical privacy behavior can be classified only according to sensitivity, or only according to collection frequency, or at least one historical privacy behavior can be classified according to sensitivity and collection frequency. By classifying the collected historical privacy behaviors corresponding to the third-party SDK according to sensitivity and / or collection frequency, and by collecting and analyzing the target call object data, data support is provided for the subsequent generation of permission management strategies.

[0073] In a preferred embodiment of the present application, two historical privacy behaviors of a network interface type third-party SDK accessing a mobile terminal are preferably collected, wherein the first historical privacy behavior is the network interface type third-party SDK accessing microphone permissions, and the second historical privacy behavior is the network interface type third-party SDK accessing network permissions. Preferably, the first historical privacy behavior and the second historical privacy behavior are classified only according to sensitivity, and the classification result of the first historical privacy behavior is a sensitive behavior, and the classification result of the second historical privacy behavior is a non-sensitive behavior, thereby obtaining the historical privacy information corresponding to the network interface type third-party SDK.

[0074] Following the above embodiment of the present application, if the permission management policy is a permission control policy, wherein the step S16 performs corresponding permission management on the target calling object that has access to the privacy permission of the mobile terminal based on the received permission management policy, specifically including:

[0075] Based on the received permission management policy, the target calling object is allowed to call and access part of the privacy permissions of the mobile terminal, and no response is returned to the target calling object calling and accessing other permissions other than part of the privacy permissions of the mobile terminal, so that only the target calling object is allowed to access the access requirements corresponding to the target calling object, and no response is returned for other permissions, which effectively suppresses the target access object's abuse of the privacy permission in the mobile terminal after the mobile terminal grants the target access object the privacy permission, and avoids the privacy permission leakage problem caused by abnormalities in the target access object.

[0076] For example, the permission management policy of the receiving network interface third-party SDK is the permission control policy, which only allows the network interface third-party SDK to access the network permission of the mobile terminal's privacy permission, while other permissions will not allow the network interface third-party SDK to call other permissions.

[0077] Following the above embodiment of the present application, if the permission management policy is a blacklist control policy, wherein, step S16 performs corresponding permission management on the target calling object that has access to the privacy permission of the mobile terminal based on the received permission management policy, specifically including:

[0078] Based on the received blacklist management policy, the target calling object is directly prohibited from calling the privacy authority of the mobile terminal.

[0079] Here, there is a third-party SDK blacklist in the blacklist control policy, among which there is a list of third-party SDKs that are prohibited from using all privacy permissions in the third-party SDK blacklist; in actual application scenarios, when the method for obtaining privacy permissions of the target call object in the third-party SDK blacklist is called, the monitor checks the call stack in the privacy permission function corresponding to the target call object, and compares the target call object with the third-party SDK blacklist; when the target call object hits the third-party SDK blacklist, the privacy permission function call returns, stops the call of the call stack, and terminates the execution of subsequent operations, thereby achieving the purpose of preventing the third-party SDK blacklist from obtaining privacy information.

[0080] For example, the permission management policy for receiving a third-party SDK for drawing UI is a blacklist control policy, which directly prohibits the third-party SDK for drawing UI from calling all privacy permissions of the mobile terminal.

[0081] Following the above embodiments of the present application, an embodiment of one aspect of the present application provides a privacy rights management method based on an iOS system, further comprising:

[0082] If so, the target calling object is determined to be the application program itself in the mobile terminal, and the access corresponding to the target calling object is executed.

[0083] In a preferred embodiment of the present application, the third-party SDK list of the preferred mobile terminal contains only a certain map-type third-party SDK, a monitor is constructed, and the third-party SDK for obtaining location information is monitored, and it is determined that the third-party SDK for obtaining location information exists in the third-party SDK list of the mobile terminal, the target calling object is determined to be the application itself in the mobile terminal, and the access corresponding to the target calling object is executed.

[0084] like Figure 2As shown, this is a flow chart of a privacy permission management method based on the iOS system in an actual application scenario in one aspect of the present application, in which a dynamic file parser is called to obtain a dynamic third-party SDK list, a static analysis tool is called on the server side to parse and obtain a static third-party SDK list, and the list is sent to the client. After information supplementation, a complete third-party SDK list is formed; a monitor is constructed on the client, and a monitor is implanted in each function for obtaining user privacy permissions. When a thread calls to obtain privacy permission information, the monitor analyzes and checks whether there is a dynamic third-party SDK list and the third-party SDK obtained in the static third-party SDK list in the call stack of the thread; if not, the historical privacy information of the target calling object is collected and reported to the server; the server classifies various historical privacy behaviors according to sensitivity and collection frequency, displays and generates corresponding permission management policies, and sends the permission management policies to the client; the client manages access to privacy permissions according to the permission management policy, and prevents restricted privacy permission function calls from calling data.

[0085] Furthermore, in the actual application scenario of this application, the privacy permissions invoked in a mobile terminal installed with an iOS system include but are not limited to those shown in Table 1 below:

[0086] Table 1 Privacy permissions and their descriptions in mobile terminals

[0087] Privacy Permissions Privacy Permission Description Location Services Single positioning, continuous positioning, background positioning, obtain latitude and longitude, obtain geographic location. Address Book Read information from the address book and write information to the address book. Microphone permissions Record using microphone. Camera permissions Call the front and rear cameras of the device. Album permissions Access the user's photo album. Bluetooth permissions Call Bluetooth permissions for search, connection, and information transmission. Media Library Permissions Access the user's media library. SMS permissions Edit and send text message. Network permissions Use cellular, WIFI network.

[0088] According to another aspect of the present application, a non-volatile storage medium is also provided, on which computer-readable instructions are stored. When the computer-readable instructions can be executed by a processor, the processor implements the above-mentioned privacy authority management method based on the IOS system.

[0089] According to another aspect of the present application, a privacy rights management device based on an iOS system is provided, wherein the device includes:

[0090] one or more processors;

[0091] a computer-readable medium for storing one or more computer-readable instructions,

[0092] When the one or more computer-readable instructions are executed by the one or more processors, the one or more processors implement the above-mentioned privacy authority management method based on the IOS system.

[0093] Here, for the detailed contents of each embodiment of the privacy rights management device based on the IOS system, please refer to the corresponding part of the embodiment of the privacy rights management method based on the IOS system mentioned above, which will not be repeated here.

[0094] In summary, the present application obtains a third-party SDK list for a mobile terminal, where the mobile terminal is installed with an iOS system; constructs a monitor for monitoring call objects that access privacy permissions in the mobile terminal; monitors access to the privacy permissions of the mobile terminal through the monitor to detect the target call object; determines whether the target call object is on the third-party SDK list; if not, collects historical privacy information of the target call object accessing the privacy permissions of the mobile terminal and uploads it to a server, so that the server generates a corresponding permission management policy based on the historical privacy information; and performs corresponding permission management on the target call object that accesses the privacy permissions of the mobile terminal based on the received permission management policy. This implements a system in which, after constructing a monitor for real-time monitoring of access to privacy permissions in a mobile terminal installed with an iOS system, judgment and analysis are performed on the monitored target call objects, and historical privacy information of target call objects not on the third-party SDK list is collected and counted. Permission management of the target call objects is obtained based on the statistical analysis, thereby forming a complete management system for detection, collection, management and restriction, effectively curbing access to user privacy permissions by any third-party SDK in a mobile terminal installed with an iOS system.

[0095] It should be noted that the application can be implemented in software and / or a combination of software and hardware, for example, can be implemented using an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the application can be executed by a processor to realize the steps or functions described above. Similarly, the software program of the application (including relevant data structures) can be stored in a computer-readable recording medium, for example, a RAM memory, a magnetic or optical drive or a floppy disk and similar devices. In addition, some steps or functions of the application can be implemented using hardware, for example, as a circuit that cooperates with a processor to perform each step or function.

[0096] In addition, a part of the present application may be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can call or provide the method and / or technical solution according to the present application through the operation of the computer. The program instructions for calling the method of the present application may be stored in a fixed or removable recording medium, and / or transmitted through a data stream in a broadcast or other signal-carrying medium, and / or stored in a working memory of a computer device that runs according to the program instructions. Here, according to an embodiment of the present application, a device is included, which includes a memory for storing computer program instructions and a processor for executing program instructions, wherein, when the computer program instructions are executed by the processor, the device is triggered to run the method and / or technical solution based on the aforementioned multiple embodiments of the present application.

[0097] It is obvious to those skilled in the art that the present application is not limited to the details of the above-mentioned exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims are included in the present application. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim can also be implemented by one unit or device through software or hardware. Words such as first and second are used to indicate names and do not indicate any particular order.

Claims

1. A privacy rights management method based on the IOS system, wherein: The method comprises: Obtain a list of third-party SDKs for a mobile terminal, where the mobile terminal is installed with an iOS system; Constructing a monitor for monitoring the calling objects that access privacy rights in the mobile terminal; The privacy authority for accessing the mobile terminal is monitored by the monitor to detect the target calling object; Determine whether the target calling object exists in the third-party SDK list; If not, historical privacy information of the target calling object's privacy rights to access the mobile terminal is collected and uploaded to the server, so that the server generates a corresponding rights management policy based on the historical privacy information; wherein the server generates the corresponding rights management policy based on the historical privacy information, including: the server analyzes whether there is any unauthorized collection information in each of the historical privacy information, and if there is any abnormal historical privacy information, the server generates a corresponding rights management policy for the target calling object based on the amount and nature of the unauthorized collection information; Based on the received permission management policy, corresponding permission management is performed on the target calling object that has the privacy permission to access the mobile terminal.

2. The method according to claim 1, wherein The obtaining of a list of third-party SDKs for a mobile terminal includes: Build a file analyzer for collecting third-party SDKs in applications; The file analyzer is called to parse all applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, where the third-party SDK list includes at least two third-party SDKs.

3. The method according to claim 2, wherein: The file analyzer includes a dynamic file parser and a static analysis tool; The calling of the file analyzer parses all applications installed in the mobile terminal to obtain a third-party SDK list of the mobile terminal, wherein the third-party SDK list includes at least two third-party SDKs, including: Calling the dynamic file parser to collect a dynamic third-party SDK list corresponding to each application installed in the mobile terminal, wherein the dynamic third-party SDK list includes at least one dynamic third-party SDK; Invoking the static analysis tool to parse a static third-party SDK list corresponding to each application installed in the mobile terminal, the static third-party SDK list including at least one static third-party SDK; A list of third-party SDKs of all applications installed in the mobile terminal is obtained according to the dynamic third-party SDK list and the static third-party SDK list.

4. The method according to claim 1, wherein The collecting of historical privacy information of the target calling object's access to the privacy authority of the mobile terminal includes: Collect at least one historical privacy behavior of the target calling object; The at least one historical privacy behavior is classified according to sensitivity and / or collection frequency to obtain historical privacy information corresponding to the target calling object.

5. The method according to claim 1, wherein If the permission management policy is a permission control policy, performing corresponding permission management on the target calling object with access to the privacy permission of the mobile terminal based on the received permission management policy includes: Based on the received permission management policy, the target calling object is allowed to call and access part of the privacy permissions of the mobile terminal, and no response is returned to the target calling object calling and accessing other permissions other than part of the privacy permissions of the mobile terminal.

6. The method according to claim 1, wherein If the permission management policy is a blacklist control policy, performing corresponding permission management on the target calling object with access to the privacy permission of the mobile terminal based on the received permission management policy includes: Based on the received blacklist management policy, the target calling object is directly prohibited from calling the privacy authority of the mobile terminal.

7. The method according to claim 1, wherein The method further comprises: If so, the target calling object is determined to be the application program itself in the mobile terminal, and the access corresponding to the target calling object is executed. 8 . A non-volatile storage medium having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executable by a processor, the processor is caused to implement the method according to claim 1 .

9. A privacy rights management device based on the IOS system, wherein: The device includes: one or more processors; a computer-readable medium for storing one or more computer-readable instructions, When the one or more computer-readable instructions are executed by the one or more processors, the one or more processors are caused to implement the method according to claims 1 to 7.

Images