A method for managing heterogeneous dynamic intranets with fixed IP roles
By introducing a fixed IP role-based heterogeneous dynamic management method for the enterprise intranet, the problems of cross-system consistency verification and dynamic risk scoring were solved. This enabled real-time reconstruction and field-level sharing of pages and APIs under risk conditions, thereby improving the security and data interoperability of the enterprise intranet.
Patent Information
- Application Number
- CN202611133767.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-29
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies struggle to achieve cross-system consistency verification under fixed IPs and roles within enterprise intranets. Static configuration of page entry points and API call chains, coupled with a lack of dynamic risk scoring and field-level shared control, leads to inconsistent identity semantics, inaccurate risk assessment, and incomplete cross-system handling.
By introducing a fixed IP role-based heterogeneous dynamic management method into the enterprise intranet, and employing identity fusion, six-tuple consistency verification, and dynamic risk scoring, a set of target pages and API call chains are generated to achieve field-level shared control and cross-system auditing.
It enables real-time adjustment of pages and interfaces based on risks within the enterprise intranet, improving the accuracy of anomaly identification, reducing false positives in single systems, enhancing data interoperability and privacy protection, and strengthening audit traceability capabilities.
Smart Images

Figure CN123074764A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of enterprise intranet heterogeneous system management technology, and in particular to a method for dynamic management of heterogeneous intranet systems with fixed IP roles. Background Technology
[0002] In typical enterprise environments, production execution systems, financial management systems, video surveillance systems, endpoint protection systems, endpoint control systems, and auditing systems are often built by different vendors, with independent account systems, interface fields, permission models, page entry points, and log formats. Although enterprises typically set up fixed IPs, fixed roles, unified accounts, or single sign-on, these mechanisms often remain at the level of identity access or static authorization, making it difficult to unify "people, devices, fixed IPs, locations, business actions, time, endpoint security status, and auditing behavior" into a single access decision.
[0003] Patent CN110334489A discloses a unified identity authentication system and method, providing modules such as single sign-on, user management, account synchronization, permission management, unified auditing, and secure application access. It can also determine permissions based on user identity, authentication method, accessed applications, and API interfaces. This solution focuses on unified authentication and a unified authorization entry point, which can alleviate the problem of scattered logins across multiple applications. However, its emphasis remains on account, sub-account, and resource permission management. It does not address the need for a six-factor consistency check across production, finance, video, endpoint protection, endpoint control, and auditing systems within an intranet environment with fixed IPs and roles, nor does it generate page sets and API call orchestration chains in real time based on risk scores.
[0004] Patent CN118540114A discloses a terminal environment dynamic detection system based on dynamic access control. This system performs real-time dynamic monitoring of user identity, terminal environment, and user behavior during access. It adds secondary authentication for accesses that do not meet security conditions and records access logs for auditing and traceability. While this solution can improve the security of terminal access to business systems, it focuses on terminal access environment detection, gray-scale traffic handling, and user lifecycle log auditing. It does not establish a standard six-tuple for fixed IP, fixed role, video location, business actions, and time windows, nor does it convert risk assessment results into dynamic generation of cross-business system page and API call chains.
[0005] Patent CN113472758B discloses an access control method, device, terminal, connector, and storage medium. The client can perform baseline checks, application authorization, and continuous security detection, and add identifiers to application access requests. Application-level authorization detection is performed through a controller and gateway. This solution is suitable for protecting application access channels and terminal security baselines, but it does not address the joint orchestration of pages, fields, API write capabilities within multiple business systems, or cross-system events. Furthermore, it does not disclose an evidence chain structure centered on an identity semantic graph that records the source of risk scoring, orchestration results, and coordinated handling results.
[0006] Therefore, the existing technology has the following drawbacks:
[0007] 1. Static role authorization cannot express real-time risks within the intranet: Although enterprises can pre-define fixed roles such as ordinary employees, administrators, auditors, and leaders, the risks of the same role vary greatly under different terminals, IPs, locations, and business actions. Static roles cannot adjust page and interface capabilities in real time.
[0008] 2. Fixed IP addresses are only used as access whitelists and are not involved in cross-system risk reasoning: Existing systems typically only determine whether the accessing IP address is in the whitelist, lacking joint verification of consistency with employee primary identity, terminal device, video location, audit behavior, and business actions.
[0009] 3. Lack of unified identity semantics between heterogeneous systems: Production, finance, video, security and audit systems maintain account, device, log and permission fields respectively. The identity association of the same employee in multiple systems is unstable, which makes permission judgment and anomaly location require manual splicing.
[0010] 4. Page entry points and API call chains are mostly statically configured: Unified portals or single sign-on usually provide fixed redirects, making it difficult to generate read-only pages, secondary verification pages, risk explanation pages, review pages, or blocking policies in real time based on risk scores and task context.
[0011] 5. Lack of role-driven field-level control for data sharing: Production volume, overtime hours, financial amount, approval status and audit logs may be repeatedly maintained in multiple systems, and the existing solution is difficult to achieve "data collection once, output different shared views according to roles".
[0012] 6. Incomplete chain of evidence for handling and auditing: Existing logs usually only record logins, operations or alarms within a certain system, making it difficult to form a cross-system chain of evidence that includes identity fusion, risk scoring sources, page layout, API calls, coordinated handling and manual review results.
[0013] In summary, existing technologies cover partial capabilities such as unified identity authentication, zero-trust dynamic access, endpoint security detection, centralized management of heterogeneous devices, risk quantification, and audit traceability. However, existing technologies do not provide a comprehensive solution that, under the premise of pre-configured fixed IPs and roles within the enterprise intranet, uniformly maps data from the production execution system, financial management system, video surveillance system, endpoint protection system, endpoint control system, and audit system into an employee identity semantic graph. This solution then performs cross-system consistency verification based on a six-tuple of "personnel, device, IP, location, business action, and time," and finally transforms the risk results into a real-time set of page collections, API call chains, field-level shared scopes, and a chain of evidence for coordinated action. Summary of the Invention
[0014] This invention primarily addresses technical issues in existing technologies, such as static authorization for fixed roles, fixed IPs used only for access whitelists, inconsistent identity semantics across heterogeneous systems, inability to adjust page entry points and API call chains in real time according to risk, and incomplete field-level sharing and cross-system handling traces. It proposes a dynamic management method for heterogeneous intranet systems with fixed IPs and roles. Under the deployment conditions of fixed IPs, fixed roles, and enterprise intranets, this method achieves unified identity fusion, risk consistency verification, dynamic access orchestration, field-level sharing control, and cross-system auditing traces for multiple heterogeneous business and security systems. This transforms the platform from a mere unified login portal into an integrated management hub capable of adjusting pages, interfaces, and handling actions in real time according to risk.
[0015] This invention provides a method for managing heterogeneous dynamic intranet structures with fixed IP roles, comprising the following processes:
[0016] Step 1: The server receives the employee's access request, obtains the verification information entered by the employee in the access verification box, and identifies whether the access request is a critical access request. If it is a critical access request, identity fusion is performed; if it is not a critical access request, the access verification box is closed.
[0017] Step 2: Collect data related to the current visitor and their associated objects from the heterogeneous systems within the enterprise's intranet, and perform field standardization and event normalization; the associated objects include devices, fixed IPs, locations, business actions, time windows, terminal security status, and audit events;
[0018] Step 3: First, perform baseline verification for fixed roles and fixed IPs. If the requester's fixed role is not in the preset role template, or the accessing IP is not in the preset fixed IP whitelist, a baseline deviation result will be generated. For highly sensitive access requests that hit the preset blocking rules, access will be blocked or manual review will be performed.
[0019] Step 4: Based on the personnel primary identity, standardized fields, and normalized events formed in Steps 1 to 3, generate or update the personnel role semantic graph, and extract the six-tuple of the current access request; the six-tuple includes personnel P, device D, IP, location L, business action A, and time T;
[0020] Step 5: Perform six-tuple consistency verification and terminal security status verification respectively; the six-tuple consistency verification includes fixed role consistency verification, device consistency verification, IP consistency verification, location consistency verification, service consistency verification, and time consistency verification; the terminal security status verification includes terminal protection status verification, virus database status verification, patch status verification, peripheral device status verification, and terminal management status verification; after completing the consistency verification and terminal security status verification, calculate the dynamic risk score and determine the risk score range;
[0021] Step 6: Based on the risk score range obtained in Step 5, the six-tuple consistency verification result, the terminal security status verification result, and the task context, determine the risk range, calculate the orchestration score, and generate the target page set based on the orchestration score.
[0022] Step 7: Based on the preset fixed roles, field permission matrix and the determined risk range, output the field-level shared view; and perform hierarchical processing.
[0023] Furthermore, step 1 includes the following steps 101 to 103:
[0024] Step 101: When a person requests access to any business page or API in the heterogeneous intranet system, the server receives the access request, generates an access verification box, and obtains the verification information entered by the person in the access verification box; the verification information includes, but is not limited to, account, fixed role, access target, business action, current terminal, current IP, and necessary secondary confirmation information.
[0025] Step 102: The server identifies whether the access request is a critical access request based on whether the verification information involves write-type APIs, highly sensitive fields, fund approval, production data modification, batch export, audit record query, terminal control instructions, or abnormal work order review; the critical access requests include, but are not limited to, financial approval, production data modification, batch export, audit record query, terminal control instructions, and abnormal work order review.
[0026] Step 103: If it is a critical access request, the server calculates the identity fusion matching score and performs identity fusion based on the identity fusion matching score; if it is not a critical access request, the server closes the access verification box and ends the critical access verification process.
[0027] The identity fusion matching score is calculated using the following formula:
[0028] MatchScore = w1*S_id + w2*S_mobile + w3*S_device + w4*S_ip + w5*S_org+ w6*S_time;
[0029] wherein S_id denotes personnel number matching degree, S_mobile denotes contact information matching degree, S_device denotes terminal binding matching degree, S_ip denotes fixed IP matching degree, S_org denotes organization affiliation matching degree, S_time denotes historical access time sequence matching degree, and w1 to w6 are weights that satisfy w1+w2+w3+w4+w5+w6=1;
[0030] The identity fusion is performed according to the identity fusion matching score: when MatchScore>=T_match_high, the server maps multiple accounts of the intranet heterogeneous systems to the same main personnel identity; when T_match_low<=MatchScore<T_match_high, the server puts the relevant accounts into a manual review or low-trust pending confirmation state; when MatchScore<T_match_low, the server does not perform automatic fusion; wherein T_match_high denotes the first identity fusion threshold, and T_match_low denotes the second identity fusion threshold.
[0031] Further, the enterprise intranet heterogeneous systems include, but are not limited to, six major business systems: a production execution system, a financial management system, a video monitoring system, a terminal protection system, a terminal management and control system, and an audit system.
[0032] Further, in step 2, the field standardization includes: establishing a unified data dictionary and a field mapping table, and mapping the personnel number, login account, terminal number, fixed IP, department post, fixed role, camera area, business action, log time and alarm type in different business systems into unified fields; converting the field format, coding rule, time format, organization hierarchy and enumeration value, so that data with the same meaning uses the same name, unit and value range;
[0033] The event normalization includes: converting the original events into unified event types, and supplementing each event with tags of main personnel identity, fixed role, device, fixed IP, location, business action and time; the original events include, but are not limited to, login, approval, query, export, writing, terminal alarm, video position change and audit anomaly.
[0034] Further, step 5 includes the following steps 501 to 504:
[0035] Step 501: Perform hexad consistency check;
[0036] Step 502: Perform terminal security status check;
[0037] Step 503: Calculate the dynamic risk score according to the following formula:
[0038] RiskScore = a1*R_role + a2*R_device + a3*R_endpoint + a4*R_ip + a5*R_location + a6*R_time + a7*R_audit + a8*R_business - a9*R_trust;
[0039] Wherein, RiskScore is the dynamic risk score, R_role is the fixed role deviation risk factor; R_device is the non-compliant device risk factor; R_endpoint is the terminal protection anomaly risk factor; R_ip is the fixed IP deviation risk factor; R_location is the location conflict risk factor; R_time is the time window deviation risk factor; R_audit is the audit anomaly risk factor; R_business is the business sensitivity risk factor; R_trust is the historical credibility factor;
[0040] Step 504: Determine a risk score interval according to the dynamic risk score;
[0041] 0<=RiskScore<T_low is the first risk score interval;
[0042] T_low<=RiskScore<T_mid is the second risk score interval;
[0043] T_mid<=RiskScore<T_high is the third risk score interval;
[0044] RiskScore>=T_high is the fourth risk score interval;
[0045] Wherein, T_low represents the first dynamic risk score threshold, T_mid represents the second dynamic risk score threshold, and T_high represents the third dynamic risk score threshold.
[0046] Further, the step 6 includes the following steps 601 to 603:
[0047] Step 601: Perform risk interval judgment according to the risk score interval obtained in step 5, the hexad consistency check result, the terminal security status check result and the task context;
[0048] When 0<=RiskScore<T_low and the fixed role consistency check, IP consistency check and device consistency check are all passed, the risk interval is low risk, the normal working page is entered, and APIs matching the fixed role are allowed to be called;
[0049] When T_low<=RiskScore<T_mid, or there is an interpretable slight deviation, the risk interval is medium risk, and a risk explanation page, an access reminder page, a secondary confirmation page or a read-only page is generated;
[0050] When T_mid<=RiskScore<T_high, or there is a multi-dimensional conflict but no blocking rule is triggered, the risk interval is high risk, and degraded access, write API restriction, secondary confirmation requirement or manual review push is executed;
[0051] When RiskScore>=T_high, or the combination rule of fixed IP anomaly, highly sensitive service action and unauthorized device is triggered, the risk interval is extremely high risk, access is blocked, and terminal control, audit alarm and manual review are triggered;
[0052] Step 602, calculating an orchestration score for the candidate page or candidate function module m according to the following formula:
[0053] RouteScore(m) = b1*F_role(m) + b2*F_task(m) + b3*F_risk(m) + b4*F_urgent(m) - b5*F_cost(m);
[0054] Wherein F_role(m) is the role adaptability, F_task(m) is the task relevance, F_risk(m) is the risk permission, F_urgent(m) is the event urgency, and F_cost(m) is the cross-system dependency cost;
[0055] Step 603, generating a target page set according to the orchestration score and the dynamic risk score;
[0056] When the candidate page or candidate module is a normal page or a read-only module, and RouteScore(m)>=T_route_page, add it to the target page set; when the candidate page or candidate module involves a write-type API or a writable module, and RouteScore(m)>=T_route_write and RiskScore<T_mid, add it to the target page set; when the candidate page or candidate module involves a highly sensitive write interface, add it to the target page set only if RouteScore(m)>=T_route_write and RiskScore<T_low; when the dynamic risk score does not meet the corresponding write access condition, replace the candidate page or candidate module with a read-only page, a secondary confirmation page or a manual review page.
[0057] Further, in step 7, the performing hierarchical processing according to the risk score interval, the dynamic risk score, the orchestration score and the target page set includes:
[0058] When the risk interval is low risk, access is allowed normally, and basic logs are recorded;
[0059] When the risk interval is medium risk, access is prompted, a risk warning is displayed and a risk explanation is recorded;
[0060] When the risk interval is high risk, the first processing level executes degraded access, restricts write APIs and requires secondary confirmation; the second processing level of high risk executes read-only access, and only displays necessary pages and read-only data;
[0061] When the risk interval is extremely high risk, access is blocked and linked processing is triggered, including suspending highly sensitive API calls of the target business system, notifying the terminal management and control system to perform network isolation, peripheral disabling or permission convergence, writing high-priority events to the audit system, pushing manual review tasks to the management end, and recording the complete context and processing results in the evidence chain.
[0062] Further, after step 7, the method further includes:
[0063] Step 8: write the personnel main identity fusion result, the sextuple consistency verification result, the terminal security status verification result, the dynamic risk score composition items, the page set, the API call chain, the field sharing scope, the processing action and the manual review conclusion into the evidence chain to form a traceable closed loop;
[0064] The evidence chain at least includes: original identity identifier, fused identity identifier, fixed role verification result, fixed IP verification result, sextuple content, terminal security status, risk score composition items, target page set, API call chain, field sharing scope, processing action, processing time, processing result and review conclusion.
[0065] Correspondingly, the present invention also provides a management system for a fixed IP role-based intranet heterogeneous dynamic management method according to any embodiment of the present invention, comprising:
[0066] The data access adaptation module is used to connect to the production execution system, financial management system, video surveillance system, terminal protection system, terminal control system, and audit system, respectively.
[0067] The field standardization module is used to map fields such as employee ID, login account, terminal ID, fixed IP, department / position, role, camera area, business action, log time, and alarm type from different systems to a unified data dictionary;
[0068] The identity fusion module is used to identify the same person based on personnel number, contact information, device binding, fixed IP, organizational level, job role and historical access time, and output the person's main identity and fusion matching score.
[0069] The Personnel Role Semantic Graph module is used to establish the relationship between personnel and accounts, fixed IPs, authorized devices, fixed roles, job responsibilities, authorized locations, business actions, terminal security status, risk events, and audit logs, with personnel as the central node.
[0070] The six-element consistency verification module is used to extract personnel P, device D, IP, location L, business action A, and time T when a critical access request occurs, and compare them with the baseline relationship in the personnel role semantic graph;
[0071] The dynamic risk scoring module is used to combine fixed role deviation risk, equipment non-compliance risk, terminal protection anomaly risk, fixed IP deviation risk, video location conflict risk, time window deviation risk, audit anomaly risk, business sensitivity risk, and historical credibility to obtain a dynamic risk score.
[0072] The dynamic orchestration module is used to generate a set of target pages and an API call orchestration chain based on role responsibility vectors, task context vectors, dynamic risk scores, candidate page sets, system dependencies, and module costs.
[0073] The field-level shared control module is used to output different data views according to fixed roles and risk status;
[0074] The coordinated response module is used to trigger normal access, alert access, downgraded access, read-only access, secondary confirmation, access blocking, terminal isolation, audit alarms, and manual review based on risk ranges.
[0075] The evidence chain management module is used to record the original identity identifier, the merged identity identifier, the fixed role verification result, the fixed IP verification result, the six-tuple content, the terminal security status, the risk score components, the page set, the API call chain, the field sharing scope, the handling action, and the review conclusion.
[0076] This invention provides a dynamic management method for heterogeneous intranet systems based on fixed IP addresses and fixed roles, which has the following advantages compared with existing technologies:
[0077] 1. Upgrade from a static unified entry point to a dynamic orchestration hub. Existing unified authentication or single sign-on mainly solves the problems of "whether login is possible" and "where to redirect to". This invention further solves the problems of "which pages to display, which APIs to open, which fields to hide, and which actions to trigger under the current risk status".
[0078] 2. Fully utilize the on-site characteristics of fixed IP addresses and fixed roles. For enterprise intranet environments where fixed IP addresses and fixed roles are clearly defined, this invention uses them as a baseline for risk assessment, rather than just as login conditions, thereby improving the accuracy of anomaly identification.
[0079] 3. Six-factor consistency verification reduces false positives in a single system. Operations that appear compliant within a single system may present high risks when considered in conjunction with factors such as device, IP address, location, business actions, time, and auditing practices; this invention can detect such cross-system inconsistencies.
[0080] 4. Pages and APIs are refactored in real time according to risk. The system can provide a complete workbench when the risk is low, generate secondary confirmation and read-only pages when the risk is medium, and block sensitive APIs and transfer to the review process when the risk is high, thus balancing business continuity and security.
[0081] 5. Field-level sharing enhances data interoperability and privacy protection. Production volume, overtime hours, and financial data can be output by role through a unified shared view, reducing duplicate entry and preventing administrators or ordinary employees from seeing pay details or sensitive data that they should not be able to view.
[0082] 6. Closed-loop evidence chain enhances audit traceability. The system not only records login logs, but also identity fusion, risk factors, orchestration results, interface handling, and review results, facilitating post-event accountability and review strategies.
[0083] 7. This invention is applicable to management scenarios where multiple business systems and security systems coexist within an enterprise intranet. The system can be deployed on the enterprise intranet without requiring the business systems to be connected to the internet. Attached Figure Description
[0084] Figure 1 This is a flowchart illustrating the implementation of the fixed IP role-based intranet heterogeneous dynamic management method provided by the present invention.
[0085] Figure 2 This is an architecture diagram of the fixed IP role-based heterogeneous dynamic management method for intranet provided by the present invention. Detailed Implementation
[0086] To make the technical problems solved by this invention, the technical solutions adopted, and the technical effects achieved clearer, the 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 merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings, not all of them.
[0087] Example 1
[0088] like Figure 1-2 As shown in the figure, an embodiment of the present invention provides a method for heterogeneous dynamic management of fixed IP role intranets, which includes the following process:
[0089] Step 1: The server receives the employee's access request, obtains the verification information entered by the employee in the access verification box, and identifies whether the access request is a critical access request. If it is a critical access request, identity fusion is performed; if it is not a critical access request, the access verification box is closed.
[0090] Step 1 includes the following steps 101 to 103:
[0091] Step 101: When a person requests access to any business page or API (Application Programming Interface) in the heterogeneous intranet system, the server receives the access request, generates an access verification box, and obtains the verification information entered by the person in the access verification box; the verification information includes, but is not limited to, account, fixed role, access target, business action, current terminal, current IP, and necessary secondary confirmation information.
[0092] An enterprise's intranet consists of heterogeneous systems, including but not limited to six major business systems: production execution system, financial management system, video surveillance system, endpoint protection system, endpoint control system, and audit system. In practice, these systems can be composed of products from different vendors or self-developed systems.
[0093] Step 102: The server identifies whether the access request is a critical access request based on whether the verification information involves write-type APIs, highly sensitive fields, fund approval, production data modification, batch export, audit record query, terminal control instructions, or abnormal work order review. The critical access requests include, but are not limited to, financial approval, production data modification, batch export, audit record query, terminal control instructions, and abnormal work order review.
[0094] Step 103: If it is a critical access request, the server calculates the identity fusion matching score and performs identity fusion based on the identity fusion matching score; if it is not a critical access request, the server closes the access verification box and ends the critical access verification process.
[0095] The server pre-stores a personnel role semantic graph, which includes, but is not limited to, personnel primary identity, login account, fixed role, job responsibilities, organizational affiliation, bound device, fixed IP whitelist, authorized location, executable business actions, authorized time window, terminal security status, historical access behavior, audit events, and risk tags. Nodes in the personnel role semantic graph represent personnel, accounts, devices, IPs, locations, roles, business actions, and events, while edges represent binding, authorization, affiliation, access, triggering, review, and handling relationships. The personnel role semantic graph is centered on the personnel primary identity and includes mappings to accounts, devices, fixed IPs, fixed roles, positions, locations, and behavioral events across multiple business systems. For directly matchable fields, such as personnel number, employee number, organizational code, fixed IP, and bound terminal, strong associations can be established directly. For accounts with incomplete fields or inconsistent naming, identity fusion matching scores can be used to identify the same person.
[0096] The identity fusion matching score is calculated using the following formula:
[0097] MatchScore = w1*S_id + w2*S_mobile + w3*S_device + w4*S_ip + w5*S_org+ w6*S_time;
[0098] Wherein, S_id represents the matching degree of personnel ID, S_mobile represents the matching degree of contact information, S_device represents the matching degree of terminal binding, S_ip represents the matching degree of fixed IP, S_org represents the matching degree of organization affiliation, S_time represents the matching degree of historical access time sequence, and w1 to w6 are weights, and can satisfy w1+w2+w3+w4+w5+w6=1.
[0099] For enterprise intranet environments where fixed IPs and fixed roles are clearly defined, the matching results of S_ip and fixed role templates can be used as high-weight or pre-verification items; the fixed role template matching results do not replace the identity fusion threshold, but are used to confirm whether the merged personnel have the business baseline of the fixed role.
[0100] Perform identity fusion based on the identity fusion matching score: when MatchScore>=T_match_high, the server maps multiple intranet heterogeneous system accounts to the same main personnel identity; when T_match_low<=MatchScore<T_match_high, the server places the relevant accounts in a manual review or low-trust pending confirmation state; when MatchScore<T_match_low, the server does not perform automatic fusion. Herein, T_match_high represents the first identity fusion threshold, and T_match_low represents the second identity fusion threshold; in an example, T_match_high may be set to 0.80 to 0.95, and T_match_low may be set to 0.60 to 0.80. The fixed role consistency check is not determined in this step, but is used in the subsequent hexad consistency check to determine whether the fused main personnel identity conforms to the preset fixed role template.
[0101] Step 2: Collect data related to the current access personnel and their associated objects from the enterprise's intranet heterogeneous systems, and perform field standardization and event normalization. The associated objects include devices, fixed IPs, locations, business actions, time windows, terminal security statuses, and audit events.
[0102] The field standardization includes: establishing a unified data dictionary and field mapping table, mapping the personnel numbers, login accounts, terminal numbers, fixed IPs, department posts, fixed roles, camera areas, business actions, log times, and alarm types in different business systems into unified fields; converting field formats, encoding rules, time formats, organization hierarchies and enumeration values, so that data with the same meaning uses the same name, unit and value range.
[0103] The event normalization includes: converting original events into unified event types according to a preset event model, and supplementing each event with tags of main personnel identity, fixed role, device, fixed IP, location, business action and time. The original events include but are not limited to login, approval, query, export, write, terminal alarm, video position change and audit abnormality.
[0104] This step performs field standardization and event normalization to facilitate subsequent hexad extraction and risk scoring.
[0105] Step 3: First perform fixed role and fixed IP baseline checks; if the fixed role of the requesting personnel is not within the preset role template, or the access IP is not within the preset fixed IP whitelist, a baseline deviation result is generated; for highly sensitive access requests that hit the preset blocking rule, the access is blocked or manual review is performed.
[0106] The baseline deviation result generated in this step is used as an input factor for risk scoring.
[0107] Step 4: Based on the personnel primary identity, standardized fields, and normalized events formed in Steps 1 to 3, generate or update the personnel role semantic graph, and extract the six-tuple of the current access request; the six-tuple includes personnel P, device D, IP, location L, business action A, and time T.
[0108] The six-tuple representation is: <Personnel P, Device D, IP, Location L, Action A, Time T>.
[0109] Step 5: Perform six-tuple consistency verification and terminal security status verification respectively; the six-tuple consistency verification includes fixed role consistency verification, device consistency verification, IP consistency verification, location consistency verification, service consistency verification, and time consistency verification; the terminal security status verification includes terminal protection status verification, virus database status verification, patch status verification, peripheral device status verification, and terminal management status verification; after completing the consistency verification and terminal security status verification, calculate the dynamic risk score and determine the risk score range.
[0110] Step 5 includes the following steps 501 to 504:
[0111] Step 501: Perform a six-tuple consistency check.
[0112] The fixed role consistency check determines whether person P belongs to the preset fixed role template.
[0113] Step 1, identity fusion, is used to determine whether multiple business system accounts can be merged into the same person's primary identity. The fixed role consistency verification in this step is used to determine whether the primary identity of the person who has undergone identity fusion conforms to the preset fixed role template. The two are located in the identity confirmation and risk verification stages, respectively.
[0114] The device consistency check determines whether device D is an authorized terminal or a commonly used terminal of person P.
[0115] The IP consistency check determines whether the current IP is consistent with the fixed IP whitelist of personnel P.
[0116] The location consistency check determines whether location L is consistent with the authorized workstation, office area, duty area, or business location.
[0117] The business consistency check determines whether business action A is consistent with the fixed role, job responsibilities, approval authority, and current task context of personnel P.
[0118] The time consistency check determines whether business action A is within the authorized time window, task context, and approval process node.
[0119] Step 502: Perform terminal security status verification.
[0120] The terminal security status verification determines whether the terminal protection status, virus database status, patch status, peripheral device status, and terminal management status meet the access requirements.
[0121] Step 503: Calculate the dynamic risk score.
[0122] Calculate the dynamic risk score using the following formula:
[0123] RiskScore = a1*R_role + a2*R_device + a3*R_endpoint + a4*R_ip + a5*R_location + a6*R_time + a7*R_audit + a8*R_business - a9*R_trust;
[0124] Among them, RiskScore is a dynamic risk score; R_role is a fixed role deviation risk factor, corresponding to fixed role consistency verification; R_device is a device non-compliance risk factor, corresponding to device consistency verification; R_endpoint is an endpoint protection anomaly risk factor, corresponding to endpoint security status verification; R_ip is a fixed IP deviation risk factor, corresponding to IP consistency verification; R_location is a location conflict risk factor, corresponding to location consistency verification; R_time is a time window deviation risk factor, corresponding to time consistency verification; R_audit is an audit anomaly risk factor, obtained by normalizing abnormal access, failed operation, abnormal export, and alarm records in the audit system; R_business is a business sensitivity risk factor, obtained by the sensitivity level, write attribute, fund amount, data range, and approval node of business action A; R_trust is a historical trust factor, obtained by the number of historical compliant accesses by personnel, review approval records, and recent risk event attenuation results; a1 to a9 are weights.
[0125] In one embodiment, each risk factor can be automatically assigned a value according to a preset mapping table or piecewise function: if the current IP is consistent with the fixed IP whitelist, R_ip takes a low value of 0 or close to 0; if the current IP belongs to the same office network segment but is not a bound IP, R_ip takes a middle value; if the current IP is not on the whitelist or has an abnormal source, R_ip takes a high value close to 1. If the business action is a highly sensitive action such as fund approval, batch export, audit log deletion, or terminal isolation command, R_business takes a higher value according to the sensitivity level table; if the audit system records high-frequency access, abnormal export, or multiple failed operations in a short period of time, R_audit takes a value according to the number of abnormalities, the type of abnormality, and the time decay coefficient.
[0126] Step 504: Determine a risk score interval according to the dynamic risk score.
[0127] 0<=RiskScore<T_low is the first risk score interval;
[0128] T_low<=RiskScore<T_mid is the second risk score interval;
[0129] T_mid<=RiskScore<T_high is the third risk score interval;
[0130] RiskScore>=T_high is the fourth risk score interval.
[0131] Wherein, T_low represents the first dynamic risk score threshold, T_mid represents the second dynamic risk score threshold, and T_high represents the third dynamic risk score threshold. In an example, T_low may be 0.30, T_mid may be 0.60, and T_high may be 0.80; the actual thresholds may be configured according to the enterprise security policy. The range of the dynamic risk score RiskScore may be normalized to 0 to 1. In this step, the risk score interval is determined only according to RiskScore, and the final risk interval of low risk, medium risk, high risk or extremely high risk is determined in subsequent steps in combination with fixed role consistency verification, IP consistency verification, device consistency verification, task context and blocking rules.
[0132] The conflict escalation rule is used as a risk score correction item: if at least two dimensions in the sextuple conflict, a conflict correction value is added to the dynamic risk score RiskScore; if the conflicting dimensions involve a combination of fixed IP deviation, unauthorized device and high-sensitivity service action, the dynamic risk score RiskScore is corrected to the third risk score interval or the fourth risk score interval, and the specific risk interval and disposal action are determined in the subsequent risk interval judgment step.
[0133] Step 6: Perform risk interval judgment according to the risk score interval obtained in step 5, the sextuple consistency verification result, the terminal security state verification result and the task context, calculate an orchestration score, and generate a target page set according to the orchestration score.
[0134] Step 601: Perform risk interval judgment according to the risk score interval obtained in step 5, the sextuple consistency verification result, the terminal security state verification result and the task context.
[0135] The task context may be generated from the business objective, page entry, API type, approval document, work order number, production task, current process node, associated alarm and historical session information in the access request; for a preset task, the task template is directly read, and for a non-preset task, a task context vector is automatically generated according to the business action A, access target and process node.
[0136] When 0<=RiskScore<T_low and the fixed role consistency verification, IP consistency verification and device consistency verification are all passed, the risk interval is low risk, a normal working page is entered, and the API matching the fixed role is allowed to be called;
[0137] When T_low<=RiskScore<T_mid, or there is an interpretable slight deviation, the risk interval is medium risk, and a risk explanation page, a reminder access page, a secondary confirmation page or a read-only page is generated;
[0138] When T_mid<=RiskScore<T_high, or there is a multi-dimensional conflict but no blocking rule is hit, the risk interval is high risk, and degraded access, write API restriction, secondary confirmation requirement or manual review push is executed;
[0139] When RiskScore>=T_high, or the combination rule of fixed IP anomaly, high-sensitivity business action and unauthorized device is hit, the risk interval is extremely high risk, access is blocked, and terminal management and control, audit alarm and manual review are triggered.
[0140] Step 602: calculating an orchestration score.
[0141] A candidate page set is generated according to the fixed role accessible page list, current task context, business process node, target business system capability list and risk interval; the orchestration score is calculated for the candidate page or candidate function module m according to the following formula:
[0142] RouteScore(m) = b1*F_role(m) + b2*F_task(m) + b3*F_risk(m) + b4*F_urgent(m) - b5*F_cost(m);
[0143] Wherein, F_role(m) is the role adaptability, F_task(m) is the task relevance, F_risk(m) is the risk permission, F_urgent(m) is the event urgency, F_cost(m) is the cross-system dependency cost, and b1 to b5 are weights.
[0144] The orchestration score RouteScore(m) can be normalized to 0 to 1. The orchestration score threshold for common pages or read-only modules can be denoted as T_route_page; the orchestration score threshold for write-type APIs or writable modules can be denoted as T_route_write. The write-type APIs also need to satisfy the dynamic risk score RiskScore<T_mid; the highly sensitive write interfaces also need to satisfy the dynamic risk score RiskScore<T_low. In the example, T_route_page can be set to 0.45 to 0.60, T_route_write can be set to 0.65 to 0.85, T_low can take 0.30, and T_mid can take 0.60.
[0145] Step 603: generating a target page set according to the orchestration score and the dynamic risk score.
[0146] When a candidate page or candidate module is a common page or a read-only module and RouteScore(m)>=T_route_page, adding it to the target page set; when the candidate page or candidate module involves a write-type API or a writable module, and RouteScore(m)>=T_route_write and RiskScore<T_mid, adding it to the target page set; when the candidate page or candidate module involves a highly sensitive write interface, adding it to the target page set only when RouteScore(m)>=T_route_write and RiskScore<T_low; when the dynamic risk score does not meet the corresponding write access condition, replacing the candidate page or candidate module with a read-only page, a secondary confirmation page or a manual review page.
[0147] For example, for a production supervisor, a production dashboard page, an equipment alarm page, a terminal health page and an inspection log page can be generated in a low-risk state; a risk explanation page, an alarm confirmation page, a read-only production page and a secondary confirmation page can be generated in a medium-risk state; highly sensitive APIs are blocked in a high-risk state, and only pages for investigation, review and trace retention are retained.
[0148] For example, for a finance role, when an approval request comes from a compliant device, a fixed IP and an authorized location, a finance home page, an approval page and an audit trail page can be generated; when the request comes from a non-compliant device or an abnormal location, a compliance verification page, a secondary authentication page and a read-only approval page are generated, and fund-related API write calls are suspended.
[0149] Step 7: outputting a field-level shared view according to a preset fixed role, a field permission matrix and the determined risk interval, so that the same data source presents different field ranges under different roles and different risk states; and performing graded processing;
[0150] The field-level shared view is generated jointly by a unified data dictionary, a role-based field permission matrix, risk zones, data anonymization rules, and write control rules. The characteristics of this field-level shared view are: data is collected only once from the same data source; different fixed roles see different ranges of fields; the visibility, writability, exportability, and anonymization status of fields for the same fixed role differ under different risk zones; the view does not change the underlying data of the original business system in the heterogeneous intranet, but rather outputs a set of controlled fields through a data bus, database view, or API gateway.
[0151] Based on the risk score range, dynamic risk score RiskScore, orchestration score RouteScore(m), and target page set, tiered handling is performed:
[0152] Normal access is granted when the risk range is low, and basic logs are recorded.
[0153] When the risk range is medium risk, a visit is prompted, a risk warning is displayed, and a risk explanation is recorded.
[0154] When the risk range is high-risk and the first handling level is high, downgraded access is implemented, restricting writes to the API and requiring secondary confirmation; when the risk range is high-risk and the second handling level is high-risk and read-only access is implemented, only displaying necessary pages and read-only data.
[0155] When the risk range is extremely high, access is blocked and coordinated actions are triggered, including suspending highly sensitive API calls to the target business system, notifying the terminal management system to perform network isolation, disabling peripheral devices or consolidating permissions, writing high-priority events to the audit system, pushing manual review tasks to the management end, and recording the complete context and processing results in the evidence chain.
[0156] Step 8: Write the personnel primary identity fusion result, six-tuple consistency verification result, terminal security status verification result, dynamic risk score components, page set, API call chain, field sharing scope, handling actions, and manual review conclusions into the evidence chain to form a traceable closed loop.
[0157] The evidence chain includes at least: original identity identifier, merged identity identifier, fixed role verification result, fixed IP verification result, six-tuple content, terminal security status, risk score components, target page set, API call chain, field sharing scope, handling action, handling time, handling result, and review conclusion.
[0158] The evidence chain records can be configured with retention periods and tamper-proof strategies according to business levels. For high-risk events, hash digests, timestamps, and audit signatures can be used to save key field summaries.
[0159] The present invention further provides a field-level sharing control mechanism, so that cross-system data does not need to be maintained repeatedly in multiple systems, but is output by role through a unified data bus or a shared view. Examples are as follows:
[0160]
[0161] Through this sharing matrix, the production volume and overtime working hours in the manufacturing execution system can be collected only once, and then synchronized to the financial management system for overtime pay calculation or approval status display; the platform determines whether a field is visible, writable, or requires secondary confirmation based on fixed roles and risk statuses.
[0162] The present invention does not simply place multiple system entrances on one page, but first takes fixed roles and fixed IPs as the baseline, then integrates multi-source identities and events to form a personnel role semantic graph; subsequently, performs six-element consistency check and terminal security status check on each critical access request to obtain a dynamic risk score; then generates a target page set, an API call chain and a field-level sharing scope in real time according to the risk score and task context; and finally writes the processing result into the cross-system evidence chain.
[0163] Example 1: A production supervisor accesses the production workstation
[0164] A certain production supervisor uses an authorized terminal and a fixed IP to access the manufacturing execution system. The server identifies that its fixed role is administrator, the current IP is consistent with the fixed IP whitelist, the video location is in the authorized workshop area, the terminal protection status is normal, and the audit system does not find abnormal access. Calculated in step 5, RiskScore<T_low, and the fixed role consistency check, IP consistency check and device consistency check all pass; calculated in step 6, the RouteScore(m) of the production dashboard page, device alarm page, terminal health page and inspection log page all satisfy T_route_page, and the RouteScore(m) of the production exception review API satisfies T_route_write and RiskScore<T_mid, so the above target page set is generated and the corresponding APIs are opened. The server records the identity fusion result, the source of the low risk score, the page set and the API call orchestration result.
[0165] Example 2: A financial approval request triggers degraded access
[0166] An employee initiates a high-amount approval request in the financial management system. The server identifies that the fixed role of this employee is not a financial role, the current device is not a commonly used authorized device, the terminal protection system shows that the virus database has not been updated beyond the preset time, the video surveillance system does not detect that the employee is in the authorized office area, and the audit system records that the device has accessed sensitive pages multiple times in a short period of time. The server determines that there is a multi-dimensional conflict through six-element consistency verification, calculates a high risk score interval of T_mid<=RiskScore<T_high, and judges in step 6 that the fund approval writing page does not meet the writing access condition of RiskScore<T_mid.
[0167] At this time, the server does not generate a writable approval page, but generates a risk explanation page, a secondary verification page and a read-only approval page, suspends fund-related API write calls, writes high-priority events to the audit system, and notifies the terminal management and control system to perform restricted access on the device. All the above processes of dynamic risk scoring, orchestration score, target page set, and API call disposal are written into the evidence chain.
[0168] Third example: Cross-system data sharing.
[0169] The production execution system records the production volume and overtime hours of an employee, and the server synchronizes them to the financial management system through the intranet data bus. Ordinary employees can only view their own production volume, their own overtime hours and their own overtime pay; administrators can view the production summary and synchronization status of their own department, but do not display the salary details of other employees; auditors can view full-volume read-only details and the evidence chain; leaders can view business summaries and authorized key details. The server outputs different field sets according to the fixed role, risk score interval and dynamic risk score RiskScore; when RiskScore reaches the high-risk or extremely high-risk score interval, even if the corresponding page RouteScore(m) meets the display threshold, field drilling, export or writing is restricted, so as to reduce repeated entry and lower the diffusion risk of sensitive data.
[0170] Embodiment 2
[0171] An embodiment of the present invention provides a fixed-IP role-based intranet heterogeneous dynamic management system, comprising:
[0172] A data access adaptation module, configured to respectively interface with the production execution system, the financial management system, the video surveillance system, the terminal protection system, the terminal management and control system, and the audit system. The access manner may include API, database view, message queue, log stream, file exchange or local agent collection.
[0173] A field standardization module, configured to map fields in different systems such as employee number, login account, terminal number, fixed IP, department position, role, camera area, service action, log time, and alarm type to a unified data dictionary.
[0174] The identity fusion module is used to identify the same person based on personnel number, contact information, device binding, fixed IP, organizational level, job role and historical access time, and output the person's main identity and fusion matching score.
[0175] The Personnel Role Semantic Graph module is used to establish relationships between personnel and accounts, fixed IPs, authorized devices, fixed roles, job responsibilities, authorized locations, business actions, terminal security status, risk events, and audit logs, with personnel as the central node.
[0176] The six-element consistency verification module is used to extract personnel P, device D, IP, location L, business action A, and time T when a critical access request occurs, and compare them with the baseline relationship in the personnel role semantic graph.
[0177] The dynamic risk scoring module combines fixed role deviation risk, equipment non-compliance risk, terminal protection anomaly risk, fixed IP deviation risk, video location conflict risk, time window deviation risk, audit anomaly risk, business sensitivity risk, and historical credibility to obtain a dynamic risk score.
[0178] The dynamic orchestration module generates a set of target pages and an API call orchestration chain based on role responsibility vectors, task context vectors, dynamic risk scores, candidate page sets, system dependencies, and module costs. This module can orchestrate the same fixed role into different workbenches under different risk states.
[0179] The field-level shared control module is used to output different data views according to fixed roles and risk statuses. For example, ordinary employees can only view their own production volume, overtime hours, overtime pay, and approval status; administrators can view department summaries and abnormal statuses but not others' pay details; auditors can view read-only details and audit traces; and leaders can view business summaries and key details after authorization.
[0180] The coordinated response module is used to trigger normal access, alert access, downgraded access, read-only access, secondary confirmation, blocked access, terminal isolation, audit alarms, and manual review based on risk ranges.
[0181] The evidence chain management module is used to record the original identity identifier, the merged identity identifier, the fixed role verification result, the fixed IP verification result, the six-tuple content, the terminal security status, the risk score components, the page set, the API call chain, the field sharing scope, the handling action, and the review conclusion.
[0182] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications to the technical solutions described in the foregoing embodiments, or equivalent substitutions for some or all of the technical features, do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for managing heterogeneous dynamic intranet structures with fixed IP roles, characterized in that, The process includes the following: Step 1: The server receives the employee's access request, obtains the verification information entered by the employee in the access verification box, and identifies whether the access request is a critical access request. If it is a critical access request, identity fusion is performed; if it is not a critical access request, the access verification box is closed. Step 2: Collect data related to the current visitor and their associated objects from the heterogeneous systems within the enterprise's intranet, and perform field standardization and event normalization; the associated objects include devices, fixed IPs, locations, business actions, time windows, terminal security status, and audit events; Step 3: First, perform baseline verification for fixed roles and fixed IPs; If the requester's fixed role is not in the preset role template, or the accessing IP is not in the preset fixed IP whitelist, a baseline deviation result will be generated; for highly sensitive access requests that hit the preset blocking rules, access will be blocked or manual review will be performed. Step 4: Based on the personnel primary identity, standardized fields, and normalized events formed in Steps 1 to 3, generate or update the personnel role semantic graph, and extract the six-tuple of the current access request; the six-tuple includes personnel P, device D, IP, location L, business action A, and time T; Step 5: Perform six-tuple consistency verification and terminal security status verification respectively; the six-tuple consistency verification includes fixed role consistency verification, device consistency verification, IP consistency verification, location consistency verification, service consistency verification, and time consistency verification; the terminal security status verification includes terminal protection status verification, virus database status verification, patch status verification, peripheral device status verification, and terminal management status verification; after completing the consistency verification and terminal security status verification, calculate the dynamic risk score and determine the risk score range; Step 6: Based on the risk score range obtained in Step 5, the six-tuple consistency verification result, the terminal security status verification result, and the task context, determine the risk range, calculate the orchestration score, and generate the target page set based on the orchestration score. Step 7: Based on the preset fixed roles, field permission matrix and the determined risk range, output the field-level shared view; And implement tiered handling.
2. The fixed IP role-based heterogeneous dynamic management method for intranets according to claim 1, characterized in that, Step 1 includes the following steps 101 to 103: Step 101: When a person requests access to any business page or API in the heterogeneous intranet system, the server receives the access request, generates an access verification box, and obtains the verification information entered by the person in the access verification box; the verification information includes, but is not limited to, account, fixed role, access target, business action, current terminal, current IP, and necessary secondary confirmation information. Step 102: The server identifies whether the access request is a critical access request based on whether the verification information involves write-type APIs, highly sensitive fields, fund approval, production data modification, batch export, audit record query, terminal control instructions, or abnormal work order review; the critical access requests include, but are not limited to, financial approval, production data modification, batch export, audit record query, terminal control instructions, and abnormal work order review. Step 103: if the request is a critical access request, the server calculates an identity fusion matching score, and performs identity fusion according to the identity fusion matching score; if the request is not a critical access request, the server closes the access verification box, and ends the critical access verification process; The identity fusion matching score is calculated according to the following formula: MatchScore = w1*S_id + w2*S_mobile + w3*S_device + w4*S_ip + w5*S_org +w6*S_time; Wherein, S_id represents personnel number matching degree, S_mobile represents contact information matching degree, S_device represents terminal binding matching degree, S_ip represents fixed IP matching degree, S_org represents organization affiliation matching degree, S_time represents historical access sequence matching degree, w1 to w6 are weights, which satisfy w1+w2+w3+w4+w5+w6=1; The performing identity fusion according to the identity fusion matching score includes: when MatchScore>=T_match_high, the server maps multiple intranet heterogeneous system accounts to the same main personnel identity; when T_match_low<=MatchScore<T_match_high, the server places the relevant accounts in a manual review or low-trust pending confirmation state; when MatchScore<T_match_low, the server does not perform automatic fusion; wherein T_match_high represents the first identity fusion threshold, and T_match_low represents the second identity fusion threshold.
3. The fixed IP role-based heterogeneous dynamic management method for intranets according to claim 2, characterized in that, The enterprise's intranet heterogeneous systems include, but are not limited to, six major business systems: a production execution system, a financial management system, a video surveillance system, a terminal protection system, a terminal management and control system, and an audit system.
4. The fixed IP role-based intranet heterogeneous dynamic management method according to claim 1, characterized in that, In step 2, the field standardization includes: establishing a unified data dictionary and field mapping table, mapping the personnel number, login account, terminal number, fixed IP, department post, fixed role, camera area, business action, log time and alarm type in different business systems to unified fields; converting the field format, coding rule, time format, organization hierarchy and enumeration value, so that data with the same meaning uses the same name, unit and value range; The event normalization includes: converting original events into unified event types, and supplementing each event with a main personnel identity, fixed role, device, fixed IP, location, business action and time tag; the original events include but are not limited to login, approval, query, export, write, terminal alarm, video position change and audit abnormality.
5. The fixed IP role-based intranet heterogeneous dynamic management method according to claim 2, characterized in that, Step 5 includes the following Step 501 to Step 504: Step 501: perform hexad consistency verification; Step 502: perform terminal security status verification; Step 503: calculate the dynamic risk score according to the following formula: RiskScore = a1*R_role + a2*R_device + a3*R_endpoint + a4*R_ip + a5*R_location + a6*R_time + a7*R_audit + a8*R_business - a9*R_trust; wherein RiskScore is a dynamic risk score, R_role is a fixed role deviation risk factor; R_device is a non-compliant device risk factor; R_endpoint is an abnormal endpoint protection risk factor; R_ip is a fixed IP deviation risk factor; R_location is a location conflict risk factor; R_time is a time window deviation risk factor; R_audit is an abnormal audit risk factor; R_business is a business sensitivity risk factor; R_trust is a historical credibility factor; Step 504: Determine a risk score interval according to the dynamic risk score; 0<=RiskScore<T_low is the first risk score interval; T_low<=RiskScore<T_mid is the second risk score interval; T_mid<=RiskScore<T_high is the third risk score interval; RiskScore>=T_high is the fourth risk score interval; wherein T_low denotes a first dynamic risk score threshold, T_mid denotes a second dynamic risk score threshold, and T_high denotes a third dynamic risk score threshold.
6. The fixed IP role-based intranet heterogeneous dynamic management method according to claim 5, characterized in that, Said step 6 includes the following steps 601 to 603: Step 601: Perform risk interval judgment according to the risk score interval obtained in step 5, the sextuple consistency check result, the endpoint security state check result, and the task context; When 0<=RiskScore<T_low and the fixed role consistency check, IP consistency check and device consistency check are all passed, the risk interval is low risk, a normal working page is entered, and APIs matching the fixed role are allowed to be invoked; When T_low<=RiskScore<T_mid, or there is an interpretable slight deviation, the risk interval is medium risk, and a risk explanation page, an access reminder page, a secondary confirmation page or a read-only page is generated; When T_mid<=RiskScore<T_high, or there is a multi-dimensional conflict but no blocking rule is hit, the risk interval is high risk, and degraded access, write API restriction, secondary confirmation requirement or manual review push is executed; When RiskScore>=T_high, or the combination rule of abnormal fixed IP, highly sensitive business action and unauthorized device is hit, the risk interval is extremely high risk, access is blocked, and endpoint control, audit alarm and manual review are triggered; Step 602: Calculate an orchestration score for the candidate page or candidate function module m according to the following formula: RouteScore(m) = b1*F_role(m) + b2*F_task(m) + b3*F_risk(m) + b4*F_urgent(m) - b5*F_cost(m); Wherein F_role(m) is the role adaptability, F_task(m) is the task relevance, F_risk(m) is the risk allowability, F_urgent(m) is the event urgency, and F_cost(m) is the cross-system dependency cost; Step 603: Generate a target page set according to the orchestration score and the dynamic risk score; When the candidate page or candidate module is a common page or a read-only module and RouteScore(m)>=T_route_page, add it to the target page set; when the candidate page or candidate module involves a write-type API or a writable module, and RouteScore(m)>=T_route_write and RiskScore<T_mid, add it to the target page set; when the candidate page or candidate module involves a highly sensitive write interface, add it to the target page set only when RouteScore(m)>=T_route_write and RiskScore<T_low; when the dynamic risk score does not meet the corresponding write access condition, replace the candidate page or candidate module with a read-only page, a secondary confirmation page or a manual review page.
7. The fixed IP role-based intranet heterogeneous dynamic management method according to claim 6, characterized in that, In step 7, the performing hierarchical handling according to the risk score interval, the dynamic risk score, the orchestration score and the target page set comprises: When the risk interval is a low risk, perform normal access and record a basic log; When the risk interval is a medium risk, perform reminder access, display a risk prompt and record a risk explanation; When the risk interval is a high risk, execute degraded access at the first handling level, restrict write APIs and require secondary confirmation; execute read-only access at the second handling level for high risk, and only display necessary pages and read-only data; When the risk interval is an extremely high risk, block access and trigger linkage handling, including suspending high-sensitivity API calls of the target service system, notifying the terminal management and control system to perform network isolation, peripheral disabling or permission convergence, writing high-priority events to the audit system, pushing manual review tasks to the management end, and recording the complete context and processing results in the evidence chain.
8. The fixed IP role-based intranet heterogeneous dynamic management method according to claim 7, characterized in that, After step 7, the method further comprises: Step 8: Write the personnel main identity fusion result, the sextuple consistency check result, the terminal security status check result, the components of the dynamic risk score, the page set, the API call chain, the field sharing scope, the handling action and the manual review conclusion into the evidence chain, to form a traceable closed loop; The evidence chain at least comprises: original identity identifier, fused identity identifier, fixed role check result, fixed IP check result, sextuple content, terminal security status, components of the risk score, target page set, API call chain, field sharing scope, handling action, handling time, handling result and review conclusion.
9. A management system for a fixed IP role-based heterogeneous dynamic management method for intranets according to any one of claims 1 to 8, characterized in that, comprises: The data access adaptation module is used to connect to the production execution system, financial management system, video surveillance system, terminal protection system, terminal control system, and audit system, respectively. The field standardization module is used to map fields such as employee ID, login account, terminal ID, fixed IP, department / position, role, camera area, business action, log time, and alarm type from different systems to a unified data dictionary; The identity fusion module is used to identify the same person based on personnel number, contact information, device binding, fixed IP, organizational level, job role and historical access time, and output the person's main identity and fusion matching score. The Personnel Role Semantic Graph module is used to establish the relationship between personnel and accounts, fixed IPs, authorized devices, fixed roles, job responsibilities, authorized locations, business actions, terminal security status, risk events, and audit logs, with personnel as the central node. The six-element consistency verification module is used to extract personnel P, device D, IP, location L, business action A, and time T when a critical access request occurs, and compare them with the baseline relationship in the personnel role semantic graph; The dynamic risk scoring module is used to combine fixed role deviation risk, equipment non-compliance risk, terminal protection abnormal risk, fixed IP deviation risk, video location conflict risk, time window deviation risk, audit abnormal risk, business sensitivity risk, and historical credibility to obtain a dynamic risk score. The dynamic orchestration module is used to generate a set of target pages and an API call orchestration chain based on role responsibility vectors, task context vectors, dynamic risk scores, candidate page sets, system dependencies, and module costs. The field-level shared control module is used to output different data views according to fixed roles and risk status; The coordinated response module is used to trigger normal access, alert access, downgraded access, read-only access, secondary confirmation, access blocking, terminal isolation, audit alarms, and manual review based on risk ranges. The evidence chain management module is used to record the original identity identifier, the merged identity identifier, the fixed role verification result, the fixed IP verification result, the six-tuple content, the terminal security status, the risk score components, the page set, the API call chain, the field sharing scope, the handling action, and the review conclusion.
Citation Information
Patent Citations
Unified identity authentication system and method
CN110334489A
