Page sensitive information processing method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of data processing, and discloses a page sensitive information processing method and device, computer equipment and a storage medium. The method comprises the following steps: receiving a page loading request, and obtaining a loading index parameter of a target page according to the page loading request; when the target index parameter exists in the loading index parameters, traversing and screening out a to-be-processed node from all page element nodes of the target page through the initialized target desensitization plug-in; obtaining node attribute information of each to-be-processed node through the target desensitization plug-in, and determining a node processing type of each to-be-processed node according to the node attribute information; and when the node processing type is a desensitization processing type, performing mask processing on the node content data of the to-be-processed node through the target desensitization plug-in according to a preset mask rule to obtain node desensitization data, and replacing and displaying the node content data of the to-be-processed node in the target page with the node desensitization data. According to the invention, the desensitization processing efficiency and the system stability are improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, computer device, and storage medium for processing sensitive information on a webpage. Background Technology

[0002] In our business system, sensitive information such as user mobile phone numbers, ID card numbers, and bank card numbers are widely distributed across multiple areas of the page. For information security reasons, this sensitive information cannot be presented in plaintext on the page; therefore, a masking mechanism needs to be added to the front-end page.

[0003] Currently, there are various page masking assistants available on the market, such as jQuery Inputmask, Vanilla Masker, and Vue input mask. However, these page assistants have significant limitations. Existing page assistants often need to be integrated during the system development phase to achieve good results. However, when dealing with legacy systems that have already been developed, there are many areas that require masking. This necessitates additional, intrusive modifications for different scenarios, which is inefficient and can easily lead to system instability.

[0004] Therefore, a new method for handling sensitive information on web pages is urgently needed. Summary of the Invention

[0005] Therefore, it is necessary to provide a method, apparatus, computer equipment, and storage medium for processing sensitive information on a webpage, in order to address the aforementioned technical problems and solve the issues of low efficiency and poor stability in existing methods for processing sensitive information on a webpage.

[0006] A method for handling sensitive information on a webpage, comprising: Receive a page loading request and obtain the loading index parameters of the target page based on the page loading request; When a target indicator parameter exists in the loading indicator parameters, the target desensitization plugin is initialized, and the target desensitization plugin is used to traverse and filter out the nodes to be processed from all page element nodes of the target page. The node attribute information of each node to be processed is obtained through the target desensitization plugin, and the node processing type of each node to be processed is determined based on the node attribute information. When the node processing type of the node to be processed is the desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the node to be processed according to the preset masking rules to obtain node desensitized data, and replaces the node content data of the node to be processed in the target page with the node desensitized data.

[0007] A page-sensitive information processing device, comprising: The indicator parameter acquisition module is used to receive page loading requests and obtain the loading indicator parameters of the target page based on the page loading requests. The node traversal and filtering module is used to initialize the target desensitization plugin when the target indicator parameter exists in the loaded indicator parameter, and to traverse and filter the nodes to be processed from all page element nodes of the target page through the target desensitization plugin. The processing type determination module is used to obtain the node attribute information of each node to be processed through the target desensitization plugin, and determine the node processing type of each node to be processed based on the node attribute information. The masking module is used to mask the node content data of the node to be processed according to a preset masking rule when the node processing type of the node to be processed is the desensitization processing type, so as to obtain node desensitized data, and replace the node content data of the node to be processed in the target page with the node desensitized data.

[0008] A computer device includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the above-described page-sensitive information processing method when executing the computer-readable instructions.

[0009] A computer-readable storage medium storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the page-sensitive information processing method described above.

[0010] In the aforementioned page sensitive information processing method, apparatus, computer equipment, and storage medium, the page sensitive information processing method receives a page loading request and obtains the loading index parameters of the target page based on the page loading request. When the target index parameters exist in the loading index parameters, the target desensitization plugin is initialized, and the target desensitization plugin traverses and filters all page element nodes of the target page to select nodes to be processed. The target desensitization plugin obtains the node attribute information of each node to be processed and determines the node processing type of each node to be processed based on the node attribute information. When the node processing type of the node to be processed is a desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the node to be processed according to a preset masking rule to obtain node desensitized data, and replaces the node content data of the node to be processed in the target page with the node desensitized data. This invention initializes the target desensitization plugin when the loading index parameters of the target page reach a preset index threshold, performs node traversal and filtering based on the target desensitization plugin, and processes different node processing types. It does not require intrusive modifications for different scenarios one by one, realizing a globally unified desensitization processing mechanism and improving desensitization processing efficiency and system stability. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating a method for processing sensitive page information according to an embodiment of the present invention; Figure 2 This is a flowchart illustrating step S20 of the page sensitive information processing method in one embodiment of the present invention; Figure 3 This is a flowchart illustrating step S203 of the page sensitive information processing method in one embodiment of the present invention; Figure 4 This is a flowchart illustrating step S30 of a page sensitive information processing method according to an embodiment of the present invention; Figure 5 This is another flowchart illustrating step S30 in a page sensitive information processing method according to an embodiment of the present invention; Figure 6 This is another flowchart illustrating step S30 in a page sensitive information processing method according to an embodiment of the present invention; Figure 7 This is a flowchart illustrating step S40 of a page sensitive information processing method according to an embodiment of the present invention; Figure 8 This is a schematic diagram of a page-sensitive information processing device according to an embodiment of the present invention; Figure 9 This is a schematic diagram of a computer device according to an embodiment of the present invention. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] The page sensitive information processing method provided in this embodiment can be applied in scenarios where the server responds to a client's request to load a page, and uses a desensitization plugin to desensitize sensitive data present in the page. The client communicates with the server. Clients include, but are not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0015] In one embodiment, such as Figure 1 As shown, a method for processing sensitive information on a webpage is provided, including the following steps S10-S40: S10. Receive a page loading request and obtain the loading index parameters of the target page based on the page loading request.

[0016] Understandably, users can access pages through the client's display interface. The client generates a page load request based on the page address the user needs to access and sends the page load request to the server. A page load request is a request message used to display the page data of a specified page on the client. The target page is the specific page that needs to be displayed on the client.

[0017] The server receives a page loading request, retrieves the page data of the target page based on the page address in the request, loads it, and obtains loading metric parameters during the loading process. Loading metric parameters are evaluation standards used to characterize the loading performance of the target page. These parameters can include multiple dimensions, such as First Contentful Paint (FCP), Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and First Input Delay (FID). FCP is the time it takes for the page to first draw any pixels containing content onto the client's display screen, reflecting the point in time when page content begins to be rendered. LCP measures the time from the start of page loading until the largest image or text block in the client's display screen is fully rendered. CLS measures the cumulative effect of changes in the layout of elements on the page; a lower CLS indicates a more stable page layout. FID is the time from the user's first interaction with the page (e.g., clicking a link, clicking a button, etc.) to the browser's actual ability to respond to that interaction.

[0018] S20. When a target indicator parameter exists in the loaded indicator parameters, the target desensitization plugin is initialized, and the target desensitization plugin is used to traverse and filter out the nodes to be processed from all page element nodes of the target page.

[0019] Understandably, after obtaining the loading metric parameters, the server determines whether the target metric parameter exists among them. The target metric parameter refers to the pre-specified loading metric parameter used to trigger the initialization process of the target de-identification plugin. In this embodiment, the target metric parameter is the Maximum Contentful Paint (LCP). When existing page events (such as window.onload and the DOM Content Loaded event of document) are triggered, a large amount of page content has not yet been rendered. At this time, if page element node traversal filtering and de-identification processing are carried out, the page element nodes that can be covered are extremely limited. When the target metric parameter exists among the loading metric parameters, it indicates that the page content of the target page has been basically rendered. At this time, the initialization process of the target de-identification plugin is triggered so that the traversal filtering and de-identification processing can cover enough page element nodes. In one specific embodiment, the following code instructions are used to monitor the target metric parameter "Largest ContentfulPaint (LCP)": const pageObserver = new PerformanceObserver((list) =>{ const entries = list.getEntries(); / / Get the latest LCP entry const latestEntry = entries[entries.length - 1]; if (latestEntry) { / / Start the target desensitization plugin initialization process } }); / / Start observing LCP performance entries pageObserver.observe({ type: 'largest-contentful-paint', buffered: true }); When the target indicator parameter is present in the loaded indicator parameters, the server initializes the target de-identification plugin. The target de-identification plugin is a pre-written script used to traverse and filter page element nodes of the target page, determine the processing type, and perform sensitive information masking. In this embodiment, the target de-identification plugin is packaged into a Software Development Kit (SDK), enabling rapid integration of the plugin into legacy systems. The server references the code via the "script" directive. <script src="xxxx / mask-code-tool.js">< / script> This indicates that an external JavaScript file, mask-code-tool.js, has been included at the path xxxx / mask-code-tool.js. This allows you to obtain the plugin path address of the target de-identification plugin and initialize it by calling the target de-identification plugin based on that path address.

[0020] After the server-side completes the initialization of the target desensitization plugin, it traverses all page element nodes of the target page and filters out nodes to be processed. A page element node is the basic unit that constitutes a web page document, specifically the Document Object Model (DOM) in web development, which represents an HTML or XML document as a tree structure, with each node being a DOM element. Page element nodes are interconnected in specific relationships, forming a complete tree diagram that represents the hierarchical structure of the HTML web page document. Nodes to be processed are those page element nodes that may contain sensitive information, filtered from the target page's page element nodes. Traversal refers to accessing information from all page element nodes in the target page's DOM tree.

[0021] In one specific embodiment, the following code instructions are used to traverse the page element nodes of the target page: const treeWalker = document.createTreeWalker( root, / / Target node NodeFilter.SHOW_ELEMENT, / / Sets which types of nodes to iterate through walkerFilter, / / Custom filter false, ); The `treeWalker` object can traverse nodes in the DOM tree in a specific order according to specified filtering conditions. The `treeWalker` object is created using the `document.createTreeWalker()` method, and then the `Node()` method of the `treeWalker` object is used to traverse the nodes. `walkerFilter` determines how to process each traversed node, and its return value is a constant of `NodeFilter`. For example, `NodeFilter.FILTER_ACCEPT` means accepting the node (as a pending node for further processing), and `NodeFilter.FILTER_SKIP` means skipping the node (not as a pending node).

[0022] S30. Obtain the node attribute information of each node to be processed through the target desensitization plugin, and determine the node processing type of each node to be processed based on the node attribute information.

[0023] Understandably, after filtering out the nodes to be processed, the server obtains the node attribute information of each node through the target de-identification plugin, and determines the node processing type for each node based on the node attribute information. Node attribute information refers to the characteristics of each page element node that constitutes the DOM tree, used to describe the type, field name, value, position, relationship, and status of the page element node. The node processing type is information used to characterize whether a page element node needs de-identification processing. Node processing types include de-identification processing type, plaintext processing type, and sensitivity monitoring type. De-identification processing type refers to the type of page element node data that needs de-identification processing; plaintext processing type refers to the type of page element node data that does not need de-identification processing; and sensitivity monitoring type refers to the type of page element node data that does not need de-identification processing temporarily but will be de-identified later based on changes. Each node to be processed has its own node attribute information, and different node attribute information corresponds to different node processing types. For example, if a node to be processed contains a mobile phone number field, the corresponding node processing type is de-identification processing, meaning it needs to be de-identified before being displayed on the client interface. If some nodes to be processed contain a user level field, then the node processing type is plaintext processing type, which means that no de-identification processing is required and the data is directly displayed on the client interface.

[0024] S40. When the node processing type of the node to be processed is the desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the node to be processed according to the preset masking rules to obtain node desensitized data, and replaces the node content data of the node to be processed in the target page with the node desensitized data.

[0025] Understandably, when the node to be processed is classified as an anonymized data type, the server uses the target anonymization plugin to mask the node content data of the node to be processed according to preset masking rules, obtaining anonymized node data. Then, the server sends the anonymized node data to the client so that the node content data of the node to be processed in the target page can be replaced with the anonymized node data. Masking is a method of anonymization; it involves hiding or replacing specific parts of sensitive information data, ensuring that the data remains usable while preventing unauthorized personnel from directly recognizing it. Preset masking rules are pre-defined rules for replacing specific parts of sensitive information data. The node content data of the node to be processed refers to the data in the node to be processed that needs to be displayed on the client's screen. Anonymized node data refers to the data after masking the node content data.

[0026] In one specific embodiment, the preset masking rule is a regular expression. Based on the regular expression, the mask characters corresponding to sensitive characters in the node content data of the node to be processed can be determined, and the sensitive characters can be replaced with the mask characters. The regular expression is used to convert sensitive characters into corresponding mask characters. During the masking process for sensitive characters, one or more characters within the sensitive characters can be masked.

[0027] The preset masking rules can include multiple regular expressions, each indicating the masking method for different sensitive characters. In this case, it's necessary to determine the regular expression corresponding to the field name of the sensitive field, and then process the sensitive characters according to the regular expression to achieve sensitive character desensitization. For example, the sensitive fields include a mobile phone number field and an ID card number field. The preset masking rules contain two regular expressions, one indicating the masking method for the mobile phone number character and the other for the ID card number character. Specifically, for the node content data corresponding to the sensitive field "mobile phone number" as "18712345678", the regular expression determines that the 4th, 5th, 6th, and 7th positions are the masking positions. That is, the characters at the 4th, 5th, 6th, and 7th positions are sensitive characters ("1234" are four sensitive characters). These sensitive characters are then replaced with "×", resulting in the desensitized node data "187××××5678".

[0028] This embodiment receives a page loading request and obtains the loading indicator parameters of the target page based on the request. If the target indicator parameters are present, the target desensitization plugin is initialized, and it iterates through all page element nodes on the target page to select nodes to be processed. The plugin obtains the node attribute information of each node to be processed and determines its processing type. When the processing type is desensitization, the plugin masks the node content data according to a preset masking rule to obtain desensitized data, which is then used to replace the node content data of the node to be processed on the target page. This embodiment enables rapid access to sensitive information masking on front-end pages without complex configuration processes or lengthy development and debugging. It allows for quick integration of the target desensitization plugin, significantly shortening the time from solution determination to feature deployment and improving the timeliness of information security protection. Furthermore, it eliminates the need for extensive customization due to differences in legacy systems, expanding its applicability and providing a unified and effective desensitization method for sensitive information in various legacy systems. In this embodiment, when the loading index parameters of the target page reach the preset index threshold, the target desensitization plugin is initialized. Based on the target desensitization plugin, node traversal and filtering are performed, and different node processing types are processed. There is no need to carry out intrusive modifications for different scenarios one by one. This realizes a globally unified desensitization processing mechanism, which improves the desensitization processing efficiency and system stability.

[0029] In one embodiment, such as Figure 2 As shown, step S20, namely, selecting the nodes to be processed from all page element nodes of the target page through the target desensitization plugin, includes: S201. Generate a node traversal task list corresponding to all page element nodes of the target page through the target desensitization plugin; one node traversal task in the node traversal task list corresponds to one page element node. S202. When the target page is in an idle state, select a node traversal task that has not yet been executed from the node traversal task list, and determine the page element node corresponding to the selected node traversal task as the node to be filtered. S203. Obtain the node label of the node to be filtered, determine whether the node to be filtered meets the preset filtering conditions based on the node label, and determine the node to be filtered that meets the preset filtering conditions as the node to be processed, and select the next node traversal task that has not yet been executed from the node traversal task list, until there are no node traversal tasks that have not yet been executed in the node traversal task list to complete the traversal.

[0030] Understandably, for the target page after its initial load, the server uses a target desensitization plugin to generate a list of node traversal tasks corresponding to all page element nodes of the target page. This list is used to determine whether each page element node on the target page might contain sensitive information. Each node traversal task in the list corresponds to one page element node; that is, the number of node traversal tasks is equal to the number of page element nodes.

[0031] To avoid conflicts between node traversal tasks and page operations, which could affect page operation efficiency, it's necessary to first determine if the target page is in an idle state. An idle state refers to a state where the target page has no page operations requiring a response within a preset idle time threshold. This preset idle time threshold is a pre-defined duration threshold used to determine the idle state; it can be set to a default value or adjusted as needed, such as a default value of 1 second. When the target page is in an idle state, an unexecuted node traversal task is selected from the node traversal task list, and the page element node corresponding to the selected task is designated as the node to be filtered. When the target page changes from an idle state to a busy state, no unexecuted node traversal tasks are selected from the node traversal task list for processing until the target page returns to an idle state.

[0032] A node tag is a specific tag corresponding to each page element node in the DOM tree, such as... 、 The server uses a target desensitization plugin to obtain the node tags of the nodes to be filtered and determines whether the node tags meet preset filtering conditions. These preset filtering conditions are pre-defined criteria used to determine whether page element nodes may contain sensitive information. When a node tag meets the preset filtering conditions, the node to be filtered is identified as a node to be processed, and the next unexecuted node traversal task is selected from the node traversal task list until there are no unexecuted node traversal tasks left in the list, at which point the traversal is complete. When a node tag does not meet the preset filtering conditions, the node to be filtered is not identified as a node to be processed, meaning that no subsequent sensitive information processing is performed on that node.

[0033] In one specific embodiment, the node traversal tasks in the node traversal task list are executed using the following code instructions: const taskController = { taskList: [], running: false, addTask(task) { this.taskList.push(task); this.runTask(); }, runTask() { if (this.running) { return; } this.running = true; / / Execute task requestIdleCallback((idle) =>{ / / Continue executing as long as there is available time. while (idle.timeRemaining()>0&&this.taskList.length) { const task = this.taskList.shift(); task(); } this.running = false; / / No free time, but there are still tasks to complete. I'll continue when I have more free time. if (this.taskList.length) { this.runTask(); } }); }, }; In this embodiment, for the target page after its initial loading, the server uses a target de-identification plugin to generate a list of node traversal tasks corresponding to all page element nodes of the target page, ensuring comprehensive coverage of node filtering. Simultaneously, the node traversal task is only executed when the target page is idle, preventing page lag caused by a large number of operations in a short period, thus ensuring page display and operational performance.

[0034] In one embodiment, such as Figure 3 As shown, step S203, namely determining the nodes to be filtered that meet the preset filtering conditions as nodes to be processed, includes: S2031. When the node label belongs to the target filter label in the preset filter conditions, obtain the parent node processing type corresponding to the node to be filtered. S2032. When the parent node processing type is not a sensitive monitoring type, determine whether the node to be filtered includes text content data; S2033. When the node to be filtered includes text content data, the node to be filtered is determined as the node to be processed.

[0035] Understandably, firstly, the server uses a target desensitization plugin to determine whether a node tag belongs to the target filter tags in the preset filtering conditions. If a node tag does not belong to the target filter tags in the preset filtering conditions, the node to be filtered will not be identified as a node to be processed (the node to be filtered will be ignored). The target filter tags in the preset filtering conditions are pre-defined node tags used to determine whether page element nodes may contain sensitive information from the node tag dimension. For example, the target filter tags are "TEXTAREA, INPUT, DIV, P, SPAN, EM, STRONG, TD, PRE". If a node tag belongs to the target filter tags in the preset filtering conditions, it is necessary to obtain the parent node processing type corresponding to the node to be filtered. The parent node processing type is the node processing type of the page element node that is one level above the node to be filtered in the DOM tree and has a branch relationship. Node processing types include three types: desensitization processing type, plaintext processing type, and sensitivity monitoring type.

[0036] Next, if the parent node's processing type is a sensitive monitoring type, the node to be filtered will not be identified as a node to be processed (it will be ignored). If the parent node's processing type is not a sensitive monitoring type, it is necessary to further determine whether the node to be filtered contains text content data, that is, whether the node to be filtered contains text nodes. In HTML pages, text is usually located inside element nodes. For example, in The `` tag can contain text content data. When this text content data is accessed via JavaScript, a text node is generated. The text node is not independent but exists as part of the element. (The `` tag is used in the `<script>` tag to specify the text content.) Hello, world! "middle is a page element node, and Hello and world! are its text nodes.

[0037] Finally, if the node to be filtered does not include text content data, the node to be filtered is not determined as a node to be processed. If the node to be filtered includes text content data, the node to be filtered is determined as a node to be processed.

[0038] In a specific embodiment, the following code instructions are used to determine whether the node to be filtered is determined as a node to be processed: const walkerFilter = { acceptNode(node) { / / Only process TEXTAREA, INPUT, DIV, P, SPAN, EM, STRONG, TD, PRE if (!NEED_MASK_TAG.includes(node.tagName)) { return NodeFilter.FILTER_SKIP; } / / If it is a node of the target filtering tag, it is recorded if (NEED_TXT_CHANGE_LISTENER_TAG.includes(node.tagName)) { listenTxtChangeDomCache.add(node); return NodeFilter.FILTER_ACCEPT; } / / If it is a child element of a sensitive monitoring type node, it is ignored if (listenTxtChangeDomCache.has(node.parentNode)) { return NodeFilter.FILTER_REJECT; } / / Only accept if it contains a text node if (getInnerTextNode(node).length) { return NodeFilter.FILTER_ACCEPT; } return NodeFilter.FILTER_SKIP; }, }; The embodiment filters the to-be-screened nodes through node label matching, parent-child hierarchical node type verification and text content data screening, ensures that the to-be-screened nodes meeting the conditions are determined as to-be-processed nodes, improves the accuracy of node screening, and reduces invalid processing, misprocessing and missed processing.

[0039] In an embodiment, the to-be-processed node includes a to-be-processed text node, and the node processing type includes a desensitization processing type, a plaintext processing type and a sensitive monitoring type. Figure 4 As shown in the figure, in step S30, that is, determining the node processing type of each to-be-processed node according to the node attribute information, includes: S301, determining the text field parameter of the to-be-processed text node according to the node attribute information; S302, when the text field parameter of the to-be-processed text node belongs to a preset sensitive field, determining the node processing type of the to-be-processed node as the desensitization processing type; S303, when the text field parameter of the to-be-processed text node does not belong to a preset sensitive field, and there is a sensitive configuration item parameter, if the sensitive configuration item parameter is a first sensitive configuration item, determining the node processing type of the to-be-processed node as the desensitization processing type; S304, when the text field parameter of the to-be-processed text node does not belong to a preset sensitive field, and there is a sensitive configuration item parameter, if the sensitive configuration item parameter is a second sensitive configuration item, determining the node processing type of the to-be-processed node as the sensitive monitoring type; S305, when the text field parameter of the to-be-processed text node does not belong to a preset sensitive field, and there is no sensitive configuration item parameter, determining the text length parameter of the to-be-processed text node according to the node attribute information, if the text length parameter has not reached a preset length threshold, determining the node processing type of the to-be-processed node as the plaintext processing type; S306, when the text field parameter of the to-be-processed text node does not belong to a preset sensitive field, and there is no sensitive configuration item parameter, determining the text length parameter of the to-be-processed text node according to the node attribute information, if the text length parameter reaches a preset length threshold, determining the node processing type of the to-be-processed node as the sensitive monitoring type.

[0040] Understandably, the to-be-processed node includes a to-be-processed text node, which refers to a node content data directly displayed in a text form. When the to-be-processed node is the to-be-processed text node, it is necessary to first determine a text field parameter of the to-be-processed text node according to node attribute information, and determine whether the text field parameter belongs to a preset sensitive field. The text field parameter refers to a field name corresponding to the node content data in the to-be-processed text node. The field name and the field value of each to-be-processed text node exist in the form of a key-value pair, for example, "user ID": "001" or "mobile phone number": "18712345678". Among them, "user ID" and "mobile phone number" are text field parameters, and "001" and "18712345678" are node content data. The preset sensitive field is a field name that needs to be desensitized and processed in advance. The preset sensitive field can be set according to actual business needs, for example, the "mobile phone number" is configured as the preset sensitive field. When the actual business needs change, the operator can modify the configuration file at any time to modify or add new sensitive fields that need to be desensitized and processed.

[0041] Then, when the text field parameter of the to-be-processed text node belongs to the preset sensitive field, the node processing type of the to-be-processed node is determined as the desensitization processing type. When the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, it is necessary to further determine whether the to-be-processed text node has a sensitive configuration item parameter. The sensitive configuration item parameter is an option parameter for providing user selection of whether the node content data needs to be desensitized and processed, represented by the "data-mask-off" attribute. The sensitive configuration item parameter includes a first sensitive configuration item and a second sensitive configuration item, and the second sensitive configuration item is the default. The first sensitive configuration item refers to a configuration option for indicating that the node content data of the to-be-processed text node needs to be desensitized and processed, represented by the "data-mask-off=false" attribute. The second sensitive configuration item refers to a configuration option for indicating that the node content data of the to-be-processed text node does not need to be desensitized and processed, represented by the "data-mask-off=true" attribute.

[0042] Then, when the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter exists, if the sensitive configuration item parameter is the first sensitive configuration item, the node processing type of the to-be-processed node is determined as the desensitization processing type. When the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter exists, if the sensitive configuration item parameter is the second sensitive configuration item, the node processing type of the to-be-processed node is determined as the sensitive monitoring type. For example, the field name of the to-be-processed text node is "user ID", which does not belong to the preset sensitive field, but because the sensitive configuration item parameter ("data-mask-off" attribute) exists, the user can directly switch between "data-mask-off=false" and "data-mask-off=true" options, and according to the needs, the node content data corresponding to "user ID" is displayed in the plaintext form or the mask form.

[0043] Finally, when the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter does not exist, the text length parameter of the to-be-processed text node needs to be determined according to the node attribute information, and the text length parameter is compared with the preset length threshold. The text length parameter refers to the character length of the node content data of the to-be-processed text node, and the preset length threshold is a length threshold value that is used to represent the need for monitoring processing and is set in advance. If the text length parameter has not reached the preset length threshold, the node processing type of the to-be-processed node is determined as the plaintext processing type. If the text length parameter reaches the preset length threshold, the node processing type of the to-be-processed node is determined as the sensitive monitoring type. That is, the node content data with a text length parameter less than the preset length threshold is displayed in the plaintext form, and the node content data with a text length parameter greater than or equal to the preset length threshold needs to be displayed in the mask form according to subsequent conditions. In addition, when the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter does not exist, specific types of node content data can also be monitored as needed, such as the to-be-processed text node of the "table" type node content data being determined as the sensitive monitoring type.

[0044] The embodiment can adapt to complex business scenarios by performing multi-level judgment on the to-be-processed text node at the field level (preset sensitive field), the configuration item level (first and second sensitive configuration items), and the content level (text length). At the same time, the preset sensitive field is directly desensitized, the non-sensitive field can also be configured as the sensitive monitoring type for real-time monitoring, and the strategy can also be dynamically adjusted by modifying the preset sensitive field or the sensitive configuration item, thereby improving the flexibility of desensitization processing.

[0045] In an embodiment, the to-be-processed node comprises a to-be-processed input box node, and the node processing type comprises a desensitization processing type, a plaintext processing type, and a sensitive monitoring type; as Figure 5 As shown in the figure, in step S30, that is, determining the node processing type of each to-be-processed node according to the node attribute information, comprises: S307, determining the editing attribute parameter and the input box field parameter of the to-be-processed input box node according to the node attribute information; S308, when the editing attribute parameter is a non-editable attribute, and the input box field parameter of the to-be-processed input box node belongs to a preset sensitive field, determining the node processing type of the to-be-processed node as the desensitization processing type; S309, when the editing attribute parameter is a non-editable attribute, and the input box field parameter of the to-be-processed input box node does not belong to a preset sensitive field, determining the node processing type of the to-be-processed node as the plaintext processing type; S310, when the editing attribute parameter is an editable attribute, determining the node processing type of the to-be-processed node as the sensitive monitoring type.

[0046] Understandably, the to-be-processed node comprises a to-be-processed input box node, which means that the text content data in the to-be-processed node is displayed in the form of an input box. When the to-be-processed node is a to-be-processed input box node, first, the editing attribute parameter and the input box field parameter of the to-be-processed input box node need to be determined according to the node attribute information. The editing attribute parameter is an attribute used to represent whether the node content data in the to-be-processed input box node can be edited. The input box field parameter is the field name corresponding to the node content data in the to-be-processed input box node.

[0047] Then, if the editing attribute parameter is an editable attribute, the node processing type of the to-be-processed node is directly determined as the sensitive monitoring type. If the editing attribute parameter is a non-editable attribute, it is further needed to judge whether the input box field parameter belongs to a preset sensitive field. When the input box field parameter belongs to a preset sensitive field, the node processing type of the to-be-processed node is determined as the desensitization processing type. When the input box field parameter does not belong to a preset sensitive field, the node processing type of the to-be-processed node is determined as the plaintext processing type.

[0048] This embodiment is aimed at the to-be-processed input box node. The editable node content data is enabled for sensitive monitoring, and the non-editable node content data is selected for desensitization or plaintext display according to the field sensitivity, which dynamically adapts to the desensitization processing demand in different scenarios and guarantees the rationality of the desensitization processing.

[0049] In an embodiment, as Figure 6 As shown, step S30, i.e., after determining the node processing type of each of the to-be-processed nodes according to the node attribute information, further includes: S311, when the node processing type of the to-be-processed node is the sensitive monitoring type, determining the to-be-processed node as a monitoring processing node; S312, if attribute update information of the monitoring processing node is received, determining the monitoring node processing type of the monitoring processing node according to the attribute update information through the target desensitization plug-in; S313, when the monitoring node processing type is the desensitization processing type, performing mask processing on the node content data of the monitoring processing node according to a preset mask rule through the target desensitization plug-in, obtaining node desensitization data, and replacing and displaying the node content data of the monitoring processing node in the target page as the node desensitization data.

[0050] Understandably, when the node processing type of the to-be-processed node is the sensitive monitoring type, the to-be-processed node is determined as a monitoring processing node. The monitoring processing node refers to a page element node that needs to re-evaluate whether desensitization processing is needed when the node content data changes. When the node content data of the monitoring processing node changes, the client generates attribute update information according to the changed data, and sends the attribute update information to the server. The attribute update information refers to the content after the node attribute information changes. If the server receives the attribute update information of the monitoring processing node, the monitoring node processing type of the monitoring processing node is determined according to the attribute update information through the target desensitization plug-in. The monitoring node processing type is kind information used to represent whether the monitoring processing node needs desensitization processing after the node content data changes, and the monitoring node processing type includes the desensitization processing type and the plaintext processing type. When the monitoring node processing type is the desensitization processing type, the node content data of the monitoring processing node is processed through the target desensitization plug-in according to a preset mask rule, node desensitization data is obtained, and the node content data of the monitoring processing node in the target page is replaced and displayed as the node desensitization data. The node desensitization data refers to the result of mask processing after the node content data changes. When the monitoring node processing type is the plaintext processing type, the node content data of the monitoring processing node in the target page remains unchanged.

[0051] In a specific embodiment, the following code instructions are used for the sensitive configuration item parameter "data-mask-off" of the monitoring processing node: maskObserver = new MutationObserver(mutationsList =>{ for (const mutation of mutationsList) { / / Handling attribute changes if (mutation.type === 'attributes'&&mutation.attributeName === 'data-mask-off') { / / Only process the data-mask-off attribute } }); An observer named `maskObserver` was created. When a change is observed in a monitored node of the DOM tree, the callback function receives a `mutationsList` parameter containing all records of the changes. If the change type is `attributes` and the changed attribute name is `data-mask-off`, the corresponding operation is executed. For example, if the field name of the monitored node is "User ID" and there is a sensitive configuration parameter ("data-mask-off" attribute), the user can directly switch between the options "data-mask-off=false" and "data-mask-off=true". When the "data-mask-off" attribute is switched to "data-mask-off=false", the node content data corresponding to "User ID" needs to be displayed in masked form, i.e., the monitored node processing type is masked. When the "data-mask-off" attribute is switched to "data-mask-off=true", the node content data corresponding to "User ID" needs to be displayed in plaintext form, i.e., the monitored node processing type is plaintext processing.

[0052] This embodiment not only masks sensitive information when the page is first loaded, but also monitors page changes in real time, realizing a real-time dynamic masking mechanism. When the page changes due to user operations, data updates, or other reasons, it can dynamically identify newly emerging sensitive information and mask it, ensuring that sensitive information displayed on the front-end page is effectively protected at all times, thus improving the flexibility and comprehensiveness of information security protection.

[0053] In one embodiment, such as Figure 7 As shown, step S40, which involves replacing the node content data of the element node to be processed in the target page with the desensitized node data, includes: S401. If there is a new element node in the target page, the new node attribute information of the new element node is obtained through the target desensitization plugin, and the new node processing type of the new element node is determined according to the new node attribute information. S402. When the new node processing type of the newly added element node is the desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the newly added element node according to the preset masking rules to obtain the desensitized data of the newly added node, and replaces the node content data of the newly added element node in the target page with the desensitized data of the newly added node.

[0054] Understandably, when a new element node appears on the target page, the client generates new node attribute information based on the new element node and sends this information to the server. A new element node refers to a newly added page element node, and new node attribute information refers to the node attribute information of the new element node. If the server receives the new node attribute information, it determines the new node processing type based on this information using the target desensitization plugin. The new node processing type is information indicating whether the new element node needs desensitization processing; it includes desensitization processing type, plaintext processing type, and sensitivity monitoring type. When the new node processing type is desensitization processing type, the target desensitization plugin masks the node content data of the new element node according to preset masking rules to obtain desensitized data, and then replaces the node content data of the new element node on the target page with this desensitized data. Desensitized data refers to the result of masking the node content data of the new element node.

[0055] In one specific embodiment, the following code instructions are used to monitor newly added element nodes: maskObserver = new MutationObserver(mutationsList =>{ for (const mutation of mutationsList) { / / Handling newly added element nodes if (mutation.type === 'childList') { mutation.addedNodes.forEach(node ​​=>{ / / do something }); } An observer named maskObserver is created. When a new element node is observed in the DOM tree, the callback function receives a mutationsList parameter containing records of all changes. If the change type is childList (addition of child nodes), the newly added nodes are traversed, and the corresponding operation is performed on the newly added element node.

[0056] In addition to masking sensitive information when the page is first loaded, this embodiment can also monitor changes in page element nodes in real time and promptly mask sensitive information in newly appearing page element nodes.

[0057] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0058] In one embodiment, a page-sensitive information processing apparatus is provided, which corresponds one-to-one with the page-sensitive information processing methods described in the above embodiments. For example... Figure 8 As shown, the sensitive information processing device for this page includes an indicator parameter acquisition module 10, a node traversal and filtering module 20, a processing type determination module 30, and a mask processing module 40. Detailed descriptions of each functional module are as follows: The indicator parameter acquisition module 10 is used to receive page loading requests and obtain the loading indicator parameters of the target page according to the page loading requests. The node traversal and filtering module 20 is used to initialize the target desensitization plugin when the target indicator parameter exists in the loaded indicator parameter, and to traverse and filter the nodes to be processed from all page element nodes of the target page through the target desensitization plugin. The processing type determination module 30 is used to obtain the node attribute information of each node to be processed through the target desensitization plugin, and determine the node processing type of each node to be processed based on the node attribute information. The masking module 40 is used to mask the node content data of the node to be processed according to a preset masking rule by the target masking plugin when the node processing type of the node to be processed is the desensitization processing type, to obtain node desensitized data, and to replace the node content data of the node to be processed in the target page with the node desensitized data.

[0059] In one embodiment, the node traversal filtering module 20 includes: The task list generation unit is configured to generate a node traversal task list corresponding to all page element nodes of the target page by using the target desensitization plug-in; one node traversal task in the node traversal task list corresponds to one page element node; The node to be screened determination unit is configured to select one node traversal task that has not been executed from the node traversal task list when the target page is in an idle state, and determine a page element node corresponding to the selected node traversal task as a node to be screened. The node label screening unit is configured to obtain a node label of the node to be screened, determine whether the node to be screened meets a preset screening condition based on the node label, determine the node to be screened that meets the preset screening condition as a node to be processed, and select a next node traversal task that has not been executed from the node traversal task list until there is no node traversal task that has not been executed in the node traversal task list.

[0060] In an embodiment, the node traversal screening module 20 further includes: The target screening label determination unit is configured to obtain a parent node processing type corresponding to the node to be screened when the node label belongs to a target screening label in the preset screening condition. The parent node processing type determination unit is configured to determine whether the node to be screened includes text content data when the parent node processing type is not a sensitive monitoring type. The node to be processed determination unit is configured to determine the node to be screened as a node to be processed when the node to be screened includes text content data.

[0061] In an embodiment, the processing type determination module 30 includes: The text field parameter determination unit is configured to determine a text field parameter of the node to be processed based on the node attribute information. The first desensitization processing type determination unit is configured to determine the node processing type of the node to be processed as a desensitization processing type when the text field parameter of the node to be processed belongs to a preset sensitive field. The second desensitization processing type determination unit is configured to determine the node processing type of the node to be processed as a desensitization processing type when the text field parameter of the node to be processed does not belong to a preset sensitive field and there is a sensitive configuration item parameter, and the sensitive configuration item parameter is a first sensitive configuration item. The first sensitive monitoring type determination unit is configured to determine the node processing type of the node to be processed as a sensitive monitoring type when the text field parameter of the node to be processed does not belong to a preset sensitive field and there is a sensitive configuration item parameter, and the sensitive configuration item parameter is a second sensitive configuration item. The first plaintext processing type determination unit is configured to determine a text length parameter of the text node to be processed according to the node attribute information when the text field parameter of the text node to be processed does not belong to the preset sensitive field and no sensitive configuration item parameter exists, and determine the node processing type of the text node to be processed as a plaintext processing type if the text length parameter has not reached a preset length threshold. The second sensitive monitoring type determination unit is configured to determine a text length parameter of the text node to be processed according to the node attribute information when the text field parameter of the text node to be processed does not belong to the preset sensitive field and no sensitive configuration item parameter exists, and determine the node processing type of the text node to be processed as a sensitive monitoring type if the text length parameter has reached a preset length threshold.

[0062] In an embodiment, the processing type determination module 30 further includes: The input box attribute parameter acquisition unit is configured to determine an editing attribute parameter and an input box field parameter of the input box node to be processed according to the node attribute information. The third desensitization processing type determination unit is configured to determine the node processing type of the input box node to be processed as a desensitization processing type when the editing attribute parameter is an uneditable attribute and the input box field parameter of the input box node to be processed belongs to the preset sensitive field. The second plaintext processing type determination unit is configured to determine the node processing type of the input box node to be processed as a plaintext processing type when the editing attribute parameter is an uneditable attribute and the input box field parameter of the input box node to be processed does not belong to the preset sensitive field. The third sensitive monitoring type determination unit is configured to determine the node processing type of the input box node to be processed as a sensitive monitoring type when the editing attribute parameter is an editable attribute.

[0063] In an embodiment, the processing type determination module 30 further includes: The monitoring processing node determination unit is configured to determine the text node to be processed as a monitoring processing node when the node processing type of the text node to be processed is a sensitive monitoring type. The monitoring node processing type determination unit is configured to determine a monitoring node processing type of the monitoring processing node according to attribute update information of the monitoring processing node through the target desensitization plug-in if the attribute update information is received. The monitoring node mask processing unit is configured to perform mask processing on node content data of the monitoring processing node according to a preset mask rule through the target desensitization plug-in when the monitoring node processing type is a desensitization processing type, to obtain node desensitization data, and replace and display the node content data of the monitoring processing node in the target page as the node desensitization data.

[0064] In an embodiment, the mask processing module 40 comprises: The newly-added node processing type determination unit is configured to, if the target page contains a newly-added element node, acquire newly-added node attribute information of the newly-added element node through the target desensitization plug-in, and determine a newly-added node processing type of the newly-added element node according to the newly-added node attribute information. The newly-added node mask processing unit is configured to, when the newly-added node processing type of the newly-added element node is the desensitization processing type, perform mask processing on node content data of the newly-added element node according to a preset mask rule through the target desensitization plug-in, to obtain newly-added node desensitization data, and replace and display the node content data of the newly-added element node in the target page as the newly-added node desensitization data.

[0065] The specific limitations of the page sensitive information processing apparatus can refer to the limitations of the page sensitive information processing method described above, which will not be repeated here. Each module in the above page sensitive information processing apparatus can be realized by software, hardware, and combinations thereof, in whole or in part. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0066] In an embodiment, a computer device is provided, which can be a server, and the internal structure diagram thereof can be as shown in Figure 9 The computer device comprises a processor, a memory, a network interface, and a database connected through a system bus. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a readable storage medium and an internal memory. The readable storage medium stores an operating system, computer readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer readable instructions in the readable storage medium. The database of the computer device is configured to store data related to the page sensitive information processing method. The network interface of the computer device is configured to communicate with an external terminal through a network connection. The computer readable instructions are executed by the processor to implement a page sensitive information processing method. The readable storage medium provided in the embodiment comprises a non-volatile readable storage medium and a volatile readable storage medium.

[0067] In an embodiment, a computer device is provided, comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, and the processor executes the computer readable instructions to implement the following steps: receiving a page loading request, and acquiring loading index parameters of a target page according to the page loading request; When a target indicator parameter exists in the loading indicator parameters, the target desensitization plugin is initialized, and the target desensitization plugin is used to traverse and filter out the nodes to be processed from all page element nodes of the target page. The node attribute information of each node to be processed is obtained through the target desensitization plugin, and the node processing type of each node to be processed is determined based on the node attribute information. When the node processing type of the node to be processed is the desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the node to be processed according to the preset masking rules to obtain node desensitized data, and replaces the node content data of the node to be processed in the target page with the node desensitized data.

[0068] In one embodiment, one or more computer-readable storage media storing computer-readable instructions are provided. The readable storage media provided in this embodiment include non-volatile readable storage media and volatile readable storage media. The readable storage media stores computer-readable instructions, which, when executed by one or more processors, perform the following steps: Receive a page loading request and obtain the loading index parameters of the target page based on the page loading request; When a target indicator parameter exists in the loading indicator parameters, the target desensitization plugin is initialized, and the target desensitization plugin is used to traverse and filter out the nodes to be processed from all page element nodes of the target page. The node attribute information of each node to be processed is obtained through the target desensitization plugin, and the node processing type of each node to be processed is determined based on the node attribute information. When the node processing type of the node to be processed is the desensitization processing type, the target desensitization plugin performs masking processing on the node content data of the node to be processed according to the preset masking rules to obtain node desensitized data, and replaces the node content data of the node to be processed in the target page with the node desensitized data.

[0069] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by instructing related hardware with computer-readable instructions. These computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When executed, these computer-readable instructions can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0070] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0071] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method of processing page sensitive information, characterized by, The method comprises the following steps: receiving a page loading request, and obtaining a loading index parameter of a target page according to the page loading request; when the loading index parameter contains a target index parameter, initializing a target desensitization plug-in, and screening a to-be-processed node from all page element nodes of the target page through the target desensitization plug-in; obtaining node attribute information of each to-be-processed node through the target desensitization plug-in, and determining a node processing type of each to-be-processed node according to the node attribute information; when the node processing type of the to-be-processed node is a desensitization processing type, performing mask processing on node content data of the to-be-processed node according to a preset mask rule through the target desensitization plug-in, obtaining node desensitization data, and replacing and displaying the node content data of the to-be-processed node in the target page as the node desensitization data.

2. The page sensitive information processing method of claim 1, wherein, The method comprises the following steps: generating a node traversal task list corresponding to all page element nodes of the target page through the target desensitization plug-in; one node traversal task in the node traversal task list corresponds to one page element node; when the target page is in an idle state, selecting one unexecuted node traversal task from the node traversal task list, and determining a page element node corresponding to the selected node traversal task as a to-be-screened node; obtaining a node label of the to-be-screened node, judging whether the to-be-screened node meets a preset screening condition based on the node label, determining the to-be-screened node meeting the preset screening condition as a to-be-processed node, and selecting a next unexecuted node traversal task from the node traversal task list until there is no unexecuted node traversal task in the node traversal task list.

3. The page sensitive information processing method of claim 2, wherein, The method comprises the following steps: when the node label belongs to a target screening label in the preset screening condition, obtaining a parent node processing type corresponding to the to-be-screened node; when the parent node processing type is not a sensitive monitoring type, judging whether the to-be-screened node includes text content data; when the to-be-screened node includes text content data, determining the to-be-screened node as a to-be-processed node.

4. The page sensitive information handling method of claim 1, wherein, The to-be-processed node includes a to-be-processed text node, and the node processing type includes a desensitization processing type, a plaintext processing type and a sensitive monitoring type. The method comprises the following steps: determining a text field parameter of the to-be-processed text node according to the node attribute information; when the text field parameter of the to-be-processed text node belongs to a preset sensitive field, determining the node processing type of the to-be-processed node as the desensitization processing type; when the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and there is a sensitive configuration item parameter, if the sensitive configuration item parameter is a first sensitive configuration item, determining the node processing type of the to-be-processed node as the desensitization processing type; When the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter exists, if the sensitive configuration item parameter is a second sensitive configuration item, the node processing type of the to-be-processed node is determined as a sensitive monitoring type; When the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter does not exist, the text length parameter of the to-be-processed text node is determined according to the node attribute information, if the text length parameter has not reached a preset length threshold, the node processing type of the to-be-processed node is determined as a plaintext processing type; When the text field parameter of the to-be-processed text node does not belong to the preset sensitive field, and the sensitive configuration item parameter does not exist, the text length parameter of the to-be-processed text node is determined according to the node attribute information, if the text length parameter reaches the preset length threshold, the node processing type of the to-be-processed node is determined as a sensitive monitoring type.

5. The page sensitive information handling method of claim 1, wherein, The to-be-processed node includes a to-be-processed input box node, and the node processing type includes a desensitization processing type, a plaintext processing type and a sensitive monitoring type; The node attribute information includes an editing attribute parameter and an input box field parameter of the to-be-processed input box node. When the editing attribute parameter is an uneditable attribute, and the input box field parameter of the to-be-processed input box node belongs to the preset sensitive field, the node processing type of the to-be-processed node is determined as the desensitization processing type; When the editing attribute parameter is an uneditable attribute, and the input box field parameter of the to-be-processed input box node does not belong to the preset sensitive field, the node processing type of the to-be-processed node is determined as the plaintext processing type; When the editing attribute parameter is an editable attribute, the node processing type of the to-be-processed node is determined as the sensitive monitoring type. After the node processing type of each to-be-processed node is determined according to the node attribute information, the method further includes:

6. The page sensitive information handling method of claim 1, wherein, When the node processing type of the to-be-processed node is the sensitive monitoring type, the to-be-processed node is determined as a monitoring processing node; If attribute update information of the monitoring processing node is received, a monitoring node processing type of the monitoring processing node is determined according to the attribute update information through the target desensitization plug-in; When the monitoring node processing type is the desensitization processing type, node content data of the monitoring processing node is masked according to a preset masking rule through the target desensitization plug-in, to obtain node desensitization data, and the node content data of the monitoring processing node in the target page is replaced and displayed as the node desensitization data. After the node content data of the to-be-processed node in the target page is replaced and displayed as the node desensitization data, the method further includes:

7. The page sensitive information handling method of claim 1, wherein, If there is a new element node in the target page, new node attribute information of the new element node is obtained through the target desensitization plug-in, and a new node processing type of the new element node is determined according to the new node attribute information. ​ When the new node processing type of the new element node is a desensitization processing type, the node content data of the new element node is processed by the target desensitization plug-in according to a preset mask rule to obtain new node desensitization data, and the node content data of the new element node in the target page is replaced and displayed as the new node desensitization data.

8. A page sensitive information processing apparatus, characterized by comprising: Comprise: An index parameter acquisition module is configured to receive a page loading request, and acquire loading index parameters of a target page according to the page loading request; A node traversal and screening module is configured to initialize a target desensitization plug-in when a target index parameter exists in the loading index parameters, and screen out to-be-processed nodes from all page element nodes of the target page through the target desensitization plug-in; A processing type determination module is configured to acquire node attribute information of each to-be-processed node through the target desensitization plug-in, and determine a node processing type of each to-be-processed node according to the node attribute information; A mask processing module is configured to, when the node processing type of the to-be-processed node is a desensitization processing type, process node content data of the to-be-processed node by the target desensitization plug-in according to a preset mask rule to obtain node desensitization data, and replace and display the node content data of the to-be-processed node in the target page as the node desensitization data.

9. A computer device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein, The processor executes the computer readable instructions to implement the page sensitive information processing method in any one of claims 1 to 7.

10. A computer-readable storage medium having stored computer-readable instructions, wherein, The computer readable instructions are executed by one or more processors to cause the one or more processors to perform the page sensitive information processing method in any one of claims 1 to 7.

Images