Method and apparatus for managing codes
The code management method and apparatus address data security challenges in globalized applications by securing development code through intermediate analysis, ensuring compliance with regional data sovereignty regulations and preventing unauthorized data transmission.
Patent Information
- Application Number
- JP2024525255
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-27
- Filing Date
- 2022-10-08
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2042-10-08
AI Technical Summary
Globalized applications face challenges in managing data security due to varying data sovereignty protection requirements across different regions, making it difficult to ensure compliance and safety of user data.
A code management method and apparatus that includes a retrieval module, compilation module, and generation module to secure development code, ensuring compliance and safety through intermediate code analysis and generation of executable files.
Ensures data security and compliance by managing code safety throughout the application lifecycle, preventing unauthorized data transmission and ensuring adherence to regional data sovereignty regulations.
Smart Images

Figure 2024541026000001_ABST
Abstract
Description
[Technical field]
[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on October 27, 2021, bearing application number 202111258200.3 and entitled "Method and Apparatus for Code Management," the entire contents of which are incorporated herein by reference.
[0002] [Technical field] TECHNICAL FIELD Embodiments of the present disclosure relate to the computer field, and more particularly, to a code management method, apparatus, electronic device, and computer storage medium. [Background technology]
[0003] With the development of Internet technology, various Internet applications have become an important part of people's lives. Such applications generate a large amount of data every day, which raises data security issues in various aspects, such as data sovereignty protection. For example, some countries may prohibit certain types of user data from being sent to overseas servers.
[0004] This challenge is more prominent for some globalized applications, which may need to provide services to users in multiple different regions based on the same technical architecture. However, these regions may have very different data security constraints, such as specific data sovereignty protection requirements, which makes data security protection more difficult. Summary of the Invention
[0005] A first aspect of the present disclosure provides a code management method, the method including, in response to a request to build an executable file, obtaining corresponding development code from a code base, compiling the development code into intermediate code and determining safety of the intermediate code, and, in response to the intermediate code being determined to be safe, generating the executable file based on the intermediate code.
[0006] A second aspect of the present disclosure provides a proxy management apparatus, the apparatus including: an acquisition module configured to, in response to a request to build an executable file, acquire corresponding development code from a code base, a compilation module configured to compile the development code into intermediate code and determine safety of the intermediate code, and a generation module configured to, in response to the intermediate code being determined to be safe, generate an executable file based on the intermediate code.
[0007] A third aspect of the present disclosure provides an electronic device comprising a memory and a processor, the memory adapted to store one or more computer instructions, wherein the one or more computer instructions are executable by the processor to implement a method according to the first aspect of the present disclosure.
[0008] A fourth aspect of the present disclosure provides a computer-readable storage medium having stored thereon one or more computer instructions, the one or more computer instructions being executable by a processor to implement a method according to the first aspect of the present disclosure.
[0009] A fifth aspect of the present disclosure provides a computer program product comprising one or more computer instructions, the one or more computer instructions being operable, when executed by a processor, to implement a method according to the first aspect of the present disclosure. [Brief description of the drawings]
[0010] These and other features, advantages, and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the drawings, in which like or similar drawing legends represent like or similar elements. [Figure 1] FIG. 1 shows a schematic block diagram of a data security protection system according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 illustrates a schematic block diagram of a computing security subsystem according to some embodiments of the present disclosure. [Figure 3A] 1 illustrates an example deployment environment into which a data exchange subsystem may be deployed according to some embodiments of the present disclosure. [Figure 3B] 1 illustrates an implementation of DES in an internal data center (IDC) at the TTP side and an internal data center overseas (RoW IDC) where non-TTPs are located, according to some embodiments of the present disclosure. [Figure 3C] 1 illustrates a block diagram of an example architecture of a DE according to some embodiments of the present disclosure. [Figure 3D] 1 illustrates a flowchart of a data exchange process according to some embodiments of the present disclosure. [Figure 3E] 4 shows an example data stream flow chart of various data processing implemented in a DES according to some embodiments of the present disclosure. [Figure 3F] FIG. 2 illustrates a schematic block diagram of a data exchange architecture for an MQ channel according to some embodiments of the present disclosure. [Figure 3G] FIG. 2 illustrates a schematic block diagram of a data exchange architecture for an HDFS channel according to some embodiments of the present disclosure. [Figure 3H] 1 illustrates a schematic diagram of a target object store (TOS) channel for copying data from a TTP IDC to an overseas IDC according to some embodiments of the present disclosure. [Figure 3I] 1 illustrates a schematic diagram of a TOS channel for copying data from an overseas IDC to a TTP IDC according to some embodiments of the present disclosure. [Figure 3J]1 illustrates a message sequence diagram for a TOS channel according to some embodiments of the present disclosure. [Figure 3K] FIG. 2 illustrates a schematic block diagram of a data exchange architecture for a service invocation channel according to some embodiments of the present disclosure. [Figure 3L] 4 illustrates an example of a non-TTP to TTP data exchange in a service invocation channel according to some embodiments of the present disclosure. [Figure 3M] 4 illustrates an example of a TTP to non-TTP data exchange in a service invocation channel according to some embodiments of the present disclosure. [Figure 4A] 1 illustrates a flowchart of a method for managing network traffic of a mobile end application according to some embodiments of the present disclosure. [Figure 4B] 1 illustrates a schematic diagram of an analysis and restriction process for native-type network traffic according to some embodiments of the present disclosure. [Figure 4C] 1 illustrates a schematic diagram of an analysis and restriction process for web page view type network traffic according to some embodiments of the present disclosure. [Figure 4D] 1 illustrates a schematic diagram of an analysis and restriction process for third-party SDK-type network traffic according to some embodiments of the present disclosure. [Figure 4E] FIG. 2 illustrates a module diagram of a security sandbox subsystem according to some embodiments of the present disclosure. [Diagram 5] 1 illustrates a flowchart of an example process for managing recommendation policies according to some embodiments of the present disclosure. [Figure 6] 1 illustrates a flowchart of an example process for code management according to some embodiments of the present disclosure. [Figure 7] FIG. 1 illustrates an example block diagram of an apparatus for code management according to some embodiments of the present disclosure. [Figure 8] FIG. 1 shows a block diagram of an example device that can be used to implement embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] The following describes the embodiments of the present disclosure in more detail with reference to the drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be realized in various forms and should not be construed as being limited to the embodiments described herein, but rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are used for illustrative purposes only and are not used to limit the scope of protection of the present disclosure.
[0012] In describing embodiments of the present disclosure, the term "comprises" and similar terms should be understood as open inclusion, i.e., "including, but not limited to." The term "based on" should be understood as "based at least in part on." The term "in one embodiment" or "in this embodiment" should be understood as "at least one embodiment." The terms "first," "second," etc. may refer to different or the same object. The following may include other explicit and implicit definitions.
[0013] In the following, the basic principles and some exemplary implementations of the present disclosure will be described with reference to the drawings.
[0014] Overall architecture of data security protection system According to an embodiment of the present disclosure, a data security protection system is provided. Figure 1 shows a schematic block diagram of a data security protection system 1000 according to an embodiment of the present disclosure. As shown in Figure 1, the data security protection system 1000 includes multiple subsystems for protecting the security of related data generated in the process of a user using a target application from different dimensions.
[0015] Generally, to support the running of the target application, on the one hand, a user needs to be able to run the target application 1080, for example, via a suitable electronic device, and on the other hand, it is also necessary to deploy the target application platform 1030 in a suitable computing environment (e.g., a cloud computing environment), for example, to run various types of services to support the normal running of the target application 1080.
[0016] In some embodiments, the data security protection system 1000 can ensure the security of data generated during the operation of the target application 1090 from the perspective of the safety of running the code. As shown in FIG 1, the data security protection system 1000 may include a security computing subsystem 1060. The security computing subsystem 1060 can be used to ensure the safety of code corresponding to the target application 1080 and also to ensure the safety of code corresponding to the target application platform 1030.
[0017] The service operation file obtained by compiling by the computing subsystem 1060 may be deployed to the target application platform 1030, for example. The installation file (e.g., apk file) of the target application obtained by compiling by the computing subsystem 1060 may be released to the application mall 1120, for example. A specific implementation of the security computing subsystem 1060 will be discussed in detail below in conjunction with FIG. 2.
[0018] 1, the security computing subsystem 1060 may be based on a cloud infrastructure 1070. In some embodiments, the cloud infrastructure 1070 may be provided by, for example, a trusted partner. In this disclosure, a "trusted partner" may be referred to as a Trusted Technology Partner (TTP). A TTP may include, for example, any individual, company, or organization that is trusted with technology within a particular domain (e.g., a particular country or jurisdiction).
[0019] In some embodiments, as shown in Fig. 1, a data security protection system 1000 may include a trusted security environment 1010 provided by a TTP. Different from traditional application platform deployment, a target application platform 1030 may be deployed in the trusted security environment 1010 to improve the safety of data generated by the target application platform 1030 and the transparency and reliability of its operation mechanism.
[0020] In some embodiments, the target application 1080 can provide a content recommendation service to the user through a recommendation algorithm. Such content recommendations may include, but are not limited to, for example, multimedia content recommendations, user recommendations, product recommendations, etc. Considering that currently, more and more recommendation systems utilize machine learning to realize recommendation functions, managing the recommendation mechanism only from the code level may be difficult to ensure the fairness of recommendations.
[0021] 1, the data security protection system 1000 may further include a recommendation management subsystem 1050. The recommendation management subsystem 1050 can ensure the fairness of the recommendation mechanism in the target application 1080, for example, by testing the recommendation algorithm run by the target application platform 1030. A specific implementation of the recommendation management subsystem 1050 will be described in detail below.
[0022] In some embodiments, when the target application platform 1030 is considering running services to support the normal operation of the target application 1080, the target application platform 1030 may potentially interact with applications or data centers (also referred to as overseas applications or overseas data centers) outside the target region (e.g., a particular country or jurisdiction) in which it is currently deployed.
[0023] Typically, the target region typically has laws or regulations restricting data originating within the region from being communicated abroad. Certain types of data originating within the target region may be prohibited from being distributed abroad. To ensure compliance during communication between the target application platform 1030 and abroad, the data security protection subsystem may include a data exchange subsystem 1040. Similarly, the data exchange subsystem 1040 may be deployed in the trusted security environment 1010 to ensure the transparency and reliability of its operation.
[0024] 1, the data exchange subsystem 1040 may include multiple data channels for different types of data transmission. For example, multimedia data originating in the target application platform 1030 may be communicated to an overseas application 1140 and / or an overseas data center 1150 via, for example, a content delivery network 1130 provided by a third party via a corresponding data channel in the data exchange subsystem 1040.
[0025] As another example, certain internal data generated in some target application platforms 1030 can be communicated with overseas data centers 1150 and overseas development departments 1160 via corresponding data channels and / or, for example, directly connected optical cables. A specific implementation of the data exchange subsystem 1040 will be described in detail below in conjunction with Figures 3A to 3M.
[0026] Further, to ensure security of egress and ingress communications of the target application platform 1030, in some embodiments, the data security subsystem 1000 may further include an application firewall subsystem 1020. The application firewall subsystem 1020 may be deployed, for example, in a trusted security environment 1010. The trusted security environment 1010 may be used to monitor, for example, data communications from the target application 1080 to the target application platform 1030, data communications from the target application platform 1030 to the target application 1080, and / or data communications from the target application platform 1030 to the third party application 110, etc.
[0027] In this manner, the data security protection platform 1000 can not only ensure the safety and compliance of data communications between the target application platform 1030 and overseas via the data exchange subsystem 1040, but also ensure the safety and compliance of communications between the target application platform 1030 and each object within the country (e.g., the target application 1080 or the third-party application 1110) via the application firewall subsystem 1020.
[0028] In some embodiments, for the target application 1080, in order to ensure the compliance and reliability of its operation, the data security protection system 1000 may further include a security sandbox subsystem 1090, for example managed by a TTP. By the security sandbox subsystem 1090, different types of network communications involving the application service logic 1100 of the target application 1080 can be protected by the security sandbox subsystem 1090. In this manner, the data security protection system 1000 can prevent the target application 1080 from initiating unauthorized data communications, for example, in the manner of a backdoor program. A detailed implementation of the security sandbox subsystem 1090 will be described in detail below in conjunction with Figures 4A to 4E.
[0029] As a result, according to the data security protection system 1000 disclosed herein, the TTP can manage and monitor various aspects such as code security and data security throughout the entire life cycle of the target application from development to operation, thereby ensuring the security of data related to the target application and ensuring compliance of its operation.
[0030] Security Computing Subsystem In the following, the Security Computing Subsystem 1060 will be described in detail with reference to Figure 2. Figure 2 shows a schematic block diagram of the Security Computing Subsystem 1060 according to an embodiment of the present disclosure.
[0031] 2, the security computing subsystem 1060 may include, for example, a security code environment 2010. The security code environment 2010 may be provided, for example, by the TTP. The following describes the operation process of the security computing subsystem 1060 in conjunction with the submission of new development code 2140.
[0032] 2, when a developer has new developed code 2140 that needs to be deployed, the developer may submit the developed code 2140 to the security code environment 2010 via a synchronization gateway 2150 provided, for example, by a TTP. In response, the developed code 2140 is synchronized to a code base 2160 in the security code environment 2010.
[0033] In some embodiments, when a developer needs to compile using new development code 2140, the developer may send a build request to product build system 2080, for example, via synchronization gateway 2150.
[0034] Alternatively, when the code base 2160 receives new development code 2140, the code base 2160 may automatically send a code integration event to the product building system 2080 to trigger the product building system 2080 to initiate the building process of the product (artifact, e.g., executable code).
[0035] After the build process is initiated, a code pull module 2090 can obtain (pull) the code files for the build from the code base 2160. In some embodiments, the code files for the build may be specified by a developer, for example, or automatically determined by the product build system 2080.
[0036] Additionally, the compilation module 2100 may compile code pulled from the code base 2160 by the code pull module 2090, for example, into intermediate code.
[0037] Considering that some third-party code is often introduced and used during code compilation, some embodiments of the present invention require the security computing subsystem 1060 to ensure the security of the introduced third-party code.
[0038] 2, the Security Computing Subsystem 1060 may include a Third Party Independent Gateway 2030 for inspecting and verifying the safety of third party libraries 2020 that need to be installed. It should be understood that such third party libraries may be, for example, compiled link libraries or the source code itself.
[0039] Third party libraries 2020 that pass the safety test may be added to the product library 2040. As shown in FIG 2, during the construction of a product, the compilation module 2100 may obtain from the product library 2040 other products on which the compilation of the current product depends, such as products that have already been compiled and generated in the past, or products generated based on the third party libraries 2020.
[0040] Further, the compilation module 2100 can compile, for example, code pulled from the code base 2160 and dependent products obtained from the product library 2040 to generate intermediate code and perform code security detection via the security code scanning module 2110.
[0041] It should be appreciated that the security code scanning module 2110 managed by the TTP can perform any suitable code scanning process to perform security checks, and such scanning rules may be unknown to the developer, thereby ensuring the security of the code for compilation into the final product.
[0042] In some embodiments, the upload module 2120 may perform the appropriate upload based on the results of the security code scanning module 2110. If the security code scanning module 2110 determines that the compiled intermediate code is safe, the upload module 2120 may further upload the compiled executable file to the product library 2040.
[0043] Furthermore, if the security code scanning module 2110 determines that the compiled intermediate code is safe, the upload module 2120 may upload the signature information of the executable file to the product signature management module 2060.
[0044] Conversely, if the security code scanning module 2110 determines that the current intermediate code poses a risk, the upload module 2120 may upload the associated risk to the issue tracking system 2070, for example to form a risk analysis report, and in response, the compiled executable file is prohibited from being uploaded to the product library 2040.
[0045] In some embodiments, the development code 2140 in the code base 2160 may be provided in a trusted environment, e.g., for artificial testing. If it is determined that a risk exists in the development code 2140, this result may also be reported to the issue tracking system 2070.
[0046] In some embodiments, if the security code scanning module 2110 determines that the current intermediate code poses a risk, the upload module 2120 may notify the callback module 2130 to mark the corresponding code as a risk code in the code base 2160.
[0047] In some embodiments, the issue tracking system 2070 maintained by the TTP may, for example, send the received risk report information to a developer or maintainer of the development code 2140 to alert them that the current development code 2140 cannot be deployed because it cannot pass security testing.
[0048] In some embodiments, if the development code 2140 passes safety testing, it may be compiled as an executable file and further added to the product library 2040 and deployed, for example, via a deployment gateway 2050.
[0049] In some embodiments, before deploying a product (i.e., an executable file) obtained from the product library 2040, the deployment gateway 2050 may verify whether the signature of the product is valid via the product signature management system 2060. After the validity of the signature of the product is confirmed, the deployment gateway 2050 may deploy the product generated based on the development code 2140 to the network.
[0050] In some embodiments, the product may be, for example, an application program executed on a client device. The deployment gateway 2050 may, for example, release the generated installation file (e.g., an apk file) to a corresponding application store for download by a user. Thereby, embodiments of the present disclosure may ensure that the installation file that a user can download and install is always released via the deployment gateway 2050 by the security code environment 2010.
[0051] In some embodiments, the product may be, for example, a service program for deployment to the target application platform 1030. Specifically, a maintainer of the target application may initiate a request to the deployment platform to deploy a specific product to the target application platform 1030. In response, after the request passes screening, the target application platform 1030 may obtain the specific product to be deployed from the product library 2040 and authenticate the signature of the specific product. After the signature of the product passes authentication, the product may be deployed to the target application platform 1030, for example, in the manner of a virtual machine or a container.
[0052] Thereby, based on the considered security computing subsystem, the embodiment of the present disclosure can effectively monitor the process of converting code into an application program or service program that is actually deployed and used, from each stage of code upload, code creation, code compilation, third-party library invocation, etc. Based on such a method, the embodiment of the present disclosure can effectively avoid various security vulnerabilities or compliance risks introduced in source code.
[0053] Data Exchange Subsystem The operation of an application involves data exchange between application platforms under the jurisdiction of different countries and regions. For example, in the example shown in FIG. 1, it is expected that data exchange will be performed between the target application platform 1030 and a target application platform where the same application is operated overseas to provide global data exchange of the application. As described above, the data exchange subsystem (DES) 1040 can support synchronization of common data of the target application and other data that meets the rules between different platforms, and ensure the safety and compliance of the exchanged data. In general, the DES 1040 is configured to detect whether data between different platforms meets data exchange constraints. The data exchange constraints may include constraints set to meet the laws and regulations of a country or region, necessary constraints set for other requirements of enterprises, organizations and / or user protection, etc.
[0054] For example, in a country or region with a specific data sovereignty protection requirement, the TTP may conduct an inspection regarding data sovereignty protection. Therefore, in many cases regarding data exchange between platforms, it is necessary to protect the security and compliance of the data exchange. In particular, after the installation of the TTP machine room, the exchange of data between the outside and the TTP machine room is restricted, and data that is desired to be exchanged with the TTP side is subject to data sovereignty protection inspection. In such an example, the data exchange restriction may include rules related to the data sovereignty protection requirement of the specific country or region.
[0055] Such exchange data may be divided into two aspects. One aspect includes intercommunication data between platforms, and the other aspect includes maintenance data such as platform access or operation by platform maintenance personnel. The intercommunication data is mainly used to synchronize between two platforms and ensure the functional integrity of applications. Such data needs to be inspected for safety and compliance by the DES system. The intercommunication data includes, for example, online traffic data, offline data, etc. The inspection of the maintenance data is to ensure that the operations of maintenance personnel on the maintenance control plane are also compliant.
[0056] FIG. 3A illustrates an example deployment environment 3001 in which the DES 1040 is deployed according to some embodiments of the present disclosure.
[0057] In Fig. 3A, the TTP side 3027 is an environment that needs to be subject to TTP supervision and constraints in a specific country or region. The TTP side 3027 may involve various components for operating, managing, and maintaining the target application. These components include, for example, a business system 3028, an operating platform 3029, an online store 3030, an offline store 3031, etc. The TTP side 3027 further includes a maintenance platform 3032. Maintenance personnel need to access the maintenance platform 3032 to realize access, management, or maintenance of the target application.
[0058] Similarly, the non-TTP side 3020 is an environment belonging to one or more countries or regions other than a specific country or region, and is not subject to the data exchange restrictions of the country or region where the TTP side 3027 is located. The non-TTP side 3020 may involve various components for operating, managing, and maintaining the target application. These components include, for example, a business system 3020, an operating platform 3021, an online store 3022, an offline store 3023, and the like. The non-TTP side 3020 further includes a maintenance platform 3024. Maintenance personnel need to access the maintenance platform 3024 to realize access, management, or maintenance of a local application or application platform.
[0059] Domestic user traffic passes through some components of the TTP side 3027. International user traffic passes through some components of the non-TTP side 3020. In this specification, "domestic user traffic" refers to user traffic generated on an application platform under the jurisdiction of this specific country or region. "International user traffic" refers to user traffic generated on an application platform under the jurisdiction of one or more countries or regions other than this specific country or region.
[0060] In the environment of Fig. 3A, the intercommunication data includes domestic user traffic and international user traffic exchanged between the TTP side and the non-TTP side. The intercommunication data passes through the DES 1040 to facilitate inspection of data security, compliance, etc. In addition, an operation gateway 3026 may be installed to inspect the maintenance data for data security, compliance, etc.
[0061] As will be discussed in detail below, different data channels may be set in the DES 1040 based on the type of data, and inspection of the data to be exchanged in the corresponding channel may be performed. Figure 3A illustrates several channels, including a target object store (TOS) channel, a message queue (MQ) channel, an offline aggregate data channel, a log (LOG) channel, a service invocation channel, etc.
[0062] Both sides of a data exchange may have respective DES to provide data protection, for example protection of incoming and / or outgoing data.
[0063] FIG. 3B further illustrates the implementation of DES 1040 in an internal data center (IDC) at the TTP and an overseas internal data center (RoW IDC) where non-TTPs are located.
[0064] In Fig. 3B, TTP IDC 3056 is an IDC of a target application that operates in a specific country or region and is subject to the data protection detection of the TTP, and overseas IDC 3059 is an IDC of a target application that operates in one or more countries or regions other than the specific country or region and may be subject to the data protection restrictions of the other countries or regions.
[0065] 3B, the DES 1040A is implemented in the TTP IDC 3056 to detect externally incoming data and / or internally outgoing data. The DES 1040B is implemented in the overseas IDC 3059 to detect externally incoming data and / or internally outgoing data. The DES 1040A and the DES 1040B may be considered as specific deployment examples of the DES 1040.
[0066] From the perspective of TTP IDC 3056, the externally inflowing or internally outflowing data may include various types of data, the following of which are described by way of examples.
[0067] As shown in FIG. 3B, for TTP IDC 3056, the incoming data may include user requests, such as spontaneous requests initiated by domestic users in a particular country or region via target applications 3058 running domestically. As described elsewhere herein, in some embodiments, the user requests may be secured via a mobile sandbox and / or a firewall gateway 3057 at TTP IDC 3056, etc. The user requests arrive at a domestic application platform 3041 at TTP IDC 3056 for further processing. In some examples, the domestic application platform 3041 may include various services, vendor gateways, storage, etc. components. Note that if the user request is to be delivered to a data center other than TTP IDC 3056, the user request is passed to DES 1040A for data protection.
[0068] In some embodiments, for the TTP IDC 3056, the externally inflowing data may further include vendor requests initiated by the vendor 3055, such as those requesting a particular service of the domestic application platform. For example, a third-party vendor may call an application programming interface (API), such as OpenAPI, of the domestic application platform. Since it is not possible to verify whether a third-party vendor belongs to a domestic user, the vendor request is sent via a third-party gateway 3040 in the TTP IDC 3056 to a vendor gateway in the domestic application platform 3041 for inspection to determine whether it is a domestic user. If the vendor initiating the request is a domestic user, the vendor request can be responded to normally. If the vendor initiating the request is an international user, the vendor request is delivered via the DES 1040A.
[0069] In some embodiments, for the TTP IDC 3056, the incoming data may further include data synchronized from an overseas IDC 3059 to the TTP IDC 3056. For example, if the incoming data from overseas needs to undergo data security screening, the incoming data from overseas is also processed by the DES 1040A.
[0070] In some embodiments, for the TTP IDC 3056, the data coming in from outside may further include maintenance operations of the TTP IDC 3056 by maintenance personnel, such as changes to the TTP IDC 3056. Such operations may include code system changes, configuration system changes, log maintenance, etc. Code system changes may include, for example, bringing new features online, releasing bin files, etc. Code system changes may be performed by domestic maintenance personnel of the application platform of the country or region. Configuration system changes may include enabling or disabling some settings of the target application, scheduled traffic configuration, etc. In some cases, configuration system changes may be performed by overseas platform maintenance personnel for application platforms that operate across borders. Of course, this only depends on the management requirements of different applications. Log maintenance is to maintain the logs 3044 in the TTP IDC 3056.
[0071] In some embodiments, a domestic maintenance staff or an overseas maintenance staff may perform a maintenance operation on the TTP IDC 3056 under the condition of network isolation to further ensure data sovereignty protection. As shown in FIG. 3B , a domestic maintenance staff initiates a maintenance operation in the case of network isolation, and the maintenance operation is allocated via a load balancer 3045 and distributed to a code 3042, a maintenance platform 3043 or a log 3044 in the TTP IDC 3056. In addition to network isolation, the maintenance operation of the overseas maintenance staff is further security-checked via an operation gateway 3046 and distributed to a code 3042, a maintenance platform 3043 or a log 3044 in the TTP IDC 3056.
[0072] In some embodiments, for the TTP IDC 3056, the data flowing from within may include a third party request to request a third party service 3054, such as a third party service in a public network, initiated from the domestic application platform 3041 during the operation of the application platform. The third party request also needs to be data protected by the DES 1040A.
[0073] In some embodiments, for the TTP IDC 3056, the data flowing from the inside may further include data synchronized from the TTP IDC 3056 to the overseas IDC 3059. For example, during the operation of the target application, user content stored in the TTP IDC 3056 may need to be synchronized to the overseas IDC 3059. According to some provisions of data sovereignty protection, such data may be important data that needs to be reviewed by DES 1040A.
[0074] In some embodiments, for the TTP IDC 3056, the data flowing from the inside may further include code synchronization data. For example, in some cases, code review of the target application or application platform may be required due to inspection requirements such as data sovereignty protection. On the premise of satisfying the data sovereignty protection requirements, the code may be synchronized to a secure isolation environment 3051 for review so as not to be leaked. The secure isolation environment 3051 may be, for example, a physical environment such as a machine room not connected to a network, a monitored machine room, or a virtual computing environment with security protection.
[0075] From the viewpoint of the overseas IDC 3059, the DES 1040B deployed therein also performs similar security protection for data flowing in from the outside and data flowing out from the inside. For example, a user request generated through a target application 3058 operated by a user overseas may be protected by the DES 1040B after arriving at the overseas application platform 3048 (which may include various services and storage) via the load balancer 3047. In terms of maintenance, an overseas maintenance staff may also perform maintenance operations on the overseas application platform 3048 via a crystal gateway 3049 in the case of network isolation. For such maintenance operations, data protection may be performed via the DES 1040B.
[0076] For the data protected in DES 1040A or 1040B, according to different types, the schemes for implementing data sovereignty protection and the processes that need to be implemented to realize data sovereignty protection may also be different.
[0077] In the embodiment of the present disclosure, the DES 1040 (e.g., DES 1040A or 1040B) can pre-process data according to the data type so as to uniformly format the data, thereby simplifying and facilitating the subsequent inspection of data sovereignty protection and accelerating the data exchange process.
[0078] Thus, the data may be divided into different processing parts in the DES 1040 according to the data type. For example, according to the data source, the DES 1040A may include a domestic user data channel for processing data related to domestic users in a specific country or region, an overseas user data channel for processing data related to overseas users, and an engineering technology data channel for processing engineering and maintenance data, such as various research and development data such as codes, parameters, maintenance data, etc. Furthermore, according to the processing technology such as data generation, transmission, reception, and storage, the data in each channel may be further divided. As described below, according to the technology, the data in different channels may be divided into one or more of message queue (MQ) data, offline aggregation data, target object store (TOS) data, service invocation data, or other types of data.
[0079] For data that has passed the data sovereignty protection review, the unified formatted data can be converted to the original format data and the corresponding destination can be provided. According to the solution disclosed in the present disclosure, since different data sources and different types of data are different in terms of data format, processing technology, etc., the complexity of the subsequent data sovereignty protection review stage can be reduced by unified format pre-processing and post-processing. In addition, with the update of data sources and the expansion / change of technology, etc., only the pre-processing and post-processing of data can be changed without making complex changes to the processing of the data exchange constraint determination stage. Thus, the data exchange architecture has great flexibility and scalability.
[0080] In the following, several specific embodiments will be described in detail with reference to the drawings.
[0081] Overall DES architecture and data stream 3C illustrates a block diagram of an example architecture of the DES 1040 according to some embodiments of the present disclosure. In the example of FIG. 3C, the DES 1040 is shown to synchronize data between a domestic application platform 3041 and an external application platform (collectively referred to as an overseas application platform 3048) for a target application and to enforce data exchange constraint determinations.
[0082] As shown in Fig. 3C, the DES 1040 may include a DES adapter 3061, a DES center, and a DES adapter 3070. The DES center may include DES centers for different types of data channels, such as a DES center 3065A for domestic user data, a DES center 3065B for overseas user data, and a DES center 3065C for engineering technology data. The DES centers 3065A, 3065B, and 3065C have different synchronization capabilities. In the following, for ease of description, the DES centers 3065A, 3065B, and 3065C may be collectively referred to as the DES center 3065.
[0083] The DES adapter 3061 is connected to the domestic application platform 3041, and is used to receive data synchronized from the domestic application platform 3041 and to be detected by the DES 1040, and to transmit data received from the overseas application platform 3048 and to be detected by the DES 1040 to the domestic application platform 3041. The DES adapter 3070 is connected to the overseas application platform 3048, and is used to transmit data received by the domestic application platform 3041 and to be detected by the DES 1040 to the overseas application platform 3048, and to receive data synchronized from the overseas application platform 3048 and to be detected by the DES 1040. The DES adapter 3061 and the DES adapter 3070 are both connected to the DES center 3065 to deliver data to the DES center 3065.
[0084] Each DES center 3065 is configured to use data exchange constraints to detect data and ensure the safety and compliance of data exchanged between two application platforms. In general, data that meets the data exchange constraints is passed to the appropriate destination via the DES 1040, while data that does not meet the data exchange constraints may be rejected by the DES 1040.
[0085] The DES adapters 3061 and 3070 may be configured to perform pre-processing and post-processing on data to be input to the DES center 3065 so that the DES center 3065 determines whether data exchange constraints are met based on uniform format data corresponding to each data type.
[0086] In some embodiments, the DES adapter 3061 and the DES center 3065 in the DES 1040 may be implemented in the TTP IDC 3056 along with the home application platform 3041. The DES adapter 3070 may be implemented in the overseas IDC 3059 along with the overseas application platform 3048.
[0087] In some embodiments, different components in the DES 1040 may be further isolated to ensure more effective data isolation. Such data isolation may be achieved by deploying different components in different data centers. In some embodiments, data isolation may be achieved by applying Virtual Private Data Center (VPC) technology. For example, as shown in FIG. 3C, the DES adapter 3061 may be implemented in VPC1. Each DES center may be implemented in VPC2. The DES adapter 3070 may be implemented in VPC3. The data safety and compliance decision in the DES center 3065 may be performed by the TTP. In the case of data isolation, VPC1 and VPC3 do not have a direct communication connection, but VPC1 and VPC3 have a direct communication connection with VPC2, respectively, and can communicate data / information with each other. With data isolation by VPC technology, the DES center 3065 deployed in VPC2 may be an area trusted by the TTP (referred to as a TTP trusted area).
[0088] In some embodiments, the DES adapter 3061 may include a DES inlet 3062. The DES inlet 3062 may realize control plane processing, such as application for establishing and managing data channels by maintenance personnel, registration rules, etc., and allow the TTP to view data in the channel. The DES adapter 3061 may further include a DES proxy 3063. The DES proxy 3063 may realize data plane processing, such as data validation, data filtering, data conversion, data sampling, log detection, etc. Similarly, in some embodiments, the DES adapter 3070 may realize a DES inlet 3072 of the control plane and a DES proxy 3073 of the data plane.
[0089] In some embodiments, for domestic user data channels, the DES center 3065A may include a DES registration center for registering data exchange constraints, configuration data, etc. The DES center 3065A may further include further subdivided channels, including a service invocation channel for service invocation data, an MQ channel for MQ data, an HDFS channel for offline aggregated data (wherein HDFS is referred to as Hadoop Distributed File System), and a TOS channel for TOS data. The offline aggregated data includes, for example, highly parallel integrated virtual environment (HIVE) type data.
[0090] Service invocation data may include, for example, data making remote service invocations using various network or invocation protocols, such as the HTTP protocol or the RPC protocol. MQ data may include data supporting the MQ protocol and similar protocols, including, for example, data stored in various databases (e.g., MySQL, Redis databases). Offline aggregate data may include data in file systems based on HDFS technology, as well as data in file systems based on other technologies. TOS data includes object files, such as video, audio, images, documents, and other media files.
[0091] In some embodiments, not shown in FIG. 3C, DES center 3065B for overseas user data channels and DES center 3065C for engineering technical data channels may include components similar to DES center 3065A.
[0092] 3D illustrates a flow chart of a data exchange process 300 according to some embodiments of the present disclosure. The process 3004 may be implemented in the DES 1040.
[0093] 3D, in box 3301, DES 1040 obtains raw data that a target application exchanges between a first platform (e.g., domestic application platform 3041) and a second platform (e.g., international application platform 3048). Depending on the direction of the exchange, the raw data may originate from the first platform and be received by DES adapter 3061 in DES 1040. Or, the raw data may originate from the second platform and be received by DES adapter 3070 in DES 1040.
[0094] In box 3302, the DES 1040 processes the raw data based on the type of the raw data to obtain the corresponding unified format data. The processing of the raw data (the processing here may be referred to as pre-processing) may be determined based on the type of the raw data. The type of the raw data may include, for example, MQ data, offline aggregated data, TOS data, or service call data. Furthermore, in some cases, the processing of the raw data may be determined according to the data source. For example, based on the data source, the raw data may be divided into domestic user data, overseas user data, or engineering technology data. The formats corresponding to different types of data are different, and different methods may be applied to generate the corresponding unified format data.
[0095] In some embodiments, the same type of data may be provided in different formats due to different technologies used by the data sources, which increases the demands of the technology processing. Therefore, one unified format may be specified. In the pre-processing stage, a format conversion may be performed to convert the format of the raw data into the format specified by this type to obtain the unified format data.
[0096] For example, for MQ data, parsing the MQ data in different formats may facilitate analysis of content in messages encapsulated in different formats. For offline aggregate data and TOS data, different requests to invoke such data from file systems or data systems in different formats may be converted into file invocation requests fulfilled by the unified API. For service invocation, service invocation requests generated in different protocols may be converted into service invocation requests in the unified protocol.
[0097] Specific pre-processing schemes for different types of data are described in more detail below.
[0098] In box 3303, the DES 1040 determines whether the data exchange constraints are satisfied from the uniform format data. For example, the DES center 3065 in the DES 1040, especially the DES center 3065 of the corresponding data type, can perform a check whether the data exchange constraints are satisfied. The pre-processing of the uniform format makes it easier for the DES center 3065 to perform data safety and compliance checks using rules, without having to apply various different techniques to analyze the raw data.
[0099] If in box 3304 it is determined that the unified format data satisfies the data exchange constraints, the DES 1040 converts the unified format data into raw data. If the data exchange constraints are satisfied, the data is allowed to be synchronized between the platforms. To ensure that the data is synchronized correctly, the DES 1040 further processes the intermediately generated unified format data (i.e., performs a post-processing step) to convert the unified format data into raw data having the original format.
[0100] In box 3305, the DES 1040 performs an exchange of raw data between the first platform and the second platform, thereby enabling secure and compliant data exchange.
[0101] In some embodiments, as briefly mentioned above, multiple data channels corresponding to different types of raw data between different platforms may be created, and the different types of raw data may be passed to the corresponding data channels for processing. Each data channel may include a pre-processing component suitable for processing this type of raw data, a post-processing component, and a checking component for data exchange constraints. Additionally or alternatively, each data channel may register data exchange constraints that are applicable to this particular type of raw data. In this manner, separation of different types of data in terms of pre-processing, checking data exchange constraints, and post-processing may be realized.
[0102] Data channels corresponding to different types of data can be flexibly created, updated and deleted. In this way, when the data pre-processing and post-processing manner changes, or when the data exchange constraints for a certain type of data need to be updated, this can be done in the corresponding data channel without affecting other data channels. Furthermore, when a new type of raw data needs to be exchanged between the first platform and the second platform according to business needs, and this new type of data also needs to be inspected for data sovereignty protection, a new data channel can be flexibly created between the first platform and the second platform to process the new type of raw data.
[0103] 3E illustrates an example data stream 3005 flow chart of various data processes implemented in the DES 1040 according to some embodiments of the present disclosure. The data stream 3005 relates to a control plane data stream and a data plane data stream.
[0104] In the control plane, a maintenance staff can configure channels for one or more types of data in the DES 1040, and realize updates and maintenance for the channels. As shown in FIG. 3E, a domestic maintenance staff may request the configuration of a specific data type and a channel for processing the specific data type via the DES entrance 3062, and register a data directory 3081 indicating the specific data type and a data definition 3082 similar to the specific data in the DES registration center 3066. The data definition 3082 may specify channel information for processing different types of data in the DES 1040. It may also include a pre-processing scheme, a post-processing scheme, etc. for the corresponding type of data.
[0105] Similarly, an overseas maintenance personnel may request configuration of a specific data type and a channel for processing the specific data type via DES portal 3072. The overseas maintenance personnel may register a data directory 3084 indicating the specific data type and a data definition 3085 similar to the specific data in DES registration center 3066. The data definition 3085 may specify channel information for processing different types of data in DES 1040. It may also include a pre-processing scheme, a post-processing scheme, etc. for the corresponding type of data.
[0106] In the data plane, different types of data pass through respective channels in the DES 1040. As shown in Fig. 3E, for the service call data, a service call request is exchanged between the client or server 3086 on the TTP IDC side and the client or server 3090 on the overseas IDC side. The service call request is processed in the service call channel in the DES 1040 so that the service call request meets the data sovereignty protection requirement.
[0107] In the example of Fig. 3E, the service invocation channel may include at least a pre-processing module 3087 in the DES proxy 3063, an HTTP proxy 3088 in the DES center 3065, and a routing module 3089 in the DES proxy 3073. A service invocation request from a client or server 3086 on the TTP IDC side is delivered to the pre-processing module 3087. The pre-processing module 3087 processes the service invocation request using a data pre-processing scheme defined in the data definition 3082, and sends the service invocation request after unified format to the HTTP proxy 3088.
[0108] In this example, it is assumed that the service invocation request is uniformly formatted into a request conforming to a uniform protocol, i.e., the HTTP protocol. Therefore, after the HTTP proxy 3088 determines that the uniformly formatted service invocation request satisfies the data exchange constraints, the HTTP proxy 3088 may provide the uniformly formatted service invocation request to the other side client or server 3090 via the routing module 3089. Before being provided to the client or server 3090, the uniformly formatted service invocation request is converted into a service invocation request conforming to the original protocol.
[0109] For MQ data, this type of raw data is processed in an MQ channel in the DES 1040. In the example of FIG. 3E, the MQ channel may include at least a pre-processing module 3092 in the DES proxy 3063, an MQ sender 3094 in the DES center 3065, and a routing module 3097 in the DES proxy 3073.
[0110] The raw data 3091 for the MQ type is transmitted to a pre-processing module 3092. The pre-processing module 3092 processes the raw data 3091 using a data pre-processing scheme defined from the data definition 3082 to obtain uniform format data 3093. The uniform format data 3093 is extracted by an MQ sender 3094, for example via a third-party software development kit (SDK). After checking the data exchange constraints, the SDK pushes the uniform format data 3096 that meets the rules to the overseas IDC. The uniform format data 3095 that does not meet the data exchange constraints is rejected. The routing module 3097 routes the uniform format data 3096 that meets the rules to a corresponding destination, and the uniform format data 3093 is converted to the corresponding raw data 3098 before being transmitted to the destination.
[0111] For offline aggregated data and TOS data, the raw data is processed in the HDFS channel and the TOS channel, respectively, in the DES 1040. For simplicity, FIG. 3E shows an example of one channel, but it can be understood that the HDFS channel and the TOS channel may include the components shown. In the example of FIG. 3E, the HDFS channel or the TOS channel may include at least a pre-processing module 3100 in the DES proxy 3063, a file sender 3103 in the DES center 3065, and a routing module 3105 in the DES proxy 3073.
[0112] Because data of the offline aggregated data type or TOS type is stored in a file system or other storage system, the pre-processing module 3100 may initiate a request to the file transmission manager 3102 to call a file transmission API to obtain raw data 3099 for the offline aggregated data type or TOS type and transmit it to the pre-processing module 3100. The pre-processing module 3100 may process the raw data 3099 using a data pre-processing scheme defined in the data definition 3082 to obtain unified format data 3101.
[0113] Similar to MQ-type data processing, the uniform format data 3101 is extracted by a file sender 3103, for example via an SDK. After going through data exchange constraints inspection, the SDK pushes the uniform format data 3104 that meets the rules to the overseas IDC. The uniform format data that does not meet the data exchange constraints is rejected and cannot be transmitted to the overseas IDC. A routing module 3105 routes the uniform format data 3104 that meets the rules to a corresponding destination, and the uniform format data 3094 is converted to a corresponding raw data 3106 before being transmitted to the destination.
[0114] It should be understood that Figure 3E only illustrates the processing of outgoing data from the TTP IDC to the overseas IDC in the DES 1040. The reverse data stream may be processed in a similar flow in the DES 1040, and the DES 1040 may reserve corresponding components, particularly components in the DES adapter, to support such processing.
[0115] Below, several exemplary implementations of different types of data in the DES 1040 are discussed in detail.
[0116] Example implementation of data exchange for MQ 3F illustrates a schematic block diagram of a data exchange architecture 3006 for an MQ channel according to some embodiments of the present disclosure. The data exchange architecture 3006 may be implemented with DES 1040 to perform data security protection for MQ type data. The example of FIG. 3F illustrates data exchange from a TTP IDC to an overseas IDC.
[0117] As shown in Fig. 3F, a source database 3110 in the TTP IDC generates entities of MQ data to be transmitted. The MQ data may include messages such as change data or commercially customized events, and different messages may have different formats. The MQ data generated by the source database 3110 is queued in a source message queue 3112.
[0118] In the example of Figure 3F, in addition to the DES inlet 3062, the DES adapter 3061 further includes a DES front adapter 3120. The DES front adapter 3120 may be implemented as part of the DES proxy 3063 to pre-process MQ data in the direction from the TTP IDC to the overseas IDC. The DES front adapter 3120 may be configured to process the MQ data of different formats as uniform format MQ data having a uniform format, and provide the uniform format MQ data to the MQ sender 3094 to perform a determination as to whether the data exchange constraints are satisfied.
[0119] The MQ data (or message) may include data generated by different protocols. Data in each protocol has a custom format and therefore requires different pre-processing. As shown in FIG. 3F, the DES front adapter 3120 may include a parser 3122 configured to parse different types of raw MQ data and convert the different types of raw MQ data into unified format MQ data. As shown in FIG. 3F, the DES front adapter 3120 may include a MySQL® parser for parsing data generated by the MySQL® protocol, such as change data capture (CDC) data, a Redis parser for parsing data generated by the Redis protocol, such as CDC data, a document parser for parsing data in a document database, particularly CDC data, a graph parser for parsing data in a graph database, particularly CDC data, an MQ parser for parsing different types of business event data sent by a message queue, and so on. As can be understood, the parser 3122 is scalable in a flexible manner, where more, less or other parsers may be installed to parse the corresponding types of MQ data.
[0120] The unified format MQ data obtained after the parsing may be in the form of a message queue. In this case, the unified format MQ data may be put into a queue 3124 of unified format messages. In VPC2 of the TTP IDC, the MQ sender 3094 responsible for the MQ data may extract the unified format MQ data after the parsing from the queue 3124 of unified format messages via the SDK for data safety and compliance inspection. The unified format MQ data that does not meet the data exchange constraints is rejected by the MQ sender 3094 and recorded in the rejection log 3126. The unified format MQ data that meets the data exchange constraints is pushed to the DES rear adapter 3130 in the DES adapter 3070 via the SDK.
[0121] The DES rear adapter 3130 may be implemented as part of the DES proxy 3073 to post-process uniform format MQ data from the TTP IDC to the overseas IDC and transmit the data to the destination. The uniform format MQ data that satisfies the data exchange constraints is pushed to the DES rear adapter 3130 via the SDK.
[0122] The DES rear adapter 3130 may include a data replayer 3132 for performing post-processing of the uniform format MQ data. Specifically, the DES rear adapter 3130 may be configured to convert the uniform format MQ data into raw MQ data. Therefore, the DES rear adapter 3130 may include replayers corresponding to different types of MQ data to perform conversion from the uniform format to respective custom formats. As shown in FIG. 3F, the DES rear adapter 3130 may include a MySQL replayer for converting the uniform format MQ data into MQ data conforming to the MySQL protocol, a Redis replayer for converting the uniform format MQ data into MQ data conforming to the Redis protocol, a document replayer for converting the uniform format MQ data into graphic raw data, an MQ replayer for converting the uniform format data into raw data conforming to the MQ protocol, etc.
[0123] The converted raw MQ data may be queued in a unified format message queue 3134 in the DES rear adapter 3130 and synchronized from there to a target message queue 3135. The target message queue 3135 is used to store the MQ data synchronized indirectly from the source message queue 3112 via the DES 1040. The target database 3136 can obtain the expected MQ data from the target message queue 3135.
[0124] In FIG. 3F, only components involved in data exchange in the direction from the TTP IDC to the overseas IDC are shown. The example of FIG. 3F shows data exchange in the direction from the overseas IDC to the TTP IDC. DES 1040 may include similar components for processing data exchange in this direction. For example, DES adapter 3070 may include a DES front adapter with similar functionality to DES front adapter 3120. Also, DES adapter 3061 may include a DES rear adapter with similar functionality to DES rear adapter 3130. For the purpose of simplicity, the processing in this direction will not be detailed.
[0125] It will be appreciated that the components for processing MQ data exchanges in the DES shown in Figure 3F are merely an example, and in other examples, different functional modules may be subdivided, integrated, etc. in other manners as desired, and may further include more, fewer, or different functional modules.
[0126] Example implementation of data exchange for offline aggregated data FIG. 3G illustrates a schematic block diagram of a data exchange architecture 3500 for an HDFS channel according to some embodiments of the present disclosure. The data exchange architecture 3500 may be implemented in DES 1040 to perform data security protection on the offline aggregated data. The example of FIG. 3G illustrates an offline aggregated data exchange between HDFS 3502 at the TTP IDC side and HDFS 3504 at the overseas IDC side. Some offline aggregated data in HDFS 3502 and HDFS 3504 may need to be synchronized with each other.
[0127] As shown in FIG. 3G, in the data exchange architecture 3500, the data transmission detector 3510 on the TTP IDC side is responsible for detecting whether the HDFS 3502 stores offline aggregated data that needs to be distributed to the HDFS 3504 on the other side. If it finds offline aggregated data to be distributed, the data distribution transmitter 3520 may pass a request for data distribution to the file sender 3550. Before being passed to the file sender, the data pre-processing module 3530 is configured to perform data pre-processing to process the offline aggregated data as unified format data.
[0128] In the file transmitter 3550, the data delivery server 3556 is configured to control the data delivery service based on the data exchange constraints. If the data delivery server 3556 determines that the pre-processed unified format data from the HDFS 3502 complies with the data exchange constraints, it may call the delivery work 3558 to deliver the unified format data to the overseas IDC through the delivery task 3562 under the delivery work 3558. In some embodiments, the delivery work 3558 may further include a data validation task 3560, which may be configured to perform data validation as necessary. The unified format data may pass through the HDFS gateway 3564, and after post-processing is performed, the original offline aggregated data may be obtained and stored in the HDFS 3504.
[0129] Similarly, in the data exchange architecture 3500, the data delivery detector 3570 on the overseas IDC side is responsible for detecting whether the HDFS 3504 stores offline aggregated data that needs to be delivered to the HDFS 3502 on the TTP IDC side. If it finds offline aggregated data to be delivered, the data delivery transmitter 3572 may pass a request for data delivery to the file sender 3550. Before being passed to the file sender, the data pre-processing module 3570 is configured to perform data pre-processing to process the offline aggregated data as unified format data.
[0130] In the file transmitter 3550, if the data delivery server 3556 determines that the pre-processed unified format data from the HDFS 3504 meets the data exchange constraints, it may call the delivery work 3554 to deliver the unified format data to the TTP IDC through the delivery task 3552 under the delivery work 3554. After the unified format data undergoes post-processing, it obtains the original offline aggregated data and stores it in the HDFS 3502.
[0131] As can be appreciated, the components for handling offline aggregate data exchange in the DES shown in Figure 3G are merely an example. In other examples, different functional modules may be subdivided, integrated, etc. in other manners as desired, and may further include more, fewer, or different functional modules.
[0132] Example implementation of data exchange for object stores Overall, the TOS channel can determine whether an object file satisfies data exchange constraints and, if so, copy the object file from a source IDC (e.g., a TTP IDC or an overseas IDC) to a destination IDC (e.g., an overseas IDC or a TTP IDC). Object files can be, for example, video, audio, images, documents, or other media files.
[0133] In some embodiments, the object file may be copied from the object store via the API, and the determination of the data exchange constraints may be performed, and the object file may be pushed to the destination object store using the API. During the data exchange of the object file, it is determined whether the data exchange constraints are satisfied by the copy request corresponding to the object file. The details of the TOS channel are described below with reference to Figures 3H-3J.
[0134] 3H illustrates a schematic diagram of a target object store (TOS) channel 3600 for copying data from a TTP IDC to an overseas IDC according to some embodiments of the present disclosure. In this example, the data being exchanged is an object file stored in an object store 3606 at the TTP IDC and is expected to be exchanged to an object store 3607 of the overseas IDC.
[0135] In Figure 3H, an API 3605 in the TTP IDC is configured to push copy requests to the work node 3605 and receive exchanged copy results from the work node 3605 from the other side of the overseas IDC. As shown, at the time of data stream initiation 3601, a copy request for an object file to be exchanged is delivered to the work node 3605 by an API (which may be referred to as a DES-TOS API) 3602. This copy request may indicate information related to the object file to be exchanged, such as the format of the object file (video, audio, text, etc.), the object file identifier, and other file metadata. This copy request has a unified format.
[0136] Work node 3605 in trust domain VPC2 is configured to respond to copy requests for object files and perform decisions regarding data exchange constraints. Specifically, work node 3605 can determine whether an object file to be exchanged from a unified format copy request satisfies the data exchange constraints.
[0137] In some embodiments, on the TTP IDC side, registration of data exchange constraints may be initiated at an initial stage or at a subsequent required time. At constraint registration initiation 3622, the data exchange constraints to be used may be registered with a DES registration center 3624 in the TTP trust domain via a DES entry 3620 in the TTP IDC. The registration of data exchange constraints may be realized by calling the API 3602. A work node 3605 may access the currently used data exchange constraints via the DES registration center 3624.
[0138] In some embodiments, the data exchange constraints may indicate a whitelist of object files that are permitted to be exchanged or a blacklist of object files that are not permitted to be exchanged, where each list may identify file objects that are permitted or not permitted to be exchanged by object file format, identifier, etc.
[0139] In enforcing the data exchange constraints, the work node 3605 allows execution of copy requests that satisfy the data exchange constraints. If execution of the copy request is allowed, the work node 3605 accesses the object store 3606 at the TTP IDC to copy the object file to the object store 3607 at the overseas IDC. Invalid requests (i.e., copy requests that do not satisfy the data exchange constraints) are rejected and therefore cannot be executed. The work node 3605 may write the copied object file to the object store 3607 via the API 3610 at the overseas IDC. Thus, data stream termination 3611 is reached.
[0140] 3I shows a schematic diagram of a TOS channel 3650 for copying data from an overseas IDC to a TTP IDC according to some embodiments of the present disclosure. In this example, an object file to be exchanged is stored in an object store 3607 at the overseas TTP IDC and is expected to be exchanged into an object store 3606 at the TTP IDC.
[0141] In FIG. 3I, the API 3610 in the overseas IDC is configured to push a copy request to the work node 3605 and receive the exchanged copy result from the work node 3605 from the other side TTP IDC. As shown in FIG. 3I, at the time of data stream start 3651, a copy request for an object file to be exchanged is delivered to the work node 3605 by the API 3610. This copy request can indicate information related to the object file to be exchanged, such as the format of the object file (video, audio, text, etc.), the object file identifier, and other file metadata. This copy request has a uniform format. The work node 3605 in the trust domain VPC2 can determine whether the object file to be exchanged satisfies the data exchange constraint from the copy request in the uniform format.
[0142] In some embodiments, the overseas IDC may initiate the registration of data exchange constraints at an initial stage or at a subsequent required time. At constraint registration initiation 3632, the data exchange constraints to be used may be registered in the DES registration center 3624 in the TTP trust domain via the DES entry 3630 in the overseas IDC. The registration of data exchange constraints may be realized by calling the API 3610. The work node 3605 may access the currently used data exchange constraints via the DES registration center 3624.
[0143] When enforcing the data exchange constraints, the work node 3605 allows execution of copy requests that satisfy the data exchange constraints. If execution of the copy request is allowed, the work node 3605 accesses the object store 3607 at the overseas IDC to copy the object file to the object store 3606 at the TTP IDC. Invalid requests (i.e., copy requests that do not satisfy the data exchange constraints) are rejected and therefore cannot be executed. The work node 3605 may write the copied object file to the object store 3606 via the API 3602 at the TTP IDC. Thus, data stream termination 3652 is reached.
[0144] It will be appreciated that the components for handling TOS data exchange in a DES shown in Figures 3H and 3I are merely examples, and that in other examples, different functional modules may be subdivided, combined, etc. in other manners as desired, and may further include more, fewer, or different functional modules.
[0145] 3J illustrates a message sequence 3012 in a TOS channel in accordance with some embodiments of the present disclosure. The message sequence 3012 in FIG. 3J involves a TTP 3701, a maintenance person 3702, a platform staff 3703, a DES entrance 3704, an API 3705, a work node 3605, and an object store 3708.
[0146] Depending on the direction of data exchange, DES inlet 3704, API 3705 and object store 3708 in Figure 3J may be the corresponding components in any one of Figures 3H and 3I. For example, in TOS channel 3600 copied from TTP IDC to overseas IDC shown in Figure 3H, DES inlet 3704 includes DES inlet 3620 shown in Figure 3H, API 3705 includes API 3602 in Figure 3H, and object store 3708 includes object store 3606 in Figure 3H. In TOS channel 3650 copied from overseas IDC to TTP IDC, DES inlet 3704 includes DES inlet 3630 shown in Figure 3I, API 3705 includes API 3610 in Figure 3I, and object store 3708 includes object store 3607 in Figure 3I.
[0147] In message sequence 3012, the maintainer 3702 registers 3711 a data exchange constraint with the DES inlet 3704. The data exchange constraint can restrict copying of object files between object stores 3606 and 3607 of different IDCs. After the registration is completed, the DES inlet 3704 can send a response 3714 to the maintainer. The DES inlet 3704 registers 3712 container information related to the data exchange constraint with the API 3705, and after the registration is completed, the API 3705 can send a response 3713 to the DES inlet 3704. The rules registered via the DES inlet 3704 can be cached 3715 with the API 3705, and can also be cached 3716 with the work node 3605.
[0148] Platform staff 3703 may initiate 3717 a copy request for the object file to API 3705. API 3705 may perform authentication 3718. Work node 3605 may pull 3719 the copy request from API 3705 as well as perform data exchange constraint determination 3720 on the object file to be copied. If copying the object file is allowed, work node 3605 performs 3721 the file copy, copying the corresponding object file from object store 3706. Of course, regardless of the result not satisfying the data exchange determination, work node 3605 returns 3722 feedback to API 3705. If copying the object file is allowed, the feedback includes the object file that was copied. If copying the object file is not allowed, the feedback is used to indicate that the copy request was denied.
[0149] In some embodiments, platform staff 3703 can call back 3723 API 3705, which can return 3724 a copy request ID to platform staff 3703. In some embodiments, TTP 3701 can look at 3725 the historical status of object file copies via DES inlet 3704 to see if the exchange of object files within a certain time period in the past complies with the requirements of the data exchange constraints. DES inlet 3704 can return 3726 the results to be viewed.
[0150] Example implementation of data exchange protection for service invocation FIG. 3K illustrates a schematic block diagram of a data exchange architecture 3800 for a service invocation channel according to some embodiments of the present disclosure. The data exchange architecture 3800 may be implemented in a DES 1040 and used to perform data security protection for service invocation type data. The example of FIG. 3L illustrates a service invocation data exchange between a target platform service 3802 on the TTP IDC side and a foreign (non-TTP) platform service 3804 on the foreign IDC side. For example, a service on the target platform service 3802 may need to invoke a service on the foreign platform service 3804. Conversely, a service on the foreign platform service 3804 may also need to invoke a service on the target platform service 3802.
[0151] Different service platforms may apply various different service invocation protocols, such as HTTP protocol or Thrift RPC protocol. In some embodiments of the present disclosure, it is desirable to be able to process unified format data, such as HTTP protocol data, when implementing data sovereignty protection in the VPC trust domain.
[0152] In FIG. 3K, in the control plane, the non-TTP control plane is used for channel registration, channel architecture updates, and discovery, and the TTP / TTP control plane is used for channel request authorization, channel ban, channel discovery, etc. In the data plane, the HTTP load balancer 3810 is an L7 balancer product from TTP Cloud, which is a critical component that ensures that all DES-RPC channel traffic passes through the VPC trust domain. The HTTP channel is a DES-RPC channel that supports the HTTP protocol. The Thrift RPC channel is a DES-RPC channel that supports the Thrift RPC protocol. Before being sent to TTP's HTTP load balancer, the Thrift RPC channel is wrapped in an HTTP channel.
[0153] In the channel registration phase, a DES-RPC channel is declared using channel information and a data definition. The channel information may include the type of channel, e.g., Thrift RPC or HTTP. The channel information may further include an RPC call tuple. The call tuple may include src dc, src service, dst dc, dst service, rpc method / http route.
[0154] The data definition may depend on the data flow direction: For non-TTP to TTP data flow, declare responses in Thrift IDL with compliance comments; For TTP to non-TTP data flow, declare requests in Thrift IDL with compliance comments. In some embodiments, a DES-RPC channel is available only if it passes compliance registration.
[0155] It will be appreciated that the components for processing service invocation data exchange in the DES shown in Figure 3K are merely an example, and in other examples, different functional modules may be subdivided, integrated, etc. in other manners as desired, and may further include more, fewer, or different functional modules.
[0156] FIG. 3L illustrates an example of data exchange from a non-TTP to a TTP in the service invocation channel illustrated in FIG. 3K according to some embodiments of the present disclosure. As illustrated in FIG. 3L, a call initiated by a service A 3901 in an overseas domain is forwarded to an HTTP load balancer 3905 of a TTP by an HTTP proxy 3902 or a Thrift proxy 3903. Service A 3901 may be an example of an overseas platform service illustrated in FIG. 3M. In the case of an HTTP request, the call is forwarded to an HTTP load balancer 3905 by an HTTP proxy 3902. In the case of a Thrift request, the call is forwarded to an HTTP load balancer 3905 by a Thrift proxy 3903.
[0157] It is proposed that service discovery from the corresponding service proxy in the overseas IDC, e.g. HTTP proxy 3902 or Thrift proxy 3903 to the VPC trust realm HTTP load balancer 3905, is realized by DNS. It is proposed that service discovery of the proxy, which forwards the corresponding request to the TTP IDC realm, uses customized / generic service discovery.
[0158] The HTTP load balancer 3905 may include a compliance plugin 3906. For invalid requests, the compliance plugin 3906 returns an error. For Thrift rpc calls, the request is wrapped in HTTP to generate a new HTTP request. The body of the new HTTP request is the Thrift binary file.
[0159] In the VPC trust domain, TTP's HTTP load balancer 3905 forwards the request to TTP's HTTP proxy 3907 and Thrift proxy 3908, respectively. The HTTP proxy 3907 and Thrift proxy 3908 then forward the request to the target services Service B 3908 and Service C 3910, respectively. In case of a Thrift rpc call, the Thrift proxy 3908 recovers the original Thrift request from the generated new HTTP request before sending the request.
[0160] The TTP HTTP proxy 3907 and the Thrift proxy 3908 inspect the response before sending it to the TTP HTTP load balancer 3905. If the response does not pass the compliance inspection, an error is returned. In the case of a Thrift rpc call, the Thrift response is wrapped in HTTP to generate a new HTTP response. The body of the new HTTP response is a Thrift binary file.
[0161] FIG 3M illustrates an example of data exchange from a TTP to a non-TTP in the service invocation channel illustrated in FIG 3K according to some embodiments of the present disclosure. As illustrated in FIG 3M, a call initiated by a service A 3951 of the TTP is forwarded to an HTTP load balancer 3955 of the TTP by an HTTP proxy 3952 and a Thrift proxy 3953 of the TTP. In the case of an HTTP request, the call is forwarded to the HTTP load balancer 3955 by the HTTP proxy 3952. In the case of a Thrift request, the call is forwarded to the HTTP load balancer 3955 by the Thrift proxy 3953.
[0162] For malformed requests, it returns an error. For responses that do not pass compliance checks, it returns an error. For Thrift rpc calls, the request is wrapped in HTTP to generate a new HTTP request. The body of the new HTTP request is the Thrift binary file.
[0163] The HTTP load balancer 3955 of the TTP forwards the request to a non-TTP (i.e., overseas domain) HTTP proxy 3957 and a Thrift proxy 3958. The HTTP proxy 3957 and the Thrift proxy 3958 then forward the request to a service B 3959 and a service C 3960 in the overseas domain.
[0164] In case of a Thrift rpc call, the Thrift proxy recovers the original Thrift request from the generated new HTTP request before sending it.
[0165] The non-TTP HTTP proxy 3957 and the Thrift proxy 3958 send the response to the TTP HTTP load balancer 3955. In the case of a Thrift rpc call, the Thrift response is wrapped in HTTP to generate a new HTTP response. The body of the new HTTP response is a Thrift binary file.
[0166] Security Sandbox Subsystem A client application needs to communicate with a server to transmit data. The network traffic of the client application can transmit a large amount of user data. Therefore, a method of network traffic that can manage the client application is required so that the user data is not transmitted to an unauthorized server via the network traffic of the client application. For example, in a data sovereignty protection scenario, the method can prevent the user data from being transmitted to a server outside the data sovereignty country.
[0167] However, the types of network traffic of a client application are very rich. The client application may include a mobile side application and a computer (PC side) application. The network traffic of a client application may include a native type of network traffic and a web page view type of network traffic, etc. However, the network traffic of a client application is not all managed and controlled by the application owner. For example, the network traffic of a client application may include network traffic from a third-party advertiser. Therefore, it is very difficult to manage the various types of network traffic of a client application.
[0168] An exemplary embodiment of the present disclosure proposes a method for managing network traffic of a client application, which includes: detecting a network transmission of user data of a target user from a client application to a server based on a determination for a target user, analyzing the network traffic at different layers of the network transmission based on a type of network traffic corresponding to the network transmission, and sending the network traffic to a server limited by the data exchange constraint based on the analysis indicating that the network traffic satisfies a data exchange constraint corresponding to the target user.
[0169] This method can effectively prevent user data from being transmitted to unauthorized servers via various types of network traffic by analyzing network traffic at different layers of network transmission based on the type of network traffic and restricting the transmission of network traffic that does not meet data exchange constraints.
[0170] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following, the solution of the present disclosure will be described in detail with reference to a mobile application as an example.
[0171] 4A illustrates a flowchart of an example method 4100 for managing network traffic of a mobile-side application according to some embodiments of the present disclosure. The method 4100 can be implemented, for example, in the security sandbox subsystem 1090 of FIG. 1. The mobile-end application can be a mobile-side target application 1080.
[0172] In box 4102, based on the determination for the target user, detect a network transmission of user data of the target user from the target application 1080 to a server. In other words, if it determines that the current user is the target user, the security sandbox subsystem 1090 can detect a network transmission of user data of the target user.
[0173] In some embodiments, network traffic may be routed to the security sandbox subsystem 1090 based on the determination for the target user such that the security sandbox subsystem 1090 can detect and analyze network traffic corresponding to network transmissions of user data. The security sandbox subsystem 1090 can analyze the network requests of the target application 1080 and restrict network requests that do not satisfy conditions based on the data exchange constraints.
[0174] The data exchange restrictions may include exchange restrictions related to data sovereignty, such as data sovereignty protection rules. The data sovereignty protection rules may be determined based on national or regional regulations. The data sovereignty protection rules may be determined by the application operator (e.g., related to user data usage protocols).
[0175] The data sovereignty protection rule may be set based on a specific scenario. For example, the data sovereignty protection rule may stipulate that the user data of the data sovereign nation is not allowed to be transmitted to any server other than the data sovereign nation. In another embodiment, the data sovereignty protection rule may stipulate that the privacy user data of the data sovereign nation is not allowed to be transmitted to any server that is not registered. The scope of the present disclosure is not limited thereto.
[0176] 1, a network request of a target application 1080 is transmitted to the application firewall subsystem 1020 after being analyzed and processed by the security sandbox subsystem 1090. The principles and details of the security sandbox subsystem 1090 will be described in detail below.
[0177] A target user is a user whose user data transmission needs to be detected and managed. The target user may be a user who has the nationality of a data sovereign state. Alternatively or additionally, the target user may be a user who is determined based on the specific rules of data sovereign protection. For example, the target user may be a user who has the nationality of a data sovereign state and is currently geographically located in this data sovereign state.
[0178] In some embodiments, the target user may be determined based on user information. The user information may include a user's account information, personal information, registration information, etc. Alternatively or additionally, the target user may be determined based on device information. The device information may include Subscriber Identity Module (SIM) information, IP address, network service provider information, device system setting information, application setting information, etc.
[0179] In some implementations, target users may be determined based on a combination of various information. Various information may have different priorities. For example, SIM information, network service provider information may have a higher priority than IP address, system configuration information, application configuration information, etc.
[0180] In some embodiments, the determination of the target user may be based on a determination of the region in which the target user is located. The target user may be determined by using the user information or device information to determine the region in which the target user is located. For example, the region setting in the system settings of the smartphone may be used to determine the region in which the current user is located, thereby determining whether the current user is the target user. Also, for example, the country code of the SIM card may be used to determine the region in which the target user is located, thereby determining the target user.
[0181] In some embodiments, the target user may be determined when the application is first launched. In other words, whether the current user is the target user may be determined when the application is first launched. Alternatively or additionally, whether the current user is the target user may be determined when the user registers. Alternatively or additionally, whether the current user is the target user may be determined when the user logs in, logs out, or switches accounts.
[0182] In some embodiments, the determination result may be stored locally or on a server. The determination result may be stored after the first determination that the user is a target user, and may be configured to use the stored determination result within a threshold time period. In this way, when the user re-registers, there is no need to determine the user again.
[0183] At box 4104, the network traffic is analyzed at different layers of the network transmission based on the type of network traffic corresponding to the network transmission.
[0184] The network traffic in the target application 1080 may include multiple types of network traffic, such as native, webpage view, and third party software development kit (SDK) type network traffic. The native type network traffic is generated and processed by the operating system (e.g., Android and IOS) code in the business layer. The native type network traffic may be fully controlled by the owner of the target application 1080.
[0185] Third party SDK type network traffic is generated and processed by third party SDKs. Typically, a target application 1080 may access third party SDKs to implement registration or sharing functions. Third party SDK type network traffic is generated and processed by these third party SDKs. It should be understood that third party SDK type network traffic is typically not fully controlled by the application owner.
[0186] The network traffic of the web page view type may include network traffic controlled by the application owner, for example, network traffic generated by an application's built-in browser calling native application code. The network traffic of the web page view type may further include network traffic controlled by a third party, for example, network traffic generated and controlled by a third-party advertiser.
[0187] Based on the type of network traffic, the security sandbox subsystem 1090 can adopt appropriate analysis policies to better manage the network transmission of user data in an application.
[0188] In box 4106, based on the analysis indicating that the network traffic satisfies the data exchange constraint corresponding to the target user, send the network traffic to a server restricted by the data exchange constraint. Different data exchange constraints may be set for different target users. For example, stricter data exchange constraints may be set for target users with higher sensitivity. The data exchange constraints may limit which user data can be transmitted to which servers. In some implementations, the data exchange constraints corresponding to the target user may be determined based on user information or corresponding device information of the target user.
[0189] In some embodiments, the security sandbox subsystem 1090 may include multiple sub-modules for different types of network traffic, such as a sub-module for managing native type network traffic, a sub-module for managing web page view type network traffic, and a sub-module for managing third party SDK type network traffic. These sub-modules can analyze the relevant types of network traffic and restrict or block network traffic that does not meet the data exchange constraints. Details of managing different types of network traffic are described in more detail below with reference to Figures 4B to 4E.
[0190] 4B illustrates a schematic diagram of an analysis and restriction process 4200 for native-type network traffic according to some embodiments of the present disclosure. FIG. 4B illustrates a sub-module 4210 for analyzing and restricting native-type network traffic. The sub-module 4210 may be a part of the security sandbox subsystem 1090 or may be a specific implementation of the security sandbox subsystem 1090.
[0191] As shown in FIG. 4B, the business logic layer 4220 sends the network request to the lower OS 4230. The business logic layer 4220 may be a specific realization of the application service logic 1100 shown in FIG. 1 that is involved in network transmission. The submodule 4210 can analyze and restrict the network request at the network layer as a blocker. The submodule 4210 can restrict the network request by analyzing the endpoint, the parameters of the network request, or the schema. For example, it can determine whether to restrict the network request based on whether the schema has already been registered. Alternatively or additionally, it can determine whether to restrict the network request based on whether a field requested in the network request is related to sensitive information.
[0192] In some implementations, sub-module 4210 may include a blocker for Android and a blocker for IOS. Additionally, sub-module 4210 may further include a blocker for C++. In this manner, by analyzing and limiting a network request at the network layer, it is possible to better determine whether the network request should be limited based on the protocol information of the network request.
[0193] 4C illustrates a schematic diagram of an analysis and restriction process 4300 for network traffic of a web page view type according to some embodiments of the present disclosure. FIG. 4C illustrates a sub-module 4310 for analyzing and restricting network traffic of a web page view type. The sub-module 4310 may be a part of the security sandbox subsystem 1090 or may be a specific implementation of the security sandbox subsystem 1090.
[0194] Submodule 4310 can divert webpage view type network traffic to a native network interface so that the webpage view type network traffic can be analyzed and restricted by submodule 4210 for native type network traffic. In some embodiments, submodule 4310 can utilize a JavaScript (JS) hook mechanism to divert webpage view type network traffic to a native network interface.
[0195] As shown in FIG. 4C, the submodule 4310 may include a starter 4311, a navigation URL blocker 4312, and an internal request blocker 4313. The submodule 4310 may communicate with a browser 4320 embedded in an application so that network traffic of a web page view type can be managed and detected by the submodule 4310. The starter 4311 may perform JS injection when the browser 4320 embedded in an application is opened (created) so that network traffic of a web page view type can be transferred to a native network interface using a hook mechanism. The network traffic transferred to the native network interface can be taken over by a native network module.
[0196] In some embodiments, network traffic redirection can be performed using JS hook technology in the following manner:
[0197] The navigation URL blocker 4312 can analyze and restrict the URL of the main page (initial page). For example, the navigation URL blocker 4312 can determine whether to restrict this network request based on whether the schema of the URL is registered. If this network request is not restricted, the browser 4320 can load this main page.
[0198] The internal request blocker 4313 can redirect network traffic related to static resources and dynamic resources of the main page to the native network interface, so that these network traffic can be restricted and analyzed at the network layer by the submodule 4210. The specific analysis and restriction process is similar to that of native type network traffic, and will not be further described here.
[0199] In some embodiments, for network traffic of web page view types controlled by an application owner and network traffic of web page view types controlled by a third party, submodule 4310 may adopt different analysis and restriction policies. For example, for network traffic of web page view types controlled by a third party, there is no need to further analyze the static and dynamic resources of the main page, and the navigation URL blocker 4312 may be used only to analyze the related network traffic by determining whether the URL of the main page is registered.
[0200] 4D illustrates a schematic diagram of an analysis and restriction process 4400 for third-party SDK-type network traffic according to some embodiments of the present disclosure. FIG. 4D illustrates a sub-module 4410 for analyzing and restricting third-party SDK-type network traffic. The sub-module 4410 may be a part of the security sandbox subsystem 1090 or may be a specific implementation of the security sandbox subsystem 1090.
[0201] Submodule 4410 can analyze and restrict third-party SDK-type network traffic at the application programming interface (API) layer. Submodule 4410 can restrict third-party SDK-type network traffic by analyzing whether data requested by the API of the third-party SDK at the API layer satisfies data exchange constraints.
[0202] In some embodiments, the submodule 4410 can wrap an API that requests user data in a third-party SDK and add a decision logic based on a data exchange constraint to the wrap. In other words, the submodule 4410 can determine a wrapped API by adding a decision logic to an API of a third-party SDK. In this way, the business logic layer 4220 calls the wrapped API with the decision logic added, rather than directly calling the API of the third-party SDK.
[0203] 4D , sub-module 4410 may include a wrapper module for each third-party SDK, e.g., wrapper module 4412 for SDK 4411, wrapper module 4414 for SDK 4413, and wrapper module 4416 for SDK 4415. A wrapper module (e.g., wrapper module 4412) can wrap an API in a corresponding SDK (e.g., SDK 4411) to generate a corresponding wrapped API. In some embodiments, sub-module 4410 can dynamically augment the wrapper modules to wrap APIs of third-party SDKs.
[0204] In some embodiments, the API of a third party SDK can be wrapped in the following manner: The wrapper module 4412 can define an API exposed to the business layer that is the same as the API in the SDK 4411. The wrapper module 4412 can implement this API and define wrapper classes for the SDK 4411 data types.
[0205] The judgment logic may determine whether the API of the wrapped third-party SDK can be called based on the data exchange constraints. In some embodiments, the judgment logic may analyze whether the API of the third-party SDK can be called based on the name of the SDK, the name of the API, the name of the parameters of the API, etc. If the judgment result is YES, the API of the third-party SDK can be called and returns a value to the business layer. If the judgment result is NO, the API of the third-party SDK is not called, that is, the network traffic related to this API is limited. It should be understood that the judgment logic may vary based on a specific scenario. For example, the judgment logic may be set to not allow the third-party SDK to input user privacy data.
[0206] In this manner, by performing analysis and restriction at the API layer, submodule 4410 can manage and detect third-party SDK type network traffic without knowing the internal code of the third-party SDK.
[0207] FIG. 4E illustrates a module diagram of the security sandbox subsystem 1090 according to some embodiments of the present disclosure. As shown in FIG. 4E, the security sandbox subsystem 1090 includes an initiation module 4520. The initiation module 4520 is configured to initiate detection of network transmission of user data of the target user from a client application to a server based on a determination of the target user. The initiation module 4520 can activate a management module to detect, manage, analyze, and restrict network traffic corresponding to the network transmission of the user data.
[0208] The management module is configured to analyze the network traffic at different layers of the network transmission based on a type of network traffic corresponding to the network transmission, and, based on the analysis indicating that the network traffic satisfies the data exchange constraint corresponding to the target user, send the network traffic to a server defined by the data exchange constraint.
[0209] In some embodiments, the management module may include a sub-module (also referred to as a first management module) 4210, a sub-module (also referred to as a second management module) 4310, and a sub-module (also referred to as a third management module) 4410. Sub-module 4210, sub-module 4310, and sub-module 4410 may analyze and limit network traffic of client applications.
[0210] In some embodiments, sub-module 4210 is configured to analyze the network traffic at the network layer based on the type of the network traffic being a native type.
[0211] In some embodiments, submodule 4310 is configured, based on network traffic whose type is a web page view type, to divert the network traffic of the web page view type to a network interface of a client application to be managed by a native network module of the client application, and to analyze the divert network traffic at a network layer.
[0212] In some embodiments, redirecting the web page view type network traffic to a network interface of the mobile side application includes redirecting the web page view type network traffic utilizing a JavaScript hook mechanism.
[0213] In some embodiments, sub-module 4410 is configured to analyze the network traffic at an application programming interface API layer based on the network traffic being a type of the network traffic being a third-party SDK type.
[0214] In some embodiments, analyzing the network traffic at an API layer includes determining a wrapped API by adding decision logic based on the data exchange constraints to an API of a third-party SDK, and invoking the wrapped API to analyze the network traffic utilizing the decision logic.
[0215] In some embodiments, the activation module 4520 can activate the sub-modules 4210, 4310, and 4410 based on the determination for the target user. For example, the activation module 4520 can determine whether the current user is the target user when the user is registered. If the determination result is YES, the activation module 4520 can activate the sub-modules 4210, 4310, and 4410. Also, for example, the activation module 4520 can obtain the determination result for this user locally or from a server when the user is registered, and determine whether to activate the sub-modules 4210, 4310, and 4410 based on the determination result.
[0216] The security sandbox subsystem 1090 may further include a sampling module 4510 for sampling network traffic. In some embodiments, the sampling module 4510 can send a sampling signal to the wake-up module 4520 to trigger the wake-up module 4520. The sampling signal can indicate a sampling rate at which to sample the network traffic.
[0217] The sampling module 4510 can sample target users and different types of network traffic based on data exchange constraints. For example, the sampling module 4510 can sample different types of network traffic at different sampling rates. By utilizing the sampling module 4510, only a portion of the network traffic needs to be analyzed, thereby reducing overhead and maintaining application stability.
[0218] It should be understood that the security sandbox subsystem 1090 may further include other modules or may include only some of the modules shown in FIG. 4E. For example, if the target application 1080 is only a native application on the mobile side, the security sandbox subsystem 1090 may not include the sub-module 4310 for web page view type network traffic. The scope of the present disclosure is not limited thereto.
[0219] In some embodiments, network traffic may be analyzed and restricted at the Socket layer based on the type of network traffic. For example, third-party SDK type network traffic may be redirected at the Socket layer so that third-party SDK type network requests can be directly analyzed. Alternatively or additionally, native type network traffic and web page view type network traffic may be analyzed and restricted at the Socket layer.
[0220] In some embodiments, a local server may be established as a proxy on the target application 1080. The network requests of the target application 1080 may be forwarded to the local server, and the network traffic may be analyzed and restricted on the local server, thereby managing the network requests forwarded by the local server to external servers. In this manner, different types of network traffic may be analyzed and restricted while taking into account protocol information, thus better managing the application's network traffic from being transmitted to unauthorized external servers.
[0221] Above, the principles and details of analyzing and restricting different types of network traffic have been described in detail with reference to Figures 4B to 4E. It should be understood that the above restriction rules, judgment logics and data exchange constraints are merely exemplary and do not limit the scope of the present disclosure. For example, different data sovereignty protection rules can be set according to the legal requirements of different countries. It should be noted that depending on the definition of the layers of a computer network, the network traffic can be analyzed and restricted at layers close to or similar to the above layers.
[0222] It should be noted that in the above description, the security sandbox subsystem 1090 can directly analyze and restrict network traffic in the target application 1080. In other words, only network traffic that is not restricted by the security sandbox subsystem 1090 can continue to be transmitted. Alternatively or additionally, the security sandbox subsystem 1090 may not directly restrict network traffic and may only provide an analysis report. In such a case, a copy of the network request may be sent to the security sandbox subsystem 1090 at the same time as the network request is normally transmitted. The security sandbox subsystem 1090 may analyze the copy of the network request and provide an analysis report.
[0223] In some embodiments, in the case of multiple data sovereign countries, multiple security sandbox subsystems 1090 may be configured to process for each data sovereign country accordingly. For example, based on the determination of the region where the target user is located, a corresponding security sandbox subsystem may be activated to analyze and restrict network traffic so that the network transmission of user data in the application complies with the data sovereignty protection rules of the corresponding country.
[0224] Recommended Management Subsystem As discussed above, target applications may provide users with various content recommendations, such as multimedia content recommendations, user recommendations, product recommendations, etc., through, for example, recommendation mechanisms. In such applications, the fairness of recommendation policies is already the focus of many local management efforts. For example, some applications may induce users to pay attention to certain content that is not related to the user's habits through recommendation mechanisms. Such recommendation mechanisms may be subject to fraud.
[0225] On the one hand, common recommendation algorithms often rely on machine learning models to be implemented, and code-level verification, for example, performed by the security computing subsystem 1060, may not be able to effectively detect the fairness of recommendation algorithms. On the other hand, people also do not expect users' privacy data to be exposed during inspection, because the training and updating of recommendation models are often closely related to actual user data, which may lead to data compliance risks.
[0226] The embodiment of the present disclosure further proposes a method for managing recommendation policies. Figure 5 shows a flowchart of a process 500 for managing recommendation policies. The process 500 may be performed by the recommendation management subsystem 1050, for example.
[0227] 5, in box 502, the recommendation management subsystem 1050 obtains a set of object features associated with a set of objects in a target application, where the set of object features are obtained by transformation based on attributes of the set of objects, and the set of object features do not directly represent attributes of the set of objects.
[0228] In some embodiments, the recommendation management subsystem 1050 may obtain the set of object features via an application programming interface API provided by the target application. In some embodiments, the recommendation management subsystem 1050 may obtain the set of object features associated with the set of objects in the target application 1080 from the target application platform 1030, for example via a proprietary API.
[0229] In some embodiments, the set of object features may be, for example, obtained by a feature extraction model transforming the set of object attributes. In this manner, the recommendation policy manager or other third parties can be prevented from determining the original attribute information of the object based on the object features, thereby ensuring the safety of data in the target application.
[0230] In box 504, the recommendation management subsystem 1050 determines a first object feature and a second object feature from the set of object features, where a first difference between the first object feature and the second object feature is less than a first threshold.
[0231] In some embodiments, the set of object features may be represented, for example, as a plurality of vectors. Further, the recommendation management subsystem 1050 may select, from the set of object features, at least one pair of object features whose difference is less than a first threshold, for example based on the difference between the vectors.
[0232] In box 506, the recommendation management subsystem 1050 determines a first recommendation result corresponding to the first object feature and a second recommendation result corresponding to the second object feature based on a recommendation policy in the target application.
[0233] In some embodiments, the recommendation management subsystem 1050 may provide a first object feature to a recommendation model associated with the recommendation policy to determine a first recommendation result, and provide a second object feature to the recommendation model to determine a second recommendation result.
[0234] In some embodiments, to ensure the safety of the recommendation policy, the recommendation management subsystem 1050 may send the selected first and second object features to a remotely run recommendation model via an API provided by the target application to determine the first and second recommendation results. Illustratively, the recommendation model may be run by, for example, a maintainer of the target application.
[0235] In some embodiments, the process of generating the first recommendation result and the second recommendation result does not affect the recommendation model actually deployed in the target application.
[0236] In some embodiments, the first recommendation result and the second recommendation result may be represented by a vector output by the recommendation model, so that the recommendation management subsystem 1050 cannot directly decipher the semantics of the first recommendation result and the second recommendation result, thereby further improving the safety of data in the target application.
[0237] In box 508, the recommendation management subsystem 1050 evaluates a recommendation policy based on the first recommendation result and the second recommendation result.
[0238] In some embodiments, the recommendation management subsystem 1050 may determine a second difference between the first recommendation result and the second recommendation result and determine the fairness of the recommendation policy based on a comparison between the second difference and a second threshold.
[0239] Specifically, for a reasonable recommendation policy, for two similar objects, the recommendation results should be similar, so if the recommendation management subsystem 1050 determines that the second difference exceeds a second threshold, it may determine that the recommendation policy has relatively poor fairness.
[0240] Alternatively, the recommendation manager subsystem 1050 may determine the fairness of the recommendation policy based on, for example, a percentage of object feature pairs whose second difference exceeds a second threshold. For example, the recommendation manager subsystem 1050 may randomly sample, for example, a number of object feature pairs, and determine that the recommendation policy has relatively poor fairness if a percentage of the object feature pairs whose second difference exceeds the second threshold exceeds a threshold percentage.
[0241] In some embodiments, the recommendation management subsystem 1050 may determine the fairness of the recommendation policy based on the relevance between the object feature for input to the recommendation model and the historical recommendation results. Specifically, the recommendation management subsystem 1050 may obtain a third object feature and historical recommendation results for the third object feature from the target application. Further, the recommendation management subsystem 1050 determines the fairness of the recommendation policy based on the relevance between the third object feature and the historical recommendation results. For example, the recommendation management subsystem 1050 may base the determination on whether the object feature and the type information of the historical recommendation results match.
[0242] In some embodiments, the recommendation management subsystem 1050 may determine a vector representation corresponding to the third object feature and the historical recommendation results, and determine a relevance between the third object feature and the historical recommendation results based on a difference between the two vector representations. For example, if the vector difference between an object and its historical recommendation results is greater than a threshold, the recommendation management subsystem 1050 may determine that the recommendation policy has relatively poor fairness.
[0243] In some embodiments, as mentioned above, source code associated with a recommended policy, for example, may be inspected by security computing subsystem 1060. In particular, security computing subsystem 1060 may obtain source code corresponding to a recommended policy, for example, and evaluate the recommended policy based on the source code or intermediate code corresponding to the source code.
[0244] In some embodiments, the recommendation policy may be used to recommend at least one multimedia content to a user in, for example, the target application 1080. Examples of multimedia content may include, for example, images, videos, music, or combinations thereof.
[0245] Exemplary Processes, Apparatus and Devices 6 illustrates a flowchart of an example process 600 for code management according to some embodiments of the present disclosure. As shown in FIG. 6, in box 602, the Security Computing Subsystem 1060 responds to a request to build an executable file by obtaining corresponding development code from a code base. In 604, the Security Computing Subsystem 1060 compiles the development code into intermediate code and determines the safety of the intermediate code. In 606, in response to the intermediate code being determined to be safe, the Security Computing Subsystem 1060 generates an executable file based on the intermediate code.
[0246] In some embodiments, the method further includes providing the intermediate code to a code scanning module to determine a safety of the intermediate code.
[0247] In some embodiments, compiling the development code into the intermediate code includes obtaining a third party library associated with the development code and generating the intermediate code based on the development code and the third party library.
[0248] In some embodiments, obtaining a third-party library associated with the development code includes sending a request to obtain a third-party library associated with the development code, and in response to the third-party library being determined to be safe, obtaining the third-party library.
[0249] In some embodiments, the method further includes, in response to determining that the intermediate code has a risk, refusing to build the executable file and causing the risk portions in corresponding development code in the code base to be marked.
[0250] In some embodiments, the method further includes generating a report regarding the risk.
[0251] In some embodiments, the method further includes generating a signature for the executable file and uploading the signature to a signature management system.
[0252] In some embodiments, the executable file includes an installation file for the target application. The method further includes transmitting the installation file to an application store via a deployment gateway.
[0253] In some embodiments, the executable file includes a service program run by the target application platform. The method further includes authenticating a signature of the authentic service program and, in response to the signature being authenticated, causing the service program to be deployed to the target application platform via a deployment gateway.
[0254] In some embodiments, obtaining the corresponding development code from the code base includes synchronizing the development code to the code base via a synchronization gateway, sending a request to a product build system via the synchronization gateway to build the executable file, and a code pull module obtaining the corresponding development code from the code base based on the request.
[0255] In some embodiments, compiling the development code into the intermediate code includes a compilation module compiling corresponding development code into the intermediate code, the compilation module sending the intermediate code to a security code scanning module, and the security code scanning module determining security of the intermediate code.
[0256] In some embodiments, compiling the corresponding development code into the intermediate code by the compilation module includes the compilation module obtaining a third party library associated with the development code from a product library, where the third party library is added to the product library via a third party independent gateway in response to the third party library being determined to be safe by the third party independent gateway, and the compilation module generating the intermediate code based on the development code and the third party library.
[0257] In some embodiments, the method further includes, in response to the intermediate code being determined to be safe by the security code scanning module, an upload module uploading an executable file generated based on the intermediate code to a product library, and a deployment gateway obtaining the executable file from the product library so that the executable file is deployed.
[0258] In some embodiments, the deployment gateway obtaining the executable file from the product library so that the executable file is deployed includes the deployment gateway obtaining the executable file and a signature of the executable file from the product library, sending the signature of the executable file to a product signature management module, and in response to authentication of the signature by the product signature management module, the executable file being deployed via the deployment gateway.
[0259] The embodiments of the present disclosure further provide a corresponding apparatus for implementing the above method or process.Figure 7 shows a schematic structural block diagram of an apparatus 600 for managing recommendation policies according to some embodiments of the present disclosure.
[0260] 7, the apparatus 700 includes an obtaining module 710 configured to obtain corresponding development code from a code base in response to a request to build an executable file. The apparatus 700 further includes a compiling module 720 configured to compile the development code into intermediate code and determine safety of the intermediate code. The apparatus 700 further includes a generating module 730 configured to generate an executable file based on the intermediate code in response to the intermediate code being determined to be safe.
[0261] FIG. 8 shows a schematic block diagram of an example device 800 that may be used to implement embodiments of the present disclosure. For example, the system 1000 or each of its subsystems according to embodiments of the present disclosure may be implemented by the device 800. As shown in the figure, the device 800 includes a central processing unit (CPU) 801. The CPU 801 may perform various appropriate operations and processes based on computer program instructions stored in a read-only memory (ROM) 802 or loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may store various programs and data required for the operation of the device 800. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.
[0262] Several components in the device 800 are connected to an I / O interface 805. These components include an input unit 806 such as a keyboard, a mouse, etc., an output unit 807 such as various types of displays, speakers, etc., a storage unit 808 such as a magnetic disk, an optical disk, etc., and a communication unit 809 such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information / data with other devices via a computer network, for example the Internet, and / or various communication networks.
[0263] Each of the processes and operations described above, such as process 600, may be executed by processing unit 801. For example, in some embodiments, process 600 may be implemented as a computer software program, which may be tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, some or all of the computer program may be loaded and / or installed in device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by CPU 801, one or more operations of process 600 described above may be performed.
[0264] The present disclosure may be a method, an apparatus, a system, and / or a computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions stored thereon for carrying out aspects of the present disclosure.
[0265] A computer-readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include portable computer disks, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), static random access memories (SRAMs), portable compact disk read-only memories (CD-ROMs), digital versatile disks (DVDs), memory sticks, floppy ticks, machine-encoded devices such as punch cards or slot-in-projection structures on which instructions are stored, and any suitable combination of the above. A computer-readable storage medium as used herein is not to be construed as a momentary signal itself, such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a wave guide or other transmission medium (e.g., light pulses through a fiber optic cable), or an electrical signal transmitted through an electrical wire.
[0266] The computer readable program instructions described herein may be downloaded from a computer readable storage medium into each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer readable program instructions from the network and forwards the computer readable program instructions to be stored in a computer readable storage medium in each computing / processing device.
[0267] The computer program instructions for carrying out the operations of the present disclosure may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or target code written in any combination of one or more programming languages, including object-oriented programming languages (e.g., Smalltalk, C++, etc.), and traditional procedural programming languages (e.g., "C" or similar programming languages). The computer readable program instructions may be executed entirely on the user computer, partially on the user computer, as a separate software package, partially on the user computer and partially on a remote computer, or entirely on a remote computer or server. When a remote computer is involved, the remote computer may be connected to the user computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected via the Internet using an Internet Service Provider). In some embodiments, state information of the computer readable program instructions is used to personalize and customize electronic circuitry, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), that is capable of executing the computer readable program instructions, thereby implementing aspects of the present disclosure.
[0268] Aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present disclosure. It will be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, may be implemented by computer readable program instructions.
[0269] These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine such that, when these instructions are executed by a processing unit of the computer or other programmable data processing apparatus, an apparatus is generated that implements the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions may be stored on a computer-readable storage medium such that the instructions cause a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. The computer-readable medium on which the instructions are stored thereby includes an article of manufacture including instructions that implement each aspect of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.
[0270] The computer readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device such that a computer-implemented process occurs by performing a series of operational steps on the computer, other programmable data processing apparatus, or other device, whereby the instructions executing on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.
[0271] The flowcharts and block diagrams in the drawings show possible architectures, functions and operations of the systems, methods and computer program products according to some embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, a program segment or a part of instructions. The module, program segment or part of instructions includes one or more executable instructions for implementing the specified logic function. In some implementations, the functions illustrated in the blocks may occur in a different order than that illustrated in the drawings. For example, two consecutive blocks may actually be executed essentially in parallel or may be executed in a reverse order depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts may be realized by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.
[0272] Although each embodiment of the present disclosure has been described above, the above description is illustrative, not exhaustive, and is not limited to each disclosed embodiment. Many modifications and changes are obvious to those skilled in the art without departing from the scope and spirit of each described embodiment. The selection of terms used in this specification aims to best interpret the principles, practical applications, or technical improvements in the market of each embodiment, or to enable other skilled in the art to understand each embodiment disclosed in this specification.
Claims
1. Responding to a request to build an executable file, retrieving corresponding development code from a code base; compiling the development code into an intermediate code and determining safety of the intermediate code; responsive to the intermediate code being determined to be safe, generating an executable file based on the intermediate code; A method of code management, including:
2. providing the intermediate code to a code scanning module to determine the security of the intermediate code. The method of claim 1.
3. Compiling the development code into intermediate code includes: acquiring third party libraries related to said development code; generating the intermediate code based on the development code and the third-party library; The method of claim 1 , comprising:
4. Acquiring third-party libraries related to said development code submitting a request to obtain the third party library associated with the development code; acquiring the third-party library in response to the third-party library being determined to be safe; The method of claim 3 , comprising:
5. refusing to build the executable file in response to the intermediate code being determined to pose a risk; and causing risk portions of said corresponding development code in said code base to be marked; The method of claim 1 further comprising:
6. generating a report regarding the risk. The method according to claim 5.
7. generating a signature for the executable file; uploading said signature to a signature management system; The method of claim 1 further comprising:
8. The executable file includes an installation file for a target application, the method comprising: and transmitting the installation file to an application store via a deployment gateway. The method of claim 1.
9. The executable file includes a service program run by a target application platform, and the method further comprises: authenticating a signature of the service program; in response to the signature being authenticated, causing the service program to be deployed to the target application platform via a deployment gateway; The method of claim 1 further comprising:
10. Retrieving the corresponding development code from a code base includes: synchronizing development code with said code base via a synchronization gateway; sending the request to build an executable file to a product build system via the synchronization gateway; a code pull module obtaining the corresponding development code from the code base based on the request; The method of claim 1 , comprising:
11. Compiling the development code into intermediate code includes: a compilation module compiling the corresponding development code into the intermediate code; the compilation module sending the intermediate code to a security code scanning module; the security code scanning module determining the security of the intermediate code; The method of claim 1 , comprising:
12. a compilation module for compiling the corresponding development code into the intermediate code, the compilation module obtaining a third party library associated with the development code from a product library, the third party library being added to the product library via the third party independent gateway in response to the third party library being determined to be safe by the third party independent gateway; the compilation module generating the intermediate code based on the development code and the third-party library; The method of claim 11 , comprising:
13. an upload module, in response to the intermediate code being determined to be safe by the security code scanning module, uploading an executable file generated based on the intermediate code to a product library; a deployment gateway for obtaining the executable file from the product library and deploying the executable file; The method of claim 1 further comprising:
14. A deployment gateway obtains the executable file from the product library and deploys the executable file, the deployment gateway obtaining the executable file and a signature of the executable file from the product library; sending the signature of the executable file to a production signature management module; In response to authentication of the signature by the production signature management module, causing the executable file to be deployed via the deployment gateway. The method of claim 13, comprising:
15. an retrieval module configured to respond to a request to build an executable file and retrieve corresponding development code from a code base; a compilation module configured to compile the development code into an intermediate code and determine safety of the intermediate code; a generation module configured to generate an executable file based on the intermediate code in response to the intermediate code being determined to be safe; A code management device comprising:
16. A memory and a processor, The memory is adapted to store one or more computer instructions, which, when executed by the processor, implement the method according to any one of claims 1 to 14. electronic equipment.
17. one or more computer instructions stored thereon which, when executed by a processor, implement the method according to any one of claims 1 to 14; A computer-readable storage medium.
18. comprising one or more computer instructions which, when executed by a processor, implement the method according to any one of claims 1 to 14, Computer program products.
Citation Information
Patent Citations
Compiler
JP1997081411A
Extensive system for representing and checking the integrity of program components during the editing process
JP2007521567A
Compilling method, program and compilling processor for two or more modules
JP2009026048A
Execution code provision method and software development system
JP2021005250A
Method and apparatus for intermediate representation of applications
US20160357530A1
