A change compliance control method, system, device and storage medium

Abstract

This article provides a change compliance control method, system, device and storage medium, wherein the change compliance control method includes: obtaining pending change plans; performing compliance processing on the pending change plans to determine compliant pending change plans; and grayscale production of the pending change plans in network devices related to the pending change plans. This article can implement pre-compliance checks and in-process defense, can control change risks to the maximum extent, and reduce production incidents and safety compliance issues caused by changes.

Description

Technical Field

[0001] This article relates to the field of change monitoring, and in particular to a change compliance management method, system, device and storage medium. Background Art

[0002] As the iteration speed of financial technology products increases, the transformation of IT architecture continues to deepen, and the density of financial technology changes increases exponentially. Experience shows that 70% of production accidents are caused by changes in some deployments. In the existing technology, there is no solution for monitoring deployment changes. Emergency response can only be made after production events occur due to changes. There are problems such as poor timeliness of change monitoring and easy production events.

[0003] Based on this, the impact on change compliance management and rapid response to production incidents caused by changes have become issues that the industry urgently needs to explore and solve. Summary of the invention

[0004] This article aims to solve the problem that there is no effective supervision on changes in the existing technology. Emergency treatment can only be taken after an accident occurs during the change. There are problems such as poor timeliness of change monitoring and easy to cause production incidents.

[0005] In order to solve the above technical problems, the first aspect of this document provides a change compliance management method, including:

[0006] Get pending change plans;

[0007] Carry out compliance processing on the pending change plans and determine the compliant change plans to be put into production;

[0008] In the network equipment related to the change plan to be put into production, the change plan to be put into production is put into production in grayscale.

[0009] As a further embodiment of this invention, the pending change plan is subjected to compliance processing, and determining the compliant pending change plan includes:

[0010] Determine whether the pending change plan contains confidential information, and if so, decrypt the pending change plan;

[0011] Check whether the content and format of the pending change plan meet the requirements. If the content and format of the pending change plan do not meet the requirements, process the content and format of the pending change plan until they meet the requirements.

[0012] The change plan obtained after the above two steps will be a compliant change plan to be put into production.

[0013] As a further embodiment of this invention, determining whether the change plan contains confidential information includes:

[0014] The change plan to be processed is matched with each confidential information in the preset confidential information set. If the change plan to be processed contains the confidential information in the preset confidential information set, it is determined that the change plan to be processed contains confidential information.

[0015] As a further embodiment of this invention, the change compliance control method further includes:

[0016] Conduct risk analysis on network equipment and determine risk levels;

[0017] Determining the risk level of the change plan to be put into production according to the risk level of the network equipment;

[0018] For network equipment with risk levels greater than the preset value and change plans to be put into production, prompt information will be issued.

[0019] Before the network device performs grayscale production of the change plan to be put into production, the method further includes:

[0020] Send the change plan to be put into production to the auditors of the relevant departments for review, and record the review information of the auditors of each department;

[0021] Determine whether the audit information of the auditors of each department is approved. If the audit information of the auditors of all departments is approved, send the change plan to be put into production to the approval personnel of the relevant departments for approval, and record the approval information of the approval personnel of each department;

[0022] After all departments' reviewers have approved it, the change plan to be put into production will be put into production in a grayscale manner.

[0023] As a further embodiment of the present invention, in a network device related to the change plan to be put into production, grayscale production of the change plan to be put into production includes:

[0024] Isolate the network equipment related to one of the change plans to be put into production;

[0025] Sending the change plan to be put into production to the isolated network equipment;

[0026] Check whether the isolated network device is abnormal. If an abnormality occurs, call the emergency command / rollback command in the change plan to be put into production. If there is no abnormality, start the isolated network device for external service and continue to isolate the next network device related to the change plan to be put into production.

[0027] As a further embodiment of this invention, issuing the change plan to be put into production to the isolated network device includes:

[0028] Divide the change plan to be put into production into steps to obtain multiple sub-scenarios;

[0029] Sending the sub-scenario to the isolated network devices one by one;

[0030] After each sub-scenario is successfully sent, it is automatically detected whether the isolated network device is abnormal. If there is no abnormality, the next sub-scenario is sent to the isolated network device.

[0031] A second aspect of the present invention provides a change compliance management system, including:

[0032] The acquisition module is used to obtain the pending change plan;

[0033] A detection module, used to perform compliance detection on the pending change plan and determine a compliant change plan to be put into production;

[0034] The production module is used to perform grayscale production of the change plan to be put into production in the network equipment related to the change plan to be put into production.

[0035] The third aspect of this document provides a computer device, including a memory, a processor, and a computer program stored on the memory, and when the computer program is run by the processor, it executes instructions of the change compliance management method described in any of the aforementioned embodiments.

[0036] A fourth aspect of the present invention provides a computer storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor of a computer device, the computer program executes instructions of the change compliance management method described in any of the aforementioned embodiments.

[0037] The change compliance control method, system, device and storage medium provided in this article can implement pre-compliance inspection by performing compliance detection on the change plans to be processed and determining the compliant change plans to be put into production, that is, screening out the compliant change plans to be processed before the change plans are put into production, thereby reducing the probability of non-compliance of the change plans. By gray-scale production of the change plans to be put into production in the network devices related to the change plans to be put into production, it is possible to achieve in-process defense, that is, avoid large-scale production accidents caused by abnormal change plans during production. This article can control the risk of changes to the maximum extent and reduce production incidents and safety compliance issues caused by changes.

[0038] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 A first flow chart of the method for changing compliance control in the embodiment of this document is shown;

[0041] Figure 2 A first flow chart of the compliance detection process of the embodiment of this document is shown;

[0042] Figure 3 A second flow chart of the compliance detection process of the embodiment of this document is shown;

[0043] Figure 4 A second flow chart of the method for changing compliance control in the embodiment of this document is shown;

[0044] Figure 5 A flow chart showing the grayscale production process of the embodiment of this article is shown;

[0045] Figure 6 A flow chart of detecting a change plan to be put into production according to an embodiment of this invention is shown;

[0046] Figure 7 The structure diagram of the compliance control system of the embodiment of this article is shown;

[0047] Figure 8 A structural diagram showing a change in the compliance control architecture of a specific embodiment of this document is shown;

[0048] Fig. 9 A structural diagram of a computer device according to an embodiment of this invention is shown.

[0049] Description of the accompanying symbols:

[0050] 710. Acquisition module;

[0051] 720, detection module;

[0052] 730, production module;

[0053] 902. Computer equipment;

[0054] 904, processor;

[0055] 906. Memory;

[0056] 908, driving mechanism;

[0057] 910, input / output module;

[0058] 912. Input device;

[0059] 914. Output device;

[0060] 916. Presentation equipment;

[0061] 918. Graphical user interface;

[0062] 920, network interface;

[0063] 922, communication link;

[0064] 924. Communication bus. DETAILED DESCRIPTION

[0065] The following will be combined with the drawings in the embodiments of this article to clearly and completely describe the technical solutions in the embodiments of this article. Obviously, the described embodiments are only part of the embodiments of this article, not all of the embodiments. Based on the embodiments of this article, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this article.

[0066] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0067] This specification provides method operation steps as described in the embodiments or flow charts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel.

[0068] It should be noted that the change compliance management method and system in this article can be used in the financial field, such as changes in the configuration of network equipment in a bank data center or changes in financial products, and can also be used in any field other than the financial field. The application field of the change compliance management method and system in this article is not limited.

[0069] The "ex-ante" mentioned in this article refers to before the change plan is put into production, the "in-progress" mentioned in this article refers to during the change plan being put into production, and the "ex-post" mentioned in this article refers to after the change plan is put into production.

[0070] In one embodiment of the present invention, a change compliance management method is provided to solve the problem that there is no effective supervision on changes in the prior art, and emergency measures are only taken after an accident occurs during the change. There are problems such as poor timeliness of change monitoring and easy occurrence of production incidents. The change compliance management method provided in this article is applied to the control center to realize the control of change plans for network equipment.

[0071] Specifically, Figure 1 As shown, the change compliance control methods include:

[0072] Step 110, obtaining a change plan to be processed;

[0073] Step 120, performing compliance processing on the pending change plan to determine a compliant change plan to be put into production;

[0074] Step 130: grayscale production of the change plan to be put into production in the network devices related to the change plan to be put into production.

[0075] In detail, the pending change plan refers to the change plan for the existing product or configuration design, and the change plan records the modification information of the existing product / configuration, such as adjusting the interest rate of the loan product, opening a firewall, modifying the network device configuration (such as modifying the switch port configuration), modifying the routing protocol, adding ACL (Access Control Lists) strategy, etc. The change plan is a collection of multiple commands, and the specific content included is set by the developer according to the needs of the demand personnel, and this article does not limit this. The pending change plan can be stored in a database, and when step 110 is executed, the pending change plan is obtained from the database.

[0076] The content of compliance testing includes but is not limited to confidentiality inspection, compliance inspection, etc. The specific content of compliance testing can be determined based on actual needs.

[0077] Network devices include servers, servers, and devices connected to servers, such as switches, routers, load balancers, firewalls, etc. Network devices can be deployed in different areas, such as different equipment parks.

[0078] Grayscale production refers to the production of network devices related to the change plan to be put into production one by one. The network devices related to the change plan to be put into production refer to the devices with the same functions as the change plan to be put into production, that is, the change plan to be put into production will be issued to these devices with the same functions.

[0079] In specific implementation, in order to improve the change efficiency, the change compliance management method described in this article can be implemented by multiple threads in parallel, that is, multiple threads execute the above steps 110 to 130 in parallel, and each thread is responsible for processing a pending change plan.

[0080] This embodiment can implement compliance checks on pending change plans and determine compliant pending change plans by implementing compliance checks, that is, screening out compliant pending change plans before the change plans are put into production, thereby reducing the probability of non-compliance of the change plans. By gray-scale production of the pending change plans in network devices related to the pending change plans, in-process defense can be implemented, that is, large-scale production accidents caused by abnormal change plans can be avoided during production. This article can control the risk of changes to the maximum extent and reduce production incidents and safety compliance issues caused by changes.

[0081] In one embodiment of this invention, Figure 2 As shown, the above step 120 performs compliance processing on the pending change plan to determine a compliant pending change plan, including:

[0082] Step 210, determining whether the pending change plan contains confidential information, and if so, decrypting the pending change plan;

[0083] Step 220, detecting whether the content and format of the pending change plan meet the regulations. If the content and format of the pending change plan do not meet the regulations, processing the content and format of the pending change plan until they meet the regulations.

[0084] Step 230, the change plan obtained after the above two steps is used as a compliant change plan to be put into production.

[0085] Specifically, the confidential information in step 210 includes but is not limited to plain text passwords and sensitive information. Step 210 determines whether the change plan contains confidential information, including:

[0086] The change plan is matched with each confidential information in the preset confidential information set. If the change plan contains the confidential information in the preset confidential information set, it is determined that the change plan contains confidential information.

[0087] The preset confidential information set includes various confidential information or rules for identifying confidential information. For plain text passwords, the preset confidential information set includes possible passwords for various network devices. For sensitive information, the preset confidential information set records the identification rules for sensitive information. This article does not limit the specific content included in the preset confidential information set.

[0088] When decryption processing is performed in step 210, the program can be used to implement encryption processing of all or part of the confidential information, and the confidential information can also be sent to the operation and maintenance personnel (for example, the confidential information is prompted in the monitoring page so that the operation and maintenance personnel can find the confidential information), and the operation and maintenance personnel manually perform decryption processing. Decryption processing, for example, encrypts the confidential information, and the encryption algorithms that can be used include but are not limited to DES (Data Encryption Standard), RSA (asymmetric encryption algorithm), SHA (Secure Hash Algorithm, information digest algorithm), AES (Advanced Encryption Standard, Rijndael encryption method), ECC (Elliptic Curves Cryptography, public key encryption method), etc. Through the implementation of step 210, risks can be controlled before the change plan is implemented to avoid the risk of confidential information leakage.

[0089] In step 220, for content detection, for example, whether the variable content in the change plan complies with the fixed requirements, such as whether the auditor has the audit qualification, etc. For format detection, for example, whether there are preset variables in the change plan, such as auditors, etc. During implementation, automated tools can be used to detect whether the content and format of the change plan to be processed comply with the regulations. The automated tools can be written according to the regulations. The regulations vary according to the application field, and the specific content corresponding to them is different. This article does not limit this. Through the implementation of step 220, the audit risk after the change plan is put into production can be reduced.

[0090] When implementing this embodiment, the execution steps of step 210 and step 220 are not limited. Step 210 may be executed first and then step 220, or step 220 may be executed first and then step 210.

[0091] In step 230 , the change plan obtained after the above two steps refers to the change plan that complies with step 210 and step 220 .

[0092] Usually, if a device has a problem, it will affect the access connectivity of a region. However, different regions have different importance, and different network devices are located in different locations, so the impact is also different. For example, the impact of network devices involved in key business is greater than that of office business within the bank. For another example, if a network device connected to a server has a problem, it will only affect the use of one server, but if a network device at a key node has a problem, it may affect the servers of the entire region. In order to understand the impact of the change before the change plan is put into production (i.e. in advance), such as Figure 3 As shown, the change compliance control method also includes:

[0093] Step 310, performing risk analysis on the network equipment to determine the risk level;

[0094] Step 320, determining the risk level of the change plan to be put into production according to the risk level of the network device;

[0095] Step 330: For network devices and change plans to be put into production whose risk levels are greater than a predetermined value, a prompt message is issued.

[0096] In step 310, the process of performing risk analysis on network equipment includes: analyzing the risk level of the network equipment according to the area where the network equipment is located and the importance of regional applications. The area where the network equipment is located can be determined based on the layout of the network equipment, and can also be determined based on the positioning device in the network equipment. The importance of the application of the area where the network equipment is located is determined by the business carried by the network equipment and its connection with other network equipment (such as a server). In one embodiment, the higher the risk level, the higher the degree of risk. This article does not limit the specific division of risk levels. During implementation, it can be divided according to actual conditions.

[0097] In step 320, the risk situation of the network device will directly determine the risk situation of the change plan issued in the network device. During the specific implementation, the risk level of the network device can be assigned to the risk level of the change plan to be put into production to be issued by the network device. For example, the risk level of network device A1 is X1, and the change plan to be put into production B1 is an operation on network device A1, then the risk level of the change plan to be put into production B1 is X1.

[0098] When step 330 is implemented, the change plans to be put into production whose risk levels are greater than a predetermined value can be marked to facilitate focusing on the change plans during compliance processing and when the change plans are put into production. For example, the review and approval of the change plans before they are put into production can be strengthened, and the frequency of abnormal detection during and after the change plans are put into production can be increased.

[0099] In one embodiment of this invention, in order to further ensure the compliance, security and effectiveness of the change in process control, Figure 4 As shown, before the network device performs grayscale production of the change plan to be put into production in step 130, it also includes:

[0100] Step 1201, sending the change plan to be put into production to the reviewers of the relevant departments for review, and recording the review information of the reviewers of each department;

[0101] Step 1202, determining whether the audit information of the audit personnel of each department is approved. If the audit information of the audit personnel of all departments is approved, executing step 1203;

[0102] Step 1203, sending the change plan to be put into production to the approval personnel of the relevant departments for approval, recording the approval information of the approval personnel of each department, and executing step 130 after the approval personnel of all departments have approved it.

[0103] In step 1201, the audit is mainly to proofread the content of the change plan (such as compliance). The change plan to be put into production will be sent to various departments in the change process for review. During the specific review, at least two reviewers can be set for each review link to ensure the accuracy of the change plan. The review information of the reviewers of each part includes at least: reviewer identification (including name, ID, etc.), review time, and review result (normal, abnormal). The reviewers of the relevant departments of the change plan to be put into production can be pre-determined according to needs, and this article does not limit this.

[0104] In step 1202, if there is audit information that the audit fails, then return to modify the production plan, and after the modification, return to re-execute the audit process.

[0105] Step 1203 can ensure the traceability and reversibility of the change plan in the process. Approval is mainly to determine the review status of the change plan and the execution time of the change plan. The approval information of the approvers of each department includes at least: the approval personnel identification (including name, ID, etc.), approval time, and approval results, where the approval results include whether the implementation is allowed, change implementation opinions, etc. The approvers related to each change plan to be put into production can be pre-determined according to needs, and this article does not limit this.

[0106] When this embodiment is implemented, the review and approval can be performed at the same time. This embodiment can link the change compliance control method with the change process control, and perform compliance control on each link in the change flow process to ensure that the change is compliant, reasonable, safe and effective.

[0107] In one embodiment of this invention, Figure 5 As shown, the above step 130 performs grayscale production of the change plan to be put into production in the network equipment related to the change plan to be put into production, including:

[0108] Step 510, isolating the network devices related to one of the change solutions to be put into production;

[0109] Step 520, issuing the change plan to be put into production to the isolated network device;

[0110] Step 530, detect whether the isolated network device is abnormal. If an abnormality occurs, call the emergency command / rollback command in the change plan to be put into production. If there is no abnormality, it means that the production is successful, then start the isolated network device for external service, and continue to isolate the next network device related to the change plan to be put into production.

[0111] In step 510, network devices related to the change plan to be put into production can be randomly selected for isolation. For example, the network devices related to a change plan to be put into production include five network devices, that is, the change plan to be put into production needs to change these five network devices, and one of the five network devices can be selected for isolation. During implementation, network devices can also be selected from the network devices related to the change plan to be put into production for isolation according to a predetermined rule.

[0112] During the specific implementation, in order to ensure the safety of the change while improving the efficiency of the change, the network devices related to the change plan to be put into production can be grouped. For example, network devices with the same functions in the same geographical range (same park) can be divided into a group, and each group of network devices can be isolated and the change plan to be put into production can be issued.

[0113] In step 520, the corresponding tool is called to send the commands in the change plan to be put into production to the isolated network devices one by one.

[0114] Step 530 is executed after the change plan to be put into production has been completely issued to the isolated network devices, and detects whether the network equipment is abnormal, that is, detects whether the change plan to be put into production causes generation problems. During specific implementation, the detection command provided in the change plan can be used to detect whether the change plan to be put into production causes production problems.

[0115] The change plan described in this article pre-deploys an emergency command / rollback command. When a production problem occurs, the emergency command / rollback command in the change plan to be put into production will be called, and the execution command interface will be called to execute the emergency command / rollback command.

[0116] The above steps 510 to 530 are repeated in a loop until all network devices related to the scheme to be changed have completed the change of the change scheme.

[0117] This embodiment controls the risk in one fault domain, one node in one cluster, ensures the continuity of external services, can implement in-process defense, improve the accuracy of abnormal detection of change plans, quickly locate the abnormal location, and ensure the continuity of the server's external services.

[0118] In the implementation of this article, in order to accurately determine which link of the change plan change process has an abnormality on the isolated network device, such as Figure 6 As shown, the above step 130 performs grayscale production of the change plan to be put into production on the network device, including:

[0119] Step 610, isolating one of the network devices related to the change plan to be put into production;

[0120] Step 620, dividing the change plan to be put into production into steps to obtain multiple sub-scenarios;

[0121] Step 630, sending a sub-scenario to the isolated network device;

[0122] Step 640: After each sub-scenario is successfully issued, it is automatically detected whether the isolated network device is abnormal (for example, whether it has an impact on the line network). If there is an abnormality, the emergency command / rollback command in the change plan to be put into production is called. If there is no abnormality, it is determined whether there is an unexecuted sub-scenario. If so, it returns to step 630. If not, it executes step 650.

[0123] Step 650, determine whether all network devices related to the change plan to be put into production have completed the modification of the change plan. If the judgment result is no, return to execute step 610. If the judgment result is yes, the change of the change plan to be put into production is completed.

[0124] Specifically, in step 620, sub-scenarios can be divided according to different functions. For example, if the change plan to be put into production includes five functions (opening ports, adding routes, adding ACL protocols, etc.), the change plan to be put into production can be divided into five sub-scenarios. Sub-scenarios can also be divided according to commands, for example, each command is divided into a sub-scenario. The specific division form of sub-scenario is not limited in this article. Each sub-scenario is followed by an emergency command / rollback command.

[0125] In the above step 640, a detection command may be added after each sub-scenario command to check whether the network device is abnormal. The detection command may be determined according to the sub-scenario execution function, which is not limited in this document.

[0126] When making a plan change to the unchanged server group, this embodiment adopts a segmented implementation method to divide the change steps into sub-scenarios, which can refine each sub-scenario into risk points, narrow the scope of risk, and perform rollback in time when a sub-scenario is executed abnormally, so as to avoid discovering the abnormality after the change plan is executed, thereby reducing the risk of change.

[0127] In one embodiment of the present invention, a correspondence between the change plan and the application, underlying infrastructure, and technical nodes may be established in advance. When a problem is found after the change, the underlying infrastructure and technical nodes may be searched and queried based on the correspondence, thereby locating which commands on which devices may have caused the problem.

[0128] Furthermore, the change plan also includes emergency steps and rollback steps. If some unexpected production problems occur during the application of network equipment, the emergency steps and rollback steps in the change plan are read to perform emergency and rollback operations.

[0129] The underlying infrastructure described herein includes but is not limited to servers and network devices connected to the servers. In specific implementation, a corresponding relationship can be established according to the services carried by the area where the network devices are located.

[0130] This embodiment can improve emergency response efficiency after the event and minimize the business impact time caused by the change.

[0131] The change compliance control method provided in this article can achieve the following technical effects: perform compliance control in all aspects of change management, effectively reduce change risks, reduce production incidents and security audit risks caused by changes, implement high-availability management of changes, and promote change work to develop in a safe, compliant, and efficient direction, ensuring the continuity and reliability of services provided by the business to the outside world.

[0132] Based on the same inventive concept, this article also provides a change compliance control system, as described in the following embodiments. Since the principle of solving the problem by the change compliance control system is similar to that of the change compliance control method, the implementation of the change compliance control system can refer to the change compliance control method, and the repeated parts will not be repeated.

[0133] Specifically, Figure 7 As shown, the change compliance control system includes:

[0134] An acquisition module 710 is used to acquire a change plan to be processed;

[0135] A detection module 720 is used to perform compliance processing on the pending change plan and determine a compliant pending change plan;

[0136] The production module 730 is used to perform grayscale production of the change plan to be put into production in the network equipment related to the change plan to be put into production.

[0137] This embodiment can implement compliance checks on pending change plans and determine compliant pending change plans by implementing compliance checks, that is, screening out compliant pending change plans before the change plans are put into production, thereby reducing the probability of non-compliance of the change plans. By gray-scale production of the pending change plans in network devices related to the pending change plans, in-process defense can be implemented, that is, large-scale production accidents caused by abnormal change plans can be avoided during production. This article can control the risk of changes to the maximum extent and reduce production incidents and safety compliance issues caused by changes.

[0138] In order to more clearly illustrate the technical solution of this article, a specific example is given below for detailed description. Specifically, Figure 8 As shown in the figure, the change compliance control framework consists of three parts: pre-control, in-process control and post-control. The following is a detailed description of these three parts:

[0139] (1) Pre-process control: Conduct confidentiality checks, plan compliance checks, risk assessments, and review and approval process control on the change plans to be processed.

[0140] Among them, the confidentiality check includes: matching the change plan to be processed with each confidential information in the preset confidential information set. If the change plan to be processed contains confidential information in the preset confidential information set, it is determined that the change plan to be processed contains confidential information, and the change plan to be processed is declassified.

[0141] The plan compliance check includes: checking whether the content and format of the pending change plan comply with the regulations. If the content and format of the pending change plan do not comply with the regulations, the content and format of the pending change plan will be processed until they comply with the regulations.

[0142] After the confidentiality inspection and plan compliance check, the change plan to be put into production will be obtained.

[0143] Risk assessment includes: conducting risk analysis on network equipment to determine risk levels; determining the risk level of the change plan to be put into production based on the risk level of the network equipment; and issuing prompt information for network equipment and change plans to be put into production whose risk level is greater than a predetermined value.

[0144] The review and approval process control includes: sending the change plan to be put into production to the reviewers of the relevant departments for review, and recording the review information of the reviewers of each department; judging whether the review information of the reviewers of each department is approved. If the review information of the reviewers of all departments is approved, sending the change plan to be put into production to the approval personnel of the relevant departments for approval, and recording the approval information of the approval personnel of each department; after the approval information of all departments is approved, the change plan to be put into production is grayed out.

[0145] (2) In-process control: grayscale production, phased implementation, and breakpoint rollback are carried out for the production plan.

[0146] Among them, grayscale production includes: isolating one of the network devices related to the change plan to be put into production; issuing the change plan to be put into production to the isolated network device; detecting whether the isolated network device is abnormal, if an abnormality occurs, calling the emergency command / rollback command in the change plan to be put into production, if there is no abnormality, indicating that the production is successful, then starting the isolated network device for external services, and continuing to isolate the next network device related to the change plan to be put into production.

[0147] The staged implementation includes: isolating one of the network devices related to the change plan to be put into production; issuing the change plan to be put into production to the isolated network device; detecting whether the network device is abnormal. If an abnormality occurs, calling the emergency command / rollback command in the change plan to be put into production; if there is no abnormality, indicating that the production is successful, the isolated network device is started for external service, and the next network device related to the change plan to be put into production is continuously isolated.

[0148] Breakpoint rollback includes: inserting an emergency command / rollback command after each command or each sub-scenario command of the change plan to be put into production.

[0149] (3) Post-event control, plan visualization, one-click emergency response, and one-click rollback.

[0150] Solution visualization: The monitoring page shows the implementation process of the change solution in the network equipment. Specifically, the correspondence between the change and the application, underlying infrastructure, and technical nodes is established according to the business carried by the area where the network equipment is located. When a problem occurs in the change solution, the network configuration is searched for according to the time and application of the problem, and then the commands on which devices may have caused the problem are located.

[0151] One-click emergency response and one-click rollback: Use software to implement one-click emergency response and one-click rollback for changes, improve emergency response efficiency, and minimize the business impact time caused by changes.

[0152] Emergency response refers to the need for emergency response if some unexpected production problems occur during the change process. Specifically, the tool automatically reads the emergency steps and rollback steps in the plan, calls the execution command interface, and sends these commands to the device for emergency response and rollback.

[0153] In one embodiment of the present invention, a computer device is also provided for implementing the method described in any of the above embodiments, such as Fig. 9 As shown, the computer device 902 may include one or more processors 904, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 902 may also include any memory 906, which is used to store any kind of information such as code, settings, data, etc. Non-limitingly, for example, the memory 906 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 902. In one case, when the processor 904 executes an associated instruction stored in any memory or a combination of memories, the computer device 902 may perform any operation of the associated instruction. The computer device 902 also includes one or more drive mechanisms 908 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0154] The computer device 902 may also include an input / output module 910 (I / O) for receiving various inputs (via input devices 912) and for providing various outputs (via output devices 914). A specific output mechanism may include a presentation device 916 and an associated graphical user interface 918 (GUI). In other embodiments, the input / output module 910 (I / O), the input device 912, and the output device 914 may not be included, and the computer device 902 may be used as a computer device in a network. The computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the components described above together.

[0155] The communication link 922 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0156] Corresponds to Figure 1-Figure 6 The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0157] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 1 to 6 The method shown.

[0158] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0159] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0160] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.

[0161] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0162] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, 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 units, or can be electrical, mechanical or other forms of connection.

[0163] The units described as separate components may or may not be physically separated, and the components shown as units 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 units may be selected according to actual needs to achieve the purpose of the embodiments of this article.

[0164] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0165] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0166] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.

Claims

1. A change compliance control method, characterized in that: include: Get pending change plans; Carry out compliance processing on the pending change plans and determine the compliant change plans to be put into production; In the network device related to the change plan to be put into production, grayscale production of the change plan to be put into production includes: Isolate the network equipment related to one of the change plans to be put into production; The change plan to be put into production is issued to the isolated network device, comprising: dividing the change plan to be put into production into steps to obtain multiple sub-scenarios; issuing the sub-scenarios to the isolated network device one by one; after each sub-scenario is successfully issued, automatically detecting whether the isolated network device is abnormal, if an abnormality occurs, calling the emergency command / rollback command in the change plan to be put into production, if no abnormality occurs, determining whether there are any unexecuted sub-scenarios, if so, continuing to issue the next sub-scenario to the isolated network device, if not, starting the isolated network device for external services, and continuing to isolate the next network device related to the change plan to be put into production, wherein the sub-scenarios are divided according to different functions.

2. The change compliance control method according to claim 1, characterized in that: The pending change plans are processed for compliance, and the compliant change plans to be put into production are determined to include: Determine whether the pending change plan contains confidential information, and if so, decrypt the pending change plan; Check whether the content and format of the pending change plan meet the requirements. If the content and format of the pending change plan do not meet the requirements, process the content and format of the pending change plan until they meet the requirements. The change plan obtained after the above two steps will be a compliant change plan to be put into production.

3. The change compliance control method according to claim 2, characterized in that: Determine whether the pending change plan contains confidential information, including: The change plan to be processed is matched with each confidential information in the preset confidential information set. If the change plan to be processed contains the confidential information in the preset confidential information set, it is determined that the change plan to be processed contains confidential information.

4. The change compliance control method according to claim 1, characterized in that: Also includes: Conduct risk analysis on network equipment and determine risk levels; Determining the risk level of the change plan to be put into production according to the risk level of the network equipment; For network equipment with risk levels greater than the preset value and change plans to be put into production, prompt information will be issued.

5. The change compliance control method according to claim 1, characterized in that: In the network device related to the change plan to be put into production, before the change plan to be put into production is put into production in a phased manner, the method further includes: Send the change plan to be put into production to the auditors of the relevant departments for review, and record the review information of the auditors of each department; Determine whether the audit information of the auditors of each department is approved. If the audit information of the auditors of all departments is approved, send the change plan to be put into production to the approval personnel of the relevant departments for approval, and record the approval information of the approval personnel of each department; After approval by all departments, the change plan to be put into production will be put into production in a grayscale manner.

6. A change compliance management system, characterized in that: include: The acquisition module is used to obtain the pending change plan; A detection module, used for carrying out compliance processing on the pending change plan and determining a compliant change plan to be put into production; The production module is used to perform grayscale production of the change plan to be put into production in the network equipment related to the change plan to be put into production, including: Isolate the network equipment related to one of the change plans to be put into production; The change plan to be put into production is issued to the isolated network device, comprising: dividing the change plan to be put into production into steps to obtain multiple sub-scenarios; issuing the sub-scenarios to the isolated network device one by one; after each sub-scenario is successfully issued, automatically detecting whether the isolated network device is abnormal, if an abnormality occurs, calling the emergency command / rollback command in the change plan to be put into production, if no abnormality occurs, determining whether there are any unexecuted sub-scenarios, if so, continuing to issue the next sub-scenario to the isolated network device, if not, starting the isolated network device for external services, and continuing to isolate the next network device related to the change plan to be put into production, wherein the sub-scenarios are divided according to different functions.

7. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 5.

8. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the method according to any one of claims 1 to 5.

Images