Method and device for detecting privacy compliance of applet

Through automated detection methods and multiple detection methods, combined with static and dynamic scanning technology, the problems of low efficiency and insufficient accuracy of privacy compliance detection of mini programs are solved, and efficient and accurate privacy compliance detection is achieved.

CN118940280APending Publication Date: 2024-11-12ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411161432.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-22
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The privacy compliance detection of existing technology small and medium-sized programs mainly relies on manual intervention, resulting in high costs and long cycles, making it difficult to effectively detect multiple privacy compliance risk points.

Method used

Use automated detection methods to determine the detection items based on privacy compliance detection needs, and conduct privacy compliance inspection through a combination of dynamic simulation, static scanning and dynamic simulation, including combining static and Dynamic scanning technology.

Benefits of technology

It greatly improves the efficiency and accuracy of privacy compliance testing of mini programs, reduces manual intervention, and improves detection efficiency and accuracy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118940280A_ABST
    Figure CN118940280A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an applet privacy compliance detection method and device. When privacy compliance detection is carried out, an applet privacy compliance detection request is obtained, and privacy compliance detection items are determined according to privacy compliance detection requirements in the applet privacy compliance detection request. Then, according to page touch path characteristics of the privacy compliance detection item and source code accessibility of the to-be-detected applet, a privacy compliance detection mode for the privacy compliance detection item is determined, and the privacy compliance detection mode comprises a privacy compliance detection mode for performing dynamic simulation according to a specified compliance risk point touch path; and a privacy compliance detection mode based on combination of static scanning and dynamic simulation or a privacy compliance detection mode for dynamic simulation according to page traversal touch. And then, performing privacy compliance detection on the determined privacy compliance detection item on the to-be-detected applet by using the determined privacy compliance detection mode.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of this specification generally relate to the field of artificial intelligence, and in particular, to a method and device for detecting privacy compliance of mini-programs. Background Art

[0002] It has gradually become a trend to provide personal information data to Internet service platforms through mini-programs installed on mobile application platforms to obtain Internet services. As the protection of personal privacy information continues to strengthen, the compliance sharing and use of personal information has become more and more important, and the privacy compliance issues of mini-programs are particularly important.

[0003] Currently, the privacy compliance testing for mini programs in the industry mainly relies on manual intervention. However, due to the large number of mini programs, the large size and multiple pages of a single mini program, and the many risk points of mini programs, manual intervention solutions have the problems of high cost and slow cycle. Summary of the invention

[0004] The embodiments of this specification provide a small program privacy compliance detection solution. Using this small program privacy compliance detection solution, it is possible to achieve automatic detection of multiple privacy compliance risk points, thereby greatly improving the efficiency of small program privacy compliance detection and ensuring the accuracy of small program privacy compliance detection.

[0005] According to one aspect of an embodiment of the present specification, a method for mini-program privacy compliance detection is provided, including: obtaining a mini-program privacy compliance detection request, the mini-program privacy compliance detection request including a privacy compliance detection requirement; determining a privacy compliance detection item based on the privacy compliance detection requirement; determining a privacy compliance detection method for the privacy compliance detection item based on the page touch path characteristics of the privacy compliance detection item and the availability of the source code of the mini-program to be detected, the privacy compliance detection method including a privacy compliance detection method for dynamic simulation according to a specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method for dynamic simulation according to page traversal touches; and performing a privacy compliance detection on the mini-program to be detected for the privacy compliance detection item using the determined privacy compliance detection method.

[0006] Optionally, in an example of the above aspect, based on the compliance risk detection characteristics of the privacy compliance detection item and the source code availability of the mini-program to be detected, determining the privacy compliance detection method for the privacy compliance detection item includes: in response to the page touch path characteristics indicating a deterministic page touch path, determining the privacy compliance detection method as a privacy compliance detection method that performs dynamic simulation according to the specified page touch path; in response to the page touch path characteristics indicating an indeterminate page touch path and the mini-program to be detected has source code availability, determining the privacy compliance detection method as a privacy compliance detection method based on a combination of static scanning and dynamic simulation; in response to the page touch path characteristics indicating an indeterminate page touch path and the mini-program to be detected does not have source code availability, determining the privacy compliance detection method as a privacy compliance detection method that performs dynamic simulation according to page traversal clicks.

[0007] Optionally, in an example of the above aspect, the privacy compliance detection method is a privacy compliance detection method that performs dynamic simulation according to a specified page touch path. Performing privacy compliance detection on the mini-program to be detected using the determined privacy compliance detection method includes: dynamically simulating touch of the mini-program to be detected according to the specified page touch path; and performing privacy compliance detection during the dynamic simulation touch to obtain a privacy compliance detection result.

[0008] Optionally, in an example of the above aspect, the privacy compliance detection method is a privacy compliance detection method based on a combination of static scanning and dynamic simulation. Using the determined privacy compliance detection method to perform privacy compliance detection on the mini program to be detected includes: performing static code scanning on the source code of the mini program to obtain page attributes of all pages of the mini program, the page attributes including URL addresses and JsAPI call permission types; performing page filtering and page clustering on the pages of the mini program based on the JsAPI call permission type; and for each page cluster, selecting a page for dynamic simulation detection to obtain privacy compliance detection results.

[0009] Optionally, in an example of the above aspect, the privacy compliance detection method is a privacy compliance detection method that performs dynamic simulation according to page traversal. Using the determined privacy compliance detection method to perform privacy compliance detection on the mini-program to be detected includes: performing page breadth traversal from the homepage of the mini-program; and performing dynamic simulation detection on the traversed pages to obtain privacy compliance detection results.

[0010] Optionally, in an example of the above aspect, the privacy compliance detection item includes at least two privacy compliance detection items. The mini-program privacy compliance detection method also includes: according to the page touch path of the page where the privacy compliance detection item is located in the mini-program, determining from the privacy compliance detection items a combination of privacy compliance detection items that can be combined for detection in a single dynamic detection process. Correspondingly, using the determined privacy compliance detection method to perform a privacy compliance detection on the privacy compliance detection items of the mini-program to be detected includes: for each combination of privacy compliance detection items, performing a single dynamic detection process on the mini-program to be detected to perform a privacy compliance detection on the privacy compliance detection items in the privacy compliance detection item combination using the corresponding privacy compliance detection method, and for non-combinable privacy compliance detection items, performing a single dynamic detection process on the mini-program to be detected to perform a privacy compliance detection using the corresponding privacy compliance detection method.

[0011] Optionally, in an example of the above aspect, obtaining the mini-program privacy compliance detection request includes: obtaining the mini-program privacy compliance detection request via a page-level interface or a system-level interface.

[0012] Optionally, in an example of the above aspect, the mini program to be detected is acquired via one of the following methods: a mini program acquisition method based on the mini program application ID; a mini program acquisition method based on the mini program application name; a mini program acquisition method based on the mini program specified page URL; and a mini program acquisition method based on the mini program QR code.

[0013] Optionally, in an example of the above aspect, the mini-program privacy compliance detection method also includes: generating a privacy compliance detection report based on the privacy compliance detection results.

[0014] Optionally, in an example of the above aspect, the mini-program privacy compliance detection method is implemented via a mini-program privacy compliance detection model, and the mini-program privacy compliance detection model includes a detection initiation interface layer, a compliance detection item configuration layer, a compliance detection capability support layer and a compliance detection execution layer.

[0015] According to another aspect of an embodiment of the present specification, there is provided a mini-program privacy compliance detection device, including: a compliance detection request acquisition unit, which acquires a mini-program privacy compliance detection request, wherein the mini-program privacy compliance detection request includes a privacy compliance detection requirement; a compliance detection item determination unit, which determines a privacy compliance detection item according to the privacy compliance detection requirement; a compliance detection method determination unit, which determines a privacy compliance detection method for the privacy compliance detection item according to the page touch path characteristics of the privacy compliance detection item and the source code availability of the mini-program to be detected, wherein the privacy compliance detection method includes a privacy compliance detection method that performs dynamic simulation according to a specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touches; and a compliance detection unit, which uses the determined privacy compliance detection method to perform privacy compliance detection on the mini-program to be detected for the privacy compliance detection item.

[0016] According to another aspect of an embodiment of the present specification, a mini-program privacy compliance detection device is provided, comprising: at least one processor; a memory coupled to the at least one processor; and a computer program stored in the memory, wherein the at least one processor executes the computer program to implement the mini-program privacy compliance detection method as described above.

[0017] According to another aspect of an embodiment of the present specification, a computer-readable storage medium is provided, which stores executable instructions, which, when executed, cause a processor to execute the mini-program privacy compliance detection method as described above.

[0018] According to another aspect of an embodiment of the present specification, a computer program product is provided, including a computer program, wherein the computer program is executed by a processor to implement the mini-program privacy compliance detection method as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] A further understanding of the nature and advantages of the content of this specification may be achieved by referring to the following drawings. In the drawings, similar components or features may have the same reference numerals.

[0020] Figure 1 An example flowchart of a mini-program privacy compliance detection method according to an embodiment of the present specification is shown.

[0021] Figure 2 An example schematic diagram of a privacy compliance detection solution that performs dynamic simulation according to a specified page touch path according to an embodiment of the present specification is shown.

[0022] Figure 3A detection effect diagram of a privacy compliance detection solution that performs dynamic simulation according to a specified page touch path according to an embodiment of the present specification is shown.

[0023] Figure 4 An example detection flowchart of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of the present specification is shown.

[0024] Figure 5 An example schematic diagram of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of the present specification is shown.

[0025] Figure 6 A detection effect diagram of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of this specification is shown.

[0026] Figure 7 An example schematic diagram of a privacy compliance detection solution that performs dynamic simulation according to page traversal touches according to an embodiment of the present specification is shown.

[0027] Figure 8 An example schematic diagram of a mini-program privacy compliance detection model according to an embodiment of the present specification is shown.

[0028] Fig. 9 An example block diagram of a mini-program privacy compliance detection device according to an embodiment of the present specification is shown.

[0029] Fig.10 An example schematic diagram of a mini-program privacy compliance detection device implemented based on a computer system according to an embodiment of the present specification is shown. DETAILED DESCRIPTION

[0030] The subject matter described herein will now be discussed with reference to example embodiments. It should be understood that the discussion of these embodiments is only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not a limitation of the scope of protection, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed can be changed without departing from the scope of protection of the contents of this specification. Various examples can omit, replace or add various processes or components as needed. For example, the described method can be performed in an order different from the described order, and various steps can be added, omitted or combined. In addition, the features described relative to some examples can also be combined in other examples.

[0031] As used herein, the term "including" and its variations represent open terms, meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.

[0032] The flowcharts used in this specification illustrate the operations implemented by the system according to some embodiments in this specification. It should be clearly understood that the operations of the flowcharts may not be implemented in sequence. On the contrary, the operations may be implemented in reverse order or simultaneously. In addition, one or more other operations may be added to the flowchart. One or more operations may be removed from the flowchart.

[0033] The following will describe a mini-program privacy compliance detection method and a mini-program privacy compliance detection device according to an embodiment of this specification with reference to the accompanying drawings.

[0034] Figure 1 An example flowchart of a mini-program privacy compliance detection method 100 according to an embodiment of the present specification is shown.

[0035] like Figure 1 As shown, at 110, a mini program privacy compliance detection request is obtained.

[0036] In some embodiments, a mini-program privacy compliance detection request can be initiated by a user. For example, a user can initiate a request through the request initiation interface of the mini-program privacy compliance detection device (for example, a request initiation input box in the user interaction interface, etc.), and the initiated mini-program privacy compliance detection request includes a privacy compliance detection requirement. The privacy compliance detection requirement is used to indicate the compliance detection requirements during privacy compliance detection, for example, for compliance detection content that needs to be detected, etc. For example, a privacy compliance detection requirement may be "detect whether all high-activity mini-programs on the XXX application platform have a privacy policy." Privacy compliance detection requirements are usually proposed by users (for example, business parties). In addition, in some embodiments, the mini-program privacy compliance detection request may also include at least one of the program identification information, data source information, and mini-program source code of the mini-program to be detected.

[0037] Examples of request initiation interfaces may include, but are not limited to, page-level interfaces, system-level interfaces, and the like. The page-level detection interface is used to initiate mini-program privacy compliance detection through a page. The system-level interface is used to support the initiation of mini-program privacy compliance detection based on TR, HTTP, and messages, and return the privacy compliance detection results through messages. In some embodiments, the mini-program privacy compliance detection device may perform mini-program privacy compliance detection based on the mini-program privacy compliance detection model. In this case, the TR interface, HTTP interface, message interface, and page initiation interface may be configured in the detection initiation interface layer of the mini-program privacy compliance detection model. When a user initiates a mini-program privacy compliance detection, the mini-program privacy compliance detection may be initiated in accordance with the corresponding privacy compliance detection initiation method by triggering the TR interface, HTTP interface, message interface, or page initiation interface in the detection initiation interface layer.

[0038] The data source information is used to indicate the data source of the mini program to be detected, that is, the acquisition method of the mini program to be detected. In some embodiments, the data source may include the mini program application ID, the mini program application name, the mini program designated page URL, and the mini program QR code. The mini program application ID refers to obtaining the mini program by searching the mini program homepage URL spliced ​​with the application ID. The mini program application name refers to obtaining the mini program by performing a simulated search based on the mini program application name in the relevant APP. The mini program designated page URL refers to obtaining the mini program by searching the designated page URL spliced ​​with the mini program application ID. The mini program QR code refers to obtaining the mini program by scanning the mini program QR code in the relevant APP. In the example of performing mini program privacy compliance detection based on the mini program privacy compliance detection model, the mini program application ID, mini program application name, mini program designated page URL, and mini program QR code can be configured in the data source support layer of the mini program privacy compliance detection model for the user to configure the mini program acquisition method. In this way, a variety of mini program acquisition methods from different data sources can be supported, thereby supporting more mini program privacy compliance detection scenarios.

[0039] After receiving the mini program privacy compliance detection request, at 120, the privacy compliance detection item is determined according to the privacy compliance detection requirement in the mini program privacy compliance detection request. In some examples, a set of privacy compliance detection items can be pre-set, and then the privacy compliance detection item is selected or determined from the pre-set set of privacy compliance detection items. Examples of privacy compliance detection items may include, but are not limited to, privacy policy compliance detection items, user authorization compliance detection items, personal information collection compliance detection items, personal data use compliance detection items, etc. Privacy policy compliance detection items include compliance detection items related to privacy policies, such as privacy policy availability (i.e., whether there is a privacy policy), privacy policy pop-up window, privacy policy default check, privacy policy mandatory check, etc. User authorization compliance detection items include compliance detection items related to user authorization, such as notification of permission application purpose (i.e., simultaneous notification of purpose when applying for permission), excessive user authorization, forced user authorization, frequent interruptions after user refusal, etc. Personal information collection compliance detection items include compliance detection items related to personal information collection, such as minimum necessity of collection (i.e., following the principle of minimum necessity when collecting information), user authorization of collection, non-frequent collection frequency, necessity of collection timing, etc. The compliance detection items for personal data use include compliance detection items related to personal data use, such as personalized recommendation risks, etc. For example, when the privacy compliance detection requirement is "detect whether all high-activity mini-programs on the XXX application platform have privacy policies", the determined privacy compliance detection item may be "privacy policy availability".

[0040] In the example of performing mini-program privacy compliance detection based on the mini-program privacy compliance detection model, privacy policy compliance detection items, user authorization compliance detection items, personal information collection compliance detection items, personal data use compliance detection items, etc. can be pre-configured in the compliance detection item configuration layer of the mini-program privacy compliance detection model. After receiving the mini-program privacy compliance detection request, the corresponding privacy compliance detection items are configured in the compliance detection item configuration layer according to the privacy compliance detection requirements, thereby realizing the customized configuration of the privacy compliance detection items.

[0041] At 130, a privacy compliance detection method for the privacy compliance detection item is determined based on the page touch path characteristics of the configured privacy compliance detection item and the source code availability of the mini-program to be detected. Here, the privacy compliance detection method may include, for example, a privacy compliance detection method that performs dynamic simulation according to the touch path of a specified compliance risk point, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touch.

[0042] The page touch path characteristics of the privacy compliance detection item are used to reflect whether the page where the privacy compliance detection item is located or the page where the corresponding compliance risk point is located has a deterministic touch path. The page touch path refers to the page operation path that touches the page where the privacy compliance detection item is located from the homepage of the mini-program. If the page where the privacy compliance detection item is located can be touched according to the deterministic page operation steps or page operation procedures from the homepage of the mini-program, the privacy compliance detection item is considered to have a deterministic touch path. The page touch path of the privacy compliance detection item can also be called a page detection path, a compliance risk point touch path, or a compliance risk point detection path. In some embodiments, the page touch path characteristics of the privacy compliance detection item can be determined according to the detection item name, detection item type, or detection requirement of the privacy compliance detection item. For example, with respect to privacy policy availability, since the privacy policy is usually set in the fixed page structure of the mini-program, the touch path from the homepage of the mini-program to the page where the privacy policy is located is usually fixed, so that the compliance risk point corresponding to the privacy policy availability can be touched through a deterministic touch path. In other words, privacy policy availability has a deterministic compliance risk point touch path. For the mini program that forces user authorization, the corresponding compliance risk points can be set randomly, and there is no deterministic path to reach them. Therefore, the mini program that forces user authorization does not have a deterministic path to reach the compliance risk points.

[0043] The source code availability of the mini program to be tested is used to indicate whether the source code of the mini program is available. In some examples, it can be determined whether the mini program has source code availability based on the open source and / or agreement access rights of the mini program. If the mini program is an open source mini program, it is determined that the mini program has source code availability. If the mini program has agreement access rights, that is, the mini program privacy compliance detection party has an agreement with the mini program provider (or mini program developer) to ensure that the mini program privacy compliance detection party has the right to obtain the source program, then it is determined that the mini program has source code availability. Here, the agreement accessibility may include, for example, source code licensing rights, source code rights sharing rights, etc. For example, if the mini program is provided by a mini program provider within a system that determines that the mini program has source code availability, for example, the mini program provider is a brother team in the same company as the mini program privacy compliance detection party and has signed a source code sharing agreement, then it is determined that the mini program has source code availability.

[0044] When determining the privacy compliance detection method, first, determine whether the page touch path characteristics of the privacy compliance detection item indicate a deterministic page touch path. In response to the page touch path characteristics indicating a deterministic compliance risk point touch path, the privacy compliance detection method is determined as a privacy compliance detection method that performs dynamic simulation according to the specified compliance risk point touch path. If the page touch path characteristics indicate a non-deterministic compliance risk point touch path, determine whether the source code of the mini program to be detected is accessible. If the source code is accessible, the privacy compliance detection method is determined as a privacy compliance detection method based on a combination of static scanning and dynamic simulation. If the mini program to be detected does not have source code accessibility, the privacy compliance detection method is determined as a privacy compliance detection method that performs dynamic simulation according to page traversal clicks.

[0045] For example, if the privacy compliance detection item is "privacy policy availability", then due to the deterministic compliance risk point touch path, the privacy compliance detection method is determined as a privacy compliance detection method that performs dynamic simulation according to the specified compliance risk point touch path. If the privacy compliance detection item is "mandatory user authorization" and the mini program has source code availability (for example, an open source mini program), the privacy compliance detection method is determined as a privacy compliance detection method based on a combination of static scanning and dynamic simulation. If the privacy compliance detection item is "mandatory user authorization" and the mini program does not have source code availability (for example, a mini program that does not allow the public disclosure of source code), the privacy compliance detection method is determined as a privacy compliance detection method that performs dynamic simulation according to page traversal clicks.

[0046] After determining the privacy compliance detection method, at 140, the determined privacy compliance detection method is used to perform privacy compliance detection on the mini-program to be detected for the privacy compliance detection items.

[0047] If the privacy compliance detection method is a privacy compliance detection method that dynamically simulates the designated page touch path, then when performing privacy compliance detection, the mini program is dynamically simulated according to the designated page touch path to touch the compliance risk point. For example, call the interface to connect to the real device, open the mobile application platform to render the mini program, and enter the mini program homepage. Subsequently, according to the designated page touch path, call the operation interface to initiate an operation instruction (for example, click, return, swipe the screen, etc.) to perform a dynamic simulation touch operation of the mini program to touch the compliance risk point. Then, perform compliance risk point detection during the dynamic simulation touch to obtain the privacy compliance detection result.

[0048] Figure 2 An example schematic diagram of a privacy compliance detection solution that performs dynamic simulation according to a specified page touch path according to an embodiment of the present specification is shown. Figure 2The example shown is a privacy compliance check for the privacy policy of a mini-program. Figure 3 A detection effect diagram of a privacy compliance detection solution that performs dynamic simulation according to a page touch path according to an embodiment of the present specification is shown.

[0049] like Figure 2 As shown, first, open the mini program homepage and render the page. Then, perform a pop-up window test on the first screen privacy policy. For example, click Figure 3 The three-dot area circled in the upper right corner is processed by the pop-up window. Then, check whether there is a privacy policy option in the pop-up window, that is, the option circled in the lower right corner. If there is an option, it means that there is a privacy policy. Next, click the option to render the specific privacy policy page (that is, the privacy policy main information page), and perform a privacy policy compliance check on the main page in the presented privacy policy main information page.

[0050] Figure 4 An example detection flowchart of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of the present specification is shown.

[0051] If the privacy compliance detection method is a privacy compliance detection method based on a combination of static scanning and dynamic simulation, then when performing privacy compliance detection, the source code of the mini program is statically scanned to obtain the page attributes of all pages of the mini program. Here, all pages include, for example, mobile phone number page sets, location information page sets, etc. Page attributes include, for example, URL addresses and JsAPI call permission types. JsAPI call permission types refer to the user permission types involved in JsAPI calls, such as: Bluetooth, mobile phone, avatar nickname, address, etc.

[0052] Specifically, when performing static scanning, code decompression, rule scanning and page traversal are performed in sequence, followed by page JsAPI detection, page scheme and page path detection to produce page-JsAPI call correspondence, page schema and page path. Page JsAPI detection is used to detect whether the page of the mini program has called JsAPI. For example, page 1 calls the jsapi of the mobile phone number, thereby producing the correspondence between the page and the JsAPI call. After the correspondence between the page and the JsAPI call is produced, the page without the JsAPI call is directly discarded, and the page with the JsAPI call is rendered, and the rendered page is dynamically simulated to perform privacy compliance detection. Page scheme detection is used to detect how many pages the mini program has, and each page has a page url. When performing page path detection, the page and path collection are obtained according to the page scheme and page path, the page is traversed, and the risk judgment is made based on the path length.

[0053] Subsequently, the pages of the mini program are filtered and clustered based on the JsAPI call permission type. For example, pages of the JsAPI call permission type that are not related to privacy compliance are filtered out from the page set, and each type of page is clustered into a page cluster.

[0054] After completing the above page filtering and page clustering, for each page cluster, select a page for dynamic simulation detection to obtain the privacy compliance detection results. Specifically, call the interface to connect to the real device, open the mobile application platform to render the applet, and enter the applet specified page (that is, the selected applet page). Get all valid click points on the specified page, simulate traversal clicks, and observe page changes to perform privacy compliance detection.

[0055] Figure 5 An example schematic diagram of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of this specification is shown, and Figure 6 A detection effect diagram of a privacy compliance detection solution based on a combination of static scanning and dynamic simulation according to an embodiment of this specification is shown.

[0056] If the privacy compliance detection method is a privacy compliance detection method that performs dynamic simulation according to page traversal, when performing privacy compliance detection, the page breadth traversal is performed from the homepage of the mini-program. Subsequently, dynamic simulation detection is performed on the traversed pages to obtain the privacy compliance detection result.

[0057] Figure 7 An example schematic diagram of a privacy compliance detection solution that performs dynamic simulation according to page traversal touches according to an embodiment of the present specification is shown.

[0058] It should be noted that the above description is for the privacy compliance detection process of a single privacy compliance detection item. In some embodiments, the privacy compliance detection item may include at least two privacy compliance detection items. In this case, according to the page touch path of the page where the privacy compliance detection item is located in the mini program to be detected, the privacy compliance detection item combination that can be combined and detected in a single dynamic detection process can be determined from the privacy compliance detection items to be detected. For example, according to the page touch path of the page where the privacy compliance detection item is located in the mini program to be detected, it is determined whether the page touch paths of the pages where multiple privacy compliance detection items are located have set inclusion with each other, that is, whether the page touch path of the page where one privacy compliance detection item is located is a sub-path of the page touch path of the page where another privacy compliance detection item is located. For example, if multiple privacy compliance detection items are located on the same page, the multiple privacy compliance detection items can be combined into a privacy compliance detection combination. If the page touch path of privacy compliance detection item A is obtained by continuing the page operation on the basis of the page touch path of privacy compliance detection item B, the page touch path of privacy compliance detection item B is considered to be a sub-path of the page touch path of privacy compliance detection item A. In this case, privacy compliance detection items A and B can be combined into a privacy compliance detection combination.

[0059] Then, for each combination of privacy compliance detection items, a single dynamic detection process is performed on the mini-program to be detected to perform privacy compliance detection on the privacy compliance detection items in the combination of privacy compliance detection items using corresponding privacy compliance detection methods, and for non-combinable privacy compliance detection items, a single dynamic detection process is performed on the mini-program to be detected to perform privacy compliance detection using corresponding privacy compliance detection methods. According to this privacy compliance detection method, privacy compliance detection for multiple privacy compliance detection items can be achieved in a single dynamic simulation process without the need for each privacy compliance detection item to independently perform a dynamic simulation process, thereby improving the efficiency of privacy compliance detection.

[0060] Optionally, after obtaining the privacy compliance detection result as above, a privacy compliance detection report is generated based on the privacy compliance detection result at 150. The generated privacy compliance detection report may have a specified format, such as PDF format.

[0061] For example, after obtaining the privacy compliance test results, use FreeMaker to load the details of the privacy compliance test results according to the HTML template to generate an HTML page. Then, use Flying Saucer to convert the HTML page into a privacy compliance test report in PDF format. When generating a privacy compliance test report, you can also set data such as fonts, watermarks, icons, density, and transparency.

[0062] In some embodiments, mini-program privacy compliance detection can be performed based on the mini-program privacy compliance detection model. Figure 8 FIG. 8 is a schematic diagram showing an example of a mini-program privacy compliance detection model 800 according to an embodiment of the present specification. Figure 8 As shown, the mini program privacy compliance detection model 800 includes a detection initiation interface layer 810, a data source support layer 820, a compliance detection item configuration layer 830, a compliance detection execution layer 840 and a compliance detection capability support layer 850.

[0063] The detection initiation interface layer 810 is provided with a page-level detection initiation interface and a system-level detection initiation interface. The page-level detection initiation interface is a general detection initiation interface, which is used to initiate the privacy compliance detection of the mini-program through the page. The system-level detection initiation interface includes, for example, a TR interface, an HTTP interface, and a message interface, which is used to support detection initiation requests based on TR, HTTP, and messages, and return privacy compliance detection results through messages.

[0064] The data source support layer 820 is provided with supportable data sources, and the supported data sources include the mini program application ID, the mini program application name, the mini program designated page URL and the mini program QR code, etc. The compliance detection item configuration layer 830 is used for users to configure compliance detection items. The compliance detection item configuration layer is pre-configured with a variety of compliance detection items, such as privacy policy compliance detection items, user authorization compliance detection items, personal information collection compliance detection items, personal data use compliance detection items, etc. Privacy policy compliance detection items include compliance detection items related to privacy policies, such as privacy policy settings, privacy policy pop-ups, privacy policy default check, privacy policy mandatory check, etc. User authorization compliance detection items include compliance detection items related to user authorization, such as application permission synchronization notification purpose, excessive authorization, forced user authorization, frequent interruptions after user refusal, etc. Personal information collection compliance detection items include compliance detection items related to personal information collection, such as collection of minimum necessary compliance, collection of user authorization, frequency of collection, necessity of collection timing, etc. Personal data use compliance detection items include compliance detection items related to personal data use, such as personalized recommendation risks, etc.

[0065] The compliance detection capability support layer 850 is used to provide supportable privacy compliance detection capabilities for use by the privacy detection execution layer 840 to implement the privacy compliance detection of the mini program. The compliance detection capability support layer is provided with static scanning capabilities and dynamic simulation capabilities. Static scanning capabilities may include, for example, code decompression, page traversal, source code scanning, JsAPI detection, scheme detection, page path detection, etc. Dynamic simulation capabilities may include, for example, effective page traversal clicks, automatic pop-up window processing, page long text recognition, page similarity recognition, default check of checkboxes, three-party detection capabilities, etc. Effective page traversal clicks are used to traverse all valid click points on the mini program page and perform traversal clicks. Automatic pop-up window processing is used to identify permission pop-ups, advertising pop-ups, etc. of the mini program page, and automatically close them. Page long text recognition is used to obtain page long text through screenshot + OCR + sliding screen + text splicing. Page similarity recognition is used to comprehensively judge the similarity between pages through information such as image similarity, source code similarity, and page title. The default check of the checkbox is used to identify whether the checkbox of the mini program page is checked by default. The third-party detection capability is used to support the third-party risk detection capability. In addition, in some embodiments, the dynamic simulation capability may also include page anomaly detection and page scenario detection. Page anomaly detection is used to identify whether the mini program page has an error or 404 or a white screen. Page scenario detection is used to identify the scenario of the current mini program page through page keywords, such as: login / refueling / catering, etc.

[0066] The privacy detection execution layer 840 is used to configure compliance detection items and determine the privacy compliance detection method, and use the privacy compliance detection capabilities corresponding to the privacy compliance detection method to perform privacy compliance detection on the mini program for the configured compliance detection items, and generate a privacy compliance detection report.

[0067] The following describes the mini-program privacy compliance detection process based on the mini-program privacy compliance detection model.

[0068] The user initiates a mini-program privacy compliance detection request via a detection initiation interface in the detection initiation interface layer 810, and the initiated mini-program privacy compliance detection request includes a privacy compliance detection requirement. In addition, the user can also configure the data source of the mini-program via the data source support layer 820, that is, the method of obtaining the mini-program, for example, obtaining the mini-program based on the mini-program application ID, obtaining the mini-program based on the mini-program application name, obtaining the mini-program based on the mini-program schema, or obtaining the mini-program based on the mini-program QR code.

[0069] After receiving the mini-program privacy compliance detection request, the privacy compliance detection items to be detected can be configured in the compliance detection item configuration layer 830 based on the mini-program privacy detection requirements, and the privacy compliance detection method can be determined based on the compliance risk detection characteristics of the configured privacy compliance detection items and the source code availability of the mini-program to be detected. After determining the privacy compliance detection method, the compliance detection execution layer 840 uses the static scanning capabilities and / or dynamic simulation capabilities supported by the compliance detection capability support layer 850 to perform privacy compliance detection for the configured privacy compliance detection items and generate a privacy compliance report.

[0070] Fig. 9 FIG. 9 is a block diagram showing an example of a mini-program privacy compliance detection device 900 according to an embodiment of the present specification. Fig. 9 As shown, the mini program privacy compliance detection device 900 includes a compliance detection request acquisition unit 910, a compliance detection item determination unit 920, a compliance detection method determination unit 930 and a compliance detection unit 940.

[0071] The compliance detection request acquisition unit 910 is used to obtain the mini program privacy compliance detection request, and the obtained mini program privacy compliance detection request includes the privacy compliance detection requirement. The operation of the compliance detection request acquisition unit 910 can refer to the above reference Figure 1 The operation of 110 is described.

[0072] The compliance detection item determination unit 920 is used to determine the privacy compliance detection item according to the privacy compliance detection requirement. The operation of the compliance detection item determination unit 920 can refer to the above reference Figure 1 The operation of 120 is described.

[0073] The compliance detection method determination unit 930 is used to determine the privacy compliance detection method for the privacy compliance detection item according to the page touch path characteristics of the privacy compliance detection item and the source code availability of the applet to be detected. The privacy compliance detection method includes a privacy compliance detection method that performs dynamic simulation according to the specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touch. The operation of the compliance detection method determination unit 930 can refer to the above reference Figure 1 The operation of 130 is described.

[0074] The compliance detection unit 940 is used to use the determined privacy compliance detection method to perform privacy compliance detection on the mini program to be detected for the determined privacy compliance detection items. The operation of the compliance detection unit 940 can refer to the above reference Figure 1 The operation of 140 is described.

[0075] Optionally, the mini program privacy compliance detection device 900 may further include a compliance detection report generation unit 950. The compliance detection report generation unit 950 is used to generate a privacy compliance detection report based on the privacy compliance detection result. The operation of the compliance detection report generation unit 950 can refer to the above reference Figure 1 The operation of 150 is described.

[0076] As above Figures 1 to 9 , describes a method and a device for detecting mini-program privacy compliance according to an embodiment of this specification. The above mini-program privacy compliance detection device can be implemented by hardware, or by software, or by a combination of hardware and software.

[0077] Fig.10 FIG. 1 shows an example schematic diagram of a mini-program privacy compliance detection device 1000 implemented based on a computer system according to an embodiment of this specification. Fig.10 As shown, the mini-program privacy compliance detection device 1000 may include at least one processor 1010, a memory (e.g., a non-volatile memory) 1020, a memory 1030, and a communication interface 1040, and the at least one processor 1010, the memory 1020, the memory 1030, and the communication interface 1040 are connected together via a bus 1060. At least one processor 1010 executes at least one computer-readable instruction stored or encoded in the memory (i.e., the above-mentioned element implemented in the form of software).

[0078] In one embodiment, computer executable instructions are stored in a memory, which when executed cause at least one processor 1010 to: obtain a mini-program privacy compliance detection request; determine a privacy compliance detection item based on the privacy compliance detection requirements in the mini-program privacy compliance detection request; determine a privacy compliance detection method for the privacy compliance detection item based on the page touch path characteristics of the privacy compliance detection item and the availability of the source code of the mini-program to be detected, the privacy compliance detection method including a privacy compliance detection method that performs dynamic simulation according to a specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touches; and use the determined privacy compliance detection method to perform privacy compliance detection on the privacy compliance detection item of the mini-program to be detected.

[0079] It should be understood that the computer executable instructions stored in the memory, when executed, cause at least one processor 1010 to perform the above combined operations in various embodiments of this specification. Figure 1-Figure 9 Describes the various operations and functions.

[0080] According to one embodiment, a program product such as a machine-readable medium (e.g., a non-transitory machine-readable medium) is provided. The machine-readable medium may have instructions (i.e., the above-mentioned elements implemented in the form of software), which, when executed by a machine, causes the machine to perform the above-mentioned combination of various embodiments of this specification. Figure 1-Figure 9 Specifically, a system or device equipped with a readable storage medium may be provided, on which a software program code implementing the functions of any of the above-mentioned embodiments is stored, and a computer or processor of the system or device reads and executes the instructions stored in the readable storage medium.

[0081] In this case, the program code itself read from the machine-readable medium can realize the function of any one of the above-mentioned embodiments, and thus the machine-readable code and the machine-readable storage medium storing the machine-readable code constitute a part of the present invention.

[0082] Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or a cloud via a communication network.

[0083] According to one embodiment, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the processor performs the above combination of the various embodiments of this specification. Figure 1-Figure 9 Describes the various operations and functions.

[0084] Those skilled in the art should understand that the various embodiments disclosed above can be modified and altered in various ways without departing from the essence of the invention. Therefore, the protection scope of the present invention should be defined by the appended claims.

[0085] It should be noted that not all steps and units in the above-mentioned processes and system structure diagrams are necessary, and some steps or units can be ignored according to actual needs. The execution order of each step is not fixed and can be determined as needed. The device structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.

[0086] In the above embodiments, the hardware unit or module can be realized by mechanical or electrical means. For example, a hardware unit, module or processor can include permanent dedicated circuit or logic (such as special processor, FPGA or ASIC) to complete the corresponding operation. The hardware unit or processor can also include programmable logic or circuit (such as general-purpose processor or other programmable processor), which can be temporarily set by software to complete the corresponding operation. Specific implementation (mechanical method or dedicated permanent circuit or temporary circuit) can be determined based on cost and time consideration.

[0087] The specific embodiments described above in conjunction with the accompanying drawings describe exemplary embodiments, but do not represent all embodiments that can be implemented or fall within the scope of protection of the claims. The term "exemplary" used throughout this specification means "used as an example, instance or illustration" and does not mean "preferred" or "having advantages" over other embodiments. For the purpose of providing an understanding of the described technology, the specific embodiments include specific details. However, these technologies can be implemented without these specific details. In some instances, in order to avoid making the concepts of the described embodiments difficult to understand, well-known structures and devices are shown in block diagram form.

[0088] The above description of the present disclosure is provided to enable any person of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of protection of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is consistent with the widest range of principles and novel features disclosed herein.

Claims

1. A method for detecting privacy compliance of a mini program, comprising: Obtain a Mini Program privacy compliance detection request, where the Mini Program privacy compliance detection request includes a privacy compliance detection requirement; Determine privacy compliance testing items according to the privacy compliance testing requirements; Determine a privacy compliance detection method for the privacy compliance detection item according to the page touch path characteristics of the privacy compliance detection item and the source code availability of the mini program to be detected, wherein the privacy compliance detection method includes a privacy compliance detection method that performs dynamic simulation according to a specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touch; and Use the determined privacy compliance detection method to perform a privacy compliance detection on the mini-program to be detected for the privacy compliance detection item.

2. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: Determining the privacy compliance detection method for the privacy compliance detection item according to the page touch path characteristics of the privacy compliance detection item and the availability of the source code of the mini program to be detected includes: In response to the page touch path characteristic indicating a deterministic page touch path, determining the privacy compliance detection mode as a privacy compliance detection mode that performs dynamic simulation according to the specified page touch path, In response to the page touch path characteristic indicating a non-deterministic page touch path and the applet to be detected having source code availability, determining the privacy compliance detection method as a privacy compliance detection method based on a combination of static scanning and dynamic simulation, In response to the page touch path characteristic indicating a non-deterministic page touch path and the applet to be detected not having source code accessibility, the privacy compliance detection method is determined to be a privacy compliance detection method that performs dynamic simulation according to page traversal clicks.

3. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: The privacy compliance detection method is a privacy compliance detection method that performs dynamic simulation according to the specified page access path. Using the determined privacy compliance detection method to perform privacy compliance detection on the mini program to be detected includes: Performing dynamic simulation touch on the mini program to be detected according to the designated page touch path; and A privacy compliance check is performed during the dynamic simulation to obtain a privacy compliance check result.

4. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: The privacy compliance detection method is a privacy compliance detection method based on the combination of static scanning and dynamic simulation. Using the determined privacy compliance detection method to perform privacy compliance detection on the mini program to be detected includes: Performing static code scanning on the source code of the mini program to obtain page attributes of all pages of the mini program, wherein the page attributes include URL addresses and JsAPI call permission types; Filtering and clustering the pages of the mini program based on the JsAPI call permission type; and For each page cluster, a page is selected for dynamic simulation detection to obtain the privacy compliance detection results.

5. The mini program privacy compliance detection method according to claim 1, wherein: The privacy compliance detection method is a privacy compliance detection method that performs dynamic simulation according to page traversal touches. Using the determined privacy compliance detection method to perform privacy compliance detection on the mini program to be detected includes: Performing a page-wide traversal starting from the homepage of the mini program; and Dynamic simulation detection is performed on the traversed pages to obtain privacy compliance detection results.

6. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: The privacy compliance detection items include at least two privacy compliance detection items, and the mini program privacy compliance detection method also includes: According to the page touch path of the page where the privacy compliance detection item is located in the mini program, a combination of privacy compliance detection items that can be combined for detection in a single dynamic detection process is determined from the privacy compliance detection items. Using the determined privacy compliance detection method to perform a privacy compliance detection on the mini program to be detected for the privacy compliance detection item includes: For each privacy compliance detection item combination, a single dynamic detection process is performed on the mini program to be detected to perform privacy compliance detection on the privacy compliance detection items in the privacy compliance detection item combination using corresponding privacy compliance detection methods. For non-combinable privacy compliance detection items, privacy compliance detection is performed using the corresponding privacy compliance detection method by performing a single dynamic detection process on the mini-program to be detected.

7. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: Obtaining a Mini Program privacy compliance test request includes: Obtain the Mini Program privacy compliance detection request through the page-level interface or system-level interface.

8. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: The mini program to be detected is obtained in one of the following ways: How to obtain a mini program based on the mini program application ID; How to obtain the Mini Program based on the Mini Program application name; Mini Program acquisition method based on the Mini Program specified page URL; and How to obtain the Mini Program based on the Mini Program QR code.

9. The mini program privacy compliance detection method according to claim 1, further comprising: Generate a privacy compliance testing report based on the privacy compliance testing results.

10. The method for detecting the privacy compliance of a mini program according to claim 1, wherein: The mini-program privacy compliance detection method is implemented via a mini-program privacy compliance detection model, which includes a detection initiation interface layer, a compliance detection item configuration layer, a compliance detection capability support layer, and a compliance detection execution layer.

11. A mini program privacy compliance detection device, comprising: A compliance detection request acquisition unit, which acquires a mini-program privacy compliance detection request, wherein the mini-program privacy compliance detection request includes a privacy compliance detection requirement; A compliance detection item determination unit, which determines the privacy compliance detection item according to the privacy compliance detection requirement; a compliance detection method determination unit, which determines a privacy compliance detection method for the privacy compliance detection item according to the page touch path characteristics of the privacy compliance detection item and the source code availability of the mini program to be detected, wherein the privacy compliance detection method includes a privacy compliance detection method that performs dynamic simulation according to a specified page touch path, a privacy compliance detection method based on a combination of static scanning and dynamic simulation, or a privacy compliance detection method that performs dynamic simulation according to page traversal touch; and The compliance detection unit uses the determined privacy compliance detection method to perform a privacy compliance detection on the mini-program to be detected for the privacy compliance detection item.

12. A mini program privacy compliance detection device, comprising: at least one processor; a memory coupled to the at least one processor; as well as A computer program stored in the memory, and the at least one processor executes the computer program to implement the mini-program privacy compliance detection method as described in any one of claims 1 to 10.

13. A computer-readable storage medium storing executable instructions, which, when executed, cause a processor to execute a mini-program privacy compliance detection method as described in any one of claims 1 to 10.

14. A computer program product, comprising a computer program, wherein the computer program is executed by a processor to implement the mini-program privacy compliance detection method as described in any one of claims 1 to 10.

Citation Information

Cited By

  • Mini-program privacy compliance testing

    WO2026040910A1