A secure running method, device and equipment of an application program and a storage medium

Abstract

The application relates to a security running method, device and equipment of an application program and a storage medium. The method comprises the following steps: obtaining a current user instruction for a current application program, analyzing the current user instruction, and obtaining first metadata of the current user instruction; determining an instruction type of the current user instruction according to the first metadata; when the instruction type is a main instruction type and security verification of a first execution permission of the current user instruction is passed, obtaining a subordinate sub-instruction of the current user instruction from the first metadata; when it is determined that the subordinate sub-instruction belongs to an executable instruction and security verification of a second execution permission of the subordinate sub-instruction is passed, executing the subordinate sub-instruction, and obtaining an execution result of the current user instruction. Compared with the prior art, the application dynamically adjusts permission settings of different instructions by using a security configuration file, can quickly adapt to changing business and security requirements, and thus effectively prevents unauthorized access and operation.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer security operation, in particular to a security operation method and device of application program, equipment, storage medium and computer program product. BACKGROUND

[0002] Linux operating system is an open source operating system, which is widely used in various devices due to its stability, security and high efficiency. In the Linux operating system, the command processing system is its core part, which is responsible for receiving user input, executing corresponding operations and returning results.

[0003] In the traditional Linux environment, polymorphic binary technology is usually used to reduce the occupied space of the file system, and multiple functions are executed through an executable binary file. For example, BusyBox is a widely used polymorphic binary application, which integrates a large number of commonly used UNIX commands and tools.

[0004] However, this kind of integration method usually limits the fine-grained permission control of individual commands, each command can only be run with the same permission, and the permission setting cannot be adjusted according to different use scenarios, which has many limitations such as poor security and poor flexibility when executing commands. SUMMARY

[0005] Therefore, it is necessary to provide a security operation method and device of application program with high security and high configuration flexibility.

[0006] In a first aspect, the present application provides a security operation method of application program, the method comprising:

[0007] obtaining a current user instruction for a current application program, parsing the current user instruction, and obtaining first metadata of the current user instruction;

[0008] determining the instruction type of the current user instruction according to the first metadata;

[0009] when the instruction type is a main instruction type, performing security verification on the first execution permission of the current user instruction based on a first security configuration file to obtain a first security verification result;

[0010] when the first security verification result is verified, obtaining a subordinate sub-instruction of the current user instruction from the first metadata;

[0011] when it is determined that the subordinate sub-instruction belongs to an executable instruction, performing security verification on the second execution permission of the subordinate sub-instruction based on a second security configuration file to obtain a second security verification result;

[0012] When the second security verification result is a verification pass, the lower-level sub-instruction is executed to obtain an execution result of the current user instruction.

[0013] In one of the embodiments, the security verification on the first execution permission of the current user instruction based on the first security profile includes:

[0014] A first security profile corresponding to the current user instruction is obtained; the first security profile is configured for a first execution permission of a main instruction type of the current application program;

[0015] The first execution permission of the current user instruction is verified according to the first security profile to obtain a first security verification result.

[0016] In one of the embodiments, before the first security profile corresponding to the current user instruction is obtained, the method further includes:

[0017] A first user list of the current application program and a first execution permission of a main instruction type corresponding to each first user account in the first user list are obtained; the first execution permission includes at least one of a first execution trigger permission, a first execution time window permission, a first execution frequency permission and a first concurrent execution permission of the first user account for an instruction belonging to the main instruction type;

[0018] The first security profile corresponding to the first user account is configured based on the first execution permission of each first user account.

[0019] In one of the embodiments, the security verification on the second execution permission of the lower-level sub-instruction based on the second security profile includes:

[0020] A second security profile corresponding to the lower-level sub-instruction is obtained; the second security profile is configured for a second execution permission of a sub-instruction type of the current application program;

[0021] The second execution permission of the lower-level sub-instruction is verified according to the second security profile to obtain a second security verification result.

[0022] In one of the embodiments, before the second security profile corresponding to the lower-level sub-instruction is obtained, the method further includes:

[0023] obtaining a second username list of the current application program and a second execution permission of each second user account in the second username list corresponding to a sub-instruction type;

[0024] configuring a second security configuration file corresponding to the second user account based on the second execution permission of each second user account.

[0025] In one of the embodiments, the method further comprises at least one of the following:

[0026] when the first security verification result is a verification failure, rejecting execution of the current user instruction and recording a first exception log;

[0027] when the second security verification result is a verification failure, rejecting execution of the sub-instruction and recording a second exception log.

[0028] In one of the embodiments, the method further comprises at least one of the following:

[0029] when the instruction type is a sub-instruction type and the current user instruction belongs to the executable instruction, performing security verification on a second execution permission of the current user instruction based on the second security configuration file, obtaining a third security verification result; when the third security verification result is a verification pass, executing the current user instruction and obtaining an execution result of the current user instruction;

[0030] when the instruction type is a sub-instruction type and the current user instruction does not belong to the executable instruction, or the sub-instruction does not belong to the executable instruction, alarming the current user instruction and recording a third exception log.

[0031] In a second aspect, the application further provides a security running device of an application program, the device comprising:

[0032] an instruction analysis module, configured to obtain a current user instruction of a current application program, analyze the current user instruction, and obtain first metadata of the current user instruction;

[0033] an instruction type determination module, configured to determine an instruction type of the current user instruction according to the first metadata;

[0034] a first verification module, configured to, when the instruction type is a main instruction type, perform security verification on a first execution permission of the current user instruction based on a first security configuration file, and obtain a first security verification result;

[0035] a lower-level instruction obtaining module, configured to obtain a lower-level sub-instruction of the current user instruction from the first metadata when the first security verification result is a verification pass;

[0036] a second verification module, configured to perform security verification on a second execution permission of the lower-level sub-instruction based on a second security configuration file when it is determined that the lower-level sub-instruction belongs to an executable instruction, to obtain a second security verification result;

[0037] an instruction execution module, configured to execute the lower-level sub-instruction to obtain an execution result of the current user instruction when the second security verification result is a verification pass.

[0038] In a third aspect, the present application also provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method as described above when executing the computer program.

[0039] In a fourth aspect, the present application also provides a computer readable storage medium, which stores a computer program, and the computer program implements the steps of the method as described above when executed by a processor.

[0040] In a fifth aspect, the present application also provides a computer program product, comprising a computer program, and the computer program implements the steps of the method as described above when executed by a processor.

[0041] The application program safe running method, device, equipment, storage medium and computer program product, when the client initiates a user request for the current application program, the server parses the current user instruction from the user request, obtains the first metadata of the current user instruction by acquiring the current user instruction for the current application program, parsing the current user instruction, and determining the instruction type of the current user instruction from the first metadata, when the server determines that the instruction type of the current user instruction is the main instruction type, the first execution permission of the current user instruction is verified based on the first security configuration file, and the first security verification result is obtained, so as to ensure that the execution of the current user instruction conforms to the safe running strategy, then, when the first security verification result is verified, the server obtains the subordinate sub-instruction of the current user instruction from the first metadata, when the server determines that the subordinate sub-instruction belongs to the executable instruction, the second execution permission of the subordinate sub-instruction is verified based on the second security configuration file, and the second security verification result is obtained, so as to ensure that the execution of the subordinate sub-instruction conforms to the safe running strategy, when the second security verification result is verified, the subordinate sub-instruction is executed, the execution result of the current user instruction is obtained, the security verification of the execution permission is performed by using the corresponding security configuration file for different types and different user instructions, the more fine-grained permission control can be realized, and the permission settings of different instructions are dynamically adjusted by using the security configuration file, so that the changing business and security requirements can be quickly adapted, thereby effectively preventing unauthorized access and operation. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can also be obtained without creative labor.

[0043] Figure 1 An application environment diagram of the application program safe running method in an embodiment;

[0044] Figure 2 A flowchart of the application program safe running method in an embodiment;

[0045] Figure 3 A system block diagram of the application program safe running method in an application example;

[0046] Figure 4 A command safe execution control flowchart in an application example;

[0047] Figure 5 A general flowchart in an application example;

[0048] Figure 6 A structural block diagram of a security running device of an application in an embodiment;

[0049] Figure 7 An internal structural diagram of a computer device in an embodiment. DETAILED DESCRIPTION

[0050] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not to limit the present application.

[0051] The security running method of the application provided by the embodiment can be applied to an application environment as shown in Figure 1 The terminal 102 communicates with the server 104 through a network. The data storage system can store data required to be processed by the server 104. The data storage system can be integrated on the server 104, or placed on a cloud or other network server. The server 104 can obtain the first metadata in the current user instruction by acquiring and analyzing the current user instruction for the current application program sent by the terminal 102, determine the instruction type of the current user instruction through the first metadata, select the first security configuration file to perform security verification on the current user instruction according to the instruction type of the current user instruction, extract the subordinate sub-instruction of the current user instruction from the first metadata after the security verification is passed, and determine whether the subordinate sub-instruction is an executable instruction. If so, the second security configuration file is selected to perform security verification on the subordinate sub-instruction, and after the security verification is passed, the subordinate sub-instruction is executed, so that each instruction can only be executed under the condition of meeting the preset security policy, thereby improving the security of the current application program running.

[0052] The terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things device can be a smart speaker, a smart television, a smart air conditioner, a smart vehicle-mounted device, a projection device, etc. The portable wearable device can be a smart watch, a smart bracelet, etc. The server 104 can be a standalone physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0053] In an exemplary embodiment, as shown in Figure 2 A security running method of an application is provided, which is applied to the server 104 in Figure 1 It should be understood that the method can also be applied to Figure 1The terminal 102 in the server 104 can also be applied to a system comprising the server 104 and the terminal 102, and is realized through the interaction between the server 104 and the terminal 102. The method of the embodiment comprises the following steps:

[0054] In step S201, the current user instruction for the current application program is acquired, and the current user instruction is parsed to obtain the first metadata of the current user instruction.

[0055] The current application program refers to a software program or system that is running on the server and is used to realize the interaction between the client and the server. The client can be a device or other application program that can trigger an instruction. In an optional embodiment, the current application program further refers to an application program based on a business completion polymorphic binary.

[0056] The current user instruction refers to an instruction that is being processed by the current application program. The instruction can be a button clicked on the current application program, a command entered, or an option selected, and is used to instruct the current application program to perform a specific operation or function. The current user instruction is usually contained in a user request. The server can identify the specific operation that the user wants to perform by listening to, reading, and parsing the data in the user request, so as to extract the current user instruction.

[0057] The parsing of the current user instruction refers to the process of decomposing the current user instruction on the current application program by the server to obtain more basic elements carried in the current user instruction, such as instruction identification and parameters, so that the server can identify the specific operation that the user wants to perform.

[0058] The first metadata refers to the data associated with the current user instruction, and the first metadata includes but is not limited to the instruction identification, instruction type, priority, operation object, and operation parameter of the current user instruction, so that the server can process and understand the current user instruction.

[0059] For example, the server listens to the user request from the current application program in real time. When the user request is received, the server reads and parses various data carried in the user request to extract the current user instruction from the data. Then, the server parses the current user instruction according to a predefined format or protocol, identifies and extracts the instruction identification, instruction type, priority, operation object, and operation parameter of the current user instruction, and other first metadata related information.

[0060] The server can parse the current user instruction in a predefined format or protocol during parsing. The predefined format includes, but is not limited to, XML (eXtensible Markup Language), JSON (JavaScript Object Notation), CSV (Comma-Separated Values), and the like. The parsing protocol includes, but is not limited to, HTTP protocol (HyperText Transfer Protocol), TCP / IP protocol (Transmission Control Protocol / Internet Protocol), and the like.

[0061] In step S202, the instruction type of the current user instruction is determined according to the first metadata.

[0062] The instruction type refers to the category or classification of the current user instruction, and different instruction types correspond to different processing logic and permission requirements. In this embodiment, the instruction type mainly includes a main instruction type and a sub-instruction type. The main instruction type corresponds to a main instruction, which can be used to call a function, execute a specific task, or start or specify an operation or function. The sub-instruction type corresponds to a sub-instruction, which is appended to the main instruction to provide more detailed or specific operations. The sub-instruction can usually be used to modify the behavior or parameters of the main instruction or to execute additional tasks related to the main instruction. One main instruction can have one or more sub-instructions to refine or expand the function of the main instruction.

[0063] For example, the server determines the instruction type of the current user instruction according to at least one of the instruction identifier, the instruction type, the priority, the operation object, and the operation parameter of the current user instruction contained in the first metadata.

[0064] In step S203, when the instruction type is the main instruction type, the first execution permission of the current user instruction is verified based on the first security configuration file to obtain a first security verification result.

[0065] The main instruction type refers to an instruction type with higher priority or greater importance in the running process of the current application.

[0066] The first security profile refers to a security profile used to verify the first execution permission of the current user instruction. The first security profile defines information that different clients have permission to execute specific types of instructions and specific operations that these instructions can perform. The first execution permission refers to the permission of different clients to execute the current user instruction. The first security verification result refers to the result obtained after verifying the first execution permission of the current user instruction according to the first security profile. The first security verification result can be used to indicate whether the security verification of the current user instruction passes or not. If it passes, it means that the client has permission to execute the current user instruction. If it does not pass, it means that the client does not have permission to execute the current user instruction.

[0067] For example, when it is determined that the instruction type of the current user instruction is the main instruction type, the server performs security verification on the first execution permission of the current user instruction based on the first security profile to determine whether the client has execution permission for the current user instruction of the current application, and further obtains the first security verification result.

[0068] In addition, when performing security verification on the first execution permission, the server can also log the verification process to facilitate tracking and recording of the verification of the instruction, and facilitate analysis of the verification situation afterwards.

[0069] Step S204, when the first security verification result is verified, the lower-level sub-instruction of the current user instruction is obtained from the first metadata.

[0070] The lower-level sub-instruction refers to an instruction that is included in or related to the current user instruction, which is a lower-level or more detailed operation. The lower-level sub-instruction is carried in the first metadata as a component of the current instruction.

[0071] For example, when the first security verification result of the security verification on the first execution permission of the current user instruction is verified, the server obtains the lower-level sub-instruction of the current user instruction from the first metadata.

[0072] Step S205, when it is determined that the lower-level sub-instruction is an executable instruction, the second execution permission of the lower-level sub-instruction is verified based on the second security profile, and a second security verification result is obtained.

[0073] The executable instruction refers to an instruction that has been identified by the server as valid and executable.

[0074] The second security profile refers to a security profile used to verify the second execution permission of the subordinate sub-instruction. The second security profile is similar to the first security profile. The second security profile defines information that different clients have the right to execute characteristic type instructions, and specific operations that these instructions can execute. The second execution permission refers to the permission of different clients to execute the subordinate sub-instruction. The second security verification result refers to a result obtained by verifying the second execution permission of the subordinate sub-instruction according to the second security profile. The second security verification result can be used to indicate whether the security verification of the subordinate sub-instruction passes. If it passes, it means that the client has the permission to execute the subordinate sub-instruction. If it does not pass, it means that the client does not have the permission to execute the subordinate sub-instruction.

[0075] For example, when it is determined that the subordinate sub-instruction belongs to an executable instruction, the server performs security verification on the second execution permission of the subordinate sub-instruction based on the second security profile to determine whether the client has the execution permission for the subordinate sub-instruction of the current application, and then obtains the second security verification result.

[0076] In addition, when performing security verification on the second execution permission, the server can also log the verification process to facilitate tracking and recording of the verification of the instruction, and facilitate analysis of the verification situation afterwards.

[0077] In step S206, when the second security verification result is verified, the subordinate sub-instruction is executed to obtain the execution result of the current user instruction.

[0078] The execution of the subordinate sub-instruction refers to the process of executing the subordinate sub-instruction by the server to run the current application after the instruction passes the necessary permission verification. The execution result of the current user instruction refers to the result obtained after executing the subordinate sub-instruction, i.e., the running result of the current application.

[0079] For example, when the second security verification result of the security verification on the second execution permission of the subordinate sub-instruction is verified, the server executes the subordinate sub-instruction to obtain the execution result of the current user instruction, and then makes the current application run safely under the action of the current user instruction and its subordinate sub-instruction.

[0080] When the server executes the subordinate sub-instruction, it can include but is not limited to calling and parsing the subordinate sub-instruction from the instruction entry of the subordinate sub-instruction to obtain the second metadata of the subordinate sub-instruction, and then executing the subordinate sub-instruction based on the second metadata.

[0081] In addition, when the server executes the subordinate sub-instruction, the execution information of the subordinate sub-instruction can also be logged, including execution time, specific operations, execution result, etc., to facilitate tracking and recording of the running of the system, and facilitate analysis of the execution situation afterwards.

[0082] In the security running method of the application program, when the client initiates a user request for the current application program, the server parses the current user instruction from the user request, obtains the first metadata of the current user instruction by acquiring the current user instruction for the current application program, parsing the current user instruction, and determining the instruction type of the current user instruction from the first metadata. When the server determines that the instruction type of the current user instruction is a main instruction type, the first execution permission of the current user instruction is verified based on the first security configuration file to obtain a first security verification result, so as to ensure that the execution of the current user instruction conforms to the security running strategy. Subsequently, when the first security verification result is verified, the server obtains the subordinate sub-instruction of the current user instruction from the first metadata. When the server determines that the subordinate sub-instruction belongs to an executable instruction, the second execution permission of the subordinate sub-instruction is verified based on the second security configuration file to obtain a second security verification result, so as to ensure that the execution of the subordinate sub-instruction conforms to the security running strategy. When the second security verification result is verified, the subordinate sub-instruction is executed, and the execution result of the current user instruction is obtained. The security verification of the execution permission is performed based on the corresponding security configuration file for different types and different user instructions, so that more fine-grained permission control can be realized. In addition, the permission settings of different instructions are dynamically adjusted by using the security configuration file, so that the changing business and security requirements can be quickly adapted, thereby effectively preventing unauthorized access and operation.

[0083] In one embodiment, the first execution permission of the current user instruction is verified based on the first security configuration file to obtain a first security verification result, including:

[0084] The first security configuration file corresponding to the current user instruction is obtained. The first execution permission of the current user instruction is verified based on the first security configuration file to obtain a first security verification result.

[0085] The first security configuration file is obtained by configuring the first execution permission of the main instruction type of the current application program. Specifically, the first security configuration file is pre-generated and stored in the data storage system of the server. The first security configuration file defines various permissions of the instructions corresponding to the main instruction type when the instructions are executed in detail, and is used to determine whether the execution of the instructions corresponding to the main instruction type conforms to the preset security policy.

[0086] For example, the server obtains the first security configuration file corresponding to the current user instruction from the data storage system, and verifies the first execution permission of the current user instruction based on the first security configuration file in detail to obtain a first security verification result.

[0087] In the embodiment, the server obtains the first security configuration file corresponding to the current user instruction, verifies the first execution permission of the current user instruction according to the first security configuration file, obtains the first security verification result corresponding to the first execution permission, and performs matching verification on the current user instruction before the execution of the current user instruction, so as to ensure that the execution of all current user instructions conforms to the preset security policy, thereby achieving the purpose of improving the system operation safety.

[0088] In one embodiment, before obtaining the first security configuration file corresponding to the current user instruction, the method further comprises:

[0089] obtaining a first user list of the current application program and a first execution permission of each first user account in the first user list corresponding to a main instruction type; and configuring a first security configuration file corresponding to the first user account based on the first execution permission of each first user account.

[0090] The first user list refers to a list of user information that has been registered or authorized in the current application program. The first user list includes first user accounts of each user and a first execution permission of each user account corresponding to a main instruction type. The first user account is a unique identifier of the user, which can be a user name, a user ID, or other information capable of distinguishing different user identities. The first user list can be pre-stored in a data storage system or input from an external device at the time of configuration.

[0091] The first execution permission includes at least one of a first execution trigger permission, a first execution time window permission, a first execution frequency permission, and a first concurrent execution permission of the first user account for instructions belonging to the main instruction type.

[0092] The first execution trigger permission refers to the permission of the first user account to trigger the execution of a specific instruction. The first execution time window permission refers to the permission of the first user account to execute instructions within certain time periods. The first execution frequency permission refers to the permission of the first user account to execute instructions a certain number of times within a certain time window. The first concurrent execution permission refers to the permission of the first user account to execute a certain number of instructions simultaneously.

[0093] For example, the server obtains a first user list of the current application program and a first execution permission of each first user account in the first user list corresponding to a main instruction type from a data storage system; and configures a first security configuration file corresponding to the first user account based on at least one of the first execution trigger permission, the first execution time window permission, the first execution frequency permission, and the first concurrent execution permission of the first user account.

[0094] In the embodiment, by obtaining the first username list of the current application program and the first execution permission of the first user account in the first username list corresponding to the main instruction type, then, based on the first execution permission of the first user account, the first security configuration file corresponding to the first user account is configured, different execution trigger permissions, execution time window permissions, execution frequency permissions and concurrent execution permissions are defined for different user accounts to verify the execution of the current user instruction in detail, and the first security configuration file can be dynamically adjusted according to the permission change of the user account, can quickly respond to the business change demand, high flexibility, at the same time, by configuring the concurrent execution permission, the use efficiency of system resources can be effectively improved, and the utilization of system resources is optimized.

[0095] In one embodiment, the second execution permission of the subordinate sub-instruction is verified based on the second security configuration file to obtain a second security verification result, including:

[0096] The second security configuration file corresponding to the subordinate sub-instruction is obtained; and the second execution permission of the subordinate sub-instruction is verified according to the second security configuration file to obtain a second security verification result.

[0097] The second security configuration file is obtained by configuring the second execution permission of the sub-instruction type of the current application program. Specifically, the second security configuration file is similar to the first security configuration file, and is also pre-generated and stored in the data storage system of the server. The second security configuration file defines various permissions of the instruction corresponding to the sub-instruction type when the instruction is executed, and is used to determine whether the execution of the instruction corresponding to the sub-instruction type conforms to the preset security policy.

[0098] For example, the server obtains the second security configuration file corresponding to the subordinate sub-instruction from the data storage system; and the second execution permission of the subordinate sub-instruction is verified according to the second security configuration file to obtain a second security verification result.

[0099] In the embodiment, the server obtains the second security configuration file corresponding to the subordinate sub-instruction, and verifies the second execution permission of the subordinate sub-instruction according to the second security configuration file, so as to obtain the second security verification result corresponding to the second execution permission, so as to match and verify the subordinate sub-instruction before the execution of the subordinate sub-instruction, so as to ensure that the execution of all the subordinate sub-instructions conforms to the preset security policy, and thus the purpose of improving the system operation safety is achieved.

[0100] In one embodiment, before obtaining the second security configuration file corresponding to the subordinate sub-instruction, the method further includes:

[0101] obtain a second user list of the current application program and a second execution permission of each second user account in the second user list corresponding to a sub-instruction type; and configure a second security configuration file corresponding to each second user account based on the second execution permission of each second user account.

[0102] The second user list refers to a list of user information that has been registered or authorized in the current application program. The second user list includes second user accounts of each user and a second execution permission of each user account corresponding to a sub-instruction type. The second user account is a unique identifier of a user, which can be a user name, a user ID, or other information capable of distinguishing different user identities. The second user list is the same as or similar to the first user list. Since a sub-instruction belongs to a main instruction, the second user account in the second user list belongs to the first user account in the first user list, that is, the first user account includes all second user accounts. In addition, the second user list can also add a corresponding second execution permission to the second user account in the first user list to reduce the occupation of system storage resources. The second user list can be pre-stored in a data storage system or input from an external device during configuration.

[0103] The second execution permission includes at least one of a second execution trigger permission, a second execution time window permission, a second execution frequency permission, and a second concurrent execution permission of the second user account for an instruction belonging to a sub-instruction type. The second execution trigger permission, the second execution time window permission, the second execution frequency permission, and the second concurrent execution permission are similar to the first execution trigger permission, the first execution time window permission, the first execution frequency permission, and the first concurrent execution permission in the above embodiments except for the instruction type. For details, refer to the description of the above embodiments, which will not be repeated here.

[0104] For example, the server obtains a second user list of the current application program and a second execution permission of each second user account in the second user list corresponding to a sub-instruction type from a data storage system; and configures a second security configuration file corresponding to each second user account based on at least one of a second execution trigger permission, a second execution time window permission, a second execution frequency permission, and a second concurrent execution permission of each second user account.

[0105] In this embodiment, by obtaining the second username list of the current application program and the second execution permission of the second user account in the second username list corresponding to the sub-instruction type, then, based on the second execution permission of the second user account, the second security configuration file corresponding to the second user account is configured, and similarly, different execution trigger permissions, execution time window permissions, execution frequency permissions and concurrent execution permissions are defined for different user accounts to verify the execution of the subordinate sub-instruction in detail, and the second security configuration file can be dynamically adjusted according to the permission change of the user account, can quickly respond to the business change demand, and has high flexibility, and at the same time, by configuring the concurrent execution permission, the use efficiency of system resources can be effectively improved, and the utilization of system resources is optimized.

[0106] In one embodiment, the above-mentioned security running method of the application program further comprises at least one of the following:

[0107] When the first security verification result is not passed, the execution of the current user instruction is refused and the first exception log is recorded.

[0108] The first exception log refers to a log file used to record the event that the verification is not passed and the current user instruction is refused to execute and related information thereof when the first security verification result is not passed and the current user instruction is refused to execute, and the related information includes but is not limited to the occurrence time, the user account, the instruction content of the current user instruction, the reason for the verification failure, etc.

[0109] For example, when the first security verification result is not passed, the server refuses the execution of the current user instruction and records the first exception log.

[0110] When the second security verification result is not passed, the execution of the subordinate sub-instruction is refused and the second exception log is recorded.

[0111] The second exception log refers to a log file used to record the event that the verification is not passed and the subordinate sub-instruction is refused to execute and related information thereof when the second security verification result is not passed and the subordinate sub-instruction is refused to execute, and the related information also includes but is not limited to the occurrence time, the user account, the instruction content of the current user instruction, the reason for the verification failure, etc.

[0112] For example, when the second security verification result is not passed, the server refuses the execution of the subordinate sub-instruction and records the second exception log.

[0113] In this embodiment, by logging the verification of the current user instruction and the subordinate sub-instruction, detailed tracking information and records can be provided for the verification operation of the instruction to support compliance review and investigation of security incidents, and it is beneficial to comprehensively analyze the running situation of the current application program after the event.

[0114] In one embodiment, the method for secure running of the application further comprises at least one of the following:

[0115] When the instruction type is the sub-instruction type and the current user instruction belongs to the executable instruction, the second execution permission of the current user instruction is verified based on the second security profile to obtain a third security verification result; when the third security verification result is verified, the current user instruction is executed to obtain an execution result of the current user instruction.

[0116] The third verification result is a result obtained by verifying the second execution permission of the current user instruction based on the second security profile, and the third security verification result can be used to indicate whether the security verification of the current user instruction is passed. If it is passed, it means that the client has the permission to execute the current user instruction; if it is not passed, it means that the client does not have the permission to execute the current user instruction.

[0117] For example, when the instruction type of the obtained current user instruction is the sub-instruction type and the current user instruction belongs to the executable instruction, the server verifies the second execution permission of the current user instruction based on the second security profile to determine whether the client has the execution permission for the current application, and further obtains a third security verification result; when the third security verification result of the security verification of the second execution permission of the current user instruction is verified, the server executes the current user instruction to obtain an execution result of the current user instruction, and further makes the current application run safely under the action of the current user instruction.

[0118] When the instruction type is the sub-instruction type and the current user instruction does not belong to the executable instruction, or the lower-level sub-instruction does not belong to the executable instruction, an alarm is given for the current user instruction and a third abnormal log is recorded.

[0119] The executable instruction does not belong to the executable instruction of the current application.

[0120] The third abnormal log is that when the current user instruction or the lower-level sub-instruction of the sub-instruction type does not belong to the executable instruction of the current application, the current user instruction or the lower-level sub-instruction will not be executed and an alarm will be given for the current user instruction. The third abnormal log is used for the related information that the current user instruction or the lower-level sub-instruction will not be executed and the related information that the alarm is given for the current user instruction.

[0121] For example, when the instruction type of the current user instruction obtained by the server is a sub-instruction type and the current user instruction does not belong to an executable instruction, the current user instruction will not be executed, the server will alarm the current user instruction, and information that the current user instruction is not executed and alarm information will be recorded in the third exception log, or when the lower-level sub-instruction does not belong to an executable instruction, the lower-level sub-instruction will not be executed, the server will alarm the current user instruction corresponding to the lower-level sub-instruction, and information that the lower-level sub-instruction is not executed and alarm information will be recorded in the third exception log.

[0122] In this embodiment, by logging the running processes of the current user instruction and the lower-level sub-instruction, detailed tracking information and records can be provided for the running processes of the response instructions of the current application program, to support compliance review and investigation of security incidents, and to facilitate comprehensive post-analysis of the running status of the current application program.

[0123] In an application example, a method for secure running of an application program is provided, which is mainly applied in a multi-user operating system environment, such as a server, a cloud computing infrastructure, and a large multi-task processing system. In the foregoing environment, the system runs a plurality of application programs, each of which can be triggered by different users or service accounts. In order to improve security and reasonable allocation of system resources, the permissions, time windows, frequencies, and command concurrency of the application program need to be accurately controlled. Hereinafter, the application program is taken as a polymorphic binary application program as an example, in which:

[0124] Multicall Binary: Multicall Binary is a programming method, a binary file can simulate and execute multiple programs, and it determines which function to execute according to the name called or the parameters passed.

[0125] Permission Verification: In software and computer systems, permission verification refers to the process of checking whether a user or program has the right to perform a certain operation or access certain data.

[0126] Time Window Verification: Time window verification refers to the process of checking operation requests within a specific time range that allows certain operations to be performed.

[0127] Frequency Control: Frequency control refers to the process of limiting the number of executions of a specific operation within a given time period.

[0128] Concurrency Control: Concurrency control ensures the number of running programs at the same time.

[0129] Resource Management: Resource management refers to the process of allocating, optimizing, and monitoring resources such as CPU, memory, storage, and others in a computer system.

[0130] BusyBox: BusyBox is a software that integrates multiple UNIX (Uniplexed Information and Computering System) system tools, commonly used in embedded operating systems. It provides a set of simplified UNIX command-line tools packaged in a single executable file.

[0131] Executable binary file: A special type of binary file that contains machine code that can be directly interpreted and executed by a computer. Executable binary files are created through the compilation process, which converts source code written in high-level programming languages into instructions that can be directly understood and executed by a computer's central processing unit.

[0132] Binary application: A program that has been compiled from source code into machine language. Binary applications are packaged in binary format files and can be directly run on a computer's operating system. Binary applications directly contain instruction sets that can be directly interpreted and executed by a computer processor.

[0133] Artificial Intelligence (AI): Artificial Intelligence (AI) is a branch of computer science that aims to create machines and software systems that can perform tasks that typically require human intelligence.

[0134] Service Level Agreement (SLA): Service Level Agreement (SLA) is a formal agreement between a service provider and a customer that clearly outlines the specific expectations and standards for the service.

[0135] Based on the above, the steps of this example are as follows:

[0136] Step 1: Design an application based on a business completion polymorphic binary.

[0137] In this step, for example, a command similar to Busybox is designed syskits (example polymorphic binary name), which integrates more than 100 commonly used commands such as cp, ls, rsync, cat, etc. into a polymorphic binary named syskits, which can execute the ls command using syskits ls [options], or use ls to soft link to syskits and directly execute the ls command using ls [options]. Each tool (such as ls, cp, etc.) in this embodiment involves a separate module, and these modules constitute the command implementation body of the system. Each module is responsible for the logical processing of a specific command. For the specific design framework, please refer to Figure 3 , the main structure includes:

[0138] Command parsing module, used to parse the command submitted by the user or the system, determine the command type and parameters, and provide necessary information for subsequent permission verification and execution.

[0139] Permission verification module, used to verify whether the user or service initiating the command has sufficient permission to execute the command, to ensure system security.

[0140] Run-time window checking module, used to check whether the command is within the configured time window for execution, such as night or off-peak hours, to reduce the impact on system performance.

[0141] Command running frequency checking module, used to manage the execution frequency of commands to prevent individual command running too fast causing system overload, such as limiting the execution frequency of some important commands to ensure system stability.

[0142] Command concurrency checking module, used to control the number of same sub-commands that can be executed at the same time to avoid resource contention causing performance problems.

[0143] Command routing module, used to quickly find sub-commands.

[0144] General command line framework, used to provide parsing, metadata storage interface for main commands and sub-commands.

[0145] Error handling module, used to handle various exceptional conditions

[0146] Log recording module, used to record the execution details of all commands for auditing, monitoring and troubleshooting.

[0147] Step 2: Deploy the polymorphic binary program to the corresponding environment.

[0148] Step 3: Create a secure execution control configuration, which is a configuration file that defines the execution permissions, time window, frequency and command concurrency limit of each command in detail.

[0149] Configuration Template:

[0150] {

[0151] "User 1": [

[0152] {

[0153] "cmd": "Subcommand 1",

[0154] "time_window": "Time Window 1",

[0155] "frequency": "Frequency 1",

[0156] "max_concurrency": Concurrency 1

[0157] },

[0158] {

[0159] "cmd": "Subcommand 2",

[0160] "time_window": "Time Window 2",

[0161] "frequency": "Frequency 2",

[0162] "max_concurrency": Concurrency 2

[0163] }

[0164] ],

[0165] "User 2": [

[0166] {

[0167] "cmd": "Subcommand 3",

[0168] "time_window": "Time Window 3",

[0169] "frequency": "Frequency 3",

[0170] "max_concurrency": Concurrency 3

[0171] },

[0172] {

[0173] "cmd": "Subcommand 4",

[0174] "time_window": "Time Window 4",

[0175] "frequency": "Frequency 4",

[0176] "max_concurrency": Concurrency 4

[0177] } ]

[0179] }

[0180] Specific configuration information is explained as follows:

[0181] User: Aligns with system users. If not set, the default is no restrictions.

[0182] cmd: Business command configured for security execution control. For example, there is a command similar to Busybox, syskits, which integrates more than 100 commonly used command lines such as cp, ls, rsync, cat, etc. into a polymorphic binary syskits. It can execute the ls command using syskits ls [options], or use the ls soft link to syskits to directly execute the ls command.

[0183] time_window: Running time window.

[0184] frequency: Running frequency setting.

[0185] max_concurrency: Concurrent running setting.

[0186] Example scenario: In a data center environment, a server needs to perform multiple data backup tasks, which have strict requirements for execution time and resource usage.

[0187] Configuration example: Generate a configuration file named syskits.conf under / etc in the Linux system to limit the permissions of the sub-commands of the polymorphic binary syskits.

[0188] {

[0189] "root": [

[0190] {

[0191] "cmd": "rsync",

[0192] "time_window": "00:00-03:00",

[0193] "frequency": "1 / day",

[0194] "max_concurrency": 2

[0195] },

[0196] {

[0197] "cmd": "cp",

[0198] "time_window": "00:00-03:00",

[0199] "frequency": "1 / day",

[0200] "max_concurrency": 10

[0201] } ]

[0203] }

[0204] Step four: dynamic permission check, command security execution control flow as shown in Figure 4 .

[0205] Before each command execution, the system dynamically checks whether the current user and system time meet the permissions and conditions set in the configuration file; ensure that the command execution complies with the preset security policy.

[0206] Step five: command execution and security monitoring, the overall flow as shown in Figure 5 .

[0207] If the check passes, execute the command; otherwise, refuse to execute and record related events; so that the command is only executed under authorized conditions, improving the security and resource utilization efficiency of the system.

[0208] In addition, the present example can also be applied in cloud service provider environment, only need to adjust the command execution strategy according to the customer's demand, to adapt to different service level agreement (SLA).

[0209] For example, the integration of SLA parameters, such as maximum response time and availability requirements, into the configuration file, so that the command execution strategy can be dynamically adjusted according to the SLA of different customers.

[0210] For example, AI-based command scheduling optimization, by using AI algorithms to analyze historical execution data, optimize command scheduling and resource allocation, to improve command execution efficiency, optimize resource use, and meet higher service standards.

[0211] Thus, the present example has the following beneficial effects:

[0212] 1. Dynamic permission management

[0213] Dynamic permission management provides higher security and flexibility, dynamically specifying which user roles can execute specific commands at certain times through configuration files, adapting to changing business and security needs, thus more effectively preventing unauthorized access.

[0214] 2. Time window control

[0215] By limiting the time window for command execution (such as only allowing certain operations to be performed at night or during off-peak hours), the security and performance of the system are significantly improved, reducing potential security vulnerability exposure during critical periods and optimizing the use of system resources.

[0216] 3. Limiting the frequency and concurrency of executing commands

[0217] Limiting the concurrency of executing commands prevents excessive use of system resources and potential denial of service attacks (DoS), by limiting the frequency or number of commands executed, such as the number of executions per hour or per day, the system can handle requests more smoothly, avoiding resource exhaustion in a short period of time.

[0218] 4. Parsing and applying configuration files

[0219] Through efficient parsing and application of configuration files, fast permission updates and command control are achieved, greatly reducing the complexity and error probability of system maintenance, allowing permissions and policies to be quickly changed in response.

[0220] 5. Audit and logging

[0221] Through comprehensive audit and logging functions, detailed tracking and recording of system operations are provided, supporting compliance reviews and security incident investigations.

[0222] It should be understood that although each step in the flowchart involved in each embodiment as described above is displayed in sequence according to the direction of the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, as described above, at least some of the steps in the flowchart involved in each embodiment can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the order of execution of these steps or stages is not necessarily sequential, but can be alternately or alternately executed with at least part of other steps or steps or stages in other steps.

[0223] Based on the same inventive concept, the application further provides an application security running device for implementing the method for running the application securely.

[0224] In one exemplary embodiment, as shown in Figure 6 An application security running device is provided, comprising: an instruction analysis module 601, an instruction type determination module 602, a first verification module 603, a lower-level instruction acquisition module 604, a second verification module 605, and an instruction execution module 606. Wherein:

[0225] The instruction analysis module 601 is configured to obtain a current user instruction for a current application, analyze the current user instruction, and obtain first metadata of the current user instruction.

[0226] The instruction type determination module 602 is configured to determine an instruction type of the current user instruction according to the first metadata.

[0227] The first verification module 603 is configured to, when the instruction type is a main instruction type, perform security verification on a first execution permission of the current user instruction based on a first security configuration file, and obtain a first security verification result.

[0228] The lower-level instruction acquisition module 604 is configured to, when the first security verification result is passed, acquire a lower-level sub-instruction of the current user instruction from the first metadata.

[0229] The second verification module 605 is configured to, when it is determined that the lower-level sub-instruction belongs to an executable instruction, perform security verification on a second execution permission of the lower-level sub-instruction based on a second security configuration file, and obtain a second security verification result.

[0230] The instruction execution module 606 is configured to, when the second security verification result is passed, execute the lower-level sub-instruction, and obtain an execution result of the current user instruction.

[0231] In one optional embodiment, the first verification module 603 is further configured to acquire a first security configuration file corresponding to the current user instruction; the first security configuration file is obtained by configuring a first execution permission of the main instruction type of the current application; and the first execution permission of the current user instruction is verified according to the first security configuration file, and the first security verification result is obtained.

[0232] In an optional embodiment, the first verification module 603 is further configured to obtain a first user list of the current application program and first execution permissions of the first user accounts in the first user list corresponding to the main instruction type respectively; the first execution permissions comprise at least one of first execution trigger permissions, first execution time window permissions, first execution frequency permissions and first concurrent execution permissions of the first user accounts for instructions belonging to the main instruction type; and the first security configuration files corresponding to the first user accounts are configured based on the first execution permissions of the first user accounts respectively.

[0233] In an optional embodiment, the second verification module 605 is further configured to obtain a second security configuration file corresponding to the sub-instruction; the second security configuration file is configured based on second execution permissions of the sub-instruction type of the current application program; and the second execution permissions of the sub-instruction are verified based on the second security configuration file to obtain a second security verification result.

[0234] In an optional embodiment, the second verification module 605 is further configured to obtain a second user list of the current application program and second execution permissions of the second user accounts in the second user list corresponding to the sub-instruction type respectively; the second execution permissions comprise at least one of second execution trigger permissions, second execution time window permissions, second execution frequency permissions and second concurrent execution permissions of the second user accounts for instructions belonging to the sub-instruction type; and the second security configuration files corresponding to the second user accounts are configured based on the second execution permissions of the second user accounts respectively.

[0235] In an optional embodiment, the security running device of the application program further comprises a third verification module configured to, when the instruction type is the sub-instruction type and the current user instruction belongs to the executable instruction, perform security verification on the second execution permissions of the current user instruction based on the second security configuration file to obtain a third security verification result; and when the third security verification result is verified, execute the current user instruction to obtain an execution result of the current user instruction.

[0236] In an optional embodiment, the security running device of the application program further comprises a first log recording module configured to, when the first security verification result is not verified, refuse execution of the current user instruction and record a first abnormal log.

[0237] In an optional embodiment, the security running device of the application program further comprises a second log recording module configured to, when the second security verification result is not verified, refuse execution of the sub-instruction and record a second abnormal log.

[0238] In an alternative embodiment, the security running device of the application program further comprises a third log recording module, configured to alarm and record a third abnormal log when the instruction type is the sub-instruction type and the current user instruction does not belong to the executable instruction, or the lower-level sub-instruction does not belong to the executable instruction.

[0239] The modules in the security running device of the application program can be implemented by software, hardware or a combination thereof. The modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to the modules.

[0240] In an exemplary embodiment, a computer device is provided, which can be a server, and the internal structure diagram thereof can be as shown in Figure 7 The computer device comprises a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The database of the computer device is configured to store a first security configuration file, a second security configuration file, a first user list, a first execution permission of a first user account, a second user list, a second execution permission of a second user account, various log information, etc. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to communicate with external terminals through a network connection. The computer program is executed by the processor to implement a security running method of an application program.

[0241] Those skilled in the art can understand that Figure 7 The structure shown in the above embodiment is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can comprise more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0242] In an exemplary embodiment, a computer device is provided, which comprises a memory and a processor, and the memory stores a computer program. The processor executes the computer program to implement the security running method of the application program in the above embodiment.

[0243] In one embodiment, a computer readable storage medium is provided, and a computer program is stored on the computer readable storage medium, and the computer program is executed by a processor to implement the secure running method of the application program in the above embodiment.

[0244] In one embodiment, a computer program product is provided, and the computer program product comprises a computer program, and the computer program is executed by a processor to implement the secure running method of the application program in the above embodiment.

[0245] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of the related data need to comply with the relevant provisions.

[0246] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0247] The technical features of the above embodiments can be combined in any manner. To make the description concise, all possible combinations of the technical features in the above embodiments are not described, but as long as the combinations of the technical features do not exist, they should be considered as the scope of the present application.

[0248] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. A method for securely running an application, characterized in that, The method includes: Obtain the current user instruction for the current application, parse the current user instruction, and obtain the first metadata of the current user instruction; The instruction type of the current user instruction is determined based on the first metadata; When the instruction type is the primary instruction type, the first execution permission of the current user instruction is verified based on the first security configuration file to obtain the first security verification result. When the first security verification result is successful, the next-level sub-instruction of the current user instruction is obtained from the first metadata; When it is determined that the lower-level sub-instruction is an executable instruction, the second execution permission of the lower-level sub-instruction is verified based on the second security configuration file to obtain the second security verification result; When the second security verification result is successful, the lower-level sub-instruction is executed to obtain the execution result of the current user instruction; The method further includes: Obtain the first user list of the current application and the first execution permission of each first user account in the first user list corresponding to the main instruction type; based on the first execution permission of each first user account, configure the first security configuration file corresponding to the first user account; the first security configuration file is dynamically adjusted according to the changes in the permissions of the first user account; Obtain the second user list of the current application and the second execution permissions of each sub-instruction type of the second user account in the second user list; based on the second execution permissions of each of the second user accounts, configure the second security configuration file corresponding to the second user account; the second security configuration file is dynamically adjusted according to the changes in the permissions of the second user account.

2. The method according to claim 1, characterized in that, The security verification of the first execution permission of the current user instruction based on the first security configuration file, to obtain the first security verification result, includes: Obtain the first security configuration file corresponding to the current user instruction; the first security configuration file is obtained by configuring the first execution permission for the main instruction type of the current application; The first execution permission of the current user's instruction is verified according to the first security configuration file to obtain the first security verification result.

3. The method according to claim 1, characterized in that, The first execution permission includes at least one of the following: first execution trigger permission, first execution time window permission, first execution frequency permission, and first concurrent execution permission for the first user account to execute instructions belonging to the main instruction type.

4. The method according to claim 1, characterized in that, The security verification of the second execution permission of the lower-level sub-instruction based on the second security configuration file, to obtain the second security verification result, includes: Obtain the second security configuration file corresponding to the lower-level sub-instruction; the second security configuration file is obtained by configuring the second execution permission for the sub-instruction type of the current application; The second execution permission of the lower-level sub-instruction is verified according to the second security configuration file to obtain the second security verification result.

5. The method according to claim 1, characterized in that, The second execution permission includes at least one of the following: second execution trigger permission, second execution time window permission, second execution frequency permission, and second concurrent execution permission for the second user account regarding instructions belonging to the sub-instruction type.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes at least one of the following: When the first security verification result is that the verification fails, the execution of the current user instruction is rejected and the first exception log is recorded; When the second security verification result is that the verification fails, the execution of the lower-level sub-instruction is rejected and a second exception log is recorded.

7. The method according to any one of claims 1 to 5, wherein the method further comprises at least one of the following: When the instruction type is a sub-instruction type and the current user instruction belongs to the executable instruction, the second execution permission of the current user instruction is verified based on the second security configuration file to obtain a third security verification result; When the third security verification result is successful, the current user instruction is executed to obtain the execution result of the current user instruction; When the instruction type is a sub-instruction type and the current user instruction does not belong to the executable instruction, or the lower-level sub-instruction does not belong to the executable instruction, an alarm is triggered for the current user instruction and a third abnormal log is recorded.

8. A secure operating device for an application, characterized in that, The device includes: The instruction parsing module is used to obtain the current user instruction for the current application, parse the current user instruction, and obtain the first metadata of the current user instruction; The instruction type determination module is used to determine the instruction type of the current user instruction based on the first metadata. The first verification module is used to perform security verification on the first execution permission of the current user instruction based on the first security configuration file when the instruction type is the main instruction type, and obtain the first security verification result. The lower-level instruction acquisition module is used to acquire the lower-level sub-instruction of the current user instruction from the first metadata when the first security verification result is verification passed. The second verification module is used to perform security verification on the second execution permission of the lower-level sub-instruction based on the second security configuration file when it is determined that the lower-level sub-instruction is an executable instruction, and obtain the second security verification result. The instruction execution module is used to execute the lower-level sub-instruction when the second security verification result is a successful verification, and to obtain the execution result of the current user instruction; The first verification module is also used to obtain the first user list of the current application and the first execution permission of the first user account in the first user list corresponding to the main instruction type; based on the first execution permission of the first user account, configure the first security configuration file corresponding to the first user account; the first security configuration file is dynamically adjusted according to the permission changes of the first user account; The second verification module is also used to obtain the second user list of the current application and the second execution permissions of the sub-instruction types corresponding to each second user account in the second user list; based on the second execution permissions of each second user account, configure the second security configuration file corresponding to the second user account; the second security configuration file is dynamically adjusted according to the changes in the permissions of the second user account.

9. A computer device comprising a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images