阅读说明：本技术 一种基于前端模块的安全管控方法和安全管控系统 (Safety management and control method and safety management and control system based on front-end module ) 是由 陈敏 于 2021-06-23 设计创作，主要内容包括：本发明公开了一种基于前端模块的安全管控方法和安全管控系统,安全管控方法包括：对操作行为进行监测,获得监测数据；为监测数据匹配相应的安全策略,并分配操作凭证,安全策略包括打开前端模块或操作前端模块权限的验证方法；根据安全策略,验证打开前端模块或操作前端模块的权限；通过验证后,授权打开前端模块或操作前端模块,并将验证结果发送给前端模块；接收到前端模块提交的调用请求、操作凭证和验证结果后,对操作凭证和验证结果进行校验；通过校验后,执行调用请求。对操作行为进行监测,利于分析安全等级,并匹配相应的安全策略,从而对前端模块的权限进行安全管控,提高安全性,防止前端模块被修改、替换或盗用。(The invention discloses a safety management and control method and a safety management and control system based on a front-end module, wherein the safety management and control method comprises the following steps: monitoring the operation behavior to obtain monitoring data; matching corresponding security policies for the monitoring data, and distributing operation certificates, wherein the security policies comprise verification methods for opening the front-end module or operating the front-end module; verifying the authority to open or operate the front-end module according to the security policy; after passing the verification, authorizing to open the front-end module or operate the front-end module, and sending the verification result to the front-end module; after receiving a call request, an operation certificate and a verification result submitted by a front-end module, verifying the operation certificate and the verification result; and after the verification is passed, executing the calling request. The operation behavior is monitored, the safety level analysis is facilitated, and the corresponding safety strategy is matched, so that the authority of the front-end module is safely controlled, the safety is improved, and the front-end module is prevented from being modified, replaced or stolen.)

1. A safety control method based on a front-end module is characterized by comprising the following steps:

monitoring the operation behavior of the front-end module to obtain monitoring data;

matching a corresponding security policy for the monitoring data, and distributing an operation certificate, wherein the security policy comprises a verification method for opening a front-end module or operating the front-end module;

verifying the authority to open or operate the front-end module according to the security policy;

after passing the verification, authorizing to open the front-end module or operate the front-end module, and sending a verification result to the front-end module;

after receiving a call request, an operation certificate and a verification result submitted by a front-end module, verifying the operation certificate and the verification result;

and after the verification is passed, executing the calling request.

2. The security management method according to claim 1, wherein the method of verifying the right comprises any one of the following methods or a combination thereof:

operator identity verification, verification code verification, sliding jigsaw verification, secondary authorization verification and user authorization verification.

3. The security management method of claim 2, wherein the method of matching the monitoring data with the corresponding security policy comprises:

the evaluation index of the combing monitoring data;

setting a grade and a grade threshold value for the evaluation index;

presetting a safety strategy for the grade of the evaluation index;

and matching the grade and the corresponding security policy for the monitoring data.

4. The safety management method according to claim 3, wherein the evaluation index includes any one of the following indices or a combination thereof: the service calling times of the front-end module, the service calling track of the front-end module and the number of users in contact in operation;

matching corresponding security policies for the plurality of evaluation indexes;

the highest level security policy is enforced.

5. The safety management and control method according to claim 1, further comprising an exception management and control method:

judging whether the monitoring data has abnormal data or not;

if yes, the front-end module is forbidden, and the front-end module or the operating system is forced to exit.

6. The security management method of claim 1, wherein verifying the operation document comprises verifying authenticity of the operation document or verifying running water of the operation document;

the verification and verification result comprises any one or combination of the following verification: checking whether the running water of the verification result is matched or not; verifying whether the levels of the security policies match; and verifying whether the authorized user is consistent with the current operating user.

7. The method of claim 1, further comprising a method of exiting the front end module by:

and after leaving the front-end module, destroying the verification information and the operation voucher of the front-end module.

8. The method of claim 1, further comprising limiting the operational inferiority of the front-end module by:

acquiring the use times of the operation certificate and the calling times of calling service;

judging whether a first condition is met, wherein the first condition comprises the following steps: the using times exceed a first threshold value, and the calling times exceed a second threshold value;

and if so, upgrading the security policy or forbidding the front-end module.

9. A security management system for implementing the security management method according to any one of claims 1 to 8, comprising a monitoring module, a policy control module, an authorization verification module, a regression verification module and an execution module,

the monitoring module is used for monitoring the operation behavior of the front-end module to obtain monitoring data;

the strategy control module is used for matching a corresponding security strategy for the monitoring data and distributing an operation certificate;

the authorization verification module is used for verifying the authority of opening the front-end module or operating the front-end module according to the security policy, authorizing the opening of the front-end module or operating the front-end module after the authorization is passed, and sending a verification result to the front-end module;

the regression verification module is used for verifying the operation certificate and the verification result after receiving the call request, the operation certificate and the verification result submitted by the front-end module;

and after the verification is passed, executing the calling request through an execution module.

10. The safety management and control system of claim 9, further comprising an interception module, an exception management and control module, and a destruction module, wherein if the authorization credential fails to pass the verification, the invocation request is intercepted by the interception module;

the abnormal control module is used for judging whether the monitoring data has abnormal data or not, if so, forbidding the front-end module and forcibly quitting the front-end module or the operating system;

the destruction module is used for destroying the verification information and the operation voucher of the front-end module after leaving the front-end module.

Technical Field

The invention relates to the technical field of safety, in particular to a safety management and control method and a safety management and control system based on a front-end module.

Background

The modular programming refers to a programming method in which a large program is divided into a plurality of small program modules according to functions during programming, each small program module completes a certain function, necessary relations are established among the modules, and the whole function is completed through mutual cooperation of the modules. Each module is relatively independent, the function is single, the structure is clear, and the interface is simple. Modular programs are more simplified in design and maintenance and have therefore become popular.

For example, the management property WEB system adopts modular design, one module performs one or more functions, the modules are independent from each other and are carried in a foreground WEB framework, and the module can be opened through a module code; the technology is realized by adopting a realization mode of static resources and dynamic data, the static resources are responsible for the effect display of the front end, the dynamic data are responsible for calculation and data interaction with the background server, and data support is provided for the front end module. The front end module is a module that interacts with the operator.

Different front-end modules have different functions and different required operation authorities, for example, all job numbers of a common module can be operated; the front-end module related to the user can operate only by being authorized by the user; the common front-end module is not accessed without limit, and the risk of batch crawling of data exists; however, the prior art lacks authorization verification of the module, so that the module is easy to invade.

Disclosure of Invention

Aiming at the technical problems in the prior art, the invention provides a safety management and control method and a safety management and control system based on a front-end module.

The invention discloses a safety management and control method based on a front-end module, which comprises the following steps: monitoring the operation behavior of the front-end module to obtain monitoring data; matching a corresponding security policy for the monitoring data, and distributing an operation certificate, wherein the security policy comprises a verification method for opening a front-end module or operating the front-end module; verifying the authority to open or operate the front-end module according to the security policy; after passing the verification, authorizing to open the front-end module or operate the front-end module, and sending a verification result to the front-end module; after receiving a call request, an operation certificate and a verification result submitted by a front-end module, verifying the operation certificate and the verification result; and after the verification is passed, executing the calling request.

Preferably, the method for verifying the authority includes any one or a combination of the following methods:

operator identity verification, verification code verification, sliding jigsaw verification, secondary authorization verification and user authorization verification.

Preferably, the method for matching the monitoring data with the corresponding security policy includes:

the evaluation index of the combing monitoring data;

setting a grade and a grade threshold value thereof for the evaluation index;

presetting a safety strategy for the grade of the evaluation index;

and matching the grade and the corresponding security policy for the monitoring data.

Preferably, the evaluation index includes any one of the following indexes or a combination thereof: the service calling times of the front-end module, the service calling track of the front-end module and the number of users in contact in operation;

matching corresponding security policies for the plurality of evaluation indexes;

the highest level security policy is enforced.

Preferably, the safety control method further includes an exception control method:

judging whether the monitoring data has abnormal data or not;

if yes, the front-end module is forbidden, and the front-end module or the operating system is forced to exit.

Preferably, the verifying the operation certificate comprises verifying authenticity of the operation certificate or verifying running water of the operation certificate;

the verification and verification result comprises any one or combination of the following verification: checking whether the running water of the verification result is matched or not; verifying whether the levels of the security policies match; and verifying whether the authorized user is consistent with the current operating user.

Preferably, the safety control method of the present invention further comprises a method of leaving the front-end module:

and after leaving the front-end module, destroying the verification information and the operation voucher of the front-end module.

Preferably, the safety control method of the present invention further includes a method of limiting the operational inferiority of the front-end module:

acquiring the use times of the operation certificate and the calling times of calling service;

judging whether a first condition is met, wherein the first condition comprises the following steps: the using times exceed a first threshold value, and the calling times exceed a second threshold value;

and if so, upgrading the security policy or forbidding the front-end module.

The invention also provides a safety management and control system for realizing the safety management and control method, which comprises a monitoring module, a strategy control module, an authorization verification module, a regression verification module and an execution module,

the monitoring module is used for monitoring the operation behavior of the front-end module to obtain monitoring data;

the strategy control module is used for matching a corresponding security strategy for the monitoring data and distributing an operation certificate;

the authorization verification module is used for verifying the authority of opening the front-end module or operating the front-end module according to the security policy, authorizing the opening of the front-end module or operating the front-end module after the authorization is passed, and sending a verification result to the front-end module;

the regression verification module is used for verifying the operation certificate and the verification result after receiving the call request, the operation certificate and the verification result submitted by the front-end module;

and after the verification is passed, executing the calling request through an execution module.

Preferably, the security management and control system further comprises an interception module, an exception management and control module and a destruction module, and if the authorization credential does not pass the verification, the interception module intercepts the call request;

the abnormal control module is used for judging whether the monitoring data has abnormal data or not, if so, forbidding the front-end module and forcibly quitting the front-end module or the operating system;

the destruction module is used for destroying the verification information and the operation voucher of the front-end module after leaving the front-end module.

Compared with the prior art, the invention has the beneficial effects that: the operation behavior of the operator is monitored, so that the safety level of the operator is analyzed, and the operator and the safety level are matched with corresponding safety strategies, so that the opening authority or the operation authority of the front-end module is safely controlled, and the safety of the front-end module and the data thereof is improved; the operation of the front-end module is tracked and checked by distributing the operation certificate for the operation of opening the front-end module, the safety of the operation of the front-end module is improved by carrying out regression check on the check result and the operation certificate, and the front-end module is prevented from being modified, replaced or stolen; therefore, the operation safety of the front-end module is improved, and the safety defense performance of the operation system is improved.

Drawings

FIG. 1 is a flow chart of a front-end module-based security management method of the present invention;

FIG. 2 is a logic block diagram of the policing system of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

The invention is described in further detail below with reference to the attached drawing figures:

a front-end module-based security management method, as shown in fig. 1, includes:

step 101: and monitoring the operation behavior of the front-end module to obtain monitoring data.

Step 102: and matching corresponding security policies for the monitoring data, and distributing operation certificates, wherein the security policies comprise a verification method for opening the front-end module or operating the front-end module. The operation certificate can be a unique certificate, and the operation certificate is prevented from being embezzled.

Step 103: and verifying the authority for opening the front-end module or operating the front-end module according to the security policy.

Step 104: and after passing the verification, authorizing to open the front-end module or operate the front-end module, and sending a verification result to the front-end module. And if the verification is not passed, disabling the front-end module.

Step 105: and after receiving the call request, the operation certificate and the verification result submitted by the front-end module, verifying the operation certificate and the verification result. Specifically, the front-end module sends the received verification result and the operation certificate to the back-end for verification while submitting the call request, so as to realize the function of secondary verification.

Step 106: and after the verification is passed, executing the calling request. And if the verification is not passed, rejecting the calling request.

The operation behavior of the operator is monitored, so that the safety level of the operator can be analyzed, the operator and the safety level can be matched, and a corresponding safety strategy can be matched, so that the opening authority or the operation authority of the front-end module can be safely controlled, and the safety of the front-end module and the data thereof can be improved; the operation of the front-end module is tracked and checked by distributing the operation certificate for the operation of opening the front-end module, the safety of the operation of the front-end module is improved by carrying out regression check on the check result and the operation certificate, and the front-end module is prevented from being modified, replaced or stolen; therefore, the operation safety of the front-end module is improved, and the safety defense performance of the operation system is improved.

The method for verifying the authority comprises any one or combination of the following methods: operator identity verification, verification code verification, sliding jigsaw verification, secondary authorization verification and user authorization verification.

The identity of the operator can be read from the operating system for verification, and the operator can also be subjected to secondary identity verification when the front-end module is opened. The identity of the operator typically has certain front end module operating privileges, e.g., a normal operator can only operate normal front end modules, but not high-level modules.

Verification codes (CAPTCHA, computer Automated piping test to all Computers and human aps) and sliding puzzle verification are automatic program verification ways to distinguish a user as a computer or a human, which can prevent a robot from crawling data. The size, the gap direction and the placement position of the figure lacking block verified by the sliding jigsaw puzzle are all generated randomly, the robot identification difficulty is increased, whether the robot operates or not can be judged through the moving track of the figure lacking block, and the robot crawling data is blocked.

The secondary authorization verification is an authorization verification mode that multiple persons assist in operating the same service, when an operator performs a certain service operation, the operator initiates an authorization application to an authorizer, and after the authorizer checks and authorizes, the operator performs service handling. The secondary authorization verification can be realized through an authorization code, an intelligent key and an authorization approval mode.

User authorization means that part of services need to be agreed by users in handling, for example, a package is modified in telecommunication services, and the users can authorize through a service password, an identity certificate and a random short message code; the service password authentication needs a user to provide a password certificate, the system verifies whether the provided service certificate is correct or not, if the provided service certificate is wrong, the authorization fails, and the failure times of a single user on the day cannot exceed 5 times; the identity document verification is to judge whether the document information provided by the user is consistent with the document information stored by the system when the user registers, if so, the authorization is successful, if not, the authorization is failed, and the failure times of the single user on the day cannot exceed 5 times; the random short message code verification is temporary authorization, when a service is transacted, a random code short message is issued to a common user, and the common user provides a random code for verification and authorization.

Different security levels can be preset for the security policy, and the security policy with a higher security level is matched for the operator when the monitoring data shows that the security of the operator has risks. In one specific implementation nomenclature, the security policies are shown in the following table:

however, the setting of the security policy is not limited to this, and may be adjusted according to the needs of the actual service.

In step 102, the method for matching the monitoring data with the corresponding security policy includes:

step 201: and (4) combing the evaluation index of the monitoring data. Such as, but not limited to, the number of service calls of the front-end module, the service call trajectory of the front-end module, and the number of users contacted in the operation.

Step 202: and setting grades and grade threshold values thereof for the evaluation indexes.

Step 203: and presetting a safety strategy for the grade of the evaluation index.

Step 204: and matching the grade and the corresponding security policy for the monitoring data.

The method for combing the monitoring data comprises the following steps: high frequency analysis, trajectory analysis, limit analysis, fixed settings, and time settings.

The high frequency analysis is performed by analyzing the calling service accessed by the operator, analyzing whether a controlled threshold value is exceeded within a specified time, and if the controlled threshold value is exceeded, enabling a security policy corresponding to security and the like.

Number of calls of same service within 1 minute	Security policy level
		5	LV2
10	LV3
		15	LV4
20	LV5
		30	LV6

The trajectory analysis is to analyze operation behaviors within a certain time (for example, the last 30 minutes) of the operation job number, for example, a service call flow of the front-end module is as follows:

operational front end module	Service execution order	Service track
			1090	1	S1
1090	2	S2
			1090	3	S3
1090	4	S4

And analyzing whether a missing service call exists in one operation flow of one front-end module within 30 minutes of the operation work number, and if the missing service call exists, indicating that the front-end service call has abnormal behavior, upgrading the level of the security policy.

And (4) limited quantity analysis, wherein thresholds are set through different dimensions, whether the operation of an operator exceeds the thresholds or not is dynamically analyzed, and if the operation exceeds the thresholds, the security policy level is upgraded. For example, the number of users that the operator has been exposed to a day is analyzed. The limit analysis is set as follows:

firstly, according to the analysis of the last month, the number of the work number (1) contacting users every day is less than 50, the safety strategy grade is LV1, the operation voucher is publicly verified, and no operation perception change exists at the front end; when the number of the front-end module is more than 50, the current front-end module needs to perform graphic code verification; when the number of the bits is larger than 100, the current front-end module needs to perform secondary authorization verification. I.e. different levels are matched according to the number of touch users and corresponding security policy levels are matched according to the levels.

The fixed setting, the fixed security policy level can be set for a specific front-end module, for example, the user profile change front-end module can be set to LV4, and when operating, the user must be authorized, otherwise the front-end module function operation cannot be performed.

And temporarily setting the security policy level adopted on the day when the work number or the total work number is specified, for example, temporarily setting the work number (1) on the day when the user is not allowed to use the loss report front-end module, and setting the security level to be the LV5 level.

In summary, after various analyses, the current operation may have multiple levels of security policies, and is executed at the highest level. That is, the highest-level security policy may be executed for a plurality of evaluation indexes matching the corresponding security policies.

Meanwhile, the front-end module is forbidden under the condition that abnormal data exist in the monitoring data, and the front-end module or the operating system is forced to quit. The exception data includes a high frequency call or an exception call, etc. The method for forcibly exiting the front-end module comprises the following steps: and ending the session through the session ID of the front-end module, through the operator ID and through the operated client address, and exiting the front-end module.

In step 105, the checking of the operation certificate includes checking whether the operation certificate is true or false, or checking a running water of the operation certificate. The verification of the verification result comprises any one of the following verification or their group full speed: checking whether the running water of the verification result is matched or not; verifying whether the levels of the security policies match; and verifying whether the authorized user is consistent with the current operating user.

The safety control method of the invention can also comprise a method for leaving the front-end module: and after leaving the front-end module, destroying the verification information and the operation voucher of the front-end module. And after leaving the front-end module, the residual information occupies a large amount of storage resources.

The safety control method of the invention can also comprise a method for limiting the operation time of the front-end module:

step 301: and acquiring the use times of the operation certificate and the calling times of the calling service.

Step 302: judging whether a first condition is met, wherein the first condition comprises the following steps: the number of uses exceeds a first threshold and the number of calls exceeds a second threshold.

If yes, go to step 303: upgrading a security policy or disabling the front-end module. Avoiding high frequency operation or high frequency calling service of a single front end module.

The invention also provides a safety control system for implementing the safety control method, as shown in fig. 2, comprising a monitoring module 21, a policy control module 22, an authorization verification module 23, a regression verification module 24 and an execution module 25,

the monitoring module 21 is configured to monitor an operation behavior of the front-end module to obtain monitoring data;

the policy control module 22 is configured to match a corresponding security policy for the monitoring data, and allocate an operation credential;

the authorization verification module 23 is configured to verify the authority to open the front-end module 1 or operate the front-end module 1 according to the security policy, authorize to open the front-end module 1 or operate the front-end module 1 after verification is passed, and send a verification result to the front-end module;

the regression verification module 24 is configured to verify the operation credential and the verification result after receiving the call request, the operation credential, and the verification result submitted by the front-end module 1;

after passing the verification, the call request is executed by the execution module 25.

The method of the invention can also comprise an interception module 26, an exception management and control module 27 and a destruction module 11, if the authorization voucher does not pass the verification, the interception module 26 intercepts the calling request;

the exception management and control module 27 is configured to determine whether the monitoring data has exception data, disable the front-end module and forcibly quit the front-end module or the operating system if the monitoring data has exception data;

the destruction module 11 is configured to destroy the verification information and the operation certificate of the front-end module after leaving the front-end module 1. In one embodiment, the exception management and control module 27 matches the security policy according to the monitoring data, and when LV5 is matched, the front-end module is disabled, and then exits the front-end module forcibly, unlike the authorization verification module 23, the exception management and control module 27 does not need the front-end module to submit the request. After the authorization verification module 23 passes the verification, on one hand, the information of the verification result is sent to the front-end module, on the other hand, the information is stored in the background server, and during the regression verification, the regression verification module calls the data of the background server to verify the verification result submitted by the front-end module.

The front-end module 1 faces an operator, and the rear-end exception management and control module 27, the policy control module, the authorization verification module, the regression verification module, the interception module, the execution module, and the service may be deployed on a server. The monitoring module 21 and the destruction module 11 may be deployed on the host of the front-end module 1. But is not limited thereto.

In a specific embodiment, the structure of the verification result record of the background server is as follows:

{ operation credential: { security policy level, authentication result, front-end module of operation, user information, generation time, verification record { verification service: number of times verified } } }.

The invention analyzes the monitoring data, generates or matches a security strategy, and controls the security verification of the front-end module; the policy control module can improve the self-decision-making capability and achieve the capabilities of quick self-checking, self-checking and self-control. By unifying the safety control method of the front-end modules, development authorization verification of each front-end module is avoided, and the development cost is greatly reduced under the condition of safety authorization. Safety is an important guarantee of a production environment, is a central importance of a production system, and can bring abundant benefits to enterprises only by guaranteeing safe and stable operation of the production system.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.