TWI825607B - Method of checking system modification - Google Patents

Abstract

A method of checking system modification comprises: receiving a first log-in account and a first modification content through a user interface, and transmitting the first log-in account and the first modification content, receiving a second log-in account through the user interface and transmitting the second log-in account to the server, determining whether the second log-in account matches the first log-in account, receiving a second modification content by the server through the user interface when the second log-in account matches the first log-in account, and determining whether the second modification content matches the first modification content, and storing a modification result corresponding to the second modification content when the second modification content matches the first modification content.

Description

System change checking method

The invention relates to a system change checking method.

With the rapid development of information technology, most companies will use information security defense systems to enhance the security of internal and client data. Generally speaking, establishing a complete information security system is not easy and requires a lot of manpower and time. Therefore, enterprise information security systems are usually outsourced to relevant vendors to help build them.

After the information security system is established, the system still needs to be updated regularly or irregularly to ensure that the enterprise can have a good user experience and maintain data security. However, since updates to the system are usually performed by engineers from the system manufacturer, not personnel within the enterprise. Therefore, when the system manufacturer's engineers are not familiar with the internal operations of the enterprise, they may mistakenly update functions that the enterprise is still using to other versions. In addition, if the working hours of the system manufacturer's engineers roughly overlap with the company's working hours, the engineers will most likely be unable to avoid updating the system while the system is being used. As a result, the engineers can only guess that the system has not been used. The time period used and updated during that time period.

In view of the above, the present invention provides a system change checking method that meets the above requirements.

A system change checking method according to an embodiment of the present invention includes: receiving a first login account and a first change content through a user interface, and transmitting the first login account and the first change content to a server ; Use the user interface to receive a second login account, and transmit the second login account to the server; use the server to determine whether the second login account matches the first login account; when the server determines that the second login account When the second login account matches the first login account, use the server to receive a second change content through the user interface; use the server to determine whether the second change content matches the first change content; and when using the server When the server determines that the second change content matches the first change content, the server stores a change result corresponding to the second change content.

In summary, according to the system change checking method shown in one or more embodiments of the present invention, it can be ensured that the user changes or updates the system at the appropriate time, and at the same time, it can be ensured that the system is operated by an authorized user. Make an update. Moreover, after the system configuration is illegally modified, the configuration can be restored to the state before the modification.

The above description of the present disclosure and the following description of the embodiments are used to demonstrate and explain the spirit and principles of the present invention, and to provide further explanation of the patent application scope of the present invention.

The detailed features and advantages of the present invention are described in detail below in the implementation mode. The content is sufficient to enable anyone skilled in the relevant art to understand the technical content of the present invention and implement it according to the content disclosed in this specification, the patent scope and the drawings. , anyone familiar with the relevant art can easily understand the relevant objectives and advantages of the present invention. The following examples further illustrate the aspects of the present invention in detail, but do not limit the scope of the present invention in any way.

Generally speaking, the information security system or cloud data management system used by an enterprise needs to be maintained and updated by the system manufacturer's engineers or the company's internal information personnel. The system change checking method provided by the present invention can be used in the context of maintaining and updating the system. The system change checking method shown in the present invention can be applied to a user interface and a server, and the user interface is communicatively connected to the server. The user interface can preferably be the screen of a terminal device such as a computer and an input device (for example, a keyboard, a mouse), etc. The user interface is used to receive data input by the above-mentioned engineers or information personnel, and can also be used to output data or Notify engineers or information personnel. The communication connection may be through wireless connection methods such as Bluetooth and the Internet. The server can be a server of the system manufacturer or an internal server of the company, which is used to maintain and update the management system based on the data received from the user interface.

Please refer to FIG. 1 , which is a flow chart of a system change checking method according to an embodiment of the present invention. It should be noted that the system change checking method of the present invention may include two stages, namely the reservation stage and the change stage. The reservation phase may include step S101; the change phase may include steps S103 to S111.

Please refer to step S101. Step S101 uses the user interface to receive the first login account and the first change content, and transmits the first login account and the first change content to the server. In another embodiment, the first change content may also include a reservation time period.

As mentioned before, the user interface is used to receive data input by engineers or information personnel (hereinafter referred to as users). In this embodiment, the user interface is used to receive the first login account and the first change content input by the user. The first change content is the system and modification content that the user wants to modify during the change stage (reservation period), and the first change content is the content that has been reserved in advance, such as new code and modifications related to existing code. Or related to the deletion of the existing program code, and the first login account contains the account number, password and other identity information of the user to be changed during the change stage (meaning that the user corresponding to the account password will perform the first login account during the reservation period) change of content).

Please continue to refer to steps S103 and S105. Step S103 is: receiving the second login account through the user interface and transmitting the second login account to the server; step S105 is: using the server to determine whether the second login account matches the first login account. Once logged into your account.

The user interface receives the second login account currently entered by the user and transmits the second login account to the server. The second login account includes, for example, the user's account number, password and other identity information. After receiving the second login account, the server can determine whether the second login account matches the first login account. The server may have a database that stores multiple first login accounts, and each first login account is used to represent a user. When the server determines that the second login account does not match the first login account, it rejects the request (step S106).

When the server determines that the second login account matches one of the first login accounts, it means that the user's identity has been verified, and the server can perform step S107: receive the second change content through the user interface. Specifically, the server can receive the second change content through the user interface, and the second change content is, for example, new code, modification to the existing code, or deletion of the existing code. When the server determines that the second login account has passed the verification in step S105, the server can receive the second change content from the user interface. The second change content is what the user input after entering the user interface of the system. instructions.

In other words, the user interface can receive a confirmation command input by the user and transmit the confirmation command to the server, where the confirmation command indicates that the user has completed inputting the second change content. For example, buttons such as "Confirm" and "Save" may appear on the user interface, and the confirmation command is the signal for the buttons such as "Confirm" and "Save" to be triggered. Then, after receiving the confirmation command, the server can continue to execute step S109.

The server further executes step S109: determining whether the second change content matches the first change content. For example, taking the above code as an example, the server can determine whether the code modified, added or deleted in the second change content is consistent with the code modified, added or deleted in the first change content. consistent.

When the server determines that the second change content does not comply with the first change content, the server executes step S110: outputting a warning notification to the user interface, and the server can reject the user's second change content.

When the server determines that the second change content matches the first change content, the server executes step S111 to store the change result corresponding to the second change content. The change result is the result of compiling the current executable file based on the second change content. When the second change content matches the first change content, it means that the second change content is within the authority range corresponding to the second login account. , and the change result can be used as the updated executable file of the system. The executable file is, for example, an executable file corresponding to the mail sending and receiving authority of the controlling employee, or an executable file corresponding to the system initialization process, etc. The present invention does not limit the actual content of the executable file. This ensures that every update to the system is correct, thereby preventing the system from running with an incorrectly updated executable file.

In another embodiment, the server may first compile the current executable file according to the second change content to generate a change result, and then determine whether the second change content conforms to the first change content. When the server determines in step S109 that the second change content matches the first change content, the server can execute step S111; when the server determines in step S109 that the second change content does not match the first change content, it will rollback the executable file. ) to the version before executing the second changed content to avoid the content of the executable file being accidentally changed.

Please refer to FIG. 2 , which is a flow chart of a system change checking method according to another embodiment of the present invention. The steps in Figure 2 are roughly the same as those in Figure 1 . The difference between Figure 2 and Figure 1 is that Figure 2 further includes step S102 , where step S102 is performed after step S101 in Figure 1 and before step S103 in Figure 1 . Therefore, step S102 will be mainly described below, and the similarities between FIG. 2 and FIG. 1 will not be described again. First, as mentioned above, in addition to receiving the first login account and the first change content, the user interface can also receive the reservation time period. Therefore, after receiving the first login account and the first change content through the user interface, the server can also determine whether the first change content and the reservation time period fall within an accessible range, where the accessible range may include the reservable time period. And the changeable content, the server can record the first changed content and reservation time period when it determines that the first change content and reservation time period are within the accessible range.

After the server receives the first login account, the first change content and the reservation time period in step S101, it then executes step S1021: determine whether the reservation time period falls within the reservable time period, and whether the first change content complies with the changeable content.

Specifically, the server may store one or more reservable time periods, and the reservable time periods may be unbooked time periods, or time periods that do not conflict with the enterprise's system running time. Therefore, when the server receives the reservation period, it can determine whether the reservation period falls within the available reservation period.

The database of the server preferably stores the changeable content corresponding to each user account (such as the first login account), that is, the scope of authority that each user account can make changes to the system. The changeable content may be, for example, an executable file or code corresponding to blocking emails containing specific data, or an executable file or code corresponding to adding a new contract expiration field in the cloud data management system, corresponding to The executable file or program code that integrates the product type and product number fields into one field, the executable file or program code that corresponds to the process of changing the system initialization, etc. are only examples. The present invention does not apply to the changeable content. Specific content is restricted.

In addition, the first login account may correspond to multiple changeable contents, and the server can determine whether the first changed content matches at least one of the changeable contents of the first login account. For example, assuming that the changeable content corresponding to the first login account includes code corresponding to both changing the system initialization process and deleting fields, the server can determine whether the changed code in the first change content corresponds to At least one of the two changeable contents. When the server determines that the first changed content does not comply with the changeable content, step S1022 may be performed: rejecting the first login account and the first changed content. That is, the server can output notifications such as "data inconsistency" to the user interface, and delete the first login account and the first change content. In addition, when the server determines that the reservation period does not fall within the reservable period, the server can also execute step S1022.

When the server determines that the reservation time period is within the reservable time period and the first change content conforms to the changeable content, step S1023 and step S1025 can then be performed, wherein step S1023 is: correspondingly recording the reservation time period and the first login account; step S1025 For: Open the permissions of the first login account during the reservation period.

After the reservation time period and the first change content have been verified, the server can record the reservation time period, the first change content, and the first login account accordingly. In addition, the server can open the permissions of the first login account during the reservation period, so that the user of the first login account has the authority to make changes during the reservation period. For example, assuming that the reservation period is from 10 am to 11 am on Monday, the server can record that the user corresponding to the first login account will make changes to the system from 10 am to 11 am on Monday. Accordingly, conflicts between the time when users make changes and the system running time can be avoided. For example, if the first change content corresponds to deleting a field, the server can only allow the first login account to modify the code about deleting the field during the reservation period. That is, the first login account has no modifications during the reservation period. Permissions for code regarding the system initialization process. Therefore, in the subsequent change stage, the server can determine whether the user's change is legal based on the content of the above record (that is, in the subsequent change stage, the server determines whether the second change content matches the first change content).

Please refer to FIG. 3 , which is a flow chart of a system change checking method according to another embodiment of the present invention. The steps in Figure 3 are generally the same as those in Figure 1 . The difference between Figure 3 and Figure 1 is that Figure 3 further includes step S108 , where step S108 is performed after step S107 in Figure 1 and before step S109 in Figure 1 . Therefore, step S108 will be mainly described below, and the similarities between FIG. 3 and FIG. 1 will not be described again.

After the server receives the second modified content in step S107, the server can then perform step S108: determine whether the time when the second modified content is received falls within the reservation period. That is, the server can determine whether the time when the second modified content is received is consistent with the reservation period. Taking the above reservation period as 10 am to 11 am on Monday as an example, the server executes step S108 to determine whether the time when the second change content is received falls within the range of 10 am to 11 am on Monday morning.

When the server determines that the time when the second change content is received falls within the reservation period (that is, the time when the second change content is received falls within the range of 10 a.m. to 11 a.m. on Monday), step S109 can be executed.

If the server determines in step S108 that the time when the second change content is received falls outside the scheduled time period, the server can perform step S110: sending a warning notification to the user interface. The step S110 described above is the step in Figure 1 S110. In addition, in the embodiment where the server first generates a change result based on the second change content before step S109, if the server determines in step S108 that the time when the second change content is received falls outside the reservation period, the server may also The executable file (the result of the change) is restored to the original version.

In a preferred implementation, the present invention first determines whether the time when the second change content is received falls within the reservation time period, and then determines whether the second change content conforms to the first change content. Accordingly, it is possible to avoid the situation where the user modifies the executable file during non-scheduled periods, further eliminating the need for the server to reply to the executable file separately.

In summary, according to the system change checking method shown in one or more embodiments of the present invention, it can be ensured that the user changes or updates the system at the appropriate time, and at the same time, it can be ensured that the system is operated by an authorized user. Make an update. Moreover, after the system configuration is illegally modified, the configuration can be restored to the state before the modification.

Although the present invention is disclosed in the foregoing embodiments, they are not intended to limit the present invention. All changes and modifications made without departing from the spirit and scope of the present invention shall fall within the scope of patent protection of the present invention. Regarding the protection scope defined by the present invention, please refer to the attached patent application scope.

S101, S103, S105, S106, S107, S108, S109, S110, S111: Steps S1021, S1022, S1023, S1025: steps

FIG. 1 is a flow chart of a system change checking method according to an embodiment of the present invention. FIG. 2 is a flow chart of a system change checking method according to another embodiment of the present invention. FIG. 3 is a flow chart of a system change checking method according to another embodiment of the present invention.

S101, S103, S105, S106, S107, S109, S110, S111: Steps

Claims (5)

A system change checking method includes: receiving a first login account and a first change content through a user interface, and transmitting the first login account and the first change content to a server, wherein the first change content Including a reservation period; using the server to determine whether the first changed content falls within an accessible range; when it is determined that the first changed content falls within the accessible range, using the server to record the first login account and the first change content; use the server to determine whether the reservation time period falls within the reservable time period within the accessible range; when the server determines that the reservation time period falls within the reservable time period, use the user The interface receives a second login account and transmits the second login account to the server; the server determines whether the second login account matches the first login account; when the server determines that the second login account matches the first login account When logging in to the account for the first time, the server receives a second change content through the user interface; the server determines whether the second change content conforms to the first change content; and when the server determines the second change content When the content matches the first change content, the server is used to store a change result corresponding to the second change content, and the method further includes: using the server to determine whether the time of receiving the second change content falls within the Appointment period; When the server determines that the time when the second change content is received falls within the scheduled time period, the second change content is executed on an executable file to generate the change result; and when the server determines that the second change content is not When the first change content is met, the server is used to restore the executable file. The system change checking method as described in claim 1, wherein when the server determines that the second change content does not comply with the first change content, the method further includes: outputting a warning notification to the user interface. The system change checking method as described in claim 1, wherein the accessible range includes a changeable content, and determining whether the first changed content falls within the accessible range includes: using the server to determine the first changed content Whether it complies with the changeable content. The system change checking method described in claim 3, wherein after recording the first login account and the first change content with the server, the method further includes: opening the permissions of the first login account in the reservation period. The system change checking method as described in claim 1, wherein the first change content includes one of a new code, a modification associated with an existing code, and a deletion associated with the existing code. By.