Password security input methods, devices, equipment, and media based on hierarchical control.

Abstract

This application discloses a method, apparatus, device, and medium for secure password input based on hierarchical control, relating to the field of computer technology. The method includes: receiving a task instruction and generating a hierarchical authorization execution plan based on the task type and operation security level; marking a password input request as the highest security level and sending a pre-verification request to a verification server when detected; establishing a temporary password authorization streaming channel with the master device after receiving the pass result, pushing the authorization request, and synchronizing the plan; injecting password data into the target application kernel through the channel after the master device completes multi-factor authentication; destroying the channel and clearing the cache after completion, and continuing task execution. This application ensures password input security by binding hierarchical authorization with a dedicated streaming channel, combined with dual verification and real-time monitoring, avoiding unnecessary triggering and unauthorized operations, and improving the compliance and security of password input.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device and medium for secure password input based on hierarchical control. Background Technology

[0002] With the widespread application of automation technologies such as AI agents in finance, office work, and government affairs, password input is frequently involved in cross-application automated task execution, highlighting increasingly prominent security and compliance issues. Existing solutions often employ a model where passwords are pre-stored locally on the device, and the AI ​​agent automatically retrieves and injects them. This not only poses a risk of password leakage due to device cracking but also exposes the AI ​​agent to unauthorized use of passwords, making it difficult to guarantee the security of user data and assets.

[0003] Traditional password input methods lack dedicated isolation and hierarchical control mechanisms. Password transmission shares channels with routine task data, lacks targeted security protection, and is easily intercepted and tampered with during transmission. Furthermore, they fail to establish an authorization system that matches the risk level of the task; the control logic for high-sensitivity password operations is the same as that for low-risk routine operations, which does not meet the requirements of controllable permissions and traceable operations in heavily regulated scenarios. Simultaneously, existing solutions lack end-to-end compliance verification and real-time user authorization, failing to filter unnecessary password requests and intercepting out-of-bounds operations. If the AI ​​Agent is hijacked or tampered with, it will directly lead to password abuse. These problems restrict the application of automation technology in high-security scenarios, necessitating the development of a password input control solution that balances efficiency and security. Summary of the Invention

[0004] This application provides a method, apparatus, device, and medium for secure password input based on hierarchical control. It receives task instructions to generate a hierarchical authorization execution plan, detects password input requests, marks them with the highest security level and performs pre-verification by a verification server, establishes a temporary streaming channel, injects the password after multi-factor authentication by the main device, and destroys the channel after completion. This achieves hierarchical control and security isolation of password input, avoids leakage risks, and ensures the security and compliance of automated execution.

[0005] In a first aspect, embodiments of this application provide a password security input method based on hierarchical control, applied to a task execution terminal, the input method comprising: Receive the task instructions issued, and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instructions; If a password input request from the target application is detected during the execution of the task instruction locally, the password input request is marked as the highest security level, and a boundary compliance pre-verification request is sent to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result. Receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization streaming channel between the task execution terminal and the main device based on the pass result; After the temporary password authorization streaming channel is established, an authorization request is pushed to the master device and the hierarchical authorization execution plan is synchronized, so that the master device completes multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and injects the input password data into the password input control kernel of the target application through the temporary password authorization streaming channel; After receiving the completion status notification of the password data injection into the password input control kernel, the temporary password authorization stream channel is destroyed and the link memory cache is cleared, and the execution of the task instruction continues locally.

[0006] Furthermore, the step of generating a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instruction includes: The task types are divided into different operation security levels, and corresponding permission boundaries and execution rules are matched for each operation security level. The password input operation is set to the highest security level, which triggers the establishment of the temporary password authorization streaming channel, and the password data injection is completed through the temporary password authorization streaming channel. Other operational security levels are executed according to the corresponding authorization boundaries and execution rules, without triggering the establishment of the temporary password authorization stream channel; The temporary password authorization stream channel is bound to the current task identifier, and each password input is valid for a single temporary password authorization stream channel.

[0007] Furthermore, after continuing the execution of the locally described task instructions, the input method further includes: If a new password input request is detected again during the continued execution of the task instructions, the new password input request will be marked as the highest security level. Send a boundary compliance pre-verification request to the verification server and receive the pass result returned by the verification server. Based on the pass result, trigger the establishment of a new temporary password authorization stream channel. The new temporary password authorization stream channel is bound to the current task identifier. The master device pushes an authorization request and synchronizes the hierarchical authorization execution plan. After the master device completes multi-factor authentication, it injects the password data into the password input control kernel of the corresponding target application through the new temporary password authorization streaming channel. Receive the injection completion status notification and destroy the new temporary password authorization stream channel; For secondary password input for the same task or application, a new temporary password authorization stream channel needs to be established.

[0008] Furthermore, in the hierarchical control-based cryptographic security input method, the input method further includes: The master device receives the authorization request pushed by the task execution terminal and the synchronous hierarchical authorization execution plan; Based on the authorization request and the hierarchical authorization execution plan, at least two identity verification methods are combined and verified within the trusted execution environment of the main device. After the combined verification is passed, the password data input window is invoked within the trusted execution environment, and password data is entered through the password data input window. The password data is then injected into the password input control kernel of the target application through a temporary password authorization streaming channel.

[0009] Furthermore, in the step of invoking the password data input window within the trusted execution environment and inputting password data through the password data input window, the input method further includes: If there is a need for pre-stored passwords, a highest-level password encryption storage module is set up and continuously retained within the trusted execution environment; After completing the combined verification, the pre-stored password is retrieved from the trusted execution environment and injected into the password input control kernel of the target application through the temporary password authorization streaming channel.

[0010] Furthermore, in the hierarchical control-based cryptographic security input method, the input method further includes: After receiving the boundary compliance pre-verification request sent by the task execution terminal, the verification server extracts the hierarchical authorization execution plan and task identifier. Based on the necessity verification of the task instruction execution corresponding to the task identifier, by comparing the task link of the password input request and the task instruction, it is confirmed that the password input request is a necessary operation step to complete the task instruction, and unnecessary and redundant password triggering requests are filtered out. Perform a consistency check and confirm, through natural language semantic comparison, that the permission boundaries used by the password in the hierarchical authorization execution plan are consistent with the task instructions; After both the necessity check and the consistency check pass, a pass result is generated and returned to the task execution terminal to trigger the task execution terminal to establish a temporary password authorization streaming channel; If any verification fails, the verification server intercepts the password input request and prevents the establishment of the temporary password authorization streaming channel.

[0011] Furthermore, after continuing the execution of the task instruction locally, the input method further includes: The verification server initiates real-time full-link boundary compliance verification to monitor whether subsequent operations of the task execution terminal are within the permission boundaries defined by the hierarchical authorization execution plan; If an operation is detected to exceed the permission boundaries defined by the hierarchical authorization execution plan, or if the use of the temporary password authorization streaming channel does not comply with preset security rules, the temporary password authorization streaming channel is destroyed and the current task is interrupted. An alarm message is pushed to the master device and the full-link audit log is retained.

[0012] In a second aspect, embodiments of this application provide a password security input device based on hierarchical control, comprising: The task planning module is used to receive the issued task instructions and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instructions. The requirement detection module is used to detect a password input request from the target application during the execution of the task instruction locally. If the password input request is detected, it is marked as the highest security level, and a boundary compliance pre-verification request is sent to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result. The channel establishment module is used to receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization stream channel between the task execution terminal and the main device based on the pass result; The password injection module is used to push an authorization request to the master device and synchronize the hierarchical authorization execution plan after the temporary password authorization stream channel is established, so that the master device can complete multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and inject the input password data into the password input control kernel of the target application through the temporary password authorization stream channel. The channel destruction module is used to destroy the temporary password authorization stream channel and clear the link memory cache after receiving the completion status notification of the password data injection into the password input control kernel, and continue the execution of the task instructions locally.

[0013] In a third aspect, embodiments of this application provide an electronic device, including: a memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the hierarchical control-based secure input method as described in the first aspect.

[0014] In a fourth aspect, embodiments of this application provide a storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform the hierarchical control-based secure input method as described in the first aspect.

[0015] This application embodiment establishes a hierarchical control system that binds task risk to authorization level. Password input is set to the highest security level and a dedicated temporary streaming channel is triggered, achieving isolation and protection between password transmission and task execution, thus avoiding the risk of leakage of locally stored passwords. The verification server, through necessity and consistency pre-verification, real-time monitoring across the entire chain, and multi-factor authentication of the main device's trusted execution environment, forms a closed-loop risk control system encompassing pre-interception, in-process control, and post-event traceability, effectively filtering redundant requests and unauthorized operations. The temporary channel is uniquely bound to the task identifier and is valid only once. After use, it is immediately destroyed and the cache is cleared, ensuring both automated execution efficiency and compliance requirements in heavily regulated scenarios. This improves password input security and controllability while optimizing the user experience. Attached Figure Description

[0016] Figure 1 This is a flowchart of a password security input method based on hierarchical control provided in an embodiment of this application; Figure 2 This is a flowchart illustrating the generation of the hierarchical authorization execution plan provided in this application embodiment; Figure 3 This is a flowchart of the two-factor password security input method provided in the embodiments of this application; Figure 4 This is a flowchart of the master device password data processing provided in the embodiments of this application; Figure 5 This is a flowchart of the master device password data storage and retrieval provided in an embodiment of this application; Figure 6 This is a flowchart of the verification server performing verification provided in the embodiments of this application; Figure 7 This is a flowchart of the end-to-end monitoring of the verification server provided in this application embodiment; Figure 8 This is a structural diagram of the password security input device based on hierarchical control provided in the embodiments of this application; Figure 9 This is a structural diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but additional steps not included in the drawings may also be present. The above processes can correspond to methods, functions, procedures, subroutines, subroutines, etc.

[0018] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0019] The hierarchical control-based secure password input method provided in this application constructs a full-process security control system around three main execution entities: the task execution terminal, the master device, and the verification server. It generates hierarchical authorization execution plans based on task risk levels, marks password input operations as the highest security level, and triggers dual pre-verification of boundary compliance by the verification server. After successful verification, the task execution terminal establishes a temporary password authorization streaming channel with the master device. The master device completes multi-factor authentication within a trusted execution environment and directly injects the password data into the target application kernel. Immediately after injection, the channel is destroyed and the entire-link cache is cleared. This ensures that password data is never stored on the ground, the AI ​​Agent is completely contactless, and all permission operations are fully traceable. While ensuring efficient execution of automated tasks, it also improves the security and compliance of password input. This hierarchical control-based secure password input method can be specifically applied to high-security automated password input scenarios such as AI Agent automated execution, RPA robot operation, remote intelligent operation and maintenance, financial transaction login, enterprise office system authentication, and government service processing. The aforementioned application scenarios are merely illustrative and explanatory. In practical applications, this hierarchical password security input method can also be used in other scenarios involving automated password input, hierarchical access control, and security verification of sensitive operations. This application does not limit these applications. Furthermore, for point-to-point scenarios involving verification servers, the verification service step can be removed, and the AI ​​Agent can perform boundary compliance pre-verification locally. After successful verification, a point-to-point temporary password authorization streaming channel is directly established with the main device to complete the authorization request push and password injection. The core unique password input triggering and hierarchical boundary control mechanisms remain unchanged.

[0020] The password security input method based on hierarchical control provided in this application is implemented collaboratively by three main execution entities. The task execution terminal is a terminal device, such as a PC, tablet, or server, equipped with an AI Agent and executing automated tasks. It only undertakes the roles of task execution, password requirement detection, and channel trigger relay, and cannot access password data throughout the process. The main device is a user-exclusive authorized terminal bound to the task execution terminal, possessing a Trusted Execution Environment (TEE). It is only used to receive authorization requests, complete identity verification, and input passwords, and is the sole secure carrier for password data processing. The verification server is an independent security verification node used for boundary compliance pre-verification, real-time monitoring of the entire link, boundary violation circuit breaking, and audit log retention, ensuring that password operations comply with authorization rules. This application does not limit the specific hardware form and deployment method of the above-mentioned execution entities.

[0021] Figure 1 This is a flowchart of a hierarchical control-based secure password input method provided in an embodiment of this application, such as... Figure 1 As shown, this hierarchical password security input method includes the following steps: Step 101: Receive the task instruction issued, and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instruction.

[0022] Among them, the task instruction is a natural language instruction issued by the user, the task type refers to the business scenario of the automated operation (such as login, data export, transaction), and the operation security level is a control level classified according to risk. The hierarchical authorization execution plan refers to the standardized executable plan generated by the AI ​​Agent based on the task instruction. It is classified according to the operation risk, and clarifies the permission boundaries, triggering nodes, channel lifecycle, and termination conditions of password input. It is a standardized execution scheme bound to the risk level.

[0023] In one embodiment, the task execution terminal receives an automated task instruction from the user, such as "Open the Tonghuashun software and export the February 2026 stock holding settlement statement." The AI ​​Agent breaks down the task execution chain, identifies the risk level of each operation in the task, and classifies the task type into three security levels: low risk (page browsing, file viewing), medium risk (file modification, data export), and the highest security level (password input). For each level, corresponding permission boundaries and execution rules are matched, with password input operations fixed at the highest security level. It is specified that this highest security level requires triggering a temporary password authorization streaming channel, while other levels do not require channel triggering. Finally, a hierarchical authorization execution plan uniquely bound to the task identifier is generated, specifying the trigger node, usage boundaries, and channel validity duration for password input. Optionally, the hierarchical authorization execution plan adopts a standardized format that is machine-verifiable and user-readable. Once generated, it cannot be arbitrarily modified; any modification requires a complete full-process compliance verification.

[0024] Step 102: If a password input request from the target application is detected during the execution of the task instruction locally, the password input request is marked as the highest security level, and a boundary compliance pre-verification request is sent to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result.

[0025] Among them, the password input request is the trigger signal for the target application to pop up the password input control, the highest security level is the control level that cannot be downgraded, and the boundary compliance pre-verification request is a verification application carrying a hierarchical authorization execution plan and task identifier.

[0026] In one embodiment, the task execution terminal executes the hierarchical authorization execution plan locally. When it detects that the target application (e.g., Tonghuashun) pops up a password input control and triggers a password input request, it immediately marks the request as the highest security level and suspends the local task execution. It then sends a boundary compliance pre-verification request to the verification server. The request carries the hierarchical authorization execution plan, task identifier, target application identifier, and task execution terminal device identifier, so that the verification server performs dual pre-verification based on the above information.

[0027] Step 103: Receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization stream channel between the task execution terminal and the main device based on the pass result.

[0028] Among them, the result is a compliance certificate generated after the verification server completes the necessity and consistency verification. The temporary password authorization stream channel is a dedicated encrypted channel between the main device TEE and the target application password control kernel. It is an end-to-end encrypted point-to-point channel triggered only by password input. It is bound to the task identifier and the target application kernel. It is not valid for one time and is destroyed after use. It does not transmit non-password data, and the AI ​​Agent cannot access the data in the channel.

[0029] In one embodiment, the task execution terminal receives the pre-verification pass result returned by the verification server and immediately triggers the channel establishment instruction. The system establishes an end-to-end asymmetric encrypted temporary password authorization stream channel based on the task identifier, the unique identifier of the master device, and the kernel address of the target application password control. This channel is only bound to the current task identifier, and each password input is valid for a single channel. It does not transmit any non-password data and only grants one-way password write permission.

[0030] Step 104: After the temporary password authorization streaming channel is established, an authorization request is pushed to the master device and the hierarchical authorization execution plan is synchronized, so that the master device completes multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and injects the input password data into the password input control kernel of the target application through the temporary password authorization streaming channel.

[0031] The authorization request is a notification to the user that password authorization needs to be completed. Multi-factor authentication is a combination of at least two verification methods within the TEE, such as face and fingerprint, PIN code (Personal Identification Number) and OTP dynamic password (One-Time Password), to ensure that the authorization operation is initiated by a legitimate user. Password data injection is to directly write the password into the target application's password control kernel.

[0032] In one embodiment, after the temporary password authorization streaming channel is successfully established, the task execution terminal pushes an authorization request to the bound master device, synchronizes a complete hierarchical authorization execution plan, and informs the user of the password usage scenario, permission boundaries, and channel lifecycle. The master device receives the request and plan within the trusted execution environment and initiates multi-factor authentication, exemplarily facial recognition and fingerprint authentication. After successful authentication, a dedicated encrypted input window for the TEE is opened. The user manually enters the password or retrieves a pre-stored password from the highest-level password encryption storage module within the TEE. The password data is directly injected into the password input control kernel of the target application through the temporary password authorization streaming channel. Throughout the entire process, the task execution terminal, AI Agent, and conventional command chain cannot read, intercept, cache, or tamper with the password data.

[0033] Step 105: After receiving the completion status notification of the password data injection into the password input control kernel, destroy the temporary password authorization stream channel and clear the link memory cache, and continue to execute the task instructions locally.

[0034] Among them, the injection completion status notification is the password input completion signal fed back by the target application, the channel destruction is the permanent deletion of the temporary channel, and the clear cache is the clearing of all temporary password data in the entire link.

[0035] In one embodiment, the task execution terminal receives a password data injection completion status notification from the target application and immediately triggers a channel destruction command to permanently destroy the current temporary password authorization streaming channel. At the same time, it clears the memory cache and temporary password data of the main device, the task execution terminal, and the channel link, leaving no password residue. After the cache is cleared, local task execution is resumed, and subsequent automated operations are completed according to the hierarchical authorization execution plan.

[0036] As described above, by generating tiered authorization execution plans based on task risk levels and marking password input requests as the highest security level, precise binding of operation permissions and security levels can be achieved, distinguishing between routine and sensitive operations from the source. By initiating boundary compliance pre-verification to the verification server, legality screening can be completed before password operations are triggered, effectively intercepting unnecessary and unauthorized password requests. By establishing a temporary password authorization streaming channel and injecting the password after completing multi-factor authentication of the master device, end-to-end isolated transmission of password data and real-name authorization of users can be achieved. By immediately destroying the channel and clearing the cache after password injection, zero password data residue and non-reusable channels can be achieved, minimizing the exposure of sensitive data. Furthermore, while ensuring the automated execution efficiency of the AI ​​Agent, a closed-loop security control system of pre-verification, in-process isolation, and post-destruction can be constructed, significantly improving the security, compliance, and controllability of password input.

[0037] Figure 2This is a flowchart of the hierarchical authorization execution plan generation provided in the embodiments of this application, such as... Figure 2 As shown, this hierarchical password security input method includes the following steps: Step 201: Divide the task type into different operation security levels, and match corresponding permission boundaries and execution rules for each operation security level.

[0038] In one embodiment, the AI ​​Agent of the task execution terminal performs semantic parsing and risk assessment on task instructions, classifying task types into three security levels based on their sensitivity. Optionally, the low-risk level includes page browsing, file viewing, and routine keyboard and mouse simulation, with read-only permissions and execution rules requiring no authorization and being executed directly locally; the medium-risk level includes file modification, data export, and submission of non-sensitive information, with limited-scope modification permissions and execution rules requiring one-click authorization and local execution; the highest security level refers to all password input operations, with permissions allowing only specified password input, prohibiting associated unauthorized operations, and execution rules requiring the triggering of a temporary channel and multi-factor authentication.

[0039] Step 202: Set the password input operation to the highest security level. The highest security level triggers the establishment of the temporary password authorization stream channel, and the password data injection is completed through the temporary password authorization stream channel.

[0040] In one embodiment, all password input operations, including login password, transaction password, payment password, and administrator password, are uniformly set to the highest security level that cannot be downgraded. This level is the only operation that can trigger the temporary password authorization streaming channel. The execution rules for the highest security level are clearly defined: password injection must be completed through the temporary channel, uniquely bound to the task identifier, valid only once per input, and verified in real time throughout the entire process.

[0041] Step 203: The other security levels of the operation are executed according to the corresponding authorization boundaries and execution rules, without triggering the establishment of the temporary password authorization stream channel.

[0042] In one embodiment, low-risk and medium-risk operations are executed locally according to preset permission boundaries and execution rules, without sending pre-verification requests to the verification server, without establishing a temporary password authorization streaming channel, and without streaming data transmission, ensuring automated execution efficiency. For example, medium-risk operations such as exporting settlement documents and saving files are executed directly locally after a single user authorization. In this embodiment, the temporary password authorization streaming channel is bound to the current task identifier; a single password input corresponds to a single valid channel. Subsequent password inputs for the same task or application require the establishment of a new channel; old channels cannot be reused.

[0043] As described above, by classifying task types into different operational security levels and matching them with corresponding permission boundaries and execution rules, differentiated control over automated tasks can be achieved, balancing the efficiency of low-risk operations with the security strength of high-risk operations. By uniformly setting password input operations to the highest security level and designating it as the only operation capable of triggering the temporary password authorization streaming channel, it can be ensured that all password input behaviors enter the highest level of security control process. By preventing other security level operations from triggering the temporary channel, unnecessary security interactions can be reduced, ensuring the continuity of the automated process. The above solution can form a standardized and quantifiable authorization boundary system, strictly separating password operations from regular operations, meeting the requirements of minimum permissions and operational traceability in highly regulated scenarios.

[0044] Figure 3 This is a flowchart of the two-factor password security input method provided in the embodiments of this application, such as... Figure 3 As shown, this hierarchical password security input method includes the following steps: Step 301: If a new password input request is detected again during the continued execution of the task instruction, the new password input request is marked as the highest security level.

[0045] In one embodiment, after the task execution terminal resumes the local task, if a new password input request is detected again in the same task or the same application, for example, if the login password and transaction password of Tonghuashun are entered twice, the new request is immediately marked as the highest security level and the current task execution is suspended.

[0046] Step 302: Send a boundary compliance pre-verification request to the verification server and receive the pass result returned by the verification server. Based on the pass result, trigger the establishment of a new temporary password authorization stream channel. The new temporary password authorization stream channel is bound to the current task identifier.

[0047] In one embodiment, a boundary compliance pre-verification request is resent to the verification server, carrying new password input node information, hierarchical authorization execution plan, and task identifier. After the verification server completes the dual pre-verification, it returns a pass result. Based on this result, the task execution terminal triggers the establishment of a new temporary password authorization streaming channel. The new channel is still bound to the current task identifier and is completely independent of the old channel. The old channel cannot be reused.

[0048] Step 303: Push the authorization request to the master device and synchronize the hierarchical authorization execution plan. After the master device completes the multi-factor authentication, it injects the password data into the password input control kernel of the corresponding target application through the new temporary password authorization streaming channel.

[0049] In one embodiment, a new authorization request is pushed to the master device, and the updated hierarchical authorization execution plan is synchronized. The master device re-completes multi-factor authentication in the trusted execution environment. After successful authentication, the password data is injected into the password input control kernel of the corresponding target application through a new channel, and the password data is securely isolated throughout the process.

[0050] Step 304: Receive the injection completion status notification and destroy the new temporary password authorization stream channel.

[0051] In one embodiment, upon receiving the injection completion status notification, the newly established temporary password authorization stream channel is immediately destroyed and the end-to-end cache is cleared; the above process must be repeated for each password input for the same task or application to ensure that each password input has independent security control.

[0052] As described above, by re-marking repeated password input requests within the same task or application with the highest security level, it ensures that every password operation is fully securely controlled, preventing a decrease in security level due to continuous input. By re-initiating pre-verification and establishing a new temporary password authorization stream channel, it ensures that each password input corresponds to a single independent channel, avoiding the hijacking and replay risks caused by channel reuse. By sequentially completing master device identity verification and password injection, it ensures that each password authorization is actively confirmed by the user, making the entire process legal and controllable. This solution achieves full security coverage in multi-password node scenarios, maintaining consistent, stable, and high-strength security protection capabilities regardless of whether it's a single or multiple password inputs.

[0053] Figure 4 This is a flowchart of the master device password data processing provided in the embodiments of this application, such as... Figure 4 As shown, this hierarchical password security input method includes the following steps: Step 401: The master device receives the authorization request pushed by the task execution terminal and the synchronous hierarchical authorization execution plan.

[0054] In one embodiment, the master device receives a password authorization request pushed by the task execution terminal through a secure link, and at the same time receives a complete hierarchical authorization execution plan. The hierarchical authorization execution plan specifies the password usage scenario, permission boundaries, channel lifecycle, and target application information. The master device displays the request and plan to the user for the user to confirm authorization.

[0055] Step 402: Based on the authorization request and the hierarchical authorization execution plan, perform a combination verification of at least two identity verification methods within the trusted execution environment of the main device.

[0056] Among them, the Trusted Execution Environment (TEE) is a secure operating environment independent of the main device, isolated from the regular system, which can prevent screenshots, screen recordings, and data theft; the combined verification combines at least two identity verification methods to improve authorization security.

[0057] In one embodiment, after the user confirms authorization, the main device enters the trusted execution environment and initiates multi-factor authentication. Optional authentication methods include: facial biometrics, fingerprint biometrics, voiceprint biometrics, device PIN code, OTP dynamic password, and device binding verification. For example, facial authentication and PIN code authentication are used. Only after both authentications are passed can the user be allowed to enter the password input stage. If either authentication fails, authorization is rejected. The specific combination of authentication methods is not limited here.

[0058] Step 403: After the combined verification is passed, the password data input window is invoked in the trusted execution environment, and the password data is input through the password data input window. The password data is then injected into the password input control kernel of the target application through a temporary password authorization streaming channel.

[0059] In one embodiment, after the combined verification is passed, the master device invokes a dedicated encrypted password input window within the Trusted Execution Environment. This window is independent of other application interfaces and prohibits screenshots, screen recordings, and caching. The user manually enters the password data in the window. The password data is only temporarily processed within the TEE and directly injected into the password input control kernel of the target application through the established temporary password authorization streaming channel, without any data leakage.

[0060] As described above, by having the main device receive authorization requests and hierarchical authorization execution plans within a Trusted Execution Environment (TEE), it is possible to ensure that authorization information is presented and confirmed in a secure, isolated environment, preventing information theft and tampering. By performing a combination of at least two identity verification methods within the TEE, strong authentication can be achieved, ensuring that authorization actions are initiated by legitimate users. Furthermore, by invoking a dedicated password input window within the TEE and directly injecting the password into the target application kernel, it is guaranteed that password data remains within the secure environment and is not accessed by the system or AI Agent throughout the entire process. This solution places the entire password processing workflow within a hardware-level secure area, fundamentally avoiding security threats such as password leakage, screenshot theft, and memory access.

[0061] Figure 5 This is a flowchart of the master device password data storage and retrieval provided in the embodiments of this application, such as... Figure 5 As shown, this hierarchical password security input method includes the following steps: Step 501: If there is a requirement for pre-stored passwords, then set up and continuously retain the highest level password encryption storage module in the trusted execution environment.

[0062] In one embodiment, for users who need to store passwords, the main device provides a highest-level password encryption storage module within a trusted execution environment. This module uses national cryptographic algorithms to store the user's preset passwords. The highest-level password encryption storage module is independent of the main device's conventional storage system and can only be accessed within the TEE, preventing passwords from being cracked or stolen.

[0063] Step 502: After completing the combined verification, retrieve the pre-stored password from the trusted execution environment and inject it into the password input control kernel of the target application through the temporary password authorization stream channel.

[0064] In one embodiment, after the user completes multi-factor authentication and confirms authorization, the main device does not need to manually enter the password. Instead, it directly retrieves the pre-stored password from the highest-level password encryption storage module within the TEE. After the pre-stored password is encrypted by the TEE, it is directly injected into the password input control kernel of the target application through a temporary password authorization streaming channel. Throughout this process, the password data is not stored on the ground or exposed, thus balancing security and convenience.

[0065] As described above, by setting up a high-level password encryption storage module within the main device's TEE, compliant, isolated, and encrypted password storage can be achieved, meeting users' needs for convenient use. By allowing retrieval of pre-stored passwords only after successful multi-factor authentication, it ensures that passwords can only be used with legitimate authorization, preventing unauthorized access. Furthermore, by injecting pre-stored passwords directly into the kernel via a temporary channel, secure password storage, authorized calls, and kernel injection are all achieved without being persisted to the ground, cached, or exposed in plaintext. This solution balances ease of use with high security, supporting both manual input and encrypted pre-store modes, adapting to a wider range of user habits.

[0066] Figure 6 This is a flowchart of the verification server performing verification provided in the embodiments of this application, such as... Figure 6 As shown, this hierarchical password security input method includes the following steps: Step 601: After receiving the boundary compliance pre-verification request sent by the task execution terminal, the verification server extracts the hierarchical authorization execution plan and task identifier.

[0067] In one embodiment, the verification server listens for the pre-verification request from the task execution terminal, parses the message after receiving the request, and extracts the hierarchical authorization execution plan, task identifier, target application identifier, and password input node information as the basis for verification.

[0068] Step 602: Based on the task instruction execution necessity verification corresponding to the task identifier, by comparing the password input request with the task instruction's task chain, confirm that the password input request is a necessary operation step to complete the task instruction, and filter out unnecessary and redundant password triggering requests.

[0069] In one embodiment, the verification server retrieves the original task instruction based on the task identifier, compares the password input request with the task execution link, and confirms that the password input is a necessary prerequisite for completing the task; for example, exporting a settlement statement requires logging into Tonghuashun first, so logging in with a password is a necessary step; if an unnecessary password request is detected, such as a password input that has no business relevance, it is directly filtered and blocked.

[0070] Step 603: Perform a consistency check and confirm that the permission boundaries for the password used in the hierarchical authorization execution plan are consistent with the task instructions through natural language semantic comparison.

[0071] Among them, consistency verification is a semantic comparison that confirms that the password usage permissions in the hierarchical authorization execution plan are consistent with the user's original instructions, thus preventing unauthorized access.

[0072] In one embodiment, the verification server uses natural language semantic comparison technology to compare the permission boundaries of password usage in the hierarchical authorization execution plan, such as allowing only login and prohibiting transactions, with the user's original task instructions to confirm that the two are completely consistent; if the permission boundary is detected to exceed the task instructions, such as allowing transactions in the plan but requiring data export in the instruction, the verification is determined to fail.

[0073] Step 604: After both the necessity check and the consistency check pass, a pass result is generated and returned to the task execution terminal to trigger the task execution terminal to establish a temporary password authorization streaming channel.

[0074] In one embodiment, after both the necessity check and the consistency check pass, the verification server generates a pre-verification pass result, encrypts it, and returns it to the task execution terminal to trigger the channel establishment; if either check fails, the verification server directly intercepts the password input request, prevents the establishment of the temporary password authorization streaming channel, and pushes a verification failure alarm to the master device.

[0075] As described above, by performing necessity checks on password input requests, it can be confirmed that the password operation is a necessary step to complete the task, filtering out redundant, malicious, and unnecessary password triggering behaviors. By performing consistency checks, it can be ensured that the password usage permission boundaries completely match the user's original task instructions, avoiding unauthorized design and use beyond the scope. By only allowing the establishment of temporary channels after both checks have passed, strong compliance monitoring can be performed at the entry point, blocking non-compliant password processes. The above solution can achieve accurate pre-emptive verification of password operations, reducing the security risks and resource consumption caused by invalid and unauthorized password requests.

[0076] Figure 7 This is a flowchart of the end-to-end monitoring of the verification server provided in the embodiments of this application, such as... Figure 7As shown, this hierarchical password security input method includes the following steps: Step 701: The verification server starts real-time verification of full-link boundary compliance to monitor whether the subsequent operations of the task execution terminal are within the permission boundaries defined by the hierarchical authorization execution plan.

[0077] In one embodiment, after the temporary password authorization streaming channel is established, the verification server starts full-link real-time monitoring to continuously verify the subsequent operations of the task execution terminal and whether the use of the temporary password authorization streaming channel is strictly within the permission boundaries defined by the hierarchical authorization execution plan. Optionally, the monitoring dimensions include: AI Agent operation behavior, channel data transmission content, target application operation scope, and channel lifecycle.

[0078] Step 702: When it is detected that the operation exceeds the permission boundary defined by the hierarchical authorization execution plan, or the use of the temporary password authorization streaming channel does not comply with the preset security rules, the temporary password authorization streaming channel is destroyed and the current task is interrupted, an alarm message is pushed to the master device and the full-link audit log is retained.

[0079] In one embodiment, the verification server immediately triggers a circuit breaker mechanism when any of the following abnormal situations are detected: Optionally, the task execution terminal operation exceeds the permission boundary (e.g., triggering a transaction or transfer after login); non-password data is transmitted through a temporary channel; the channel exceeds its preset lifespan; the target application is switched, or the password control is forged; or the user actively terminates authorization. The circuit breaker action interrupts the current automated task by immediately destroying the temporary password authorization streaming channel, pushing unauthorized / abnormal alarm information to the main device, and simultaneously retaining an immutable audit log across the entire chain and storing it on a blockchain for subsequent security tracing and evidence presentation.

[0080] The above-mentioned solutions, by initiating real-time compliance verification across the entire supply chain, continuously monitor whether AI Agent operations and channel usage are within the authorized scope, achieving dynamic risk management during the process. By immediately destroying channels and interrupting tasks upon detecting unauthorized operations, abnormal channel usage, or expiration, immediate circuit breaking can be implemented to prevent risk escalation. Furthermore, by pushing alarms to the main device and retaining tamper-proof audit logs, risk perception, process traceability, and event evidence can be achieved. This comprehensive solution forms a robust control mechanism with continuous monitoring, rapid response, and immediate shutdown for violations, meeting the regulatory requirements of highly compliant scenarios such as finance and government.

[0081] Figure 8 This is a structural diagram of a hierarchical control-based secure password input device provided in an embodiment of this application. The device is configured to execute the hierarchical control-based secure password input method provided in the above embodiment, and possesses the corresponding functional modules and beneficial effects for executing the method. Figure 8 As shown, the device specifically includes: The task planning module 801 is used to receive the issued task instructions and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instructions. The requirement detection module 802 is used to detect a password input request of the target application during the execution of the task instruction locally, mark the password input request as the highest security level, and send a boundary compliance pre-verification request to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result. The channel establishment module 803 is used to receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization stream channel between the task execution terminal and the main device based on the pass result; The password injection module 804 is used to push an authorization request to the master device and synchronize the hierarchical authorization execution plan after the temporary password authorization streaming channel is established, so that the master device can complete multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and inject the input password data into the password input control kernel of the target application through the temporary password authorization streaming channel. The channel destruction module 805 is used to destroy the temporary password authorization stream channel and clear the link memory cache after receiving the completion status notification of the password data injection into the password input control kernel, and continue the execution of the task instruction locally.

[0082] The above-described approach, by generating tiered authorization execution plans based on task type and operational security level, enables the matching of differentiated control rules for operations with varying risks. Password input is designated as the highest security level, achieving refined control over access boundaries. By marking password input requests with the highest security level and initiating pre-verification, compliance screening is completed before password operations are triggered, filtering out unnecessary and unauthorized requests. The establishment of a dedicated temporary password authorization stream channel ensures the isolation of password data from regular task data, reducing the risk of interception and tampering. Multi-factor authentication and kernel-level password injection on the main device guarantee that password input is authorized by legitimate users and remains untouched by the AI ​​Agent and execution terminal throughout the process. Immediately destroying the channel and clearing the cache after injection ensures zero password data residue and non-reusable channels, guaranteeing security throughout the entire lifecycle. This solution constructs a complete security closed loop—pre-verification, in-process isolation, and post-destruction—without interrupting the AI ​​Agent's automated execution process, significantly improving the security, controllability, and compliance of password input in automated scenarios.

[0083] In one possible embodiment, the task planning module 801 is specifically used for: The task types are divided into different operation security levels, and corresponding permission boundaries and execution rules are matched for each operation security level. The password input operation is set to the highest security level, which triggers the establishment of the temporary password authorization streaming channel, and the password data injection is completed through the temporary password authorization streaming channel. Other operational security levels are executed according to the corresponding authorization boundaries and execution rules, without triggering the establishment of the temporary password authorization stream channel; The temporary password authorization stream channel is bound to the current task identifier, and each password input is valid for a single temporary password authorization stream channel.

[0084] In one possible embodiment, after the channel destruction module 805, it is specifically used for: If a new password input request is detected again during the continued execution of the task instructions, the new password input request will be marked as the highest security level. Send a boundary compliance pre-verification request to the verification server and receive the pass result returned by the verification server. Based on the pass result, trigger the establishment of a new temporary password authorization stream channel. The new temporary password authorization stream channel is bound to the current task identifier. The master device pushes an authorization request and synchronizes the hierarchical authorization execution plan. After the master device completes multi-factor authentication, it injects the password data into the password input control kernel of the corresponding target application through the new temporary password authorization streaming channel. Receive the injection completion status notification and destroy the new temporary password authorization stream channel; For secondary password input for the same task or application, a new temporary password authorization stream channel needs to be established.

[0085] In one possible embodiment, after the password injection module 804, the master device is specifically used for: The master device receives the authorization request pushed by the task execution terminal and the synchronous hierarchical authorization execution plan; Based on the authorization request and the hierarchical authorization execution plan, at least two identity verification methods are combined and verified within the trusted execution environment of the main device. After the combined verification is passed, the password data input window is invoked within the trusted execution environment, and password data is entered through the password data input window. The password data is then injected into the password input control kernel of the target application through a temporary password authorization streaming channel.

[0086] In one possible embodiment, after the password injection module 804, the master device is further configured to: If there is a need for pre-stored passwords, a highest-level password encryption storage module is set up and continuously retained within the trusted execution environment; After completing the combined verification, the pre-stored password is retrieved from the trusted execution environment and injected into the password input control kernel of the target application through the temporary password authorization streaming channel.

[0087] In one possible embodiment, after the demand detection module 802, the verification server is specifically used for: After receiving the boundary compliance pre-verification request sent by the task execution terminal, the verification server extracts the hierarchical authorization execution plan and task identifier. Based on the necessity verification of the task instruction execution corresponding to the task identifier, by comparing the task link of the password input request and the task instruction, it is confirmed that the password input request is a necessary operation step to complete the task instruction, and unnecessary and redundant password triggering requests are filtered out. Perform a consistency check and confirm, through natural language semantic comparison, that the permission boundaries used by the password in the hierarchical authorization execution plan are consistent with the task instructions; After both the necessity check and the consistency check pass, a pass result is generated and returned to the task execution terminal to trigger the task execution terminal to establish a temporary password authorization streaming channel; If any verification fails, the verification server intercepts the password input request and prevents the establishment of the temporary password authorization streaming channel.

[0088] In one possible embodiment, after the channel destruction module 805, the verification server is further configured to: The verification server initiates real-time full-link boundary compliance verification to monitor whether subsequent operations of the task execution terminal are within the permission boundaries defined by the hierarchical authorization execution plan; If an operation is detected to exceed the permission boundaries defined by the hierarchical authorization execution plan, or if the use of the temporary password authorization streaming channel does not comply with preset security rules, the temporary password authorization streaming channel is destroyed and the current task is interrupted. An alarm message is pushed to the master device and the full-link audit log is retained.

[0089] Figure 9 This is a structural diagram of the electronic device provided in the embodiments of this application, such as... Figure 9 As shown, the device includes a processor 901, a memory 902, an input device 903, and an output device 904.

[0090] The number of processors 901 can be one or more. Figure 9Taking a processor 901 as an example; the processor 901, memory 902, input device 903, and output device 904 can be connected via a bus or other means. Figure 9 Taking a bus connection as an example, the memory 902, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the hierarchical control-based password security input method in this embodiment. The processor 901 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 902, thereby realizing the aforementioned hierarchical control-based password security input method. The input device 903 can be configured to receive input numeric or character information, user-issued task instructions, verification result information returned by the verification server, and identity verification and authorization status information fed back by the master device, and generate key signal inputs related to the device's task execution settings and password security control function. The output device 904 may include a display screen or other display device, and can be configured to display the automated task execution progress, password input authorization waiting prompt, boundary compliance verification status, abnormal alarm information, and password injection completion status.

[0091] This application also provides a non-volatile storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are configured to execute a hierarchical password security input method described in the above embodiments. The method includes: receiving a task instruction; generating a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instruction; if a password input request from a target application is detected during the local execution of the task instruction, marking the password input request as having the highest security level and sending a boundary compliance pre-verification request to a verification server; receiving a pass result returned by the verification server and triggering the establishment of a temporary password authorization stream channel between the task execution terminal and the main device; pushing an authorization request to the main device and synchronizing the hierarchical authorization execution plan; after the main device completes multi-factor authentication, injecting password data into the password input control kernel of the target application through the temporary password authorization stream channel; and after receiving a password data injection completion status notification, destroying the temporary password authorization stream channel and clearing the link memory cache, and continuing to execute the local task instruction.

[0092] It is worth noting that in the above embodiments of the password security input device based on hierarchical control, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not configured to limit the protection scope of the embodiments of this application.

[0093] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments provided herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the claims.

Claims

1. A password security input method based on hierarchical control, applied to a task execution terminal, characterized in that, The input method includes: Receive the task instructions issued, and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instructions; If a password input request from the target application is detected during the execution of the task instruction locally, the password input request is marked as the highest security level, and a boundary compliance pre-verification request is sent to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result. Receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization streaming channel between the task execution terminal and the main device based on the pass result; After the temporary password authorization streaming channel is established, an authorization request is pushed to the master device and the hierarchical authorization execution plan is synchronized, so that the master device completes multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and injects the input password data into the password input control kernel of the target application through the temporary password authorization streaming channel; After receiving the completion status notification of the password data injection into the password input control kernel, the temporary password authorization stream channel is destroyed and the link memory cache is cleared, and the execution of the task instruction continues locally.

2. The input method according to claim 1, characterized in that, The generation of a corresponding tiered authorization execution plan based on the task type and operation security level of the task instruction includes: The task types are divided into different operation security levels, and corresponding permission boundaries and execution rules are matched for each operation security level. The password input operation is set to the highest security level, which triggers the establishment of the temporary password authorization streaming channel, and the password data injection is completed through the temporary password authorization streaming channel. Other operational security levels are executed according to the corresponding authorization boundaries and execution rules, without triggering the establishment of the temporary password authorization stream channel; The temporary password authorization stream channel is bound to the current task identifier, and each password input is valid for a single temporary password authorization stream channel.

3. The input method according to claim 1, characterized in that, After continuing the execution of the locally described task instructions, the input method further includes: If a new password input request is detected again during the continued execution of the task instructions, the new password input request will be marked as the highest security level. Send a boundary compliance pre-verification request to the verification server and receive the pass result returned by the verification server. Based on the pass result, trigger the establishment of a new temporary password authorization stream channel. The new temporary password authorization stream channel is bound to the current task identifier. The master device pushes an authorization request and synchronizes the hierarchical authorization execution plan. After the master device completes multi-factor authentication, it injects the password data into the password input control kernel of the corresponding target application through the new temporary password authorization streaming channel. Receive the injection completion status notification and destroy the new temporary password authorization stream channel; For secondary password input for the same task or application, a new temporary password authorization stream channel needs to be established.

4. The cryptographic security input method based on hierarchical control according to claim 1, characterized in that, The input method further includes: The master device receives the authorization request pushed by the task execution terminal and the synchronous hierarchical authorization execution plan; Based on the authorization request and the hierarchical authorization execution plan, at least two identity verification methods are combined and verified within the trusted execution environment of the main device. After the combined verification is passed, the password data input window is invoked within the trusted execution environment, and password data is entered through the password data input window. The password data is then injected into the password input control kernel of the target application through a temporary password authorization streaming channel.

5. The input method according to claim 4, characterized in that, The method of invoking a password data input window within the trusted execution environment and inputting password data through the password data input window further includes: If there is a need for pre-stored passwords, a highest-level password encryption storage module is set up and continuously retained within the trusted execution environment; After completing the combined verification, the pre-stored password is retrieved from the trusted execution environment and injected into the password input control kernel of the target application through the temporary password authorization streaming channel.

6. The cryptographic security input method based on hierarchical control according to claim 1, characterized in that, The input method further includes: After receiving the boundary compliance pre-verification request sent by the task execution terminal, the verification server extracts the hierarchical authorization execution plan and task identifier. Based on the necessity verification of the task instruction execution corresponding to the task identifier, by comparing the task link of the password input request and the task instruction, it is confirmed that the password input request is a necessary operation step to complete the task instruction, and unnecessary and redundant password triggering requests are filtered out. Perform a consistency check and confirm, through natural language semantic comparison, that the permission boundaries used by the password in the hierarchical authorization execution plan are consistent with the task instructions; After both the necessity check and the consistency check pass, a pass result is generated and returned to the task execution terminal to trigger the task execution terminal to establish a temporary password authorization streaming channel; If any verification fails, the verification server intercepts the password input request and prevents the establishment of the temporary password authorization streaming channel.

7. The input method according to claim 1, characterized in that, After continuing the execution of the task instruction locally, the input method further includes: The verification server initiates real-time full-link boundary compliance verification to monitor whether subsequent operations of the task execution terminal are within the permission boundaries defined by the hierarchical authorization execution plan; If an operation is detected to exceed the permission boundaries defined by the hierarchical authorization execution plan, or if the use of the temporary password authorization streaming channel does not comply with preset security rules, the temporary password authorization streaming channel is destroyed and the current task is interrupted. An alarm message is pushed to the master device and the full-link audit log is retained.

8. A password security input device based on hierarchical control, characterized in that, include: The task planning module is used to receive the issued task instructions and generate a corresponding hierarchical authorization execution plan based on the task type and operation security level of the task instructions. The requirement detection module is used to detect a password input request from the target application during the execution of the task instruction locally. If the password input request is detected, it is marked as the highest security level, and a boundary compliance pre-verification request is sent to the verification server. The pre-verification request carries the hierarchical authorization execution plan and the task identifier of the task instruction, so that the verification server performs pre-verification based on the hierarchical authorization execution plan and the task identifier, and generates a pass result. The channel establishment module is used to receive the pass result returned by the verification server, and trigger the establishment of a temporary password authorization stream channel between the task execution terminal and the main device based on the pass result; The password injection module is used to push an authorization request to the master device and synchronize the hierarchical authorization execution plan after the temporary password authorization stream channel is established, so that the master device can complete multi-factor authentication based on the authorization request and the hierarchical authorization execution plan, and inject the input password data into the password input control kernel of the target application through the temporary password authorization stream channel. The channel destruction module is used to destroy the temporary password authorization stream channel and clear the link memory cache after receiving the completion status notification of the password data injection into the password input control kernel, and continue the execution of the task instructions locally.

9. An electronic device, characterized in that, include: Memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the hierarchical control-based secure input method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the cryptographic security input method based on hierarchical control as described in any one of claims 1-7.

Images