Information interaction method and system for security management platform

Abstract

The present invention is applicable to the field of information interaction technology, and in particular relates to an information interaction method and system for a security management platform, the method comprising: defining user attributes, configuring an approval process between users, constructing blocks corresponding to the users, arranging the blocks according to the approval process, inserting sequence pointers between adjacent blocks, and embedding a multi-level verification mechanism into the sequence pointers to generate a block chain; wherein the multi-level verification mechanism is: the current sequence pointer can be activated for verification only after the previous sequence pointer has completed verification. The present invention can fully utilize monitoring resources, reduce unnecessary resource consumption, and improve operational efficiency by splitting the access range into sensitive areas and secure areas. In addition, it can better respond to the needs of different security levels, ensuring that the overall access range is maintained smooth and stable while protecting the security of sensitive information.

Description

Technical Field

[0001] The present invention relates to the field of information interaction technology, and in particular to an information interaction method and system for a security management platform. Background Art

[0002] Information interaction on a safety management platform refers to the transmission and sharing of data and information between various units within the platform. This usually includes the exchange of data such as risk assessment, hidden danger investigation, emergency plans, and accident reports. The units here are generally different departments and different positions. This interaction enables each department to obtain the latest safety information in a timely manner for analysis and decision-making, ensuring the smooth transmission of information between different levels and positions.

[0003] In the above process, in order to protect the security of management data, different operating permissions will be configured for each user to ensure that sensitive data can only be viewed or modified by authorized personnel; therefore, "how to build a multi-level verification mechanism" is the technical problem that the present invention needs to solve. Summary of the Invention

[0004] The purpose of the present invention is to provide an information interaction method and system for a security management platform to solve the problem of "how to build a multi-level verification mechanism" raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] An information interaction method for a security management platform, the method comprising:

[0007] S100: Define user attributes, configure an approval process between users, construct blocks corresponding to the users, arrange the blocks according to the approval process, insert sequence pointers between adjacent blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a block chain;

[0008] The multi-level verification mechanism is as follows: the current sequence pointing can be activated for verification only after the previous sequence pointing has completed verification;

[0009] S200: Dividing the access range of each block, and when the user completes the verification of the sequence pointing, summarizing the access ranges of all blocks before the sequence pointing to obtain a target range, so as to provide the user with access rights to the target range;

[0010] S300: Splitting the access range into a sensitive area and a safe area;

[0011] When a user accesses data in a sensitive area, the user's terminal is located, the external device connected to the terminal is found, and the user's action instructions in the sensitive area are collected. When the action instructions are the same as the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain;

[0012] When a user accesses data in the security zone, verification is performed based on the sequential pointing, and the access permission is granted if the verification passes.

[0013] Furthermore, the S100 includes:

[0014] Based on the attributes, the user's role is determined, and the approval process is mapped to the role, a process chain is generated, and the digital chain is corrected;

[0015] The action instructions and monitoring reports are synchronized into several blocks.

[0016] Furthermore, the S100 further includes:

[0017] Using the roles, generating labels, and integrating the labels into blocks;

[0018] Insert a jump pointer into the block chain and switch the multi-level verification mechanism.

[0019] Furthermore, the S100 further includes:

[0020] Creating a storage node, establishing a corresponding relationship between the storage node and the data block, and transferring the data in the sensitive area to the storage node;

[0021] Build data channels between several blocks and the storage nodes.

[0022] Furthermore, the S200 includes:

[0023] Configuring the correspondence between the roles, blocks, and access scopes, and synchronizing the correspondence to the block chain;

[0024] A coordination framework is constructed, and the access scope is integrated into the coordination framework to generate a target scope.

[0025] Furthermore, the S300 includes:

[0026] Record the number of times the user reads the access range and add a timestamp;

[0027] The access frequency of each block is counted, and based on the access frequency, the block is divided into a plurality of sub-blocks.

[0028] Furthermore, the method further comprises:

[0029] Define special events to trigger the launch of pre-built emergency response plans;

[0030] Obtain the release permission for the special event, and determine an activation method for the release permission.

[0031] Furthermore, the system includes:

[0032] A generation module is used to define user attributes, configure the approval process between users, construct blocks corresponding to the users, arrange the blocks according to the approval process, insert sequence pointers between adjacent blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a block chain;

[0033] The multi-level verification mechanism is as follows: the current sequence pointing can be activated for verification only after the previous sequence pointing has completed verification;

[0034] An opening module is used to divide the access range of each block. When the user completes the verification of the sequence pointing, the access range of all blocks before the sequence pointing is summarized to obtain a target range, which is used to open the access rights of the target range to the user.

[0035] A sending module, configured to split the access range into a sensitive area and a safe area;

[0036] When a user accesses data in a sensitive area, the user's terminal is located, the external device connected to the terminal is found, and the user's action instructions in the sensitive area are collected. When the action instructions are the same as the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain;

[0037] When a user accesses data in the security zone, verification is performed based on the sequential pointing, and the access permission is granted if the verification passes.

[0038] Further,

[0039] The generation module includes:

[0040] A correction unit, configured to determine the user's role based on the attribute, map the approval process to the role, generate a process chain, and correct the digital chain;

[0041] a synchronization unit, configured to synchronize the action instructions and monitoring reports into a number of blocks;

[0042] an integration unit, configured to generate a tag using the role and integrate the tag into a data block;

[0043] A verification unit, configured to insert a jump pointer into the block chain and switch the multi-level verification mechanism;

[0044] A transfer unit, configured to create a storage node, establish a corresponding relationship between the storage node and the data block, and transfer the data in the sensitive area to the storage node;

[0045] A building unit, used for building a data channel between several blocks and the storage node;

[0046] The emergency response plan includes one or more of closing a sensitive area, sending an alarm message to a preset terminal, and increasing a user operation delay.

[0047] Furthermore, the sending module includes:

[0048] A configuration unit, configured to configure a correspondence between the roles, blocks, and access scopes, and synchronize the correspondence to the block chain;

[0049] The generating unit is used to construct a coordinated framework and integrate the access scope into the coordinated framework to generate a target scope.

[0050] Compared with the prior art, the present invention has the following beneficial effects:

[0051] By building digital blocks, it is possible to establish approval process relationships between users, standardize security management processes, and improve management transparency. By building digital blockchains, it is possible to strengthen the division of labor in management processes and optimize security management. By building a multi-level verification mechanism, it is possible to further improve data security and avoid data leakage. By splitting the access scope into sensitive areas and secure areas, it is possible to fully utilize monitoring resources, reduce unnecessary resource consumption, and improve operational efficiency. In addition, it can better respond to the needs of different security levels, ensuring that while protecting sensitive information, the overall access scope is maintained smooth and stable. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 A flowchart of an information interaction method for a security management platform described in some embodiments of the present invention;

[0053] Figure 2 This is a block diagram of the first sub-process of the information interaction method of the security management platform described in some embodiments of the present invention;

[0054] Figure 3 A second sub-flow diagram of the information interaction method of the security management platform described in some embodiments of the present invention;

[0055] Figure 4 A third sub-flow diagram of the information interaction method of the security management platform described in some embodiments of the present invention;

[0056] Figure 5A block diagram of the information interaction system of the security management platform described in some embodiments of the present invention;

[0057] Figure 6 A block diagram of the composition of a generation module in the information interaction system of the security management platform described in some embodiments of the present invention;

[0058] Figure 7 A block diagram of the composition of open modules in the information interaction system of the security management platform described in some embodiments of the present invention;

[0059] Figure 8 This is a block diagram of the composition of the sending module in the information interaction system of the security management platform described in some embodiments of the present invention. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0061] Combine Figure 1 The present embodiment provides an information interaction method for a security management platform. The implementation process of the method includes the following steps:

[0062] S100: Define user attributes, configure the approval process between users, build blocks corresponding to each user, and arrange the blocks according to the approval process. Insert sequence pointers between adjacent blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a block chain.

[0063] The multi-level verification mechanism is: only after the previous sequence pointer has completed verification, can the current sequence pointer be activated for verification. The specific verification method can be set as needed, such as password verification.

[0064] The attributes of the above-mentioned users include work attributes, which can be interns, operators, and technical managers. Based on the attributes, an approval process between users is configured. According to the order of the approval process, the blocks are arranged, and sequential pointers are inserted between two adjacent blocks. A multi-level verification mechanism is embedded in the sequential pointers to generate a block chain; the multi-level verification mechanism consists of multiple verification schemes.

[0065] For example, in a certain security management platform, the approval process is: And build a blockchain as mentioned above; the access scope corresponding to the intern is generally basic parameters or public data, and if the operator wants to query his corresponding access scope, he needs to pass the verification pointing to A. If the section chief wants to query his corresponding access scope, he not only needs to pass the verification pointing to B, but also the verification pointing to A. And so on. If the workshop director needs to query his corresponding access scope, he needs to verify pointing to A, pointing to B, pointing to C and pointing to D in turn.

[0066] S200: Divide the access range of each block. When the user completes the verification of the sequential pointing, the access ranges of all the blocks before the sequential pointing are summarized to obtain the target range, and the access rights of the target range are opened to the user.

[0067] Determine the access scope of each block, where each user has a different access scope. Only after the user completes the corresponding sequential pointing or all previous pointings of the sequential pointing can the user obtain access rights to the target range.

[0068] S300: Split the access range into a sensitive area and a safe area as needed;

[0069] When a user accesses data in a sensitive area, the user's terminal is located and the external device connected to the terminal is found. The external device includes one or more of an image acquisition device (such as a camera), a keyboard, and a mouse. The external device may also include other existing devices such as a USB flash drive that can be connected to the applicable terminal. The user's action instructions in the sensitive area are collected via the external device. When the action instructions are the same as the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain.

[0070] When a user accesses data in the security zone, verification is performed based on sequential pointing (receiving the password entered by the user and determining the correct number of digits in the password). Access rights are granted if the verification passes (the number of correct digits exceeds the preset threshold).

[0071] The access range is divided into sensitive areas and safe areas. If a user accesses data in a sensitive area, the user's terminal is located and the external device is determined. The external device can be a terminal camera used with the terminal, or a monitoring device in the terminal area, or a keyboard and mouse used with the terminal. These external devices are used to collect the user's action instructions in the sensitive area, and the collected action instructions are compared with the action instructions in the preset monitoring table. If the same action instructions appear, a monitoring report is generated and sent to the next block. For example,

[0072] When a section chief uses a laptop in the office area to query sensitive data within his corresponding access range, the camera in the laptop and the monitoring equipment in the office area are turned on to collect the section chief's action instructions and compare them with the monitoring table. If the collected action instructions are the same as those in the monitoring table (for example: taking pictures, copying using a USB flash drive, etc.), a monitoring report is generated and sent to the data block corresponding to the process director; the monitoring table is pre-prepared by the staff and consists of multiple action instructions.

[0073] If the user accesses data in the secure zone, when the sequential pointer is used to verify the password entered by the user, if the correct number of digits in the password exceeds the preset threshold, access permission will be granted; for example, if the password in the sequential pointer is 123456, if the user accesses data in the secure zone, access permission will be granted by only answering 5 of the digits correctly.

[0074] In some specific implementations, combined with Figure 2 The specific execution process of S100 includes:

[0075] S101: Based on the attributes, determine the user's role, map the approval process to the role, generate a process chain, and correct the blockchain.

[0076] Determine the attributes of each user and determine the user's role based on the attributes. The role is the specific work that the user is responsible for. In other words, operators in different job positions have different corresponding access scopes. The role is the specific work that each user is responsible for. Map the approval process to the role, and use the process chain to improve and correct the blockchain.

[0077] S102: Synchronize the action instructions and monitoring reports into several blocks.

[0078] In the blockchain, when the user corresponding to the previous blockchain queries the corresponding access range, the generated action instructions and monitoring reports are synchronized to the current blockchain.

[0079] For example, when an operator queries his corresponding access range, the generated action instructions and monitoring reports will be synchronized to the data block corresponding to the section chief.

[0080] In some specific implementations, combined with Figure 2 The specific execution process of S100 further includes:

[0081] S103: Generate tags using the user's role and integrate the tags into corresponding blocks.

[0082] Based on the role, determine the label of each user and insert the label into the number block, that is, each user corresponds to a number block.

[0083] S104: Insert a jump pointer into the blockchain and switch to a multi-level verification mechanism.

[0084] Insert a jump pointer into the block chain. The jump pointer means that due to the particularity of some positions, a financial technician position may involve financial data that needs to be kept confidential, and his superior section chief, process director, etc. may not have query authority; therefore, the block corresponding to the technician should directly point to the workshop director. When the workshop director queries his corresponding access scope, he does not need to verify the above-mentioned pointers B, C, and D, but can directly verify the jump pointer. This verification method is one of multiple verification schemes.

[0085] In some specific implementations, combined with Figure 2 As shown in the content, after executing S104, the execution process of S100 further includes:

[0086] S105: creating a storage node, establishing a corresponding relationship between the storage node and the data blocks, and transferring the data in the sensitive area to the storage node.

[0087] A storage node is created for each block, and the data in the sensitive area is transferred to the storage node for storage.

[0088] S106: Building data channels between several blocks and the storage node.

[0089] The data in several blocks is read through the data channel, wherein additional verification can be added to the data channel to verify the user multiple times.

[0090] In some specific implementations, combined with Figure 3 The specific execution process of S200 includes:

[0091] S201: Configure the corresponding relationship between roles, blocks and access scopes, and synchronize the corresponding relationship to the block chain.

[0092] Determine the correspondence between roles, blocks, and access scopes, and synchronize the correspondence to the blockchain. This prevents data in the blockchain from becoming disordered.

[0093] S202: Build a coordination framework, and integrate the access scope into the coordination framework to generate a target scope.

[0094] By using the coordinated architecture, the access ranges of all users are summarized in an orderly manner to obtain the target range, which is the sum of the access ranges corresponding to the current blocks.

[0095] For example, the access scope for interns is A, the access scope for operators is B, and the access scope for section chiefs is C. When a user completes the verification pointing to B, in addition to opening up access to C, the access to A and B is also opened, and the target scope is A+B+C.

[0096] In some specific implementations, combined with Figure 4 The specific execution process of S300 includes:

[0097] S301: Record the number of times the user reads the access range and add a timestamp.

[0098] Record the number of times the user reads the access range, add a timestamp, and record the user's access time.

[0099] S302: Count the access frequency of each block, and divide the block into several sub-blocks based on the access frequency.

[0100] The access frequency of each data block is counted. If the access frequency of a data block is greater than the preset threshold, the data block can be split again. The advantage of this is that it can improve the user's access efficiency and quickly find the required data.

[0101] In some specific implementations, the information interaction method of the security management platform further includes a special event processing method, which includes:

[0102] Define special events (special events may include safety accidents, production anomalies, or special operating conditions. The definition of special events can be set as needed using existing technologies based on common knowledge in the field and is therefore not detailed here). Trigger the initiation of pre-built emergency response plans, which may include one or more of: closing sensitive areas, sending alarms to preset terminals, and increasing user operation delays. Other customized plans may also be included.

[0103] Obtain the permission to release special events and determine how to activate the permission.

[0104] Define special events, and when they occur, initiate an emergency response plan. For example, a special event may be that a user verifies a certain direction multiple times and the verification fails. In this case, the sensitive area in the data block corresponding to the direction can be closed.

[0105] When a special event occurs, use the activation plan to obtain the permission to cancel the special event and cancel the special event.

[0106] For example, when pointing to B is frequently and repeatedly verified incorrectly, the sensitive area in the number block corresponding to the section chief is closed, and the authority to remove it is opened to the process director. A special password verification is activated, and the process director enters the password to reactivate the sensitive area in the number block corresponding to the section chief.

[0107] In actual use, the following block chain is constructed, namely Each job level corresponds to a data block. If a certain job level wants to access the data within its authority, all the pointers before its job level must be verified. For example, if the process director wants to access the data within his authority, he must verify pointers A, B, and C in turn.

[0108] In addition, the data within the authority of each job level is divided into sensitive areas and secure areas. When accessing the sensitive area, the computer camera, area monitoring, etc. are turned on to monitor the user's action instructions. If an action instruction in the monitoring table appears, a monitoring report is generated and sent to the previous job level; when accessing the secure area, only some digits of the password entered need to be correct to access (fuzzy verification).

[0109] Combine Figure 5 The present embodiment provides an information interaction system for a security management platform. The information interaction system 1 for the security management platform includes:

[0110] Generation module 11 is used to define user attributes, configure the approval process between users, construct digital blocks corresponding to each user, arrange the digital blocks according to the approval process, insert sequence pointers between adjacent digital blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a digital block chain;

[0111] The multi-level verification mechanism is as follows: only after the previous sequence pointer completes the password verification, can the current sequence pointer be activated for verification;

[0112] The opening module 12 is used to divide the access range of each block. When the user completes the verification of the sequence pointing, the access range of all the blocks before the sequence pointing is summarized to obtain the target range, and the access rights of the target range are opened to the user.

[0113] The sending module 13 is used to split the access range into a sensitive area and a safe area;

[0114] When a user accesses data in a sensitive area, the user's terminal is located and external devices connected to the terminal are found, where the external devices include at least a terminal camera, a keyboard, and a mouse. The user's action instructions within the access range are collected via the external devices. When the action instructions are consistent with the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain.

[0115] When a user accesses data in the security zone, the password input by the user is received based on the sequential pointing, and the correct number of digits of the password is determined. If the correct number of digits exceeds a preset threshold, the access permission is opened.

[0116] In some specific implementations, combined with Figure 6 The content shown, the generation module 11 includes:

[0117] Correction unit 111, used to determine the user's role based on the user's attributes, map the approval process to the role, generate a process chain, and correct the block chain;

[0118] Synchronization unit 112, used to synchronize action instructions and monitoring reports into several blocks;

[0119] An integration unit 113 is used to generate tags using roles and integrate the tags into the data block;

[0120] Verification unit 114, used to insert jump pointers into the block chain and switch the multi-level verification mechanism;

[0121] The transfer unit 115 is used to create a storage node, establish a corresponding relationship between the storage node and the data block, and transfer the data in the sensitive area to the storage node;

[0122] The building unit 116 is used to build a data channel between the data block and the storage node.

[0123] In some specific implementations, combined with Figure 7 As shown, the open module 12 includes:

[0124] Configuration unit 121, configured to configure the correspondence between roles, blocks, and access scopes, and synchronize the correspondence to the block chain;

[0125] The generating unit 122 is configured to construct a coordinated framework, integrate the access scope into the coordinated framework, and generate a target scope.

[0126] In some specific implementations, combined with Figure 8 The sending module 13 includes:

[0127] An adding unit 131 is used to record the number of times a user reads the access range and add a timestamp;

[0128] The segmentation unit 132 is configured to calculate the access frequency of each block and to segment the block into a plurality of sub-blocks based on the access frequency.

[0129] The generating module 11 is mainly used to complete step S100, the opening module 12 is mainly used to complete step S200, and the sending module 13 is mainly used to complete step S300;

[0130] The correction unit 111 is mainly used to complete step S101, the synchronization unit 112 is mainly used to complete step S102, the integration unit 113 is mainly used to complete step S103, the verification unit 114 is mainly used to complete step S104, the transfer unit 115 is mainly used to complete step S105, and the construction unit 116 is mainly used to complete step S106;

[0131] The configuration unit 121 is mainly used to complete step S201, and the generation unit 122 is mainly used to complete step S202;

[0132] The adding unit 131 is mainly used to complete step S301, and the splitting unit 132 is mainly used to complete step S302.

[0133] All matters not mentioned above can be achieved using existing technologies, so they will not be described in detail here.

[0134] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0135] The above-described embodiments merely illustrate several implementations of the present invention, and while their descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art would be able to make numerous variations and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be determined by the appended claims.

Claims

1. An information interaction method for a security management platform, characterized in that: The method comprises: S100: Define the attributes of the user, configure the approval process between users, build a one-to-one corresponding block with the user, and arrange the blocks according to the approval process. Insert sequence pointers between adjacent blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a block chain. Based on the attributes, determine the role of the user, map the approval process to the role, generate a process chain, and correct the block chain; synchronize action instructions and monitoring reports to the block; use the role to generate a label, and integrate the label into the block; insert a jump pointer into the block chain and switch the multi-level verification mechanism; create a storage node, establish a corresponding relationship between the storage node and the block, transfer the data in the sensitive area to the storage node; build a data channel between the block and the storage node; The multi-level verification mechanism is as follows: the current sequence pointing can be activated for verification only after the previous sequence pointing has completed verification; The process of synchronizing action instructions and monitoring reports into the block is as follows: in the block chain, when the user corresponding to the previous block queries the corresponding access scope, the generated action instructions and monitoring reports are synchronized into the current block; S200: Dividing the access range of each block, and when the user completes the verification of the sequence pointing, summarizing the access ranges of all blocks before the sequence pointing to obtain a target range, so as to provide the user with access rights to the target range; S300: Splitting the access range into a sensitive area and a safe area; When a user accesses data in a sensitive area, the user's terminal is located, the external device connected to the terminal is found, and the user's action instructions in the sensitive area are collected. When the action instructions are the same as the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain; When a user accesses data in the security zone, verification is performed based on the sequential pointing, and the access permission is granted if the verification passes.

2. The information interaction method of the security management platform according to claim 1 is characterized in that: The S200 includes: Configuring the correspondence between the roles, blocks, and access scopes, and synchronizing the correspondence to the block chain; A coordination framework is constructed, and the access scope is integrated into the coordination framework to generate a target scope.

3. The information interaction method of the security management platform according to claim 2 is characterized in that: The S300 includes: Record the number of times the user reads the access range and add a timestamp; The access frequency of each block is counted, and based on the access frequency, the block is divided into a plurality of sub-blocks.

4. The information interaction method of the security management platform according to claim 1, characterized in that: The method further comprises: Define special events to trigger the launch of pre-built emergency response plans; Obtain the release permission for the special event, and determine an activation method for the release permission.

5. An information interaction system for a security management platform, characterized in that: The system comprises: A generation module is used to define the attributes of users, configure the approval process between users, build digital blocks corresponding to the users, arrange the digital blocks according to the approval process, insert sequence pointers between adjacent digital blocks, and embed a multi-level verification mechanism into the sequence pointers to generate a digital block chain. Based on the attributes, the user's role is determined, the approval process is mapped to the role, a process chain is generated, and the digital block chain is corrected; action instructions and monitoring reports are synchronized to the digital blocks; tags are generated using the role and integrated into the digital blocks; jump pointers are inserted into the digital block chain and the multi-level verification mechanism is switched; storage nodes are created, a corresponding relationship between the storage nodes and the digital blocks is established, data in the sensitive area is transferred to the storage nodes; and a data channel between the digital blocks and the storage nodes is established; The multi-level verification mechanism is as follows: the current sequence pointing can be activated for verification only after the previous sequence pointing has completed verification; The process of synchronizing action instructions and monitoring reports into the block is as follows: in the block chain, when the user corresponding to the previous block queries the corresponding access scope, the generated action instructions and monitoring reports are synchronized into the current block; An opening module is used to divide the access range of each block. When the user completes the verification of the sequence pointing, the access range of all blocks before the sequence pointing is summarized to obtain a target range, which is used to open the access rights of the target range to the user. A sending module, configured to split the access range into a sensitive area and a safe area; When a user accesses data in a sensitive area, the user's terminal is located, the external device connected to the terminal is found, and the user's action instructions in the sensitive area are collected. When the action instructions are the same as the action instructions in the preset monitoring table, a monitoring report is generated and sent to the next block in the block chain; When a user accesses data in the security zone, verification is performed based on the sequential pointing, and the access permission is granted if the verification passes.

6. The information interaction system of the security management platform according to claim 5 is characterized in that: The generation module includes: A correction unit, configured to determine the user's role based on the attribute, map the approval process to the role, generate a process chain, and correct the digital chain; a synchronization unit, configured to synchronize the action instructions and monitoring reports into a number of blocks; an integration unit, configured to generate a tag using the role and integrate the tag into a data block; A verification unit, configured to insert a jump pointer into the block chain and switch the multi-level verification mechanism; A transfer unit, configured to create a storage node, establish a corresponding relationship between the storage node and the data block, and transfer the data in the sensitive area to the storage node; A building unit, used for building a data channel between several blocks and the storage node; The emergency response plan includes one or more of closing sensitive areas, sending alarm information to preset terminals, and increasing user operation delays.

7. The information interaction system of the security management platform according to claim 6, wherein the sending module comprises: A configuration unit, configured to configure a correspondence between the roles, blocks, and access scopes, and synchronize the correspondence to the block chain; The generating unit is used to construct a coordinated framework and integrate the access scope into the coordinated framework to generate a target scope.

Images