Enterprise product verification processing method and device, equipment and storage medium

Abstract

The invention provides an enterprise product verification processing method and device, equipment and a storage medium. Relates to the technical field of resource management. The method comprises the following steps: in response to a product submission event, determining submission related information of a target product in the product submission event; the submission related information comprises a directory structure of the target product and a standard file under the directory structure. Performing analysis processing on a standard file under a directory structure in the related information of the submitted piece to obtain analysis result information; the analysis result information comprises a product file of the target product and product directory information. And according to a preset scanning type, scheduling a preset scanning program corresponding to the scanning type, performing verification scanning on the product file and the product directory information in the analysis result information, and determining and outputting a verification scanning report. According to the method, the problem of relatively low verification efficiency of enterprise products is solved.

Description

Technical Field

[0001] The present application relates to the field of resource management technology, and in particular to a method, device, equipment and storage medium for verifying and processing enterprise products. Background Art

[0002] At present, within some large financial enterprises, based on the industry-leading architectural perspective and concepts, we will scientifically divide the enterprise-level architecture in an orderly manner based on the enterprise's strategic goals, and obtain well-divided enterprise products. Enterprise products can effectively guide business and IT teams to transform enterprise strategic goals and enterprise business knowledge into enterprise IT capabilities and business operation capabilities, and integrate business operations and IT systems.

[0003] In the prior art, the product scanning process of financial IT companies is usually a silo-style independent process based on a unified assembly line or product library. In the entire development and production process, each target link such as document verification, vulnerability scanning, virus scanning and other processes are executed completely independently.

[0004] However, in the existing technology, in the entire development and production process of the product, each target link such as document verification, vulnerability scanning, virus scanning and other processes are completely independent, data isolation, based on dependency, lack of effective reuse of versions and asset levels, and requires coordination among various departments to perform a series of verification scans. It is difficult to coordinate and coordinate in a unified manner, resulting in low verification efficiency of the company's products. Summary of the invention

[0005] The present application provides a method, device, equipment and storage medium for verifying and processing enterprise products, so as to solve the problem of low verification efficiency of enterprise products.

[0006] In a first aspect, the present application provides a method for verifying and processing enterprise products, comprising:

[0007] In response to a product submission event, determining submission-related information of a target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes a directory structure of the target product and standard files under the directory structure;

[0008] Parsing the standard files under the directory structure in the submitted related information to obtain parsing result information; wherein the parsing result information includes the product file and product directory information of the target product;

[0009] According to the preset scanning type, the preset scanning program corresponding to the scanning type is scheduled to verify and scan the product files and the product directory information in the analysis result information, and determine and output a verification scanning report; wherein, the scanning report includes the scanning results of the target product in multiple scanning dimensions.

[0010] In a possible design, the parsing of the standard files under the directory structure in the submission-related information to obtain parsing result information includes:

[0011] Decompress the standard files under the directory structure in the submission-related information to obtain decompressed product files under the directory structure;

[0012] Generate parsing result information based on the decompressed product file; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product file and product directory information of the target product after decompression.

[0013] In a possible design, according to a preset scan type, scheduling a preset scan program corresponding to the scan type, performing a verification scan on the product file and the product directory information in the parsing result information, and determining and outputting a verification scan report, includes:

[0014] According to the current preset scanning type, a preset scanning program corresponding to the current scanning type is scheduled to perform verification scanning on the product file and the product directory information in the parsing result information to determine verification scanning information; wherein the verification scanning information includes information of multiple verification targets;

[0015] According to the preset other scanning types, the preset scanning program corresponding to the other scanning types is scheduled to perform verification scanning on the product file and the product directory information. If it is determined that the repeated verification target appears, the information of the repeated verification target is determined as the verification scanning information, and verification scanning is performed on other targets to obtain the verification scanning information;

[0016] Based on the verification scan information, a verification scan report is determined and output.

[0017] In a possible design, the preset scanning type includes any one or more of the following:

[0018] The analysis result information includes difference comparison, technical component scanning, document verification, vulnerability scanning and virus scanning.

[0019] In a possible design, according to the current preset scan type, scheduling a preset scan program corresponding to the current scan type, verifying and scanning the product file and the product directory information in the parsing result information, and determining the verification scan information includes:

[0020] If the current scanning type is a difference comparison type, then according to the difference comparison type, a preset scanning program corresponding to the difference comparison type is scheduled to compare the artifact files and the artifact directory information in the analysis result information with the artifact files and the artifact directory information of the previous historical version to determine the scope change list of the target artifact;

[0021] Based on the scope change list, determine the verification scan information.

[0022] In a possible design, after parsing the standard files under the directory structure in the submission-related information to obtain parsing result information, the method further includes:

[0023] The parsing result information is sent to a product file management module; wherein the parsing result information is used to be associated with the version information of the target product.

[0024] In a second aspect, the present application provides a verification processing device for enterprise products, comprising:

[0025] A determination module, configured to determine, in response to a product submission event, submission-related information of a target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes a directory structure of the target product and standard files under the directory structure;

[0026] A parsing module, configured to parse the standard files under the directory structure in the submitted information to obtain parsing result information; wherein the parsing result information includes the product file and product directory information of the target product;

[0027] A verification module is used to schedule a preset scanning program corresponding to a preset scanning type according to the preset scanning type, to perform a verification scan on the product file and the product directory information in the analysis result information, and to determine and output a verification scan report; wherein the scan report includes the scanning results of the target product in multiple scanning dimensions.

[0028] In a possible design, the parsing module includes:

[0029] A decompression unit, configured to decompress the standard files under the directory structure in the submitted information to obtain a decompressed product file under the directory structure;

[0030] A generation unit is used to generate parsing result information based on the decompressed product file; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product file of the target product after decompression and the product directory information.

[0031] In one possible design, the verification module includes:

[0032] A first verification unit is used to schedule a preset scanning program corresponding to the current preset scanning type according to the current preset scanning type, and perform a verification scan on the product file and the product directory information in the parsing result information to determine verification scanning information; wherein the verification scanning information includes information of multiple verification targets;

[0033] The second verification unit is used to schedule the preset scanning program corresponding to the other scan types according to the preset other scan types, and perform verification scanning on the product file and the product directory information. If it is determined that the repeated verification target appears, the information of the repeated verification target is determined as the verification scanning information, and the verification scanning is performed on other targets to obtain the verification scanning information;

[0034] An output unit is used to determine and output a verification scan report based on the verification scan information.

[0035] In a possible design, the preset scanning type includes any one or more of the following:

[0036] The analysis result information includes difference comparison, technical component scanning, document verification, vulnerability scanning and virus scanning.

[0037] In a possible design, the first verification unit includes:

[0038] The comparison subunit is used for, if the current scanning type is a difference comparison type, scheduling a preset scanning program corresponding to the difference comparison type according to the difference comparison type, performing a difference comparison between the artifact file and the artifact directory information in the parsing result information and the artifact file and the artifact directory information of the previous historical version, and determining a scope change list of the target artifact;

[0039] A determination subunit is used to determine the verification scan information according to the scope change list.

[0040] In one possible design, the device further includes:

[0041] The sending module is used to parse the standard files under the directory structure in the submitted information, and after obtaining the parsing result information, send the parsing result information to the product file management module; wherein the parsing result information is used to associate with the version information of the target product.

[0042] In a third aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor and a memory; the memory stores computer execution instructions; the at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the enterprise product verification and processing method described in the first aspect and various possible designs of the first aspect.

[0043] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the verification and processing method of the enterprise product described in the first aspect and various possible designs of the first aspect is implemented.

[0044] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the verification and processing method of the enterprise product as described in the first aspect and various possible designs of the first aspect.

[0045] The present application provides a method, device, equipment and storage medium for verifying and processing enterprise products. In response to a product submission event, the submission-related information of the target product in the product submission event is determined; wherein the product submission event is used to indicate verification and processing of the target product, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure. The standard files under the directory structure in the submission-related information are parsed to obtain parsing result information; wherein the parsing result information includes the product files and product directory information of the target product. According to the preset scan type, the preset scanning program corresponding to the scan type is scheduled to verify and scan the product files and product directory information in the parsing result information, and determine and output the verification scan report; wherein the scan report includes the scan results of the target product in multiple scanning dimensions. In this solution, the scanning program corresponding to each scan type can be scheduled to verify and scan the product files and product directory information in the parsing result information, and determine and output the verification scan report. Therefore, the enterprise-level product overall verification method of this application breaks the silo-style process in the original enterprise-level assembly line. In the existing process, each link is based on the principle of process independence, and each process independently completes the download, decompression, directory structure analysis, directory structure upload, and autonomous task splitting of products, which occupies a large amount of duplicate storage resources and computing resources. This application can integrate the process from the enterprise-level perspective, from the full process integration process, merge the repeated links in multiple processes, and conduct enterprise-level overall management and control of the products put into production from the perspective of product, file, component, process, document, etc., break data isolation, coordinate and dispatch scanning programs of various scanning types to verify products, realize unified registration and unified scheduling of product verification, reuse existing work results, improve the efficiency of enterprise integration process, and provide a product verification system based on multi-dimensional control and reuse, which solves the problem of low verification efficiency of enterprise products. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0047] Figure 1 A flowchart of a method for verifying and processing enterprise products provided in an embodiment of the present application;

[0048] Figure 2 A flowchart of another method for verifying and processing enterprise products provided in an embodiment of the present application;

[0049] Figure 3 A schematic diagram of the structure of a verification and processing device for enterprise products provided in an embodiment of the present application;

[0050] Figure 4A schematic diagram of the structure of another device for verifying and processing enterprise products provided in an embodiment of the present application;

[0051] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0052] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0053] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0054] It should be noted that in the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals. The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse. In addition, in the embodiments of this application, some existing solutions in the industry such as certain software, components, models, etc. may be mentioned, and they should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or must use the solution.

[0055] At present, within some large financial enterprises, based on the industry-leading architectural perspective and concepts, we will scientifically divide the enterprise-level architecture in an orderly manner based on the enterprise's strategic goals, and obtain well-divided enterprise products. Enterprise products can effectively guide business and IT teams to transform enterprise strategic goals and enterprise business knowledge into enterprise IT capabilities and business operation capabilities, and integrate business operations and IT systems.

[0056] In one example, the product scanning process of a financial IT enterprise is usually a silo-style independent process based on a unified pipeline or product library. In the entire development and production process, each target link such as document verification, vulnerability scanning, virus scanning and other processes are completely independent. However, in the prior art, in the entire development and production process of products, each target link such as document verification, vulnerability scanning, virus scanning and other processes are completely independent, data isolation, based on dependency, lack of effective reuse of versions and asset levels, and requires coordination among departments to perform a series of verification scans. It is difficult to coordinate and coordinate uniformly, resulting in low verification efficiency of enterprise products.

[0057] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0058] Figure 1 A flowchart of a verification processing method for an enterprise product provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method includes:

[0059] Step 101, in response to a product submission event, determine the submission-related information of the target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure.

[0060] For example, the execution subject of this embodiment can be an electronic device, or a terminal device, or a verification processing device or device of an enterprise product, or other devices or equipment that can execute this embodiment, and there is no limitation on this. In this embodiment, the execution subject is introduced as an electronic device.

[0061] First, the electronic device communicates with multiple subsystems, and the electronic device and multiple subsystems together constitute a general verification system. Among them, the electronic device is deployed with a product analysis platform, and the subsystems include the enterprise IT management platform, the enterprise-level product library, the enterprise-level global technical component management subsystem, and the enterprise-level product file management IT subsystem.

[0062] Specifically, the product analysis platform is a unified management tool that dissects enterprise-level products based on enterprise-level product specifications and general file compression and decompression technology. The decompression results are used for specific processes such as document verification, vulnerability scanning and product scanning; among them, specific process tools include document indexing tools, product component scanning tools, virus scanning tools, vulnerability scanning tools, etc. Enterprise IT management platform: used for the management of relevant information such as IT products and processes, the online flow of development processes, and connecting various systems to achieve information sharing and publishing. Enterprise-level product library: used to uniformly manage the production products released by the enterprise, with the product catalog and product specifications defined by the enterprise-level specifications, and uniformly manage the enterprise-level global delivery products, that is, the products include a collection of files stored according to the product catalog and product specifications, and mainly manage file collections. Enterprise-level global technical component management subsystem: used to manage the technical components used by the products, from the enterprise-level perspective, in the dimension of component technology management, to control the content of all products in terms of technical component dependencies and technical component versions. Enterprise-level product document management IT subsystem: used to extract and index versions, keywords, summaries, etc. of components and documents in submitted products, and manage the details of products at a certain level of depth. Components include non-standard components and standard components.

[0063] In this step, first, according to the enterprise-level project management regulations and application management regulations, the target product-related application information, project management information, etc., such as defining the product name and archiving the product directory, need to be initialized in the IT management platform with the product directory and product specifications defined by the enterprise-level specifications, for example. According to the product directory and product specifications defined by the enterprise-level specifications, the standard internal file directory of the target product and the structure of the standard submission under the product internal file directory structure are determined in the enterprise-level product file management IT subsystem, where the product standard internal file directory includes the global storage structure of the target product and the internal directory structure of the target product. According to the enterprise-level project process, the user opens and submits the target product to the enterprise-level product library. At this time, the enterprise-level product library will generate a product submission event, which indicates that the target product should be verified. The product analysis platform receives the product submission event and initiates the product verification process according to the product submission event. Specifically, the submission-related information of the target product in the product submission event is determined, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure.

[0064] Step 102: parse the standard files under the directory structure in the submitted information to obtain parsing result information; wherein the parsing result information includes the product files and product directory information of the target product.

[0065] Exemplarily, the standard files under the directory structure in the submitted information are decompressed to obtain the decompressed product files under the directory structure, and the decompressed product directory information is generated based on the decompressed product files. The directory structure of the target product before decompression and the standard files under the directory structure, as well as the product files and product directory information of the target product after decompression are all parsing result information.

[0066] Step 103, according to the preset scan type, schedule the preset scan program corresponding to the scan type, verify and scan the product files and product directory information in the analysis result information, determine and output the verification scan report; wherein the scan report includes the scan results of the target product in multiple scanning dimensions.

[0067] Exemplarily, the preset scanning type refers to the verification method for executing various business functions of the target product. For example, the scanning type includes difference comparison of parsing result information, technical component scanning, document verification, vulnerability scanning and virus scanning, etc., which are not limited. Each scanning type corresponds to a preset scanning program. For example, the scanning program corresponding to the document verification type is the document verification program in the enterprise IT management platform. If the document verification is performed on the target product, the electronic device directly dispatches the document verification program in the enterprise IT management platform to perform the document verification.

[0068] In this step, according to the preset scan type, the electronic device schedules the preset scan program corresponding to the scan type from any subsystem, performs verification scans on the product files and product directory information in the parsing result information according to the scheduled scan program, and determines and outputs a verification scan report. The scan report includes the scan results of the target product in multiple scan dimensions, for example, the scan report includes the scan results of the target product in technical component scanning, document verification, vulnerability scanning, and virus scanning.

[0069] In an embodiment of the present application, in response to a product submission event, submission-related information of a target product in the product submission event is determined; wherein, the product submission event is used to instruct verification processing of the target product, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure. The standard files under the directory structure in the submission-related information are parsed to obtain parsing result information; wherein, the parsing result information includes the product files and product directory information of the target product. According to a preset scan type, a preset scanning program corresponding to the scan type is scheduled to perform verification scanning on the product files and product directory information in the parsing result information, and a verification scanning report is determined and output; wherein, the scanning report includes the scanning results of the target product in multiple scanning dimensions. In this solution, the scanning program corresponding to each scan type can be scheduled to perform verification scanning on the product files and product directory information in the parsing result information, and a verification scanning report is determined and output. Therefore, the enterprise-level product overall verification method of this application breaks the silo-style process in the original enterprise-level assembly line. In the existing process, each link is based on the principle of process independence, and each process independently completes the download, decompression, directory structure analysis, directory structure upload, and autonomous task splitting of products, which occupies a large amount of duplicate storage resources and computing resources. This application can integrate the process from the enterprise-level perspective, from the full process integration process, merge the repeated links in multiple processes, and conduct enterprise-level overall management and control of the products put into production from the perspective of product, file, component, process, document, etc., break data isolation, coordinate and dispatch scanning programs of various scanning types to verify products, realize unified registration and unified scheduling of product verification, reuse existing work results, improve the efficiency of enterprise integration process, and provide a product verification system based on multi-dimensional control and reuse, which solves the problem of low verification efficiency of enterprise products.

[0070] Figure 2 A flowchart of another method for verifying and processing enterprise products provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the method includes:

[0071] Step 201, in response to a product submission event, determine the submission-related information of the target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure.

[0072] For example, this step can be referred to Figure 1 Step 101 in the above is not described in detail.

[0073] Step 202: decompress the standard files in the directory structure of the submitted information to obtain the decompressed product files in the directory structure.

[0074] Exemplarily, the information related to the submission includes the directory structure of the target product, the standard files under the directory structure, and the file type and the standard product analysis and parsing rules corresponding to the file type. Determine the format of each standard file under the directory structure in the information related to the submission, and determine the standard product parsing rules corresponding to each format. According to the standard product parsing rules, the standard files of the corresponding format under the directory structure in the information related to the submission are decompressed to obtain the decompressed product files under the directory structure. For example, the decompression process is equivalent to the dissection process, and the standard files are decompressed to obtain multiple decompressed product files of the next level.

[0075] Step 203, generate parsing result information according to the decompressed product file; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product file of the target product after decompression and the product directory information.

[0076] Exemplarily, after completing the product analysis, based on the product analysis result, the electronic device extracts the target product in the product analysis result before and after decompression and the file and directory information. Among them, the file and directory information before decompression includes the directory structure of the target product before decompression and the standard files under the directory structure, and the file and directory information after decompression includes the product file and product directory information of the target product after decompression; the files before and after decompression include product identification information such as full text abstracts, and the directory information before and after decompression includes other product identification information.

[0077] Step 204: Send the parsing result information to the product file management module; wherein the parsing result information is used to be associated with the version information of the target product.

[0078] Exemplarily, the electronic device submits the file and directory information extracted from the parsing result information to the enterprise-level product file management IT subsystem. The enterprise-level product file management IT subsystem associates the file and directory information with the version information of the target product submitted this time.

[0079] Step 205: according to the current preset first scan type, schedule the preset scan program corresponding to the current scan type, perform verification scan on the product files and product directory information in the parsing result information, and determine the verification scan information; wherein the verification scan information includes information of multiple verification targets.

[0080] In one example, the preset scanning types include any one or more of the following: difference comparison of parsing result information, technical component scanning, document verification, vulnerability scanning, and virus scanning.

[0081] In one example, if the current scan type is a difference comparison type, the preset scanning program corresponding to the difference comparison type is scheduled according to the difference comparison type, and the artifact files and artifact directory information in the parsed result information are compared with the artifact files and artifact directory information of the previous historical version to determine the scope change list of the target artifact; based on the scope change list, the verification scan information is determined.

[0082] Exemplarily, the preset scanning type refers to the verification method for executing various business functions of the target product. For example, the scanning type includes difference comparison of parsing result information, technical component scanning, document verification, vulnerability scanning and virus scanning, etc., which are not limited. Each scanning type corresponds to a preset scanning program. For example, the scanning program corresponding to the document verification type is the document verification program in the enterprise IT management platform. If the document verification is performed on the target product, the electronic device directly dispatches the document verification program in the enterprise IT management platform to perform the document verification.

[0083] For example, if the current scan type is a difference comparison type, the preset scanning program corresponding to the difference comparison type is scheduled according to the difference comparison type, and the artifact files and artifact directory information in the parsing result information are compared with the artifact files and artifact directory information of the previous historical version with the same specification and definition. The scope change list of the target artifact is determined, and the verification scan information is determined according to the scope change list. At the same time, the key information and change information of the supplementary files of non-standard specifications should also be recorded. In particular, when the target artifact belongs to the incremental deployment form, the information submitted this time may be partial information. Therefore, the artifact comparison should not perform a full differential comparison, but a partial comparison with the artifact directory structure corresponding to the historical version is performed based on the incremental part to form version differential information. It is also possible to perform a difference comparison analysis between the artifact files and artifact directory information in the parsing result information and the preset submission standard, and submit the analysis results. The preset submission standard refers to the standard content specification that the artifact should submit.

[0084] If the scanning type is a technical component scanning type, the product technical component scanning is further performed according to the product specification and the product analysis result. Specifically, the preset scanning program corresponding to the technical component scanning type is scheduled, and the preset component technical rules and characteristics of the product are used to further analyze the internal files of the target product. Among them, the preset scanning program corresponding to the scheduling technical component scanning type includes a product component scanning tool, etc., and the internal files include the decompressed product files in the product analysis result, such as parsing the WAR format deployment package and obtaining the dependent component information. Then, the dependent component information is included in the enterprise-level global technical component management subsystem, and matched with the preset global component library and component dependency library, component version library, etc., to obtain the dependent component version list of the specific file of the target product, and upload the dependent component version list to the enterprise-level global technical component management subsystem. The dependent component version list is the verification scanning information. The enterprise-level global technical component management subsystem synchronously updates the global list range, product version dependency, and corresponding system release component status based on the dependent component version list of this product.

[0085] If the current scanning type is a document verification type, the preset scanning program corresponding to the document verification type is scheduled to perform document verification on the target product in the standard format according to the product specification, wherein the preset scanning program corresponding to the document verification type includes a document indexing tool. Specifically, according to the document format, the document content is parsed, keywords are extracted, summaries are extracted, and online formatted data is formed, and the formatted data is uploaded to the enterprise-level product file management IT subsystem for verification, approval, and other operations.

[0086] If the current scan type is a vulnerability scan type and a virus scan type, a preset scan program corresponding to the vulnerability scan type and a preset scan program corresponding to the virus scan type are scheduled to perform vulnerability scan and virus scan. Specifically, a preset virus scan tool and a vulnerability scan tool are used to perform a special virus check and vulnerability check based on the aforementioned product analysis results to obtain the check scan information.

[0087] Therefore, based on the unified enterprise-level artifact library and enterprise-level component dependency management, document scope management and document version change control, horizontal scanning results can be reused, and vertical global scheduling, including artifact document verification, vulnerability scanning, virus scanning and other processes, can be performed to conduct comprehensive verification of target artifacts, facilitating centralized management of artifacts.

[0088] Step 206, according to the preset other scanning types, schedule the preset scanning program corresponding to the other scanning types, and perform verification scanning on the product files and product directory information. If it is determined that a repeated verification target appears, the information of the repeated verification target is determined as the verification scanning information, and verification scanning is performed on other targets to obtain the verification scanning information.

[0089] Exemplarily, the electronic device can schedule preset scanning programs corresponding to other preset scanning types according to other preset scanning types to verify and scan the product files and product directory information. If it is determined that there is a duplicate verification target that has been verified and obtained the verification scanning information, the duplicate verification target does not need to be verified and scanned again, and the information of the duplicate verification target is directly determined as the verification scanning information of this verification, and other targets other than the duplicate verification target are verified and scanned to obtain the verification scanning information. Therefore, data intercommunication and reuse can be achieved under the verification of multiple scanning types, so that the data in the verification scanning report remains consistent; the existing product analysis results can also be used to avoid repeated analysis of the same product, and the scheduling can also be split according to the existing results and the scanning performance of the tool.

[0090] Step 207: Determine and output a verification scanning report based on the verification scanning information; wherein the scanning report includes scanning results of the target product in multiple scanning dimensions.

[0091] Exemplarily, the electronic device may determine and output a verification scan report based on the verification scan information of each scan type, where the scan report includes scan results of the target product in multiple scan dimensions.

[0092] In an embodiment of the present application, in response to a product submission event, the submission-related information of the target product in the product submission event is determined; wherein the product submission event is used to indicate that the target product is to be verified, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure. The standard files under the directory structure in the submission-related information are decompressed to obtain the decompressed product files under the directory structure. According to the decompressed product files, parsing result information is generated; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product files and product directory information of the target product after decompression. The parsing result information is sent to the product file management module; wherein the parsing result information is used to be associated with the version information of the target product. According to the current preset first scan type, the preset scanning program corresponding to the current scan type is scheduled to perform a verification scan on the product files and product directory information in the parsing result information to determine the verification scan information; wherein the verification scan information includes information of multiple verification targets. According to the preset other scan types, the preset scanning programs corresponding to the other scan types are scheduled to perform verification scans on the product files and product directory information. If it is determined that a duplicate verification target appears, the information of the duplicate verification target is determined as the verification scan information, and verification scans are performed on other targets to obtain the verification scan information. According to the verification scan information, a verification scan report is determined and output; wherein the scan report includes the scan results of the target product in multiple scanning dimensions. Therefore, the enterprise-level product overall verification method of the present application breaks the silo-style process in the original enterprise-level assembly line. In the existing process, each link is based on the principle of process independence, and each process independently completes the downloading, decompression, directory structure parsing, directory structure uploading, autonomous task splitting and other tasks of the product, which occupies a large amount of duplicate storage resources and computing resources. This application can integrate the process from the enterprise-level perspective, merge the repeated links in multiple processes, and conduct enterprise-level overall management and control of the products put into production from the management perspectives of products, files, components, processes, and documents. It can break data isolation, coordinate and dispatch scanning programs of various scanning types to verify the products, realize unified registration and unified scheduling of product inspection, reuse existing work results, improve the efficiency of enterprise integration processes, and provide a product inspection and verification system based on multi-dimensional control and reuse, which solves the problem of low verification efficiency of enterprise products.

[0093] In one example, the embodiment of the present application provides a verification and processing system for enterprise products, the system comprising: an electronic device and multiple subsystems, wherein the electronic device is deployed with a product analysis platform, and the subsystems include an enterprise IT management platform, an enterprise-level product library, an enterprise-level global technical component management subsystem, and an enterprise-level product file management IT subsystem. The electronic device is used to schedule the scanning program in the subsystem to perform a verification scan on the target product according to each preset scan type to obtain a verification scan report.

[0094] Figure 3 A schematic diagram of a device for verifying and processing enterprise products provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the device comprises:

[0095] The determination module 31 is used to determine the submission-related information of the target product in the product submission event in response to the product submission event; wherein the product submission event is used to indicate the verification processing of the target product, and the submission-related information includes the directory structure of the target product and the standard files under the directory structure.

[0096] The parsing module 32 is used to parse the standard files under the directory structure in the submitted information to obtain parsing result information; wherein the parsing result information includes the product files and product directory information of the target product.

[0097] The verification module 33 is used to schedule the preset scanning program corresponding to the preset scanning type according to the preset scanning type, verify the product files and product directory information in the analysis result information, determine and output the verification scanning report; wherein the scanning report includes the scanning results of the target product in multiple scanning dimensions.

[0098] The device of this embodiment can execute the technical solution in the above method. Its specific implementation process and technical principles are the same and will not be repeated here.

[0099] Figure 4 A schematic diagram of the structure of another enterprise product verification processing device provided in an embodiment of the present application, Figure 3 Based on the embodiment shown, Figure 4 As shown, the parsing module 32 includes:

[0100] The decompression unit 321 is used to decompress the standard files in the directory structure of the submitted information to obtain the decompressed product files in the directory structure.

[0101] The generation unit 322 is used to generate parsing result information according to the decompressed product file; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product file and product directory information of the target product after decompression.

[0102] In one example, the verification module 33 includes:

[0103] The first verification unit 331 is used to schedule the preset scanning program corresponding to the current scan type according to the current preset scan type, verify the product files and product directory information in the analysis result information, and determine the verification scanning information; wherein the verification scanning information includes information of multiple verification targets.

[0104] The second verification unit 332 is used to schedule the preset scanning program corresponding to the other scanning types according to the preset other scanning types, and perform verification scanning on the product files and product directory information. If it is determined that a repeated verification target appears, the information of the repeated verification target is determined as the verification scanning information, and the verification scanning is performed on other targets to obtain the verification scanning information;

[0105] The output unit 333 is used to determine and output a verification scan report based on the verification scan information.

[0106] In one example, the preset scan types include any one or more of the following:

[0107] Compare differences in analysis result information, scan technical components, verify documents, scan vulnerabilities, and scan viruses.

[0108] In one example, the first verification unit 331 includes:

[0109] The comparison subunit 3311 is used to schedule the preset scanning program corresponding to the difference comparison type according to the difference comparison type if the current scanning type is a difference comparison type, and perform a difference comparison between the artifact files and artifact directory information in the parsing result information and the artifact files and artifact directory information of the previous historical version to determine the scope change list of the target artifact.

[0110] The determination subunit 3312 is used to determine the verification scan information according to the scope change list.

[0111] In one example, the device further includes:

[0112] The sending module 41 is used to parse the standard files under the directory structure in the submitted information, and after obtaining the parsing result information, send the parsing result information to the product file management module; wherein the parsing result information is used to be associated with the version information of the target product.

[0113] The device of this embodiment can execute the technical solution in the above method. Its specific implementation process and technical principles are the same and will not be repeated here.

[0114] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. Each module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The functions of each module. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0115] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 5 As shown, the electronic device may include: a transceiver 121 , a processor 122 , and a memory 123 .

[0116] The processor 122 executes the computer execution instructions stored in the memory, so that the processor 122 executes the scheme in the above embodiment. The processor 122 can be a general-purpose processor, including a central processing unit CPU, a network processor (network processor, NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0117] The memory 123 is connected to the processor 122 via a system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0118] The transceiver 121 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.

[0119] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0120] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.

[0121] An embodiment of the present application also provides a chip for running instructions, which is used to execute the technical solution of the verification and processing method of the enterprise product in the above embodiment.

[0122] An embodiment of the present application also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the verification and processing method of the enterprise product of the above embodiment.

[0123] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, it can implement the technical solution of the verification and processing method of the enterprise product in the above embodiment.

[0124] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0125] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0126] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0127] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0128] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0129] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0130] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0131] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0132] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0133] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0134] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A verification and processing method for enterprise products, characterized in that: include: In response to a product submission event, determining submission-related information of a target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes a directory structure of the target product and standard files under the directory structure; Parsing the standard files under the directory structure in the submitted related information to obtain parsing result information; wherein the parsing result information includes the product file and product directory information of the target product; According to the preset scanning type, the preset scanning program corresponding to the scanning type is scheduled to verify and scan the product files and the product directory information in the analysis result information, and determine and output a verification scanning report; wherein, the scanning report includes the scanning results of the target product in multiple scanning dimensions.

2. The method according to claim 1, characterized in that The parsing of the standard files under the directory structure in the submitted document related information to obtain parsing result information includes: Decompress the standard files under the directory structure in the submission-related information to obtain decompressed product files under the directory structure; Generate parsing result information based on the decompressed product file; wherein the parsing result information includes the directory structure of the target product before decompression and the standard files under the directory structure, as well as the product file and product directory information of the target product after decompression.

3. The method according to claim 2, characterized in that The step of scheduling a preset scanning program corresponding to the scanning type according to the preset scanning type, performing a verification scan on the product file and the product directory information in the parsing result information, and determining and outputting a verification scan report includes: According to the current preset scanning type, a preset scanning program corresponding to the current scanning type is scheduled to perform verification scanning on the product file and the product directory information in the parsing result information to determine verification scanning information; wherein the verification scanning information includes information of multiple verification targets; According to the preset other scanning types, the preset scanning program corresponding to the other scanning types is scheduled to perform verification scanning on the product file and the product directory information. If it is determined that the repeated verification target appears, the information of the repeated verification target is determined as the verification scanning information, and verification scanning is performed on other targets to obtain the verification scanning information; Based on the verification scan information, a verification scan report is determined and output.

4. The method according to claim 3, characterized in that The preset scanning type includes any one or more of the following: The analysis result information includes difference comparison, technical component scanning, document verification, vulnerability scanning and virus scanning.

5. The method according to claim 4, characterized in that The step of scheduling a preset scanning program corresponding to the current scanning type according to the current preset scanning type, verifying and scanning the product file and the product directory information in the parsing result information, and determining the verification scanning information includes: If the current scanning type is a difference comparison type, then according to the difference comparison type, a preset scanning program corresponding to the difference comparison type is scheduled to compare the artifact files and the artifact directory information in the analysis result information with the artifact files and the artifact directory information of the previous historical version to determine the scope change list of the target artifact; Based on the scope change list, determine the verification scan information.

6. The method according to any one of claims 1 to 5, characterized in that: After parsing the standard files under the directory structure in the submitted document related information to obtain parsing result information, the method further includes: The parsing result information is sent to a product file management module; wherein the parsing result information is used to be associated with the version information of the target product.

7. A verification and processing device for enterprise products, characterized in that: include: A determination module, configured to determine, in response to a product submission event, submission-related information of a target product in the product submission event; wherein the product submission event is used to instruct verification processing of the target product, and the submission-related information includes a directory structure of the target product and standard files under the directory structure; A parsing module, configured to parse the standard files under the directory structure in the submitted information to obtain parsing result information; wherein the parsing result information includes the product file and product directory information of the target product; A verification module is used to schedule a preset scanning program corresponding to a preset scanning type according to the preset scanning type, to perform a verification scan on the product file and the product directory information in the analysis result information, and to determine and output a verification scan report; wherein the scan report includes the scanning results of the target product in multiple scanning dimensions.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images