Client content verification system, method, device and equipment based on security anchor point architecture and medium

Abstract

The invention discloses a client content verification system, method, device and equipment based on a security anchor point architecture and a medium, relates to the technical field of information security, and aims to effectively prevent an attacker from issuing and executing malicious codes to a user browser for the first time and improve the security. The client content verification system based on the security anchor point architecture comprises a first service component, a second service component and a user terminal device: when the first service component receives an application access request for the first time, the first service component creates a verification execution environment in the user terminal device, and when it is detected that the second service component feeds back a request response to the user terminal device, the second service component sends the verification execution environment to the user terminal device; the digital signature is verified, and when verification succeeds, the client device is indicated to display according to the request response; the second service component receives the service request, generates a request response carrying a digital signature and feeds back the request response; and the user terminal equipment sends a service request according to the access demand of the user, and displays the content to the user according to the indication of the first service component.

Description

Technical Field

[0001] This application relates to the field of information security technology, and in particular to a client content verification system, method, apparatus, device and medium based on a security anchor architecture. Background Technology

[0002] In today's digital age, Web applications have become an indispensable part of people's lives and work, widely used in various fields such as financial transactions, government affairs, and social entertainment. Currently, most Web applications adopt a single-service architecture or a tightly coupled multi-service architecture. In this architecture, the front-end presentation logic and the back-end business logic share the same security context. While this design simplifies the development process, it also introduces serious security vulnerabilities into Web applications. Therefore, corresponding measures need to be taken to ensure the security of Web applications.

[0003] In related technologies, various measures can be taken to ensure the security of web applications. For example, content security policies restrict the source of executable resources through HTTP (Hypertext Transfer Protocol) headers to prevent the loading of malicious resources; sub-resource integrity is used to verify the integrity of static resources to ensure that resources are not tampered with during transmission; web application firewalls filter malicious requests on the server side to prevent external attackers from illegally accessing the server; code obfuscation and encryption increase the complexity of the code, making reverse engineering more difficult and protecting the core logic of the application.

[0004] However, the applicant recognizes that the relevant technology has at least the following technical problems: On the one hand, it is difficult to solve the problem of application services being out of control for the first time. When a user accesses a web service for the first time, the browser lacks an independent reference to verify whether the initial page and security rules issued by the server are trustworthy. Once the server is a phishing website or has been compromised, attackers can directly inject malicious logic, control the security boundary from the first byte, steal user data, and hijack sessions. On the other hand, with the development of web technology, the attack surface is constantly expanding. WebAssembly (web assembly language) has improved the efficiency of malicious code execution, single-page application architecture has increased the risk of client-side attacks, third-party libraries and micro-frontend architecture have expanded the attack surface, and real-time communication applications are difficult to implement strict security checks due to the requirement of low latency. Moreover, once the application service is completely compromised, there is a lack of effective mechanisms to prevent attackers from publishing and executing malicious code to the user's browser, resulting in low security. Summary of the Invention

[0005] In view of this, this application provides a client-side content verification system, method, apparatus, device, and medium based on a secure anchor architecture. The main purpose is to solve the problem of low security caused by the lack of an effective mechanism to prevent attackers from publishing and executing malicious code to the user's browser on the first visit.

[0006] According to a first aspect of this application, a client-side content verification system based on a secure anchor architecture is provided, the system comprising a first service component, a second service component, and a user terminal device: When the first service component receives the application access request transmitted by the user terminal device for the first time, it creates a verification execution environment in the user terminal device. When it detects that the second service component has sent a request response to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. When the digital signature is successfully verified, it instructs the user terminal device to display content in accordance with the request response. The second service component receives the service request sent by the user terminal device, generates a request response carrying a digital signature for the service request, and sends it back to the user terminal device. During the interaction with the user, the user terminal device sends the service request to the second service component according to the user's access needs, and displays content to the user according to the instructions of the first service component and the request response fed back by the second service component.

[0007] According to a second aspect of this application, a client-side content verification method based on a secure anchor architecture is provided, the method being applied to a first service component, comprising: Upon first receiving an application access request transmitted from a user terminal device, a verification execution environment is created in the user terminal device. When the second service component sends a request response to the user terminal device, the digital signature carried in the request response is verified based on the verification execution environment. The request response is generated by the second service component in response to the service request sent by the user terminal device and carries the digital signature. The service request is sent by the user terminal device to the second service component according to the user's access needs during the interaction with the user. When the digital signature is successfully verified, the user terminal device is instructed to display content in accordance with the request response.

[0008] According to a third aspect of this application, a client-side content verification device based on a secure anchor architecture is provided, the device being applied to a first service component, comprising: A creation module is used to create a verification execution environment in the user terminal device when an application access request is first received from the user terminal device. The verification module is used to verify the digital signature carried in the request response based on the verification execution environment when the second service component sends a request response to the user terminal device. The request response is generated by the second service component in response to a service request sent by the user terminal device and carries the digital signature. The service request is sent by the user terminal device to the second service component according to the user's access needs during the interaction with the user. The display module is used to instruct the user terminal device to display content based on the request response when the digital signature verification is successful.

[0009] According to a fourth aspect of this application, an apparatus is provided, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method described in any of the first aspects above.

[0010] According to a fifth aspect of this application, a medium is provided that stores a computer program, when executed by a processor, implementing the steps of any one of the methods described in the first aspect.

[0011] Using the above technical solutions, this application provides a client-side content verification system, method, apparatus, device, and medium based on a secure anchor architecture. The client-side content verification system includes a first service component, a second service component, and a user terminal device. When the first service component receives an application access request from the user terminal device for the first time, it creates a verification execution environment on the user terminal device. When it detects a request response from the second service component to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. When the digital signature verification is successful, it instructs the user terminal device to display content according to the request response. By setting up the first and second service components, the secure anchor is logically isolated from the application service. A breach of the application service will not cause the entire system to crash, preventing attackers from controlling the security boundary from the first byte. Furthermore, by creating a verification execution environment on the user terminal device, content verification can be performed on the user terminal device. Even if the application server is completely controlled, malicious code execution can be prevented, effectively preventing attackers from initially publishing and executing malicious code to the user's browser, further enhancing security.

[0012] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0013] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This illustration shows a schematic diagram of a client-side content verification method based on a security anchor architecture provided in an embodiment of this application; Figure 2 This illustration shows a schematic diagram of a client-side content verification device based on a security anchor architecture, as provided in an embodiment of this application. Figure 3 A schematic diagram of the device structure of a computer device provided in an embodiment of this application is shown. Detailed Implementation

[0014] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0015] Before providing a detailed explanation of the technical solution of this application, a brief introduction to the system architecture of the client-side content verification system based on the security anchor architecture involved in this application will be given: A client-side content verification system based on a secure anchor architecture includes a first service component, a second service component, and a user terminal device: When the first service component receives an application access request from a user terminal device for the first time, it creates a verification execution environment on the user terminal device. Upon detecting a request response from the second service component to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. If the digital signature verification is successful, it instructs the user terminal device to display the content according to the request response. In summary, in practical applications, the service environment of the first service component can be a physically isolated server, a logically isolated container, or an independent cloud environment. This environment has sandbox attributes, which can prohibit network access and restrict cross-domain resource sharing. Its functions include providing an initial page, security verification logic, and signature services. It possesses security features such as minimalist design, minimized attack surface, private key storage area, and strict access control.

[0016] The second service component receives service requests sent by user terminal devices, generates a request response carrying a digital signature, and sends it back to the user terminal device. In summary, in practical applications, the service environment of the second service component is an independent service environment with a security boundary set by the security anchor. The security boundary can be constructed through several methods, such as physically isolated computing resources, logically isolated virtualization environments, independent identity authentication and authorization mechanisms, and dedicated communication channels and protocols. Its function is to implement business application logic, process and store data, and it possesses the security features of signing dynamic content with a private key and communicating with the security anchor through a secure channel.

[0017] During user terminal device interaction, based on the user's access needs, it sends service requests to the second service component, and displays content to the user according to the instructions of the first service component and the request response returned by the second service component. In summary, in practical applications, the user terminal device runs a web browser with a technically isolated verification execution environment created by secure anchors, possessing security features such as a secure content rendering mechanism.

[0018] This application provides a client-side content verification method based on a security anchor architecture, such as... Figure 1 As shown, this method is applied to the first service component, including: S10: Upon first receiving an application access request transmitted from a user terminal device, create a verification execution environment in the user terminal device.

[0019] In this embodiment, when a user initiates an application access request through a user terminal device (a user terminal device is a device through which a user interacts with the system, such as a common personal computer or smartphone, on which various applications run to support user operations), the first service component will receive the request for the first time. At this time, the first service component will create a verification execution environment in the user terminal device. The verification execution environment is a relatively independent and secure space with sandbox attributes, which can prohibit network access and restrict cross-domain resource sharing. This means that programs running in this environment cannot freely interact with external networks or access resources from other different sources, thus providing a secure and reliable environment for subsequent verification operations.

[0020] In this way, by creating an independent verification execution environment on the user's terminal device, the verification process is isolated from the regular application runtime environment. This avoids the verification process being affected by malicious code or other insecure factors that may exist in the application, providing a clean and secure environment for subsequent digital signature verification and ensuring the accuracy and security of the verification from the source. For example, suppose a user uses a browser on a smartphone to access an online banking application. When the user clicks the access button, the smartphone (user terminal device) sends an application access request to the first service component. After receiving the request, the first service component creates a verification execution environment on the smartphone. This environment is like an independent small room, isolated from other applications and the external network, preparing for subsequent verification work.

[0021] Step S10, namely creating a verification execution environment in the user terminal device, includes: S11: Feedback the initial page, which includes security anchor logic, to the user terminal device.

[0022] When the first service component receives an application access request from a user's terminal device for the first time, it sends an initial page containing security anchor logic back to the user's terminal device. This security anchor logic is a set of code used to perform content verification operations. It is the core executable code set injected by the first service component (security anchor) into the user's terminal web browser, acting as the "agent" of the first service component in the user's browser. All client operations related to content verification, environment isolation, and security responses are initiated and controlled by it. For example, when a user accesses an online financial services website, the user initiates an access request through a browser on their mobile phone. After receiving the request, the first service component sends an initial page containing security anchor logic back to the mobile browser. The initial page acts like a special "container," and the embedded security anchor logic code begins to run when the browser loads the page, laying the foundation for subsequent verification and security operations.

[0023] In this way, by providing an initial page containing security anchor logic, the core code for verification and security control is introduced into the user's terminal device. This allows the verification process to be performed locally on the user's device, reducing frequent interactions with external servers and lowering the risk of data theft or tampering during transmission. Simultaneously, the security anchor logic, as the representative of the first service component on the user's end, effectively isolates the application service logic. Even if the application service is attacked, it will not directly affect the operation of the verification and security mechanisms, thus preventing attackers from controlling the security boundary from the initial stage. S12: By running the initial page, a sandbox environment is created in the user's terminal device, the verification logic document is set up, and cross-environment communication links are initialized to complete the creation of the verification execution environment in the user's terminal device.

[0024] After receiving the initial page containing the security anchor logic, the user terminal device will run the page. During the process, a sandbox environment is first created on the user terminal device. The sandbox environment is a relatively independent and secure space with strict access control mechanisms that can prohibit network access and restrict cross-domain resource sharing. This means that programs running in this environment cannot freely interact with external networks or access resources from other sources, thus providing a secure and reliable environment for subsequent verification operations.

[0025] Next, a verification logic document will be set up, which includes the public key and the signature verification function. The public key is crucial information used to verify digital signatures; it ensures that the received data indeed comes from a legitimate sender and has not been tampered with. The signature verification function is the code that uses the public key to decrypt and compare the digital signature. By executing this function, the validity of the digital signature can be determined.

[0026] Finally, a cross-environment communication link is initialized. This link is used for secure data transmission and interaction between different environments, such as sandbox environments and external application environments. By establishing this link, the verification execution environment can work collaboratively with other parts while ensuring security.

[0027] Thus, creating a sandbox environment through the above process further enhances the security of the verification process, isolating the verification operation from potentially risky external environments. Setting up a verification logic document provides the necessary tools and parameters for digital signature verification, ensuring the accuracy and reliability of the verification. Initializing a cross-environment communication link ensures that the verification execution environment can effectively collaborate with other parts, enabling the entire verification process to complete smoothly. By creating the verification execution environment through these operations, content verification can be performed on user terminal devices. Even if the application server is completely controlled, malicious code execution can be prevented, effectively preventing attackers from initially releasing and executing malicious code to the user's browser, further enhancing system security. For example, in the online shopping platform example mentioned above, after the tablet's browser runs the initial page, a sandbox environment is created, restricting the product information verification process to this secure space. Simultaneously, a verification logic document containing public keys and signature verification functions is set up. When a product information request response is received, these tools are used for digital signature verification. Furthermore, a cross-environment communication link is initialized, allowing the verification results to be promptly fed back to the browser for product display, ensuring that users see safe and reliable product information.

[0028] S20: When a request response is detected from the second service component to the user terminal device, the digital signature carried in the request response is verified based on the verification execution environment.

[0029] In this embodiment, during interaction with the user, the user terminal device sends a service request to the second service component based on the user's access needs. (A service request is information sent by the user terminal device to the second service component to obtain a specific service, including the specific requirements of the service needed by the user.) Upon receiving the service request, the second service component generates a request response and carries a digital signature on the response. (A digital signature is a technical means to verify the integrity and authenticity of data. It uses a private key to encrypt the data, and only the corresponding public key can decrypt and verify it, thereby ensuring that the data has not been tampered with during transmission and that its source is reliable.) When the first service component detects that the second service component has sent a request response to the user terminal device, it verifies the digital signature carried in the request response based on the previously created verification execution environment. Specifically, it decrypts the digital signature using a pre-stored public key. If decryption is successful, it indicates that the digital signature verification is successful, meaning that the request response has not been tampered with during transmission and indeed comes from the second service component.

[0030] In this way, by verifying digital signatures within an independent verification execution environment, attackers can effectively prevent tampering with request responses during transmission, ensuring that the data received by the user's terminal device is complete and authentic. Simultaneously, because the verification process takes place in an independent environment, external interference is avoided, further improving the accuracy and security of the verification and guaranteeing the reliability of client-side content verification. For example, when a user accesses an e-commerce website through a computer browser, the computer (user terminal device) sends a request to a second service component to view product details. The second service component generates a request response containing the product details, signs the response data using its private key, and sends it back to the computer. Upon detecting this request response, the first service component, within the previously created verification execution environment, decrypts and verifies the digital signature using a pre-stored public key, ensuring the product details data is trustworthy.

[0031] In step S20, that is, when the second service component sends a request response to the user terminal device, the digital signature carried in the request response is verified based on the verification execution environment, including: S21: Continuously intercept the responses from the second service component based on the verification execution environment.

[0032] When a user terminal device interacts with a second service component, and the second service component sends a response back to the user terminal device, the first service component uses a verification execution environment created on the user terminal device to continuously intercept the responses from the second service component. As described above, the verification execution environment is a relatively independent and secure space with the ability to intercept and process network responses and monitor all data streams originating from the second service component. For example, in an online ticketing system, after a user sends a booking request to a ticketing server (the second service component) via a ticketing application on their mobile phone (the user terminal device), the ticketing server returns a series of response data, such as order confirmation information and ticket price details. At this time, the first service component, using the verification execution environment, acts like a "gatekeeper," intercepting these returned response data in real time to ensure that subsequent verification operations are performed before the response reaches other parts of the user terminal device.

[0033] In this way, by continuously intercepting the responses from the second service component, control can be exercised at the critical stage when the response enters the user terminal device, preventing unverified response data from directly entering the system. This effectively prevents potential malicious data or code from executing on the user terminal device, providing a pre-emptive guarantee for subsequent digital signature verification. It ensures that only responses that have been intercepted and preliminarily processed will enter the verification process, enhancing the security and controllability of the entire verification process.

[0034] S22: When a request response from the second service component to the user terminal device is intercepted, extract the digital signature from the request response.

[0035] After the verification execution environment successfully intercepts the request response from the second service component, it extracts the digital signature from the response. When generating the request response, the second service component determines the business content based on the service request sent by the user terminal device. For example, in the aforementioned ticketing reservation system, the business content might include the order number, seat information, and ticket price. The second service component then uses its private key to sign and encrypt the business content, generating a digital signature. This digital signature acts as a "unique mark" of the business content, ensuring it is not tampered with during transmission. Finally, the second service component combines the business content and the digital signature to generate the request response and sends it back to the user terminal device. Therefore, when the verification execution environment intercepts the request response, it accurately extracts the digital signature from the response data according to predetermined rules and algorithms. This provides the necessary data for subsequent decryption and verification of the digital signature using the public key, ensuring the accuracy and specificity of the verification process. Only request responses carrying valid digital signatures can pass verification, further enhancing system security.

[0036] S23: The signature verification function is called by the verification execution environment to decrypt the digital signature using the public key, thereby verifying the digital signature.

[0037] After extracting the digital signature, the verification execution environment calls a pre-configured signature verification function. This function is specifically designed to decrypt and compare the digital signature. The verification execution environment uses a pre-stored public key to decrypt the extracted digital signature. The public key is a set of keys corresponding to the private key held by the second service component; it is capable of decrypting digital signatures encrypted with the corresponding private key.

[0038] Therefore, when decryption of a digital signature using a public key is successful, it indicates that the digital signature is legitimate, meaning the request / response has not been tampered with during transmission and indeed originates from the second service component. In this case, the digital signature verification is considered successful. Conversely, when decryption fails, it indicates that the digital signature may have been tampered with or does not originate from a legitimate second service component. In this case, the digital signature verification is considered failed. For example, in a ticketing system, if decryption is successful, the user's terminal device can confidently display order confirmation information and other business content. If decryption fails, the system will block the display of related content and may issue a security warning. Thus, by calling the signature verification function and using a public key to decrypt and verify the digital signature, the reliability and security of the request / response can be accurately determined, ensuring that the data received by the user's terminal device has been verified as having a legitimate source. Even if the application server is completely compromised, malicious code execution can be prevented, effectively preventing attackers from publishing and executing malicious code to the user's browser, further enhancing system security and protecting user information security and the stable operation of the system.

[0039] S30: When the digital signature verification is successful, instruct the user terminal device to display the content according to the request response.

[0040] In this embodiment, after the first service component successfully verifies the digital signature carried in the request response, it sends an instruction to the user terminal device, requesting the user terminal device to display content based on the request response. Upon receiving the instruction, the user terminal device displays the corresponding content to the user on its display interface according to the data in the request response. Since the digital signature has already been verified, ensuring the authenticity and integrity of the request response, the displayed content is secure and reliable, and the user can view and use it with confidence.

[0041] In this way, through the above process, the user's terminal device is only instructed to display content after successful digital signature verification. This ensures that the content seen by the user is securely verified, preventing the user from accessing tampered or malicious content. It effectively prevents attackers from publishing and executing malicious code into the user's browser, further enhancing the overall system security and providing users with a safe and reliable user environment. For example, in the e-commerce website example above, after the first service component successfully verifies the digital signature, it instructs the computer browser to display product details. Users can then see accurate and reliable product information on their browser, such as price, specifications, and descriptions, allowing them to make informed purchasing decisions.

[0042] In another alternative implementation, when digital signature verification fails, a preset security response mechanism is triggered, and a security alarm operation is executed according to the instructions of the security response mechanism. Specifically, when executing the security alarm operation according to the instructions of the security response mechanism, the following four methods can be used: 1. Display security warnings.

[0043] When digital signature verification fails, a pre-defined security response mechanism is triggered. If this mechanism displays a security warning, it quickly pushes a security alert to the user's terminal device. This warning can be a visual or text message, presented in a prominent manner to promptly attract the user's attention. The push process utilizes a pre-established communication channel to ensure the warning reaches the user's terminal device accurately. For example, in an online education platform, when a student uses a tablet to access course resources, and the server reports a digital signature verification failure for the course data, a security warning message containing "Potential security risk detected, please proceed with caution" is immediately generated and quickly pushed to the student's tablet via the network.

[0044] In this way, the mechanism can inform users of security risks immediately, enabling them to understand the potential dangers of their current operations and preventing them from continuing to perform potentially dangerous actions due to ignorance, thereby effectively protecting users' personal information and device security. II. Restricting component functions.

[0045] If the security response mechanism instructs that the functionality of a component be restricted, the functions of the second service component will be strictly limited. As mentioned above, the second service component is a module responsible for providing specific business functions and service logic; restricting its functionality means prohibiting it from sending request responses to the user's terminal device. Specifically, this restriction can be implemented through access control lists or permission management mechanisms, setting the output permissions of the second service component to a prohibited state. For example, in a financial trading application, when a failed digital signature verification response from the trading server is detected, the functionality of the trading service component will be immediately restricted, preventing it from sending transaction confirmation information or other related responses to the user's mobile phone.

[0046] In this way, the above process can prevent potentially security-critical data from entering user terminal devices at the source, thus avoiding harm to users from malicious data. Furthermore, by restricting the function of the second service component, it can effectively prevent attackers from using compromised service components to send malicious commands or data to users.

[0047] III. Mode Switching.

[0048] When the security response mechanism indicates a mode switch, the current operating mode will be switched to secure mode. Secure mode is a specially configured operating mode with stricter security policies and access control mechanisms. During the switch, various settings and operating parameters of the user terminal device can be adjusted, disabling some functions and services that may pose security risks, while enabling additional security protection measures. For example, in a smart office system, when a document download response from a file server fails to verify the digital signature, the office equipment can be automatically switched to secure mode, restricting unnecessary access to the external network and allowing access only to internally authenticated resources.

[0049] In this way, by switching to safe mode, a relatively safe and reliable operating environment is provided for user terminal devices, reducing the risk of further attacks. Furthermore, switching to safe mode can effectively isolate potential security threats and protect user data and system resources.

[0050] IV. Send an alarm.

[0051] If the security response mechanism instructs that an alert be sent, it will first identify the connected Security Operations Center (SOC). The SOC is a dedicated organization responsible for monitoring, analyzing, and handling security incidents, equipped with professional security personnel and advanced security equipment. Once the SOC is identified, detailed alert information will be sent to it via pre-defined communication protocols and interfaces. This alert information includes details about the failed digital signature verification, the involved service components, user terminal device information, and potential security risk assessments. For example, in a large enterprise network system, when a failed digital signature verification is detected from a data response server of an external partner, the internal SOC will be quickly identified, and an alert containing detailed information such as the time, location, and systems involved in the incident will be sent to it.

[0052] In this way, through the above process, security incidents can be promptly notified to professional security handling organizations, enabling security personnel to quickly intervene and take corresponding measures, such as further investigating the source of the security incident, assessing the scope of security impact, and formulating response strategies, thereby effectively reducing the losses caused by security incidents to enterprises or users.

[0053] In summary, the embodiments of this invention have several significant advantages: First, it achieves true fault isolation by separating the security anchor from the application service logic. This not only effectively solves the initial loss of control problem that is difficult to handle with existing technologies, but also prevents the entire system from crashing even if the application service is attacked and compromised. Second, it possesses strong proactive defense capabilities. By performing content verification on the client side, even if the application server is completely controlled by an attacker, it can successfully prevent the execution of malicious code, thus building a solid defense for system security. Third, the entire process requires no user intervention, achieving fully automated operation. End users will not perceive any issues during use, and it will not affect the user experience in any way, ensuring ease and smoothness of use. Fourth, it is implemented using standard technologies based on existing Web standards, such as sandbox embedded frameworks, cross-execution environment messaging, and data URLs. No browser extensions or special configurations are required, reducing the complexity and cost of technical implementation. Fifth, it has broad applicability and can be applied to various types of Web applications such as Webmail, CRM (Customer Relationship Management), and instant messaging, providing security guarantees for various Web applications.

[0054] The method provided in this application embodiment includes a client-side content verification system comprising a first service component, a second service component, and a user terminal device. When the first service component receives an application access request from the user terminal device for the first time, it creates a verification execution environment on the user terminal device. Upon detecting a request response from the second service component to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. If the digital signature verification is successful, it instructs the user terminal device to display content according to the request response. By setting up the first and second service components, the security anchor point is logically isolated from the application service. A breach of the application service will not cause the entire system to crash, preventing attackers from controlling the security boundary from the first byte. Furthermore, by creating a verification execution environment on the user terminal device, content verification can be implemented on the user terminal device. Even if the application server is completely controlled, malicious code execution can be prevented, effectively preventing attackers from initially publishing and executing malicious code to the user's browser, further enhancing security.

[0055] Furthermore, as Figure 1 In a specific implementation of the method, this application provides a client-side content verification device based on a security anchor architecture, such as... Figure 2 As shown, the device is applied to the first service component, including: a creation module 201, a verification module 202, and a display module 203.

[0056] A creation module 201 is used to create a verification execution environment in the user terminal device when an application access request transmitted by the user terminal device is received for the first time. The verification module 202 is used to verify the digital signature carried in the request response based on the verification execution environment when the second service component sends a request response to the user terminal device. The request response is generated by the second service component in response to a service request sent by the user terminal device and carries the digital signature. The service request is sent by the user terminal device to the second service component according to the user's access needs during the interaction with the user. The display module 203 is used to instruct the user terminal device to display content in accordance with the request response when the digital signature verification is successful.

[0057] In a specific application scenario, module 201 is used to provide the user terminal device with an initial page containing security anchor logic, wherein the security anchor logic is a set of code used to perform content verification operations; by running the initial page, a sandbox environment is created in the user terminal device, a verification logic document is set, and a cross-environment communication link is initialized to complete the creation of the verification execution environment in the user terminal device, wherein the verification logic document includes a public key and a signature verification function.

[0058] In a specific application scenario, the verification module 202 is used to continuously intercept the responses fed back by the second service component based on the verification execution environment; when a request response fed back by the second service component to the user terminal device is intercepted, the digital signature is extracted from the request response. Specifically, when generating the request response, the second service component determines the business content based on the service request sent by the user terminal device, and uses its private key to perform signature encryption to generate the digital signature, and uses the business content and the digital signature to generate the request response; the signature verification function is called through the verification execution environment to decrypt the digital signature using the public key, thereby verifying the digital signature.

[0059] In specific application scenarios, the verification module 202 is further configured to determine that the digital signature verification is successful when the digital signature is successfully decrypted using the public key; and to determine that the digital signature verification fails when the digital signature is undecrypted using the public key.

[0060] In specific application scenarios, the device further includes: The alarm module is used to trigger a preset security response mechanism when the digital signature verification fails; and to perform a security alarm operation according to the instructions of the security response mechanism.

[0061] In specific application scenarios, the alarm module is used to push a security warning prompt to the user terminal device when the security response mechanism indicates that a security warning should be displayed, so that the user terminal device can display the security warning prompt to the user; and / or, when the security response mechanism indicates that the function of a restricted component should be restricted, the function of the second service component should be restricted to prevent the second service component from sending a request response to the user terminal device; and / or, when the security response mechanism indicates that a mode switch should be performed, the currently running mode should be switched to a safe mode, so that the user terminal device can run the safe mode; and / or, when the security response mechanism indicates that an alarm should be sent, the connected security operation center should be identified and an alarm should be sent to the security operation center.

[0062] The apparatus provided in this application embodiment includes a client content verification system comprising a first service component, a second service component, and a user terminal device. When the first service component receives an application access request from the user terminal device for the first time, it creates a verification execution environment on the user terminal device. Upon detecting a request response from the second service component to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. If the digital signature verification is successful, it instructs the user terminal device to display content according to the request response. By setting up the first and second service components, the security anchor point is logically isolated from the application service. A breach of the application service will not cause the entire system to crash, preventing attackers from controlling the security boundary from the first byte. Furthermore, by creating a verification execution environment on the user terminal device, content verification can be performed on the user terminal device. Even if the application server is completely controlled, malicious code execution can be prevented, effectively preventing attackers from initially publishing and executing malicious code to the user's browser, further enhancing security.

[0063] It should be noted that other corresponding descriptions of the functional units involved in the client content verification device based on a security anchor architecture provided in this application embodiment can be found in the following references. Figure 1 The corresponding descriptions in [the document] will not be repeated here.

[0064] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0065] The above embodiments and the technical features in the embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0066] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

[0067] In an exemplary embodiment, see Figure 3 The invention also provides a computer device including a bus, a processor, a memory, and a communication interface. It may also include an input / output interface and a display device, wherein the various functional units can communicate with each other via the bus. The memory stores a computer program, and the processor executes the program stored in the memory to perform the client content verification method based on the security anchor architecture described in the above embodiments.

[0068] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the client content verification method based on a security anchor architecture.

[0069] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented in hardware or by using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computer device (such as a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0070] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application.

[0071] Those skilled in the art will understand that the modules in the apparatus of the implementation scenario can be distributed within the apparatus of the implementation scenario as described, or they can be located in one or more apparatuses different from this implementation scenario, with corresponding changes. The modules of the above-described implementation scenario can be combined into one module, or they can be further divided into multiple sub-modules.

[0072] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of the implementation scenario.

[0073] The above disclosures are only a few specific implementation scenarios of this application. However, this application is not limited to these. Any variations that can be conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A client-side content verification system based on a secure anchor architecture, characterized in that, The system includes a first service component, a second service component, and a user terminal device: When the first service component receives the application access request transmitted by the user terminal device for the first time, it creates a verification execution environment in the user terminal device. When it detects that the second service component has sent a request response to the user terminal device, it verifies the digital signature carried in the request response based on the verification execution environment. When the digital signature is successfully verified, it instructs the user terminal device to display content in accordance with the request response. The second service component receives the service request sent by the user terminal device, generates a request response carrying a digital signature for the service request, and sends it back to the user terminal device. During the interaction with the user, the user terminal device sends the service request to the second service component according to the user's access needs, and displays content to the user according to the instructions of the first service component and the request response fed back by the second service component.

2. A client-side content verification method based on a secure anchor architecture, characterized in that, The method is applied to the first service component, including: Upon first receiving an application access request transmitted from a user terminal device, a verification execution environment is created in the user terminal device. When the second service component sends a request response to the user terminal device, the digital signature carried in the request response is verified based on the verification execution environment. The request response is generated by the second service component in response to the service request sent by the user terminal device and carries the digital signature. The service request is sent by the user terminal device to the second service component according to the user's access needs during the interaction with the user. When the digital signature is successfully verified, the user terminal device is instructed to display content in accordance with the request response.

3. The method according to claim 2, characterized in that, Creating a verification execution environment in the user terminal device includes: An initial page including security anchor logic is fed back to the user terminal device, wherein the security anchor logic is a set of code used to perform content verification operations; By running the initial page, a sandbox environment is created, a verification logic document is set, and a cross-environment communication link is initialized in the user terminal device to complete the creation of the verification execution environment in the user terminal device. The verification logic document includes a public key and a signature verification function.

4. The method according to claim 3, characterized in that, When a request response is detected from the second service component to the user terminal device, the digital signature carried in the request response is verified based on the verification execution environment, including: The system continuously intercepts the responses from the second service component based on the verification execution environment. When the second service component intercepts the request response sent by the user terminal device, the digital signature is extracted from the request response. When generating the request response, the second service component determines the service content based on the service request sent by the user terminal device, and performs signature encryption using its private key to generate the digital signature, and generates the request response using the service content and the digital signature. The signature verification function is invoked through the verification execution environment to decrypt the digital signature using the public key, thereby verifying the digital signature.

5. The method according to claim 4, characterized in that, The method further includes: When the digital signature is successfully decrypted using the public key, it is determined that the digital signature has been successfully verified. If the digital signature fails to be decrypted using the public key, the verification of the digital signature is determined to have failed.

6. The method according to claim 2, characterized in that, When a request response is detected from a second service component to the user terminal device, after verifying the digital signature carried in the request response based on the verification execution environment, the method further includes: When the verification of the digital signature fails, a preset security response mechanism is triggered; Perform security alarm operations as instructed by the security response mechanism.

7. The method according to claim 6, characterized in that, The step of executing a security alarm operation according to the instructions of the security response mechanism includes: When the security response mechanism indicates that a security warning should be displayed, a security warning prompt is pushed to the user terminal device, so that the user terminal device displays the security warning prompt to the user; and / or, When the security response mechanism indicates a restriction on component functionality, the functionality of the second service component is restricted to prevent the second service component from sending request responses to the user terminal device; and / or, When the security response mechanism indicates a mode switch, the currently running mode is switched to security mode, so that the user terminal device runs in security mode; and / or, When the security response mechanism indicates that an alarm should be sent, the connected security operations center is identified, and an alarm is sent to the security operations center.

8. A client-side content verification device based on a secure anchor architecture, characterized in that, The device is applied to a first service component and includes: A creation module is used to create a verification execution environment in the user terminal device when an application access request is first received from the user terminal device. The verification module is used to verify the digital signature carried in the request response based on the verification execution environment when the second service component sends a request response to the user terminal device. The request response is generated by the second service component in response to a service request sent by the user terminal device and carries the digital signature. The service request is sent by the user terminal device to the second service component according to the user's access needs during the interaction with the user. The display module is used to instruct the user terminal device to display content based on the request response when the digital signature verification is successful.

9. A device comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 2 to 7.

10. A medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 2 to 7.

Images