Access verification system, method and device
By configuring security plug-ins on the client, detecting and verifying the target site, the security risks of old systems are solved, access security is improved and costs are reduced, and security issues are solved from the source of access.
Patent Information
- Application Number
- CN202411043605.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-07-31
AI Technical Summary
In the prior art, old systems have become potential targets for cyber attacks due to lack of security functions. Although the plug-in Web Application Firewall (WAF) provides a layer of protection, it is costly and has limited protection levels, so it cannot fundamentally solve security risks.
The security plug-in issued on the client configuration plug-in server, through the security plug-in, detect whether the target site belongs to the protection site list, build access security information and authenticate, update access requests for verification, and realize verification of the client's target site access requests .
It effectively improves access security, reduces security maintenance costs, and realizes solving security problems from the source of access, meeting the security requirements of old systems.
Smart Images

Figure CN118573478B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present specification relate to the field of network security technology, and in particular to access verification systems, methods and devices. Background Art
[0002] With the development of computer and Internet technology, the iteration speed of business systems is getting faster and faster with the needs of users, but enterprises also have old systems that have not been updated for a long time and lack technical support. Due to their legacy nature, these systems often lack sufficient security functions, making them potential targets for network attacks. Moreover, once such systems are attacked, they may not only cause business interruptions, but also cause serious data leakage incidents. In the prior art, in order to cope with the above problems, enterprises usually adopt the strategy of plug-in Web Application Firewall (WAF, Web Application Firewall), which as a security measure can provide an additional layer of protection for the system by intercepting and filtering malicious network requests. However, this method does not fundamentally solve the security risks of old systems, and the deployment of WAF will increase the cost too much, and the protection level is not very high. Therefore, an effective solution is urgently needed to solve the above problems. Summary of the invention
[0003] In view of this, an embodiment of this specification provides an access verification system. One or more embodiments of this specification also relate to an access verification method, an access verification device, a computing device, a computer-readable storage medium and a computer program product to solve the technical defects existing in the prior art.
[0004] According to a first aspect of an embodiment of the present specification, an access verification system is provided, the access verification system comprising a client and a plug-in server, wherein the client runs a target browser and configures a security plug-in issued by the plug-in server, including:
[0005] The client is used to detect whether the target site belongs to the protection site list by using the security plug-in when accessing the target site through the target browser, wherein the protection site list is issued by the plug-in server; if so, construct access security information for the target browser and send it to the plug-in server;
[0006] The plug-in server is used to construct access authentication information based on the access security information and send it to the client;
[0007] The client is used to, upon receiving an access request submitted to the target site, update the access request to a target access request using the access authentication information, and send the request to the plug-in server;
[0008] The plug-in server is used to verify the target access request and execute the target access task according to the verification result.
[0009] According to a second aspect of an embodiment of this specification, an access verification method is provided, which is applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including:
[0010] In the case of accessing a target site through the target browser, using the security plug-in to detect whether the target site belongs to a protection site list, wherein the protection site list is issued by the plug-in server;
[0011] If so, construct access security information for the target browser;
[0012] Sending the access security information to the plug-in server, and receiving access authentication information fed back by the plug-in server in response to the access security information;
[0013] When receiving an access request submitted to the target site, the access request is updated to a target access request using the access authentication information and sent to the plug-in server for verification.
[0014] According to a third aspect of the embodiments of this specification, an access verification device is provided, which is applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including:
[0015] a detection module configured to detect, when accessing a target site through the target browser, whether the target site belongs to a protection site list by using the security plug-in, wherein the protection site list is issued by the plug-in server;
[0016] If yes, executing a construction module, wherein the construction module is configured to construct access security information for the target browser;
[0017] A sending module, configured to send the access security information to the plug-in server, and receive access authentication information fed back by the plug-in server for the access security information;
[0018] The update module is configured to, upon receiving an access request submitted to the target site, update the access request to a target access request using the access authentication information, and send the request to the plug-in server for verification.
[0019] According to a fourth aspect of an embodiment of this specification, a computing device is provided, including:
[0020] Memory and processor;
[0021] The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the above-mentioned access verification method are implemented.
[0022] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the above-mentioned access verification method are implemented.
[0023] According to a sixth aspect of the embodiments of this specification, a computer program product is provided, including a computer program or instructions, which implement the steps of the above-mentioned access verification method when executed by a processor.
[0024] The access verification system provided in this embodiment can reduce the cost of security protection and improve the comprehensiveness of security protection. The security plug-in issued by the plug-in server can be configured on the client side. On this basis, the client can first use the security plug-in to detect whether the target site belongs to the protection site list issued by the plug-in server when accessing the target site through the running target browser; thereby achieving the preliminary protection of accessing the target site using the protection site list. When it is determined that the target site belongs to the protection site list, access security information can be constructed for the target browser. After sending it to the plug-in server, the plug-in server can construct access authentication information based on the access security information, and after feeding it back to the client, the client can use the access authentication information to update the access request to the target access request after receiving the access request submitted for the target site. After that, the target access request will be verified by the plug-in server to verify the access request submitted by the client for the target site, and then the target access task can be executed according to the verification result. When the client accesses the target site, the security requirements of the old system can be met by configuring the security plug-in on the client, and the security problem can be solved by solving the trusted source from the access source, thereby effectively improving the access security and reducing the security maintenance cost of the business party. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 is a schematic diagram of an access verification system provided by an embodiment of this specification;
[0026] Figure 2 It is a schematic diagram of the structure of an access verification system provided by an embodiment of this specification;
[0027] Figure 3 is a process flow chart of an access verification system provided by an embodiment of the present specification;
[0028] Figure 4 is a flow chart of an access verification method provided by an embodiment of this specification;
[0029] Figure 5 It is a structural diagram of an access verification device provided by an embodiment of this specification;
[0030] Figure 6 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION
[0031] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.
[0032] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.
[0033] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0034] In addition, 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, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0035] First, the terms involved in one or more embodiments of this specification are explained.
[0036] Web Application Firewall (WAF), the full name of which is Web Application Firewall, is a network security device or service used to protect Web application systems. WAF provides security protection by monitoring, filtering and blocking malicious requests to Web applications. It is a Web application protection system, also known as a "website application-level intrusion prevention system."
[0037] In this specification, an access verification system is provided. This specification also relates to an access verification method, an access verification device, a computing device, a computer-readable storage medium and a computer program product, which are described in detail one by one in the following embodiments.
[0038] In actual applications, although WAF can solve security protection problems, this approach only provides a temporary, superficial solution. Deploying WAF will significantly increase the cost burden, including the cost of purchasing, maintaining, and upgrading equipment. Secondly, attackers may bypass the protection of WAF through various means, such as using complex attack vectors or targeting weaknesses in WAF configuration. In addition, WAF mainly targets external attacks and has limited protection capabilities for internal data leakage risks caused by business logic defects. Therefore, an effective solution is urgently needed to solve the above problems.
[0039] See also Figure 1 As shown in the schematic diagram, the access verification system provided by this embodiment can configure the security plug-in issued by the plug-in server on the client in order to reduce the cost of security protection and improve the comprehensiveness of security protection. On this basis, when the client accesses the target site through the running target browser, it can first use the security plug-in to detect whether the target site belongs to the protection site list issued by the plug-in server; thereby achieving the preliminary protection of access to the target site using the protection site list. When it is determined that the target site belongs to the protection site list, access security information can be constructed for the target browser. After sending it to the plug-in server, the plug-in server can construct access authentication information based on the access security information and feed it back to the client, so that the client can use the access authentication information to update the access request to the target access request after receiving the access request submitted for the target site. After that, the target access request will be verified by the plug-in server to verify the access request submitted by the client for the target site, and then the target access task can be executed according to the verification result. When the client accesses the target site, the security requirements of the old system can be met by configuring a security plug-in on the client, and the security problem can be solved by solving the trusted source from the source of access, which can effectively improve access security and reduce the security maintenance cost of the business party.
[0040] See also Figure 2 , Figure 2 A schematic diagram of the structure of an access verification system provided according to an embodiment of the present specification is shown. The access verification system 200 includes a client 210 and a plug-in server 220. The client 210 runs a target browser and configures a security plug-in issued by the plug-in server 220, including:
[0041] The client 210 is used to detect whether the target site belongs to the protection site list using the security plug-in when accessing the target site through the target browser, wherein the protection site list is issued by the plug-in server; if so, construct access security information for the target browser and send it to the plug-in server;
[0042] The plug-in server 220 is used to construct access authentication information based on the access security information and send it to the client;
[0043] The client 210 is used to update the access request to a target access request using the access authentication information when receiving the access request submitted to the target site, and send the request to the plug-in server;
[0044] The plug-in server 220 is used to verify the target access request and execute the target access task according to the verification result.
[0045] The access verification system provided in this embodiment can be applied to the security protection of the business system corresponding to any site, wherein the business system can be any system with access requirements, for example, the business system can be an information query system, a personnel management system, an information monitoring system, an archive management system, etc. When there is an access requirement for the site corresponding to the business system, security protection can be achieved through the access verification system provided in this embodiment, thereby solving the security problem from the access source.
[0046] Specifically, the client refers to the terminal device held by the user, which can be a computer, notebook, mobile phone, smart wearable device, etc.; accordingly, the target browser is the browser running on the client that supports the user to access the specified site. Correspondingly, the security plug-in specifically refers to the plug-in sent by the plug-in server to the client. The plug-in is used to verify the client's access request when the client accesses any site, so as to achieve the purpose of security protection, and there is security verification logic in the security plug-in, so that the access request can be verified when the access operation is triggered.
[0047] Accordingly, the target site specifically refers to the site that the client needs to access at the current moment. Accordingly, the protection site list specifically refers to the list constructed by the plug-in server for the sites that need to be protected. The list records all the site information that needs to be protected. After being sent to the client, the client's access to any site needs to be matched with the protection site list first, so as to achieve the purpose of preliminary access verification. Accordingly, the access security information specifically refers to the security information constructed for the target browser in the case of passing the preliminary access verification. The security information can be used as the basis for the plug-in server to construct the authentication information, ensuring that in the case of passing the preliminary access verification, the access authentication information that uniquely corresponds to the client can be constructed based on the information. This can be used as an interactive verification element, and the purpose of secondary access verification can be achieved by verifying the access authentication information. Accordingly, the access authentication information specifically refers to the unique authentication information constructed for the client. Each subsequent interactive request of the client carries the authentication information, which can achieve the purpose of secondary access verification, and can avoid accessing the target site when any access request is triggered if the access authentication information does not exist, thereby effectively improving access security.
[0048] Accordingly, an access request specifically refers to a request submitted by a user when he needs to access a target site. Accordingly, a target access request specifically refers to an access request carrying access authentication information, which is used to be forwarded to the plug-in server for secondary access verification. Accordingly, a target access task specifically refers to a task triggered and executed after the plug-in server completes the verification of the target access request. The task can be a task for the plug-in server to forward the access request to the target site, or a task for interrupting the client's access to the target site. The task type is determined by the verification result of the target access request.
[0049] Based on this, in order to reduce the cost of security protection and improve the comprehensiveness of security protection, the security plug-in issued by the plug-in server can be configured on the client. On this basis, when the client accesses the target site through the running target browser, it can first use the security plug-in to detect whether the target site belongs to the protection site list issued by the plug-in server; thereby achieving the initial protection of access to the target site using the protection site list. When it is determined that the target site belongs to the protection site list, access security information can be constructed for the target browser. After sending it to the plug-in server, the plug-in server can construct access authentication information based on the access security information and feed it back to the client. After receiving the access request submitted for the target site, the client can use the access authentication information to update the access request to the target access request. After that, the target access request will be verified by the plug-in server to verify the access request submitted by the client for the target site. Subsequently, the target access task can be executed according to the verification result.
[0050] This embodiment uses the client accessing the personnel management system within the enterprise as an example to illustrate the access verification system. The descriptions of other scenarios can refer to the same or corresponding descriptions in this embodiment, and this embodiment will not be repeated here. Specifically, when employee A of H Company needs to update the employee information of H Company (such as resignation, job change, address information change, etc.), he will access the personnel management system site through the browser on his computer. In order to ensure the security of personnel information, H Company will install a security plug-in on the computer of each employee in the company. When it is determined that employee A needs to access the personnel management system, the security plug-in configured on employee A's computer will be used to detect whether the target site currently being accessed belongs to the protection site list issued by the plug-in server; if not, it means that the site currently being accessed does not belong to the access site, and no processing is required; if so, it means that the site currently being accessed belongs to the protection site, and access security information can be constructed and sent to the plug-in server.
[0051] Furthermore, after receiving the access security information submitted by employee A's computer, the plug-in server can construct access authentication information based on the access security information and feedback it to employee A's computer. Thereafter, if employee A submits an access request to the site of the personnel management system, the access authentication information can be inserted into the access request, and the request with the inserted access authentication information can be forwarded to the plug-in server, which verifies the access authentication information in the request, thereby determining whether the access request is initiated by employee A's computer. If the verification is successful, the plug-in server can forward the access request to the personnel management system, so that the personnel management system can update the information of the designated employee according to employee A's operation request. If the verification fails, it means that the access request is not initiated by employee A's computer, and there may be a security issue, so an alarm can be issued to ensure the security of personnel information.
[0052] To summarize, when the client accesses the target site, the security requirements of the old system can be met by configuring a security plug-in on the client, and the security problem can be solved by solving the trusted source from the access source, thereby effectively improving access security and reducing the security maintenance costs of the business party.
[0053] Furthermore, in order to solve the security problem from the access source, the plug-in server can send a security plug-in and a protection site list to the client, so that when the client runs the target browser to access the site, the security plug-in can be started and the initial access verification can be completed in combination with the protection site list; in this embodiment, the client is also used to detect whether the client is configured with the security plug-in based on the startup instruction submitted for the target browser when receiving the startup instruction; if so, send a list acquisition request to the plug-in server;
[0054] The plug-in server is also used to send the protection site list to the client in response to the list acquisition request.
[0055] Based on this, when the client starts the target browser, it can detect whether the client is configured with a security plug-in based on the client's startup instructions; if not, it means that the client does not have a secure environment to access the target site. At this time, the plug-in server can actively send the security plug-in to the client for subsequent security protection, or it can directly close the client's access rights and not allow the client to access sites in the protection site list. If yes, it means that the client has installed a security plug-in, and in order to support the client to complete the access to the target site in a secure environment, the plug-in server can send the protection site list to the client, support the client to cache the protection site list locally, and use it for subsequent access to the target site, and can perform preliminary access verification on the client's access operation.
[0056] Using the above example, when employee A starts the target browser, it will be detected whether the security plug-in issued by the plug-in server is installed on employee A's computer; if so, the plug-in server can issue a protection site list, and the protection sites recorded in the protection site list include site 1, site 2...site n; at this time, employee A's computer can cache the protection site list locally. When employee A accesses the personnel management system, the site information corresponding to the personnel management system can be compared with the site information recorded in the protection site list to determine whether the site visited by employee A is a protection site, thereby achieving the purpose of preliminary access verification.
[0057] In summary, by constructing a protection site list by the plug-in server and sending it to the client cache, the client can perform preliminary verification of the access site before accessing any site, thereby effectively improving the security of site access.
[0058] In order to further improve the security of site access, the secondary authentication module can be used to perform secondary authentication on the user of the client when it is determined that the client has installed a security plug-in and cached the list of protected sites. In this embodiment, the client is also used to use the pre-started secondary authentication module to build and execute a secondary authentication task when the target site belongs to the site protection list; when it is determined that the secondary authentication is passed according to the task execution result, the step of building access security information for the target browser is executed.
[0059] Specifically, the secondary authentication module specifically refers to a module in the security plug-in used to authenticate the identity of the user holding the client. Correspondingly, the secondary authentication task specifically refers to a task triggered when the user is authenticated, which can be used to authenticate the user's face, identity information, etc.
[0060] Based on this, if the target site belongs to the site protection list, the user holding the client can also be authenticated twice through the security plug-in. At this time, the client can use the pre-started secondary authentication module to build and execute the secondary authentication task; if the secondary authentication is determined to be passed according to the task execution result, the step of building access security information for the target browser can be continued. If the secondary authentication fails, it means that there is a problem with this access, and the access operation to the target site can be interrupted.
[0061] In actual applications, since secondary authentication requires interaction with the user (e.g., face recognition requires recording a face video or taking a face photo), it is possible to set a prompt for secondary authentication at the first access stage. In addition, if the user performing secondary authentication is an employee of the enterprise, the enterprise domain authentication can be used; if not, the authentication can be completed through a third-party authentication platform. This embodiment does not make any restrictions here.
[0062] Continuing with the above example, when it is determined that the site visited by employee A is the personnel management system and is on the protection site list, since employee A is visiting the personnel management system for the first time that day, facial verification is required for employee A. At this time, the facial verification interface can be opened on the computer, and the facial image of employee A can be collected. By verifying the facial image of employee A and passing the verification, subsequent access verification operations can be performed.
[0063] In summary, by performing the secondary authentication task, the identity of the client user can be authenticated, thereby further improving the security of accessing the target site.
[0064] Furthermore, when constructing access security information, considering that the access security information needs to be used as the basis for verification of all subsequent requests triggered to the client, and needs to have a unique relationship with the client, it can be constructed in combination with the session identifier of the secondary verification task and the fingerprint information of the target browser, and the access authentication information is constructed after the hash operation of the plug-in server, which can be subsequently encapsulated in the request for verification during the interaction process. In this embodiment, the client is also used to determine the session identifier corresponding to the secondary authentication task, and the fingerprint information corresponding to the target browser; based on the session identifier and the fingerprint information, the access security information is constructed for the target browser and sent to the plug-in server;
[0065] The plug-in server is further used to perform a hash operation on the session identifier and the fingerprint information, and obtain access authentication information according to the hash operation result.
[0066] Specifically, the session identifier specifically refers to the session identifier corresponding to the secondary authentication task. Correspondingly, the fingerprint information specifically refers to the fingerprint information corresponding to the target browser running on the client, and the fingerprint information is unique, which is constructed by collecting various information of the browser and the client, such as combining the version information, language information of the browser, and the device hardware information of the client, and this embodiment does not make any limitation here.
[0067] Based on this, when constructing access security information, in order to ensure its unique matching with the client, the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser can be determined first; by combining the session identifier and fingerprint information, unique access security information can be constructed for the target browser and sent to the plug-in server. At this time, the plug-in server can perform a hash operation on the session identifier and fingerprint information to obtain access authentication information based on the hash operation result, and then verify the access authentication information to achieve the purpose of access protection.
[0068] Continuing with the above example, after completing the face verification for employee A, the session ID corresponding to the face verification task and the fingerprint information of the target browser are sent to the plug-in server. The plug-in server performs a hash operation on the session ID and the fingerprint information to obtain the token information that is uniquely matched to employee A's computer. After sending it to employee A's computer, when employee A subsequently accesses the personnel management system, the token information can be carried in the request to enable the plug-in server to authenticate the identity of employee A, so that employee A can safely access the personnel management system through the computer and avoid information leakage.
[0069] In summary, by combining the session identifier and the browser's fingerprint information to construct access security information, and performing hash operations on the access security information to construct access authentication information, the unique matching relationship between the access authentication information and the client can be guaranteed, and on this basis, subsequent interactions can be guaranteed to be more secure.
[0070] When the client receives an access request submitted to a target site, in order to achieve security protection purposes, the access authentication information issued by the plug-in server can be inserted into the access request, and then the plug-in server is verified, thereby further improving the security of accessing the site. In this embodiment, the client is also used to add the access authentication information to the access request when receiving the access request submitted to the target site, and obtain the target access request; send the target access request to the plug-in server;
[0071] The plug-in server is also used to parse the target access request to obtain access authentication information to be verified; compare the access authentication information to be verified with the access authentication information; and forward the target access request to the target site by executing a target access task when it is determined that the target access request has been verified according to the comparison result.
[0072] Specifically, the access authentication information to be verified specifically refers to the access authentication information obtained after the plug-in server parses the target access request. Based on this, when the client receives the access request submitted to the target site, in order to verify the client accessing the target site, the access authentication information can be added to the access request, thereby obtaining the target access request; then the target access request is sent to the plug-in server instead of to the target site, so that the plug-in server can verify the target access request.
[0073] Furthermore, after receiving the target access request, the plug-in server can first parse the target access request to obtain the access authentication information to be verified; at this time, the access authentication information to be verified can be compared with the access authentication information constructed by the plug-in server for the client; if it is determined according to the comparison result that the target access request has not been verified, it means that the access authentication information to be verified and the access authentication information are inconsistent, which further indicates that the client accessing the target site is not a client that establishes cached access authentication information, and an alarm message can be initiated to achieve the purpose of protection. If it is determined according to the comparison result that the target access request has been verified, it means that the access authentication information to be verified and the access authentication information are consistent, then the plug-in server can execute the target access task at this time, thereby forwarding the target access request to the target site to achieve interaction between the client and the target site.
[0074] In actual applications, when adding access authentication information to an access request, the access authentication information can be inserted into the header of the request, so that after the plug-in server receives the request carrying the access authentication information, it can extract the access authentication information from the header by parsing the request for verification.
[0075] Continuing with the above example, when receiving an access request submitted by employee A to the personnel management system site, the token information can be added to the access request header, and the access request carrying the token information can be sent to the plug-in server. At this time, the plug-in server will extract the token information to be verified from the request, and by comparing the token information to be verified with the token information sent to employee A's computer, it can be determined whether the current access request has the authority to access the personnel management system. If the token information to be verified is consistent with the token information sent to employee A's computer, the plug-in server can forward the access request to the personnel management system to update the employee's information; if the token information to be verified is inconsistent with the token information sent to employee A's computer, an alarm can be initiated to ensure the information security of the personnel management system.
[0076] In summary, by comparing the access authentication information and the access authentication information to be verified by the plug-in server, in-depth verification can be performed before accessing the target site, thereby effectively improving the security of the system and avoiding risks such as data leakage.
[0077] In specific implementation, in order to further avoid data leakage, even if the data is fed back to an unsafe client, important data leakage can still be avoided, and the fed-back data can be desensitized. In this embodiment, the client is also used to receive the initial data fed back by the target site in response to the target access request; the initial data is desensitized using the desensitization rules preset in the security plug-in to obtain the target data; and the target data is displayed through the target page in the target browser.
[0078] Specifically, the initial data refers to the data fed back by the target site in response to the access request submitted by the client. For example, if the access request is a query request, the initial data fed back is the query result; or if the access request is an update request, the initial data fed back is the data update result; correspondingly, the desensitization rule refers to the rule for desensitizing the initial data. The rule can be a string replacement rule, which is used to change the sensitive string in the initial data to a specified character, such as replacing it with "*"; the desensitization rule can also be a display desensitization rule, which is used to mask the sensitive characters by adding a mask layer after the initial data is fed back to the client, so as to achieve the purpose of desensitization. Correspondingly, the target data is the data obtained after desensitization.
[0079] Based on this, after the target site responds to the client's access request and feeds back the initial data, in order to ensure data security, the initial data can be desensitized using the desensitizing rules preset in the security plug-in, so that the sensitive data in the initial data can be hidden. After obtaining the target data, the target data can be displayed through the target page in the target browser.
[0080] In practical applications, in addition to the above-mentioned desensitization rules, other desensitization rules may also be used, such as making similar semantic changes to sensitive character strings, etc. During specific implementation, it can be selected according to actual needs, and this embodiment does not make any limitation here.
[0081] In summary, after the target site feeds back the data, the data is desensitized using the desensitization rules preset in the security plug-in, so that the data finally displayed by the client is the desensitized data, thereby effectively avoiding the risk of data leakage.
[0082] Furthermore, when the client adds a mask layer to complete data desensitization, the mask layer is used to mask sensitive characters on the basis of the initial data to achieve the purpose of desensitization. In this embodiment, the client is also used to load the initial data into the target page using the desensitization rules preset in the security plug-in; add a mask layer to the initial data in the target page, and obtain the target data according to the added result.
[0083] Specifically, the mask layer refers to a shielding layer that can block sensitive strings in the initial data and prevent them from being displayed normally. Based on this, when the client receives the initial data, it can use the desensitization rules preset in the security plug-in to load the initial data into the target page; after the loading is completed, a mask layer can be added to the initial data in the target page, and the added mask layer will cover the sensitive strings in the initial data, so that the target data can be obtained according to the addition result and displayed through the target interface.
[0084] In actual applications, the plug-in server can directly configure sensitive fields and their rules when configuring the security plug-in for the client, so that the security plug-in can desensitize the initial data according to the configured rules and sensitive fields, where the sensitive fields and rules can be configured according to actual needs. During desensitization, a mask layer can be added after the target DOM element is loaded on the page, and the mask layer is used to cover the sensitive fields, thereby achieving the purpose of desensitization.
[0085] Continuing with the above example, when it is determined that the access request is an access request submitted by employee A to the personnel management system, the plug-in server will send the access request to the personnel management system; at this time, the personnel management system will respond to the request and send the basic attributes of all employees in H Company to employee A's computer, including employee name, telephone number, address, ID number, employee work number and other information; and employee ID information and address information are private information, and the security plug-in is configured with desensitizing rules for ID information and address information. Therefore, after the information is fed back to employee A's computer, a mask layer will be added to the address information and ID information of each employee based on the desensitizing rules in the security plug-in, so that the ID information and address information of other employees will be blocked in the information displayed to employee A.
[0086] In summary, by adding a mask layer to desensitize the data, it can be ensured that the displayed data shields sensitive information, thereby effectively improving data security.
[0087] In addition, in order to improve the flexibility of desensitization during desensitization and provide data of different desensitization levels to users with different permissions, the corresponding desensitization rules can be selected according to the level corresponding to the access request. In this embodiment, on the one hand, the client is also used to determine the first access level corresponding to the access request; select the target desensitization rule that matches the first access level from the desensitization rules preset in the security plug-in, desensitize the initial data, and obtain the target data;
[0088] On the other hand, the client is further used to determine a second access level corresponding to the access request, and when the second access level meets a preset level threshold, adjust the mask layer, and determine the target data according to the adjustment result.
[0089] Specifically, the first access level and the second access level specifically refer to the level of access to the target data by the client user according to the access request, and the higher the level, the higher the authority to access the data; and different levels have different levels of data access rights. Correspondingly, the target desensitization rule specifically refers to the desensitization rule matching the first access level, which is used to desensitize the specified data field in the initial data; correspondingly, the mask layer adjustment specifically refers to the adjustment of closing the mask layer, reducing the size of the mask layer, or enlarging the size of the mask layer.
[0090] Based on this, when desensitizing the initial data, on the one hand, it can be completed according to the first access level of the access request during the desensitization stage, that is, the first access level corresponding to the access request can be determined first; at this time, the target desensitization rule that matches the first access level can be selected from the desensitization rules preset in the security plug-in, and then the initial data is desensitized according to the target desensitization rule to obtain the target data. For example, if the first access level corresponding to the access request is 1, the address information and ID card information will be shielded through the mask layer in the information fed back to employee A; if the first access level is 2, the address information will be shielded through the mask layer in the information fed back to employee A.
[0091] On the other hand, after determining the second access level corresponding to the access request, the client can also compare the second access level with the preset level threshold, so as to adjust the mask layer according to the comparison result, and determine the target data according to the adjustment result. For example, if the second access level is 1, then after comparing the second access level with the level threshold, it is determined that employee A has S1 access rights, then the added mask layer can be adjusted to only block the identity information; or if it is determined that employee A has S2 access rights, then the added mask layer can be adjusted to not block any information.
[0092] In summary, by desensitizing data in different ways, the flexibility of desensitization can be guaranteed, and different levels of data content can be fed back for different access permissions, further ensuring data security.
[0093] The access verification system provided in this embodiment can reduce the cost of security protection and improve the comprehensiveness of security protection. The security plug-in issued by the plug-in server can be configured on the client side. On this basis, the client can first use the security plug-in to detect whether the target site belongs to the protection site list issued by the plug-in server when accessing the target site through the running target browser; thereby achieving the preliminary protection of accessing the target site using the protection site list. When it is determined that the target site belongs to the protection site list, access security information can be constructed for the target browser. After sending it to the plug-in server, the plug-in server can construct access authentication information based on the access security information, and after feeding it back to the client, the client can use the access authentication information to update the access request to the target access request after receiving the access request submitted for the target site. After that, the target access request will be verified by the plug-in server to verify the access request submitted by the client for the target site, and then the target access task can be executed according to the verification result. When the client accesses the target site, the security requirements of the old system can be met by configuring the security plug-in on the client, and the security problem can be solved by solving the trusted source from the access source, thereby effectively improving the access security and reducing the security maintenance cost of the business party.
[0094] The following combination Figure 3 , taking the application of the access verification system provided in this specification in the information query scenario as an example, the access verification system is further described. Among them, Figure 3 A processing flow chart of an access verification system provided by an embodiment of the present specification is shown. The access verification system includes a client and a plug-in server, wherein the client runs a target browser and configures a security plug-in issued by the plug-in server, specifically including the following steps.
[0095] Step S302: When receiving the startup instruction submitted to the target browser, the client detects whether the client is configured with a security plug-in based on the startup instruction, and if so, sends a list acquisition request to the plug-in server.
[0096] Step S304: the plug-in server sends the protection site list to the client in response to the list acquisition request.
[0097] Step S306, when the client accesses the information query site through the target browser, the client uses the security plug-in to detect whether the information query site belongs to the protection site list. If so, the client uses the pre-started secondary authentication module to build and execute the secondary authentication task.
[0098] Step S308, when the client determines that the secondary authentication is passed based on the task execution result, it determines the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser, and constructs access security information for the target browser based on the session identifier and fingerprint information, and sends it to the plug-in server.
[0099] In step S310, the plug-in server performs a hash operation on the session identifier and the fingerprint information, obtains access authentication information according to the hash operation result, and sends it to the client.
[0100] Step S312, when the client receives the access request submitted to the information query site, it adds the access authentication information to the access request, obtains the target access request, and sends the target access request to the plug-in server.
[0101] Step S314, the plug-in server parses the target access request, obtains the access authentication information to be verified, and compares the access authentication information to be verified with the access authentication information.
[0102] Step S316, when the plug-in server determines that the target access request has been verified according to the comparison result, it forwards the target access request to the information query site by executing the target access task.
[0103] In step S318, the client receives the initial query information fed back by the information query site in response to the target access request, and uses the desensitization rules preset in the security plug-in to load the initial query information into the target page.
[0104] Step S320: the client adds a mask layer to the initial query information in the target page, obtains the target query information according to the adding result, and displays the target query information through the target page in the target browser.
[0105] To summarize, when the client accesses the target site, the security requirements of the old system can be met by configuring a security plug-in on the client, and the security problem can be solved by solving the trusted source from the access source, thereby effectively improving access security and reducing the security maintenance costs of the business party.
[0106] Corresponding to the above system embodiment, this specification also provides an access verification method embodiment. Figure 4 FIG. 1 is a flowchart of an access verification method provided by an embodiment of the present specification. Figure 4 As shown, the method is applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including:
[0107] Step S402, when accessing a target site through the target browser, using the security plug-in to detect whether the target site belongs to a protection site list, wherein the protection site list is issued by the plug-in server;
[0108] If yes, executing step S404, step S404, constructing access security information for the target browser;
[0109] Step S406, sending the access security information to the plug-in server, and receiving access authentication information fed back by the plug-in server in response to the access security information;
[0110] Step S408: upon receiving an access request submitted to the target site, the access request is updated to a target access request using the access authentication information, and sent to the plug-in server for verification.
[0111] In an optional embodiment, when the client receives a startup instruction submitted for the target browser, the client detects whether the security plug-in is configured based on the startup instruction; if so, sends a list acquisition request to the plug-in server; and receives a list of protected sites fed back by the plug-in server in response to the list acquisition request.
[0112] In an optional embodiment, when the target site belongs to the site protection list, the client uses a pre-started secondary authentication module to build and execute a secondary authentication task; when it is determined that the secondary authentication has passed based on the task execution result, the step of building access security information for the target browser is executed.
[0113] In an optional embodiment, the client determines the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser; based on the session identifier and the fingerprint information, constructs access security information for the target browser and sends it to the plug-in server.
[0114] In an optional embodiment, when the client receives an access request submitted to the target site, the client adds the access authentication information to the access request to obtain a target access request; and sends the target access request to the plug-in server.
[0115] In an optional embodiment, the client receives the initial data fed back by the target site in response to the target access request; desensitizes the initial data using desensitization rules preset in the security plug-in to obtain target data; and displays the target data through a target page in the target browser.
[0116] In an optional embodiment, the client uses the desensitization rules preset in the security plug-in to load the initial data into the target page; adds a mask layer to the initial data in the target page, and obtains the target data according to the added result.
[0117] In an optional embodiment, the client determines a first access level corresponding to the access request; selects a target desensitization rule matching the first access level from the desensitization rules preset in the security plug-in, desensitizes the initial data, and obtains target data; or,
[0118] The client determines a second access level corresponding to the access request, and when the second access level meets a preset level threshold, adjusts the mask layer, and determines target data according to the adjustment result.
[0119] The access verification method provided in this embodiment can reduce the cost of security protection and improve the comprehensiveness of security protection. The security plug-in issued by the plug-in server can be configured on the client. On this basis, the client can first use the security plug-in to detect whether the target site belongs to the protection site list issued by the plug-in server when accessing the target site through the running target browser; thereby using the protection site list to complete the preliminary protection of accessing the target site. When it is determined that the target site belongs to the protection site list, access security information can be constructed for the target browser. After sending it to the plug-in server, the plug-in server can construct access authentication information based on the access security information, and after feeding it back to the client, the client can use the access authentication information to update the access request to the target access request after receiving the access request submitted for the target site. After that, the target access request will be verified by the plug-in server to verify the access request submitted by the client for the target site, and then the target access task can be executed according to the verification result. When the client accesses the target site, the security requirements of the old system can be met by configuring the security plug-in on the client, and the security problem can be solved by solving the trusted source from the access source, thereby effectively improving the access security and reducing the security maintenance cost of the business party.
[0120] The above is a schematic scheme of an access verification method of this embodiment. It should be noted that the technical scheme of the access verification method and the technical scheme of the access verification system described above are of the same concept, and the details not described in detail in the technical scheme of the access verification method can be found in the description of the technical scheme of the access verification system described above.
[0121] Corresponding to the above method embodiment, this specification also provides an access verification device embodiment, Figure 5FIG. 1 shows a schematic diagram of the structure of an access verification device provided by an embodiment of the present specification. Figure 5 As shown, the device is applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including:
[0122] The detection module 502 is configured to detect whether the target site belongs to a protection site list by using the security plug-in when accessing the target site through the target browser, wherein the protection site list is issued by the plug-in server;
[0123] If yes, executing construction module 504, wherein construction module 504 is configured to construct access security information for the target browser;
[0124] The sending module 506 is configured to send the access security information to the plug-in server, and receive access authentication information fed back by the plug-in server for the access security information;
[0125] The updating module 508 is configured to, upon receiving an access request submitted to the target site, update the access request to a target access request using the access authentication information, and send the request to the plug-in server for verification.
[0126] The above is a schematic scheme of an access verification device of this embodiment. It should be noted that the technical scheme of the access verification device and the technical scheme of the access verification method described above are of the same concept, and the details not described in detail in the technical scheme of the access verification device can be found in the description of the technical scheme of the access verification method described above.
[0127] Figure 6 The block diagram of a computing device 600 according to an embodiment of the present specification is shown. The components of the computing device 600 include but are not limited to a memory 610 and a processor 620. The processor 620 is connected to the memory 610 via a bus 630, and the database 650 is used to store data.
[0128] The computing device 600 also includes an access device 640 that enables the computing device 600 to communicate via one or more networks 660. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 640 may include one or more of any type of network interface (e.g., a network interface card (NIC)) that is wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world-wide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, and a near field communication (NFC).
[0129] In one embodiment of the present specification, the above components of the computing device 600 and Figure 6 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 6 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
[0130] The computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 600 may also be a mobile or stationary server.
[0131] The processor 620 is used to execute the following computer executable instructions, which implement the steps of the above-mentioned access verification method when executed by the processor.
[0132] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the access verification method described above are of the same concept, and the details not described in detail in the technical scheme of the computing device can be found in the description of the technical scheme of the access verification method described above.
[0133] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned access verification method when executed by a processor.
[0134] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the access verification method described above are of the same concept, and the details not described in detail in the technical scheme of the storage medium can be found in the description of the technical scheme of the access verification method described above.
[0135] An embodiment of the present specification also provides a computer program product, including a computer program or instructions, which implement the steps of the above-mentioned access verification method when executed by a processor.
[0136] The above is a schematic scheme of a computer program product of this embodiment. It should be noted that the technical scheme of the computer program product and the technical scheme of the access verification method described above are of the same concept, and the details not described in detail in the technical scheme of the computer program product can be found in the description of the technical scheme of the access verification method described above.
[0137] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0138] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0139] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.
[0140] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0141] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can understand and use this specification well.
Claims
1. An access verification system, characterized in that: The access verification system includes a client and a plug-in server, wherein the client runs a target browser and configures a security plug-in issued by the plug-in server, including: The client is used to use the security plug-in to detect whether the target site belongs to the protection site list when accessing the target site through the target browser, wherein the protection site list is issued by the plug-in server; if so, use the pre-started secondary authentication module to build and execute the secondary authentication task; when it is determined that the secondary authentication is passed according to the task execution result, determine the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser; according to the session identifier and the fingerprint information, build access security information for the target browser and send it to the plug-in server, wherein the secondary authentication task is used for user face recognition, and the fingerprint information is built based on the version information and language information of the target browser, and the device hardware information of the client; The plug-in server is used to perform a hash operation on the session identifier and the fingerprint information, obtain access authentication information according to the hash operation result, and send it to the client; The client is used to, upon receiving an access request submitted to the target site, update the access request to a target access request using the access authentication information, and send the request to the plug-in server; The plug-in server is used to verify the target access request and execute the target access task according to the verification result.
2. The access verification system according to claim 1, characterized in that: The client is further configured to, upon receiving a startup instruction submitted for the target browser, detect whether the client is configured with the security plug-in based on the startup instruction; if so, send a list acquisition request to the plug-in server; The plug-in server is also used to send the protection site list to the client in response to the list acquisition request.
3. The access verification system according to claim 1, characterized in that: The client is further configured to, upon receiving an access request submitted to the target site, add the access authentication information to the access request to obtain a target access request; Sending the target access request to the plug-in server; The plug-in server is also used to parse the target access request to obtain access authentication information to be verified; compare the access authentication information to be verified with the access authentication information; and forward the target access request to the target site by executing a target access task when it is determined that the target access request has been verified according to the comparison result.
4. The access verification system according to any one of claims 1 to 3, characterized in that: The client is further configured to receive initial data fed back by the target site in response to the target access request; Desensitizing the initial data using the desensitization rules preset in the security plug-in to obtain target data; The target data is displayed via a target page in the target browser.
5. The access verification system according to claim 4, characterized in that: The client is also used to load the initial data into the target page using the desensitization rules preset in the security plug-in; add a mask layer to the initial data in the target page, and obtain the target data according to the adding result.
6. The access verification system according to claim 5, characterized in that: The client is further used to determine a first access level corresponding to the access request; select a target desensitization rule matching the first access level from the desensitization rules preset in the security plug-in, perform desensitization processing on the initial data, and obtain target data; or, The client is further configured to determine a second access level corresponding to the access request, and when the second access level satisfies a preset level threshold, adjust the mask layer, and determine the target data according to the adjustment result.
7. An access verification method, characterized in that: Applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including: In the case of accessing a target site through the target browser, using the security plug-in to detect whether the target site belongs to a protection site list, wherein the protection site list is issued by the plug-in server; If yes, construct and execute a secondary authentication task using a pre-started secondary authentication module; if it is determined that the secondary authentication is passed according to the task execution result, determine the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser; construct access security information for the target browser according to the session identifier and the fingerprint information, wherein the secondary authentication task is used for user face recognition, and the fingerprint information is constructed based on the version information and language information of the target browser, and the device hardware information of the client; Sending the access security information to the plug-in server, and receiving access authentication information fed back by the plug-in server in response to the access security information; When receiving an access request submitted to the target site, the access request is updated to a target access request using the access authentication information and sent to the plug-in server for verification.
8. An access verification device, characterized in that: Applied to a client, wherein the client runs a target browser and configures a security plug-in issued by a plug-in server, including: a detection module configured to detect, when accessing a target site through the target browser, whether the target site belongs to a protection site list by using the security plug-in, wherein the protection site list is issued by the plug-in server; If yes, execute the construction module, the construction module is configured to construct and execute the secondary authentication task using the pre-started secondary authentication module; if it is determined that the secondary authentication is passed according to the task execution result, determine the session identifier corresponding to the secondary authentication task and the fingerprint information corresponding to the target browser; construct access security information for the target browser according to the session identifier and the fingerprint information, wherein the secondary authentication task is used for user face recognition, and the fingerprint information is constructed based on the version information and language information of the target browser, and the device hardware information of the client; A sending module, configured to send the access security information to the plug-in server, and receive access authentication information fed back by the plug-in server for the access security information; The update module is configured to, upon receiving an access request submitted to the target site, update the access request to a target access request using the access authentication information, and send the request to the plug-in server for verification.
9. A computing device, characterized in that include: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method according to claim 7 are implemented.
10. A computer-readable storage medium, characterized in that: It stores computer executable instructions, which implement the steps of the method according to claim 7 when executed by a processor.
11. A computer program product, characterized in that The method comprises a computer program or an instruction, which implements the steps of the method according to claim 7 when the computer program or the instruction is executed by a processor.
