WO2016188335A1 - Access control method, apparatus and system for user data - Google Patents

Abstract

Disclosed are an access control method, apparatus and system for user data. The method comprises: a first server receives a data access request initiated by an account; the first server verifies whether the data access request carries context information of the account, and/or checks the context information of the account; and the first server allows sending the data access request to a third-party system when it is determined that the data access request contains the context information of the account and/or the check of the context information of the account is passed, so that the third-party system accesses a data source according to the data access request. The present application solves the technical problem of poor security of a data source due to poor security of an account initiating an access in a process in which a user accesses the data source by using a third-party system in the prior art.

Description

User data access control method, device and system

The present application claims priority to Chinese Patent Application No. 20151026, 707, filed on May 22, 2015, entitled,,,,,,,,,,,,,,,,,,,,,,

Technical field

The present invention relates to the field of Internet, and in particular to a method, device and system for access control of user data.

Background technique

Existing service providers (such as Taobao, Tmall, etc.) need to provide a large number of independent software providers ISVs to serve users in order to better serve users. In this case, the service provider realizes storing a large amount of open-ended user data in the data source server by establishing a data open platform, and the user can authorize the third-party system to access the user data stored in the data source server, thereby A solution that opens up a large amount of user data to the system provided by ISV realizes an open data application environment.

In the above-mentioned open data application environment, the security of the access user cannot be guaranteed. For example, the hacker forges the account of the legitimate user, so that the forged account can replace the legitimate user to use the third-party system to access the data source, resulting in the user of the data source server. Data was illegally accessed, causing data to be compromised.

Further, since the system provided by the ISV is an uncontrollable third-party system, in the process of processing a large amount of user data by the third-party system, various human factors cannot be estimated (for example, privately allowed within the time allowed by the user's authorization). The user data leakage caused by hacking or attacking, or the security of the uncontrollable third-party system is poor, making the data open environment of the data development platform and the system provided by the ISV less secure. .

It should be noted in detail here that in the related art, an OAuth (Open Authorization) protocol is usually used for authorization. OAuth is an open standard that allows users to authorize third-party systems to access user data without the need to provide usernames and passwords to third-party systems, and to prevent sensitive information such as passwords from being leaked to third-party systems.

It can be seen from the above that when a user authorizes a third-party system to access user data, a possible risk is as follows: the third-party system can obtain a temporary session token representing the user identity, and the temporary session token is independent of information such as user status, and is generally authorized. The time is a fixed value. If the temporary session token is stolen, the thief will be able to read and write the number of users at will. According to this, the user data is low in security. Moreover, third-party systems are mixed, and third-party systems with poor security may be maliciously controlled or maliciously operated by humans. In this case, if all user lists and user authorization information maintained on the third-party system are obtained, there are also The user authorization information may be used to read and write user data at random, resulting in low security of user data.

For example, after a legitimate user authorizes a third-party system, user B can also send a data access request initiated by user A to a third-party system. In this case, user B requests access to user A's user data, and the third-party system cannot. If the data access request is initiated by the user A, or the user B is accidentally allowed to impersonate the data access request initiated by the user A, the user B can read and write the user data of the user A at will, which also causes the user data to be low in security.

In the above prior art, in the process of the user accessing the data source by using the third-party system, due to the poor security of the account that initiated the access, the security of the data source data is poor, and no effective solution has been proposed yet.

Summary of the invention

The embodiment of the present application provides a method, an apparatus, and a system for controlling access of user data, so as to at least solve the problem that the data source is poor in the process of accessing the data source by the third-party system when the user accesses the data source in the prior art. Technical problems with poor data security.

According to an aspect of the embodiments of the present application, a method for controlling access of user data is provided, including: a first server receiving an account-initiated data access request; and a first server verifying whether the data access request carries context information of the account, and/ Or verifying the context information of the account; the first server includes the context information of the account in determining the data access request, and/or allowing the data access request to be sent to the third party system if the context information of the account is verified. Enables third-party systems to access data sources based on data access requests.

According to an aspect of the embodiments of the present application, an access control method for user data is further provided, including: the client obtains context information of the account; and the client sends an account-triggered data access request to the first server, where the data access request Include at least context information; the client receives the access data obtained by the first server according to the data access request; wherein the first server determines that the data access request includes the context information of the account, and/or the context information of the account is verified In this case, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

According to an aspect of the embodiments of the present application, an access control method for user data is provided, including: a third-party system receives a data access request sent by a first server, where the data access request is an account initiated by an account. Request for context information; third party system forwards data access request to data source server; third party The system receives data to be accessed by the data access request returned by the data source server, wherein when the data source server determines, according to the context information included in the data access request, the account that initiates the data access request is a secure access account, and the data access request is a secure access. When requested, the third-party system is allowed to access the data source based on the data access request.

According to another aspect of the embodiments of the present application, an access control apparatus for user data is provided, including: a receiving module, configured to receive an account-initiated data access request; and a verification module, including a first verification unit and/or a second check unit, wherein the first check unit is configured to verify whether the context information of the account is carried in the data access request, the second check unit checks the context information of the account, and the control module is used in the check module In the case of verification pass, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

According to another aspect of the embodiments of the present application, an access control apparatus for user data is further provided, including: an obtaining module, configured to acquire context information of an account; and a sending module, configured to send an account-triggered data access request to the first a server, wherein the data access request includes at least context information; the receiving module is configured to receive the access data acquired by the first server according to the data access request; wherein the first server determines that the data access request includes the context information of the account, and Or, in the case that the context information of the account is verified, the data access request is allowed to be sent to the third-party system, so that the third-party system accesses the data source according to the data access request.

According to another aspect of the embodiments of the present application, an access control apparatus for user data is provided, including: a first receiving module, configured to receive a data access request sent by a first server, where the data access request is initiated by an account a request for including context information of the account; a forwarding module for forwarding the data access request to the data source server; and a second receiving module, configured to receive data to be accessed by the data access request returned by the data source server, wherein, when the data source The server determines, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account, and the data access request is a secure access request, allowing the third-party system to access the data source according to the data access request.

According to still another aspect of the embodiments of the present application, an access control system for user data is provided, including: a client terminal, configured to initiate a data access request after the account is logged in; and a first server, configured to communicate with the client terminal, for After the verification data access request includes the context information of the account, and/or the verification context information is the legal information, the data access request is transparently transmitted; the third-party system server communicates with the first server, and is configured to receive the transparent transmission of the first server. a data access request; the data source server communicates with the third-party system server, and is configured to receive a data access request forwarded by the third-party system server, and determine, according to the context information included in the data access request, the account that initiates the data access request is a secure access The account, and when the data access request is a secure access request, returns the access data corresponding to the data access request to the third-party system server.

In the embodiment of the present application, the first server receives the data access request initiated by the account, verifies whether the data access request carries the context information of the account, and/or the manner of verifying the context information of the account, by using the first server. Determining that the data access request includes context information of the account, and/or allowing the data access request to be sent to the third party system if the context information of the account is verified. According to the above solution, after the current account (which may be a legitimate account or a forged account pretends to be the legitimate account) sends a data access request to the first server, the first server checks each received data access request, that is, the first The server determines whether the data access request carries the account context information, and/or whether the context information can pass the verification. When the verification of the data access request passes, the first server allows the data access request to be sent to the third-party system. The third party system can then access the data source based on the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Therefore, the third-party system is configured to access the data source according to the data access request, thereby realizing the technical effect of identifying whether the account that sends the data access request is a legitimate account before the third-party system receives the data access, and the existing solution is solved. Technology In the process of using a third-party system to access a data source, the security of the data of the data source is poor due to the poor security of the account that initiated the access.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the present application, and are intended to be a part of this application. In the drawing:

1 is a block diagram showing the hardware structure of a computer terminal of an access control method for user data according to an embodiment of the present application;

2 is a flowchart of a method for controlling access of user data according to Embodiment 1 of the present application;

3 is a schematic diagram of a service flow of an optional access control method for user data according to Embodiment 1 of the present application;

4 is a schematic flowchart of an optional access control method for user data according to the embodiment shown in FIG. 2 of the present application;

FIG. 5 is a schematic flowchart diagram of another optional access control method for user data according to the embodiment shown in FIG. 2 of the present application; FIG.

6 is a schematic diagram of a service flow interaction of an access control system for user data according to Embodiment 1 of the present application;

7 is a schematic flowchart of a method for controlling access of user data according to Embodiment 2 of the present application;

8 is a schematic flowchart of a method for controlling access of user data according to Embodiment 3 of the present application;

9 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 4 of the present application;

10 is a schematic structural diagram of an optional second verification unit according to the embodiment shown in FIG. 9 of the present application;

11 is a schematic structural diagram of another optional second verification unit according to the embodiment shown in FIG. 9 of the present application;

12 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 5 of the present application;

13 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 6 of the present application;

14 is a schematic structural diagram of an access control system for user data according to Embodiment 7 of the present application;

FIG. 15 is a structural block diagram of a computer terminal according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. It is an embodiment of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or order. It is to be understood that the data so used may be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "comprises" and "comprises" and "the" and "the" are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.

The terms referred to in this application are explained below:

Independent Software Vendors (ISVs), or independent software developers, refer to companies that specialize in the development, production, sales, and service of software.

Context information, or context information, is related to the activity status and activity information of the account. The context information of the account can be used as an important criterion to determine whether the third-party system can obtain and obtain user data with multiple high-level privilege levels.

Embodiment 1

According to an embodiment of the present application, a method embodiment of an access control method for user data is also provided, which needs to be said. It will be understood that the steps illustrated in the flowchart of the figures may be executed in a computer system such as a set of computer executable instructions, and, although the logical order is illustrated in the flowchart, in some cases, The steps shown or described are performed in an order different from that herein.

The method embodiment provided in Embodiment 1 of the present application can be executed in a mobile terminal, a computer terminal or the like. Taking a computer terminal as an example, FIG. 1 is a hardware structural block diagram of a computer terminal of an access control method for user data according to an embodiment of the present application. As shown in FIG. 1, computer terminal 10 may include one or more (only one shown) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) A memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in FIG. 1 is merely illustrative and does not limit the structure of the above electronic device. For example, computer terminal 10 may also include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG.

The memory 104 can be used to store software programs and modules of the application software, such as program instructions/modules corresponding to the access control method of the user data in the embodiment of the present application, and the processor 102 runs the software program and the module stored in the memory 104, thereby Perform various functional applications and data processing, that is, implement the vulnerability detection method of the above application. Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 104 may further include memory remotely located relative to processor 102, which may be coupled to computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Transmission device 106 is for receiving or transmitting data via a network. The network specific examples described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.

In the above operating environment, the present application provides an access control method for user data as shown in FIG. 2. FIG. 2 is a flowchart of a method for controlling access of user data according to Embodiment 1 of the present application.

As shown in FIG. 1 and FIG. 2, the computer terminal 10 may be a first server. As shown in FIG. 2, an optional access control method for user data includes the following implementation steps:

Step S202: The first server receives an account-initiated data access request.

In the above step S202 of the present application, as shown in FIG. 3, the account may be a legal account registered by the client. It can also be an illegal account after forgery. The client that logs in to the legal account may not be limited to products such as Taobao and Tmall. The user may register the account on the client. After each user logs in to the client using the account, the user may initiate the data access request by using the client.

It should be noted that, in conjunction with FIG. 3, the foregoing first server may be a gateway shown in FIG. 3, where the gateway is used to transparently transmit the data access request. In an optional solution, the first server may be a cloud load balancing server of Alibaba Cloud.

For example, taking Taobao's sellers to implement the order management function, Taobao can provide all the data sources of the seller (such as product information, transaction content, transaction amount and product evaluation of the order), because Taobao does not provide order management. The function, at this time Taobao provides an interface to enable the independent software provider to provide a third-party system that can provide order management functions. Therefore, when any registered login account successfully logs in to Taobao, it can be passed in the browser. Open the webpage of the above third-party system to initiate a data access request, to access the data source of Taobao through a third-party system to obtain access data, and further implement the order management function.

Step S204: The first server verifies whether the data access request carries the context information of the account, and/or checks the context information of the account.

The context information involved in the above step S204 of the present application is related to the activity status and activity information of the account, and is used to represent the authority of the account corresponding to the context information to the third party system to access the account user data. In the embodiment of the present application, the context information may include, but is not limited to, the online status of the account, the offline status of the account, the online time of the account, the offline time of the account, the login time of the account, the login location of the account, the login device of the account, and the account. Access to the record of user data, the data privacy level of the account, the common login device of the account, the common login location of the account, the account security status of the account, and the account risk assessment of the account.

The foregoing steps provided by the present application may be implemented to determine whether an account initiating the data access request is a legitimate account by checking whether the received data access request carries context information and/or context information of the account. Judging from the kind of information contained in the above context information, the context information is data having non-fixed values and the hacker cannot steal characteristics. Therefore, it is highly credible to verify whether the account is legal based on the context information. The solution of introducing the context checking mechanism in the present application can make the verification result of the account more accurate, and specifically, can effectively solve the problem that the user data is randomly accessed within the time allowed by the user authorization.

As an example, the Taobao seller implements the order management function. After the Taobao seller opens the third party system that provides the order management function and triggers the behavior of sending the data access request, the client's current login account will issue the context containing the seller account. Data access request for information. At this time, if a hacker or a malicious user forges the seller account, the forged account will also pretend to be the seller account and issue a data access request, then the seller triggers the sending The data access request and the data access request sent by the pretending seller are transmitted to the first server. At this time, the first server can verify whether the received data access request contains context information, and/or whether the context information is legal information. To identify fake accounts. For example, the gateway shown in FIG. 3 performs the above verification or verification on all received data access requests to implement screening of the account that initiated the data access request.

Step S206: The first server includes the context information of the account in determining the data access request, and/or allows the data access request to be sent to the third-party system if the context information of the account is verified, so that the third-party system accesses according to the data. Request access to the data source.

In the above step S206 of the present application, since the context information of the account is included in the data access request, and/or the context information is legal information, the current account may be determined to be a secure account, and therefore, the first server (may be The gateway shown in FIG. 3) allows the data access request initiated by the security account to be transparently transmitted to the third-party system, and enters the third-party system to process the data access request, that is, the third-party system accesses the data source according to the received data access request, The data source requests the user's data.

Optionally, the third-party system may request to access the user data stored in the data source server by forwarding the data access request to the data source server, and then the data source server reads the user data according to the data access request. Return to a third-party system.

It should be noted that the third-party system involved in the present application implements related system functions for a system server provided by a software provider, and can trigger a third-party system to implement related functions by at least one of the following methods: in a browser. Enter the address to open the webpage of the above third-party system to access the corresponding system server, invoke the related functions of the third-party system, and activate the third-party system by triggering the plug-in installed on the client to access the corresponding system server. The related functions of the third-party system are activated by triggering the application software installed on the client to access the corresponding system server.

It can be seen that the foregoing steps provided by the present application may enable the first server to include context information of the account in determining the data access request, and/or the first server considers to issue the data access if the context information of the account is verified. The requested account is a legitimate account and the data access request is sent to a third party system. It can be seen that the data access request sent by the first server transparently transmitted to the legal account of the third-party system is equivalent to giving the third-party system a data source access right, and instructing the third-party system to read what type in the data source. User data, thereby realizing whether the data access request received by the third-party system is sent by a legitimate account.

In the open data application environment of the present application, the data access request initiated by the legal account obtained by the user carries the context information of the account, and the unregistered account or the data access request issued by the pretending account is not carried. The context information of the account. In this case, the first server authenticates by accessing the data. Whether the request carries the context information of the account can determine whether the data access request is initiated by a legitimate account.

In another application environment in which the data is related to the present application, the data access request initiated by the legal account obtained by the user carries the context information of the account; and may be forged, unregistered, or pretending to be the data sent by the registered account. The access request appears to be carrying the context information of the account. Since the context information of the account has the activity status and activity information of the account itself, and the activity status and the activity information have variable attributes and cannot be acquired by the hacker, the forged data access request seems to carry the context information even though it is formally. The content cannot be consistent with the true contextual information of the legitimate account that it impersonates. In this case, the first server needs to check the context information of the account; or the first server further checks the context information of the account after determining whether the data access request carries the context information of the account, to determine Whether the data access request is initiated by a legitimate account.

Specifically, for products such as Taobao and Tmall, the third-party system may include an order management system, a logistics management system, or a virtual machine server, and the data source may be generated and recorded by the account when using the Taobao and Tmall websites. User data, for example, for Taobao buyers, the data source may include: user avatar, user nickname, user registration time, user login information, user mobile phone number, user mailbox, user address, user history shopping information, user shopping demand, user Collection information and user payment information, etc.

As an example, Taobao's seller implements the order management function. For a hacker or a malicious user to forge a Taobao seller account, and impersonate the data access request issued by the Taobao seller account through the forged account, it is impossible to carry the correct context information of the Taobao seller account. Therefore, the first server or the verification server does not include the account context information, or the verification of the included account context information fails, so the first server can determine that the data access request is not a data access request issued by the legitimate account; The Taobao seller triggers the data access request sent by the plug-in provided by the third-party system (such as the order management system), carries the context information of the seller account, and the first server verifies that the data request contains the account context information, and the carried context The information verification is correct, so the first server can determine that the data access request is a data access request issued by the legal account, and then send the data access request to a third-party system that provides the order management function, and provides order management. The third-party system can access the data related to the seller's account in the data source provided by Taobao (such as product information of the order, transaction content, transaction amount and product evaluation) to obtain the user. Data, complete the order management function provided by the third-party system.

As can be seen from the above, in the solution provided by the foregoing embodiment 1, the current account (which may be a legitimate account or a forged account impersonating the legitimate account) sends a data access request to the first server, and the first server receives each received message. A data access request is verified, that is, the first server determines whether the data access request carries the account. Whether the information below, and/or the context information can pass the verification, when the verification of the data access request is passed, the first server allows the data access request to be sent to the third-party system, and the third-party system can then Access requests to access the data source. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

In the optional solution provided by the foregoing embodiment of the present application, in step S206, the first server includes the context information of the account in determining the data access request, and/or allows the data access if the context information of the account is verified. After the request is sent to a third-party system, you can also perform the following implementation steps:

In the first optional implementation step, the first server does not include the context information of the account in determining the data access request, or the first server prohibits sending the data access request to the third party if the context information verification of the account fails. System and issue an alarm message.

In the foregoing implementation steps of the present application, the first server prohibits sending the data access request that fails the verification to the third-party system, and sends an alarm message for alerting that the data access request does not include the context information or the context information verification fails, Including two different situations: context information and context information verification failure, different types of alarm information can also be issued.

Through the first optional implementation step, only the first server determines that the data access request carries the account context information, and/or the context information passes the verified data access request, and can be transmitted to the third-party system, ensuring the first The data access request received by the three-party system is sent by the legal account, which ensures that when the third-party system accesses the data source according to the data access request, the account that initiates the data access request is a legitimate account, thereby ensuring the third-party system receives the The security of the originating account of the data access request.

In the second optional implementation step, the first server does not include the context information of the account in determining the data access request, or the first server sends the data access request to the third-party system if the context information verification of the account fails. .

In the foregoing implementation steps of the present application, even if the first server determines that the data access request does not include the context information of the account, or the context information verification of the account fails, the first server still sends the data access request to the third party system. It should be noted here that although the first server allows data access requests that do not contain account context information or data access requests for which the context information of the account fails to be sent to a third-party system, it does not mean that the first service The server may not perform the schemes provided in the above steps S202 to S206.

In an optional solution provided by the foregoing embodiment of the present application, before performing the step S202: the first server receives the data-initiated request initiated by the account, the following implementation steps may also be performed:

Step S2012: After the account is logged in to the client, a login request is initiated to the login server.

In the above step S2012 of the present application, the client may be a software product, such as a software such as a Taobao client or a Tmall client, or may be a mobile terminal device or a computer device. When the user logs in to the client using the account, the user initiates a login request to the login server, and the login server calculates the complete context information corresponding to the account (ie, the complete context information), and the login server stores the account password information of the account and the above complete Contextual information. In a preferred solution, after the login server receives the login request of the account, it may first determine whether the information carried in the received login request matches the account information stored locally by the login server, and if the matching is determined, the account is allowed to log in. Generate complete context information and reject account login if there is no match.

As an example, Taobao's sellers implement order management functions. When using a third-party system that provides order management functions, Taobao sellers first need to log in to Taobao client, Taobao seller account to login server, such as Taobao server, initiate login request, complete Taobao. Login for the seller account.

Step S2014: The client receives the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request.

In the above step S2014 of the present application, after the login server generates the complete context information according to the login request, the login server returns the context information (Context information) to the client, where the Context information may be the child of the complete context information generated by the login server. set.

It should be noted here that the complete context information can contain all kinds of account information specified. The login server may choose to return only one subset of the complete context information to the client for actual needs or the amount of data transmitted by the login server. The context information includes but is not limited to the user's account ID, and some variant processing algorithm of the user information The result, etc. (for example, using an irreversible algorithm such as md5, the account information is transformed to obtain a corresponding hash value). The embodiment of the present application is not limited to which subset of the complete context information is returned to the client. The context information returned by the login server to the client can be transmitted in plain text or in cipher text.

Through the above step S2014, the login server can form a subset of the complete context information and return it to the client by extracting the necessary information in the complete context information. In the case that the returned context information can satisfy the requirement of the first server to verify whether the context information is carried in the data access request, and/or to verify whether the included context information is correct, the complete context information is returned to the client. A subset of methods can be effectively reduced The amount of information sent by the login server to the client. In the case that a large number of users initiate a login request to the login server in a short period of time, this method can effectively save the system resources of the login server and reduce the data transmission burden of the login server.

As an example, the Taobao seller implements the order management function. The login server (for example, Taobao server) stores not only the user name and user password information of the Taobao seller, but also the online status and account of the account of the Taobao seller account. Offline status, online time of account, offline time of account, login time of account, login location of account, login device of account, record of account access user data, data privacy security level of account, common login device of account, account Common login location, account security status of the account, and account risk assessment of the account. When the Taobao server returns information to the seller account, the Taobao server calculates the complete context information of the generated account according to the stored information of the seller account, and returns one of the generated complete context information to the client.

Step S2016: The client sends a data access request carrying the context information to the first server.

The solution provided in step S2016 of the present application may be implemented after the client receives the context information returned by the login server, and when the client initiates the data access request, the context information is loaded into the data access request and sent to the first server. Thus, when the login account triggers the third party system to initiate a data access request (eg, the user opens a data access request generated by the third party system webpage in the browser), a data access request including the context information is generated.

Still taking the order management function of the seller of Taobao. For example, when the Taobao seller opens the third-party system that provides the order management function in the browser, the data access request data access request containing the Taobao seller account is generated and sent to the first server. The request data access request is used to instruct the third party system to access the user data of the seller account in the data source server provided by Taobao.

As can be seen from the above, the above steps S2012 to S2016 of the present application provide an alternative for generating and transmitting context information to the first server. The login request is initiated based on the above step S2012, and the context information generated by the login request is received in step S2014. When the third party system needs to access the data source, the data access request including the context information is generated, and finally sent to the step S2016 to The first server.

In an optional solution provided by the foregoing embodiment, before the step S2014: the client receives the context information returned by the login server, the following implementation steps may be performed:

Step S2013: The login server encrypts the account information, and generates context information according to the encrypted data.

In the above step S2013 of the present application, the context information may still be the complete context generated by the login server. A subset of the information. When the context information is generated, the user account information may be encrypted or transformed once, for example, by using MD5, and the context information may be generated based on the encrypted ciphertext information or the transformed data. Through the above steps, reliable transmission of information between the login server and the client is realized, thereby avoiding the possibility that the user context information is stolen, and at the same time, when the amount of data after encryption or transformation is smaller than the data amount of the original information, during the transmission process It can further save system resources and improve transmission efficiency. For example, the context information is irreversibly transformed (for example, irreversible operation such as md5), and the corresponding hash value is obtained. Since the data length of the hash value is smaller, the data transmitted between the login server and the client is not only higher. Level and take up less system resources.

In an optional solution provided by the foregoing embodiment of the present application, the step S204: verifying the context information of the account may include at least two specific implementation steps, and respectively, in combination with FIG. 4 and FIG. The implementation steps are introduced:

The first server of the present application may be the gateway shown in FIG. 3, as shown in FIG. 4, in an optional solution provided by the foregoing embodiment, the foregoing step S204: verifying the context information of the account, A specific implementation step includes the following steps S402 to S406:

Step S402: After determining that the data access request carries the context information, the first server reads the context information carried in the data access request.

In the above step S402 of the present application, after receiving the data access request, the first server reads the context information carried in the data access request after determining that the data access request carries at least the content that appears to be the context information.

Step S404: The first server matches the context information with the pre-stored complete context information. If the matching is successful, the context information of the account is determined to be legal information.

In the above step S404 of the present application, as described in the foregoing embodiment of the present application, the legal account may issue a data access request including context information, and the forged account may also impersonate a legitimate account and issue context information including what appears to be the legitimate account. Data access request. Therefore, after the context information is read by the first server, the context information is matched with the pre-stored complete context information. Pre-stored complete context information, which can be the complete context information stored or the full context information of the cache.

In a possible case, as shown in FIG. 4, when the complete context information can be fixedly stored in the login server due to the complete context information in the login server, the first server executes the context information and the pre-stored complete context information. When the matching step is performed, the first server issues a request to the login server to read the complete context information, and receives the complete context information returned by the login server.

In another possible case, as can be seen in conjunction with Figure 4, although there is full context information in the login server, Each time the first server performs the step of matching the context information with the pre-stored complete context information, the request to read the complete context information to the login server causes the login server to be overburdened. Therefore, the full context information can be cached only in the login server in order to reduce the amount of storage required for the login server. In this case, when the login server generates the context information and returns to the client, the login server may also send the complete context information to the first server for storage, and wait until the first server performs the context information and the pre-stored complete context information. When the matching step is performed, the first server reads the complete context information stored locally. After the login server sends the complete context information to the first server, whether the complete context information in the login server is to be deleted is not limited in the embodiment of the present application.

In another possible case, as can be seen from FIG. 4, although the login server has complete context information, each time the first server performs the step of matching the context information with the pre-stored complete context information, the login server is issued. A request to read the full context information can be overburdened by the login server. Therefore, the full context information can be cached only in the login server in order to reduce the amount of storage required for the login server. In this case, the context information server can be configured. When the login server generates context information and returns to the client, the login server can also send the complete context information to the context information server for storage, and wait until the first server executes the context information. When the step of matching the pre-stored complete context information is performed, the first server issues a request to the context information server to read the complete context information, and receives the complete context information returned by the context information server. After the login server sends the complete context information to the context information server, whether the complete context information in the login server is to be deleted is not limited in the embodiment of the present application.

The foregoing step S2013 and the login server perform the above steps S2013 and the two implementations for the login server. The foregoing step S404 of the present application may further include the following two specific steps:

In an optional implementation, the login server does not perform the above step S2013, that is, the login server does not encrypt the account information, then step S404: the specific step of the first server matching the context information with the pre-stored complete context information is further The method includes: the first server extracts the information type and the data content corresponding to the context information from the pre-stored complete context information, and the first server determines that the extracted data matches the context information read by the first server, The result of whether the context information read by the server matches the pre-stored complete context information.

In another optional implementation, the login server performs the above step S2013, that is, the login server encrypts or transforms the account information, and generates context information according to the encrypted or transformed data; then step S404: the first server will The specific steps of matching the context information with the pre-stored complete context information include the following two methods:

In the first mode, the first server extracts the information type and the data content corresponding to the context information from the pre-stored complete context information, and encrypts the extracted data, wherein the first server encrypts the extracted data. The algorithm is the same as or corresponding to the encryption algorithm executed by the login server in step S2013. Thereafter, the first server can determine whether the context information read by the first server matches the pre-stored complete context information by determining whether the encrypted data matches the context information read by the first server.

In the second mode, when the first server performs the step of matching the context information with the pre-stored complete context information, the first server sends a matching authentication request to the context information server, where the matching authentication request includes the first server read The context information obtained by the first server receives the context information sent by the first server, and the context information server extracts the information type and data content corresponding to the context information sent by the first server from the pre-existing local complete context information. And encrypt the extracted data. The encryption algorithm performed by the context information server on the extracted data is the same as or corresponding to the encryption algorithm executed by the login server in step S2013. Thereafter, the context information server can determine whether the context information forwarded by the first server and the pre-existing local complete are obtained by determining whether the encrypted data matches the context information forwarded by the first server received by the context information server. Whether the context information matches the result. The context information server returns the result to the first server.

Step S406: The first server generates legal access identification information of the account, where the legal access identification information is used to represent that the account that initiated the data access request is a legal account.

In the above step S406 of the present application, the legal access identification information is generated by the first server, indicating that the data access request is verified by the first server. In the case of a fake account impersonating a legitimate account, the data access request issued by the forged account impersonating the legitimate account cannot be verified by the first server, that is, the forged account cannot be regarded as a legitimate account by the first server, and the data access request initiated by the forged account is not The context information is carried. Therefore, the first server does not transparently transmit the data access request sent by the forged account, and thus does not generate a legal access identifier information for the data access request initiated by the forged account.

It should be noted that, in the foregoing embodiment of the present application, the first server may only allow the data access request through the verification to be sent to the third-party system; the first server may also allow the un-verified data access request to be sent to the third party. system. At this time, the legal access identification information can be used to identify the verification result of the first server, and the account corresponding to the data access request with the legal access identification information is a legal account.

It should be noted that, after determining that the context information of the account is legal information, the first server may implement the foregoing step S406 by updating specific element data in the user context information, in this case, the updated element data. Can be considered legal access identification information.

It can be seen from the above that the above steps S402 to S406 of the present application provide an alternative scheme for the first server to verify the context information of the account. The first server reads the account context information included in the access request, and determines whether the context information matches the pre-stored complete context information. If the matching is successful, the context information of the account is determined to be legal information, and the legal access identifier of the account is generated. information.

In an optional solution provided by the foregoing embodiment of the present application, as shown in FIG. 5, in step S204, the context information of the account is verified, and the second specific implementation step includes the following steps S502 to S506:

Step S502: After determining that the data access request carries the context information, the first server sends the context information to the context information server.

In the foregoing step S502 of the present application, after receiving the data access request, the first server reads the context information carried in the data access request after determining that the data access request carries at least the content that appears to be the context information, and The context information in the data access request is sent to the context information server.

Step S504: The first server receives the verification result of the context information server verification context information.

When it is necessary to explain here, before the above-mentioned step S504 of the present application, when the login server generates the context information and returns it to the client, the login server also sends the complete context information to the context information server for storage. And the context information server matches the context information received by the foregoing step S502 with the pre-existing local complete context information. If the matching is successful, the verification result is that the context information of the account is legal information, and the context information server verifies the verification result. After returning to the first server, the first server performs the above step S504.

The specific steps of matching the context information with the pre-existing local complete context information in the context information server of the present application may further include the following two specific steps: step:

In the first embodiment, the login server does not perform the above step S2013, that is, the login server does not encrypt the account information, and the specific steps of the context information server matching the context information with the pre-existing local complete context information include: context information The server extracts the information type and the data content corresponding to the context information sent by the first server from the pre-existing local complete context information, and the context information server determines whether the extracted data matches the context information sent by the first server, It can be concluded that the context information sent by the first server matches the pre-existing local complete context information.

In the second embodiment, the login server performs the above step S2013, that is, the login server encrypts or transforms the account information, and generates context information according to the encrypted or transformed data; then the context information read by the first server is According to the encrypted data, at this time, the specific steps of the context information server matching the context information with the pre-existing local complete context information include: the context information server is pre-stored Extracting the information type and data content corresponding to the context information sent by the first server in the local complete context information, and encrypting the extracted data. The encryption algorithm performed by the context information server on the extracted data is the same as or corresponding to the encryption algorithm executed by the login server in step S2013. Thereafter, the context information server can determine whether the context information forwarded by the first server and the pre-existing local complete are obtained by determining whether the encrypted data matches the context information forwarded by the first server received by the context information server. Whether the context information matches the result. The context information server returns the result to the first server.

Step S506: In the case that the verification result is that the context information of the account is legal information, the first server receives the legal access identifier information of the account generated by the context information server, where the legal access identifier information is used to represent the account of the initiated data access request. Is a legal account.

In the above step S506 of the present application, the legal access identification information is generated by the context information server, indicating that the data access request is verified by the context server. In the case of a fake account impersonating a legitimate account, the data access request issued by the forged account impersonating the legitimate account cannot be verified by the context server, that is, the forged account cannot be recognized as a legitimate account by the context server, and the forged account may not have the legitimate access generated by the context server. Identification information. The context information server sends the generated legal access identifier information to the first server, and the first server may control whether to allow the data access request to be sent to the third-party system according to the received legal access identifier information.

It should be noted that after receiving the legal access identifier information sent by the context information server, the first server may implement the first server storage by updating specific element data in the user context information stored in the first server. Legal access to identification information.

As can be seen from the above, the foregoing steps S502 to S506 of the present application provide an alternative for the first server to verify the context information of the account. The first server sends the read account context information to the context information server, and the context information server completes the matching authentication work of the context information, and if the matching is successful, determines that the context information of the account is legal information, and generates an account. The legal access identification information is sent to the first server. The first server implements verification of the context information of the account by receiving the legal access identifier information sent by the context information server.

It can be seen from the above that, for the above step S204: verifying the context information of the account includes two specific implementation steps. In the first specific implementation step provided in steps S402 to S406, the first server completes the acquisition of the data. The context information carried in the request is accessed, and the judgment of whether the context information matches the pre-stored complete context information is completed, and the legal access identifier information is generated for the successfully matched account, that is, the account is determined to be a legitimate account. In the second specific implementation step provided by the step S502 to the step S506, the context information server completes the context information and the pre-existence by receiving the context information carried in the data access request acquired by the first server. If the local complete context information is matched, the legal access identifier information is generated for the successfully matched account, that is, the account is determined to be a legitimate account, and the legal access identifier information is returned to the first server. The above two specific implementation steps can implement verification of the context information of the account. The first specific implementation step is completed by the first server, which is more convenient in data processing, and the second specific implementation step is completed by the context information server. The data processing task of the first server can be effectively shared, and the data processing efficiency is improved.

In the optional solution provided by the foregoing embodiment of the present application, after the step S206: allowing the data access request to be sent to the third-party system, the following implementation steps may be further included:

Step S207: The data source server receives the data access request forwarded by the third-party system.

In the above step S207 of the present application, after the third-party system receives the data access request sent by the first server, the third-party system forwards the data access request to the data source server, and the data access request is used to instruct the third-party system to request the data source. User data of the legal account stored.

Step S208: The data source server accesses the first server or the context information server. If the query obtains the legal access identifier information of the account, it determines that the data access request initiated by the legal account is a secure access request.

When it is required to be described herein, in the specific implementation step provided in the above step S204, the legal access identification information of the account may be generated by the first server and stored in the first server, or may be generated by the context information server and stored in the first server. Can also be generated by the context information server and stored in the context information server. Therefore, in the above step S208 of the present application, when the data source server queries the legal access identification information of the account, if the legal access identification information of the account is generated by the first server, the data source server accesses the first server to query whether the account has the legality. Accessing the identification information; if the legal access identification information of the account is generated by the context information server, the data source server accesses the first server or the context information server to query whether the legal access identification information of the account is available. For an account capable of querying the legal access identification information, the data source server determines that the data access request initiated by the account is a secure access request.

It should also be noted here that, for the first server, only the data access request by the check is allowed to be sent to the third-party system, and the first server allows all the data access requests to be sent to the third-party system, in step S208. Different treatment methods. For the case where the first server only allows the data access request through the verification to be sent to the third-party system, the data access request received and forwarded by the third-party system passes the verification of the first server and has the legal access identification information, then the first server The technical effect of shielding the forged account from impersonating a data access request initiated by a legitimate account can be implemented. In the case that the first server allows all data access requests to be sent to the third-party system, the data access request received and forwarded by the third-party system may pass the verification and have the legal access identification information, or may not pass the verification and have no legal access identification information. , then the data source server needs to perform the above step S208 to learn Whether the account that sends the data access request is a legitimate account, when the legal access identification information is not queried, the data source server may determine that the data access request is not a secure access request, and refuse to provide the data to be accessed by the data access request.

Through the above step S208 of the present application, it is implemented whether the data source server identifies whether the received data access request is initiated by a legitimate account. And further, when the third-party system is attacked, the data access request forwarded by the third-party system may be stolen, and the data source server may send data to the data when the user does not operate to generate a data access request to impersonate a legitimate account. The source of the access request is traced back to determine whether the data access request is initiated by a legitimate user by querying whether the first server or the context information server has legal access identification information.

Step S209: The data source server returns data to be accessed by the data access request to the third party system.

In the above step S209 of the present application, after the data source server determines that the data access request is a secure access request, the data source server returns the data to be accessed by the data access request to the third party system. The data source server implements the effect of determining whether the data access request is initiated by a legitimate account by querying whether the user has the legal access identification information of the account, and avoids the adverse consequences of the malicious account reading the user data by impersonating the legitimate account data access request.

It can be seen from the above that through the optional solutions provided in steps S207 to S209 in the foregoing embodiment of the present application, the technical effect of the data source server for authenticating the account for initiating the data access request is realized. Further, when the third-party system receives the attack, even if the user context information stored in the third-party system is utilized by the forged account, the data source server can also query whether the first server or the context information server located upstream of the third-party system has The legal access identification information of the account effectively identifies whether the data access request is issued by a legitimate user or is forged by a third-party system, thereby further ensuring the security of the user data.

It should also be noted here that the context information (Context information) of the above account can determine whether the third party system can obtain and can obtain the user data of multiple high privilege levels. Among them, high-level data generally involves user privacy, such as user mobile phone number, home address, and even credit card information. Low-level data is generally not classified, such as user nickname, user avatar information, etc., and generally can be classified according to user privacy level. . Since the context information corresponding to the account can verify whether the data access request initiated by the client account is initiated by a legitimate user, if not, the third party system cannot obtain the user data, thus effectively preventing the third party system from being hacked or artificially The reason is that the user data is maliciously read and written, and the security of the user data is greatly improved.

Further, in an optional solution provided by the foregoing embodiment of the present application, after performing step S208: determining that the account that initiates the data access request is a secure access account, the following implementation steps may also be performed:

Step S2082: The data source server verifies whether the online information of the account is included in the context information;

In the above step S2082 of the present application, the context information may include online information of the account, when passing the technical hand After the segment detects that the account is online, the account online information is generated, and the account online information is added to the context information. For example, the mechanism for periodically transmitting the heartbeat packet to the client may be used to determine whether the account is online according to the message fed back by the client, and the step of determining whether the account is online may be performed by the login server.

Step S2084: When the context information includes the online information of the account, the data source server performs the step of returning data to be accessed by the data access request to the third party system.

In the above step S2084 of the present application, when the online information of the account is included in the context information, it means that the current account is online, and the data source server performs step S209: the data source server returns data to be accessed by the data access request to the third-party system.

In the optional solution provided by the foregoing embodiment of the present application, according to other information further included in the context information, step S209: the data source server returns data to be accessed by the data access request to the third-party system, and the specific implementation steps include at least the following two types. the way:

In the first mode, when the context information further includes the security privacy level information of the account, step S209: the step of the data source server returning the data to be accessed by the data access request to the third-party system includes:

Step S2092: The data source server generates corresponding first access data according to the security privacy level information, and returns the first access data to the third party system.

In the above step S2092 of the present application, the security privacy level information is for different third-party systems, and according to the degree of trust to the third-party system, and the degree of authorization of the user to the third-party system, the third-party system may be opened to different degrees of privacy. Identification information of user data. For example, when the security privacy level information indicates that the data access request has a higher security level, for example, the first security level, the first access data may include information corresponding to the first security level, for example, the user's mailbox information, the user's mobile phone. a number, or a user's address information, etc.; when the security privacy level information indicates that the data access request has a lower security level, such as a second security level, the first access data may include information corresponding to the second security level, for example, User's nickname information, user's avatar information, etc.

In the second mode, when the context information further includes the security risk status information of the account, step S209: the step of the data source server returning the data to be accessed by the data access request to the third-party system includes:

Step S2094: The data source server security risk status information generates corresponding second access data, and returns the second access data to the third party system.

In the above step S2094 of the present application, the security risk status information is information for characterizing the current risk status of the account. For example, when the security risk status information indicates that the account is in a higher risk state, for example, the first risk state, the second access data can only include information corresponding to the first risk state, for example, the user's nickname information, the user's Avatar information, etc. When the security risk status information indicates that the account is in a lower risk state, for example, the second risk status, the second access data can include information corresponding to the second risk status, for example, the user's payment information, the user's mobile phone number, or User's address information, etc. When judging the risk status of the account, you can consider whether the account is logged in at a trusted location or whether the account is logged in using a trusted device; the risk status of the account can be divided into areas such as high security risk, suspected risk status, and trusted status. Security risk status information can be generated by the login server. The account security risk status information included in the account context information can enable the data source server to further control the degree of openness of the data.

Based on the solution provided in the foregoing Embodiment 1, the key to the access control method of the user data provided by the present application is that the context information of the account is loaded in the account-initiated data access request, so that when the account uses the third-party system to access the data source, The account can be a secure account, and the initiated data access request is also a security request. It should be noted that the third-party system involved in the present application is an uncontrollable area, and the first server, the data source server, and the login server are available. Control area.

The following describes the function implemented by the application scenario in the application scenario in detail with reference to FIG. 6 :

Step A: The client initiates a login request.

In the above step A of the present application, the account is logged in to the client, and a login request is initiated to the login server. The client can be a software product, such as a software such as a Taobao client or a Tmall client, or a mobile terminal device or a computer device. The login server stores the account password information of the account and the complete context information of the account. Take Taobao's sellers to implement order management functions. For example, when using a third-party system that provides order management functions, Taobao sellers first need to log in to Taobao client, Taobao seller account to login server, such as Taobao server, initiate login request, complete Taobao seller. Login of the account.

Step B: The login server generates context information.

In the above step B of the present application, the context information is referred to as context information. The login server also generates complete context information based on the login request. The complete context information contains all kinds of account information specified. The login server may choose to return only one subset of the full context information to the client for practical reasons or for the amount of data transferred by the login server. As an example, the Taobao seller implements the order management function. The login server (for example, Taobao server) stores not only the user name and user password information of the Taobao seller, but also the online status and account of the account of the Taobao seller account. Offline status, online time of account, offline time of account, login time of account, login location of account, login device of account, record of account access user data, data privacy security level of account, common login device of account, account Common login location, account security status of the account, and account risk assessment of the account. Taobao server returns information to the seller account, Taobao The server calculates the complete context information of the generated account based on the information of the stored seller account.

Step C: The login server returns the context information to the client.

In the above step C of the present application, the order management function of the seller of Taobao is still taken as an example. After receiving the login request, the Taobao server generates complete context information, and returns one of the generated complete context information to the client. .

Step D: The client generates a data access request containing context information.

In the above step D of the present application, the client receives the context information returned by the login server. Each time an account triggers a third-party system, a data access request containing the context information is generated. As an example, Taobao's sellers implement order management functions. Since Taobao does not provide order management functions, Taobao provides an interface to enable authorized independent software providers to provide a third-party system that can provide order management functions. When the seller account of the Taobao website clicks on the order management platform provided by the third-party system, a data access request containing the context information of the seller account is generated, and the order management platform is given the authority to obtain the user data of the seller account. The user data of the seller account is stored in the data source server provided by Taobao.

Step E: The client sends a data access request to the first server.

Step F: The first server verifies whether the context information is carried in the data access request.

In the above step F of the present application, after receiving the data access request, the first server verifies whether the data access request carries at least content that appears to be context information. For example, the order management function of the seller of Taobao is still implemented. The data access request of the seller account received by the first server may be the punishment of the real Taobao seller by opening the order management platform, or may be a forged account. Pretending to be issued by the seller's account. The first server does not know in advance whether the originating account of the received data access request is legitimate. Then, only the account that receives the login server returning context information may contain context information in the data access request it sends. At this time, the first server first verifies whether the data access request includes context information to determine the originating account of the data access request.

Step G: The first server sends context information to the context information server.

In the above step F of the present application, when the first server verifies that the data access request carries the context information, the context information carried in the data access request is read, and the context information is sent to the context information server. The first server can complete the verification work of whether the context information is legal. The first server can also entrust the context information server to complete the verification work of whether the context information is legal. In this interaction diagram, the context information server completes the verification of whether the context information is legal. Still taking the order management function of the seller of Taobao. For example, after the first server verifies that the data access request contains the context information, the context information is read. Content and send the context information of the Taobao account to the context information server.

Step H: The context information server verifies the context information.

In the above step H of the present application, the context information server matches the received context information with the pre-existing local complete context information. If the matching is successful, the verification result is that the context information of the account is legal information. The complete context information pre-stored in the context information server is information sent by the login server and stored in the context information server. Taking the order management function of the seller of Taobao.com as an example, the context information server verifies the received context information. When the context information matches the complete context information in the pre-existing context information server, the context information server considers the context. Information is legal information. For a fake account impersonating a data access request issued by the seller account, even if it contains data that looks like context information, it cannot pass the verification of the context information server.

Step I: Return legal access identification information.

In the foregoing step I of the present application, when the context information server verifies that the context information passes, the legal access identification information is generated, and the legal access identification information is returned to the first server. Taking the order management function of the seller of Taobao as an example, after the context information server considers the context information to be legal information, the context information server generates a legal access identifier, indicating that the data access request is initiated by the real seller account and carried The context information is correct.

Step J: Allow sending data access requests to third party systems.

In the above step J of the present application, the first server receives the legal access identification information returned by the context information server, and allows the data access request to be sent to the third party system. The order management function of the seller of Taobao is still taken as an example. After receiving the legal access identification information, the first server stores the legal access identification information, and allows the data access request to be transparently transmitted to the order management platform.

Step K: Forward the data access request.

In the foregoing step K of the present application, after the third-party system receives the data access request sent by the first server, the third-party system forwards the data access request to the data source server, and the data access request is used to instruct the third-party system to request the data source. User data for legitimate accounts stored in. As an example, the Taobao seller implements the order management function. When the order management platform receives the data access request, the order management platform forwards the data access request to the data source server for requesting the data source server to read the data access. Request the data to be referred to. For example, the Taobao seller's order transaction amount, transaction object, etc. in the past month.

Step L: The data source server queries whether the legal access identifier information exists.

In the above step L of the present application, the legal access identification information of the account may be generated by the first server and stored in the first In a server, the context information server may also generate and store with the first server; the data source server accesses the first server to query whether the server has legal access identification information. For example, if Taobao's seller implements the order management function, if the data source server provided by Taobao does not verify the sent data access request and responds to each data access request, then it is difficult to guarantee when the third-party system is invaded. The security of user data stored in the data source server. Therefore, the data source server will perform the verification again. At this time, the main way of verification is to query whether there is legal access identification information.

Step M: The first server returns a legal access identifier information query result to the data source server.

Step N: When the data source server queries the legal access identifier information, determine that the data access request is a secure access request.

In the above step N of the present application, the data source server accesses the first server or the context information server to query whether there is legal access identification information of the account. For an account capable of querying the legal access identification information, the data source server determines that the data access request initiated by the account is a secure access request. Taking the order management function of the seller of Taobao.com as an example, when the data source server queries the first server to have the legal access identification information of the Taobao account, the Taobao account may be deemed to have actively sent a data access request, and the data access is performed. The context information included in the request is verified. In this case, the data source server further checks whether the context information is legal information. At this point, the data source server determines that the data access request is a secure access request.

Step O: The data source server returns data to be accessed by the data access request to the third party system.

In the above step O of the present application, after confirming that the data access request is a secure access request, the data source server may further determine whether the user is online. When it is determined that the user is online, the security privacy level or the security risk status that may be included in the data access request is obtained to determine the data content that can be returned to the third-party system. Still taking the order management function of the seller of Taobao. For example, the data source server returns the data requested by the data access request to the order management platform for determining the data access request for the secure access request.

In summary, the first embodiment provided by the present application can achieve the following technical effects:

1. Since the Context information carried in the data access request is a non-fixed value, an illegal hacker cannot steal, thereby avoiding the data leakage problem caused by the theft of some fixed value authorization token of the user.

2. In the application scenario where the illegal user B attempts to access the data of the authorized user A, since the Context information requires the account to log in to the client, the login server generates the context information of the account, because the illegal user B cannot use the legitimate user A at the gateway. The identity leaves the access record (the access record can be characterized by the generated legal access identifier information). Therefore, when the illegal user B attempts to access the data of the legitimate user A through the third-party system, the data source server verifies the context information, Since the access record of the legitimate user A is not queried, the system It can be assumed that the current account and the initiated data access request will be rejected by the data source.

3. In the scenario where the uncontrollable third-party system is maliciously controlled or maliciously operated by humans, although the hacker may obtain all the user lists maintained by the third-party system, or even the information authorized by the user, also because the Context information is not satisfied. The verification will be rejected by the data source.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present application is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present application. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Embodiment 2

According to an embodiment of the present application, a method embodiment of an access control method for user data is also provided. It should be noted that the steps shown in the flowchart of the drawing may be in a computer system such as a set of computer executable instructions. The steps shown and described may be performed in a different order than the ones described herein, although the logical order is shown in the flowchart.

The method embodiment provided by the second embodiment of the present application can still be executed in a mobile terminal, a computer terminal or the like. It should be noted that the method embodiment provided in Embodiment 2 can still be run on the computer terminal shown in FIG. 1.

In the above operating environment, the present application can also provide an access control method for user data as shown in FIG. 7. FIG. 7 is a schematic flowchart of a method for controlling access of user data according to Embodiment 2 of the present application. As shown in FIG. 7, an optional access control method for user data includes the following implementation steps:

Step S602: The client obtains context information of the account.

Step S604: The client sends an account-triggered data access request to the first server, where the data access request includes at least context information.

In the above step S602 of the present application, the account may be a legal account registered by the client. The client that is logged in to the legal account may not be limited to products such as Taobao and Tmall. The user may register the account on the client. After each user logs in to the client using the account, the user may initiate the data access request by using the client. .

It should be noted that the foregoing first server may be a gateway shown in FIG. 3, where the gateway is used to transparently transmit the data access request. In an optional solution, the first server may be a cloud load balancing server of Alibaba Cloud.

Step S606: The client receives the access data acquired by the first server according to the data access request, where the first server determines that the data access request includes the context information of the account, and/or if the context information of the account is verified. Allows sending data access requests to third-party systems, allowing third-party systems to access data sources based on data access requests.

The context information involved in the above step S606 of the present application is related to the activity status and activity information of the account, and is used to represent the authority of the account corresponding to the context information to the third party system to access the account user data. In the embodiment of the present application, the context information may include, but is not limited to, the online status of the account, the offline status of the account, the online time of the account, the offline time of the account, the login time of the account, the login location of the account, the login device of the account, and the account. Access to the record of user data, the data privacy level of the account, the common login device of the account, the common login location of the account, the account security status of the account, and the account risk assessment of the account.

The foregoing steps provided by the present application may be implemented to determine whether an account initiating the data access request is a legitimate account by checking whether the received data access request carries context information and/or context information of the account. Judging from the kind of information contained in the above context information, the context information is data having non-fixed values and the hacker cannot steal characteristics. Therefore, it is highly credible to verify whether the account is legal based on the context information. The solution of introducing the context checking mechanism in the present application can make the verification result of the account more accurate, and specifically, can effectively solve the problem that the user data is randomly accessed within the time allowed by the user authorization.

Since the context information of the account is included in the data access request, and/or the context information is legal information, the current account may be determined to be a secure account, and therefore, the first server (may be the gateway shown in FIG. 3) Passing the data access request initiated by the security account to the third-party system, and entering the third-party system to process the data access request, that is, the third-party system accesses the data source according to the received data access request, and requests the data of the user from the data source. .

Optionally, the third-party system may request to access the user data stored in the data source server by forwarding the data access request to the data source server, and then the data source server reads the user data according to the data access request. Return to a third-party system.

It can be seen from the above that, in the solution provided by the foregoing embodiment 2 of the present application, after the current account (which may be a legitimate account or a forged account impersonates the legitimate account) sends a data access request to the first server, the first server will receive each received A data access request is verified, that is, the first server determines whether the data access request carries the account context information, and/or whether the context information can be verified, and when the verification of the data access request passes, the first server The data access request is allowed to be sent to a third party system, and the third party system can access the data source according to the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

In the optional solution provided by the foregoing embodiment of the present application, after the client obtains the context information of the login account, the following implementation steps may be performed:

Step S6032: After the account is logged in to the client, a login request is initiated to the login server.

In the above step S6032 of the present application, the client may be a software product, such as a software such as a Taobao client or a Tmall client, or may be a mobile terminal device or a computer device. When the user logs in to the client using the account, the login request is initiated to the login server, and the login server calculates the complete context information corresponding to the account (ie, the complete context information), and the login server stores the account password information of the account and the above complete Contextual information. In a preferred solution, after the login server receives the login request of the account, it may first determine whether the information carried in the received login request matches the account information stored locally by the login server, and if the matching is determined, the account is allowed to log in. Generate complete context information and reject account login if there is no match.

Step S6034: The client receives the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request.

Through the above steps, the login server can return a subset of the complete context information to the client by extracting the necessary information in the complete context information. In the case that the returned context information can satisfy the requirement of the first server to verify whether the context information is carried in the data access request, and/or to verify whether the included context information is correct, the complete context information is returned to the client. A subset of methods can effectively reduce the amount of information sent by the login server to the client. In the case that a large number of users initiate a login request to the login server in a short period of time, this method can effectively save the system resources of the login server and reduce the data transmission burden of the login server.

The preferred steps provided in step S6032 to step S6034 in the above second embodiment of the present application are described. The implementation scheme is the same as the preferred scheme and the application scenario provided in step S2012 to step S2014 in the first embodiment, but is not limited to the solution provided in the first embodiment.

In an optional solution provided by the foregoing embodiment, after the account is logged in to the client in step S6032, the method may further include the following steps: the login server receives the login request, and generates complete context information of the account that initiates the login request, which is complete. One of the subsets of context information is returned to the client; and the full context information is sent to the first server and/or the context information server.

In an optional solution provided by the foregoing embodiment, after the client sends the account-triggered data access request to the first server, the method may further include the following implementation steps:

Step S6052: The first server receives an account initiated data access request.

Step S6054: The first server verifies whether the data access request carries the context information of the account, and/or checks the context information of the account.

Step S6056: The first server includes the context information of the account in determining the data access request, and/or allows the data access request to be sent to the third-party system if the context information of the account is verified, so that the third-party system accesses according to the data. Request access to the data source.

In another optional solution, the first server does not include the context information of the account in determining the data access request, or the first server sends the data access request to the third-party system if the context information verification of the account fails, or The first server prohibits sending a data access request to a third party system and issues an alarm message.

In the optional solution provided by the foregoing embodiment of the present application, the step S6054: the specific step of verifying the context information of the account includes:

Step S60541: After determining that the data access request carries the context information, the first server reads the context information carried in the data access request.

Step S60542: The first server matches the context information with the pre-stored complete context information, and if the matching is successful, determining that the context information of the account is legal information;

Step S60543: The first server generates legal access identification information of the account, where the legal access identification information is used to represent that the account that initiated the data access request is a legal account.

It should be noted that the preferred embodiment provided in step S60541 to step S60543 in the foregoing embodiment 2 of the present application is the same as the preferred solution and the application scenario provided in step S402 to step S406 in the first embodiment, but is not limited thereto. The solution provided in the first embodiment.

In the optional solution provided by the foregoing embodiment of the present application, the step S6054: the specific step of verifying the context information of the account includes:

Step S60545: After determining that the data access request carries the context information, the first server sends the context information to the context information server.

Step S60546: The first server receives the verification result of the context information server verification context information;

Step S60547: In the case that the verification result is that the context information of the account is legal information, the first server receives the legal access identifier information of the account generated by the context information server, where the legal access identifier information is used to represent the account of the initiated data access request. a legal account;

The context information server matches the context information with the pre-existing local complete context information. If the matching is successful, the verification result is that the context information of the account is legal information.

It should be noted that the preferred embodiment provided in step S60545 to step S60547 in the foregoing embodiment 2 of the present application is the same as the preferred solution and the application scenario provided in step S502 to step S506 in the first embodiment, but is not limited thereto. The solution provided in the first embodiment.

In the optional solution provided by the foregoing embodiment of the present application, after the step S6056: allowing the data access request to be sent to the third-party system, the following implementation steps may be further included:

Step S60572: The data source server receives the data access request forwarded by the third-party system;

Step S60574: The data source server accesses the first server or the context information server, and if the query obtains the legal access identifier information of the account, it determines that the data access request initiated by the legal account is a secure access request;

Step S60576: The data source server returns data to be accessed by the data access request to the third party system.

It should be noted that the preferred embodiment provided in step S60572 to step S60576 in the foregoing embodiment 2 of the present application is the same as the preferred solution and the application scenario provided in step S207 to step S209 in the first embodiment, but is not limited thereto. The solution provided in the first embodiment.

It should also be noted here that the context information (Context information) of the above account can determine whether the third party system can obtain and can obtain the user data of multiple high privilege levels. Among them, high-level data generally involves user privacy, such as user mobile phone number, home address, and even credit card information. Low-level data is generally not classified, such as user nickname, user avatar information, etc., and generally can be classified according to user privacy level. . Since the context information corresponding to the account can verify whether the data access request initiated by the client account is initiated by a legitimate user, if not, the third party system cannot obtain the user data, thus effectively preventing the third party system from being hacked or artificially The reason is that the user data is maliciously read and written, and the security of the user data is greatly improved.

In the optional solution provided by the foregoing embodiment, after determining that the account that initiates the data access request is a secure access account, the step may further include: implementing, by the data source server, whether the context information includes the online information of the account; When the context information contains the online information of the account, the data source server executes to the third party. The step in which the system returns the data to be accessed by the data access request.

In the solution of the present application, the context information may include online information of the account. When the account is detected by the technical means, the account online information is generated, and the account online information is added to the context information. For example, the mechanism for periodically transmitting the heartbeat packet to the client may be used to determine whether the account is online according to the message fed back by the client, and the step of determining whether the account is online may be performed by the login server. Wherein, when the context information includes account online information, it means that the current account is online, and at this time, the data source server performs data to be accessed by returning the data access request to the third-party system.

In the optional solution provided by the foregoing embodiment, when the context information further includes the security privacy level information of the account, the step of the data source server returning the data to be accessed by the data access request to the third-party system includes: the data source server according to the security The privacy level information generates corresponding first access data and returns the first access data to the third party system.

It should be noted that, in the foregoing steps of the present application, the security privacy level information is for different third-party systems, and may be opened to the third according to the degree of trust to the third-party system and the degree of authorization of the user to the third-party system. Identification information of user data with different privacy levels of the three-party system. For example, when the security privacy level information indicates that the data access request has a higher security level, for example, the first security level, the first access data may include information corresponding to the first security level, for example, the user's mailbox information, the user's mobile phone. a number, or a user's address information, etc.; when the security privacy level information indicates that the data access request has a lower security level, such as a second security level, the first access data may include information corresponding to the second security level, for example, User's nickname information, user's avatar information, etc.

In the optional solution provided by the foregoing embodiment, when the context information further includes the security risk status information of the account, the step of the data source server returning the data to be accessed by the data access request to the third-party system includes: the data source server security risk The status information generates corresponding second access data and returns the second access data to the third party system.

It should be noted here that in the above steps of the present application, the security risk status information is information used to represent the current risk status of the account. For example, when the security risk status information indicates that the account is in a higher risk state, for example, the first risk state, the second access data can only include information corresponding to the first risk state, for example, the user's nickname information, the user's avatar. Information, etc. When the security risk status information indicates that the account is in a lower risk state, for example, the second risk status, the second access data can include information corresponding to the second risk status, for example, the user's payment information, the user's mobile phone number, or User's address information, etc. When judging the risk status of the account, you can consider whether the account is logged in at a trusted location or whether the account is logged in using a trusted device; the risk status of the account can be divided into For example: high security risks, suspected risk status, trusted status, etc. Security risk status information can be generated by the login server. The account security risk status information included in the account context information can enable the data source server to further control the degree of openness of the data.

Based on the solution provided by the foregoing embodiment 2, the key to the access control method of the user data provided by the application is that the context information of the account is loaded in the account-initiated data access request, so that when the account uses the third-party system to access the data source, The account can be a secure account, and the initiated data access request is also a security request. It should be noted that the third-party system involved in the present application is an uncontrollable area, and the first server, the data source server, and the login server are available. Control area.

Embodiment 3

According to an embodiment of the present application, a method embodiment of an access control method for user data is also provided. It should be noted that the steps shown in the flowchart of the drawing may be in a computer system such as a set of computer executable instructions. The steps shown and described may be performed in a different order than the ones described herein, although the logical order is shown in the flowchart.

The method embodiments provided in Embodiment 3 of the present application can still be executed in a mobile terminal, a computer terminal or the like. It should be noted that the method embodiment provided in Embodiment 3 can still be run on the computer terminal shown in FIG. 1.

In the above operating environment, the present application can also provide an access control method for user data as shown in FIG. 8. FIG. 8 is a schematic flowchart of a method for controlling access of user data according to Embodiment 3 of the present application. As shown in FIG. 8, an optional access control method for user data includes the following implementation steps:

Step S702: The third-party system receives the data access request sent by the first server, where the data access request is a request initiated by the account that includes context information of the account.

Step S704: The third party system forwards the data access request to the data source server.

Step S706: The third-party system receives data to be accessed by the data access request returned by the data source server, wherein when the data source server determines, according to the context information included in the data access request, the account that initiates the data access request is a secure access account, and the data When the access request is a secure access request, the third-party system is allowed to access the data source based on the data access request.

As can be seen from the above, in the solution provided in the foregoing Embodiment 3 of the present application, after the current account (which may be a legitimate account or a fake account impersonates the legal account) sends a data access request to the first server, the first server will receive each received A data access request is verified, that is, the first server determines whether the data access request carries the account context information, and/or whether the context information can be verified, and when the verification of the data access request is passed, The first server allows the data access request to be sent to the third party system, and the third party system can access the data source according to the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

In the optional solution provided by the foregoing embodiment, before the third-party system receives the data access request sent by the first server, the method may further include the following steps: the first server determines the context of the account in the data access request. In the case where the information of the account is legal information, the legal access identification information of the account is generated, wherein the legal access identification information is used to represent the account of the initiated data access request as a legal account.

In the optional solution provided by the foregoing embodiment, before the step S702: the third-party system receives the data access request sent by the first server, the method may further include the following steps:

Step S7012: The first server verifies whether the data access request carries the context information of the account, and/or checks the context information of the account.

Step S7014: The first server includes the context information of the account in determining the data access request, and/or allows the data access request to be sent to the third-party system if the context information of the account is verified, so that the third-party system accesses according to the data. Request access to a data source;

Step S7016: The first server does not include the context information of the account in determining the data access request, and/or the first server still sends the data access request to the third party system, or the first case, if the context information verification of the account fails. The server prohibits sending data access requests to third-party systems and issues alarm messages.

In the optional solution provided by the foregoing embodiment, the data source server determines, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account, and the specific implementation steps of the data access request being a secure access request include: :

Step S7052: The data source server receives the data access request forwarded by the third-party system.

Step S7054: The data source server reads the context information carried in the data access request.

Step S7056: When the data source server verifies that the context information is legal information, it is determined that the account that initiates the data access request is a secure access account, and when the query obtains the account has the legal access identifier information, determining that the data access request is a secure access request.

In the optional solution provided by the foregoing embodiment of the present application, in step S702, the third-party system receives the first server. Before the data access request is sent, the method may further include the following steps: the first server forwards the received data access request to the third-party system, where the specific implementation step of sending the data access request to the first server includes: the account login client Afterwards, the login request is initiated to the login server; the client receives the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request; the client obtains the context information of the account; the client sends the An account-triggered data access request to the first server, wherein the data access request includes at least context information;

It should be noted that the preferred embodiment provided in the foregoing embodiment 3 of the present application is the same as the implementation and the application scenario provided in the first embodiment or the second embodiment, but is not limited to the first embodiment or the second embodiment. The solution provided.

Embodiment 4

According to an embodiment of the present application, an apparatus embodiment for implementing the foregoing method embodiments is also provided. The apparatus provided by the foregoing embodiment of the present application may be run on a computer terminal.

FIG. 9 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 4 of the present application.

As shown in FIG. 9 , the device includes: a receiving module 802, a check module 804, and a control module 806. The check module 804 further includes a first check unit 8042 and/or a second check unit 8044.

The receiving module 802 is configured to receive an account-initiated data access request, and the verification module includes a first check unit and/or a second check unit, where the first check unit is configured to verify the data. Whether the context information of the account is carried in the access request, the second check unit checks the context information of the account, and the control module is configured to allow the sending of the check if the check module passes the check The data access request to the third party system causes the third party system to access the data source in accordance with the data access request.

It can be seen from the above that, in the solution provided in Embodiment 4 of the present application, when a legitimate account or a forged account impersonates the legal account to send a data access request to the first server, the first server checks each data access request received. , that is, the first server determines whether the data access request carries the account context information, and/or whether the context information can pass the verification; when the verification of the data access request passes, the first server allows the data access request to be sent to A third-party system, and then a third-party system, can access the data source based on the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

It should be noted that the foregoing receiving module 802, the checking module 804, and the control module 806 correspond to steps S202 to S206 in the first embodiment, and the three modules are the same as the examples and application scenarios implemented by the corresponding steps. However, it is not limited to the contents disclosed in the first embodiment. It should be noted that the foregoing module may be implemented in the computer terminal 10 provided in the first embodiment as a part of the device, and may be implemented by software or by hardware.

Optionally, as shown in FIG. 10, the second check unit includes: a read subunit 902, a matching subunit 904, and a generating subunit 906.

The reading subunit is configured to read the context information carried in the data access request after determining that the context information is carried in the data access request, and the matching subunit is configured to use the context information Matching the pre-stored complete context information, if the matching is successful, determining that the context information of the account is legal information; and generating a sub-unit, configured to generate legal access identification information of the account, where the legal The access identification information is used to characterize the account initiating the data access request as a legitimate account.

It should be noted that the foregoing reading subunit 902, the matching subunit 904, and the generating subunit 906 correspond to the steps S402 to S406 in the first embodiment, and the examples and applications implemented by the three modules and corresponding steps. The scene is the same, but is not limited to the content disclosed in the first embodiment. It should be noted that the foregoing module may be implemented in the computer terminal 10 provided in the first embodiment as a part of the device, and may be implemented by software or by hardware.

Optionally, as shown in FIG. 11, the second check unit includes: a sending subunit 1002, a first receiving subunit 1004, and a second receiving subunit 1006.

The sending subunit is configured to send the context information to the context information server after determining that the context information is carried in the data access request, and the first receiving subunit is configured to receive the context information server to verify the a verification result of the context information, where the second receiving subunit is configured to receive the legal access identification information of the account generated by the context information server, if the verification result is that the context information of the account is legal information, The legal access identifier information is used to represent the account of the initiated data access request as a legal account; the context information server matches the context information with the pre-existing local complete context information, where If the matching is successful, the verification result is that the context information of the account is the legal information.

It should be noted that the foregoing sending subunit 1002, the first receiving subunit 1004 and the second receiving subunit 1006 correspond to steps S502 to S506 in the first embodiment, and the three modules are implemented by corresponding steps. The examples and application scenarios are the same, but are not limited to the contents disclosed in the above embodiment 1. It should be noted that the foregoing module may be implemented in the computer terminal 10 provided in the first embodiment as a part of the device, and may be implemented by software. It can also be implemented in hardware.

Optionally, the control module is further configured to send the data access request to the third-party system if the verification unit fails to pass the verification, or prohibit the sending the data access request to the third-party system And issue an alarm message.

The preferred embodiment provided by the foregoing embodiment 4 of the present application is the same as the implementation of the method embodiment and the application scenario provided by the first embodiment, but is not limited to the solution provided by the first embodiment.

Embodiment 5

According to an embodiment of the present application, an apparatus embodiment for implementing the foregoing method embodiments is also provided. The apparatus provided by the foregoing embodiment of the present application may be run on a computer terminal.

FIG. 12 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 5 of the present application.

As shown in FIG. 12, the apparatus includes: an obtaining module 1102, a transmitting module 1104, and a receiving module 1106.

The obtaining module is configured to obtain the context information of the account, and the sending module is configured to send the data access request triggered by the account to the first server, where the data access request includes at least the context information, and the receiving module uses Receiving access data acquired by the first server according to the data access request; wherein the first server determines that the data access request includes context information of the account, and/or in the account In the case where the context information is verified, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

It can be seen from the above that, in the solution provided by the fifth embodiment of the present application, when the legal account or the forged account pretends to be the legal account and the data access request is sent to the first server, the first server checks each data access request received. That is, the first server determines whether the data access request carries the account context information, and/or whether the context information can pass the verification; when the verification of the data access request passes, the first server allows the data access request to be sent to the first The three-way system, and thus the third-party system, can access the data source based on the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

It should be noted that the foregoing obtaining module 1102, the sending module 1104, and the receiving module 1106 correspond to steps S602 to S606 in the second embodiment, and the three modules are the same as the examples and application scenarios implemented by the corresponding steps, but It is not limited to the contents disclosed in the above second embodiment. It should be noted that the above module is used as one of the devices. The part can be run in the computer terminal 10 provided in the second embodiment, and can be implemented by software or by hardware.

It should be noted that the preferred embodiment provided in the foregoing Embodiment 5 of the present application is the same as the implementation and the application scenario provided in Embodiment 2, but is not limited to the solution provided in Embodiment 2.

Embodiment 6

According to an embodiment of the present application, an apparatus embodiment for implementing the foregoing method embodiments is also provided. The apparatus provided by the foregoing embodiment of the present application may be run on a computer terminal.

FIG. 13 is a schematic structural diagram of an access control apparatus for user data according to Embodiment 6 of the present application.

As shown in FIG. 13, the apparatus includes: a first receiving module 1202, a forwarding module 1204, and a second receiving module 1206.

The first receiving module is configured to receive a data access request sent by the first server, where the data access request is a request that is initiated by the account and includes context information of the account, and a forwarding module is configured to forward the a data access request to the data source server; a second receiving module, configured to receive data to be accessed by the data access request returned by the data source server, where the data source server is included in the data access request The context information determines that the account that initiates the data access request is a secure access account, and when the data access request is a secure access request, allows a third-party system to access the data source according to the data access request.

It can be seen from the above that, in the solution provided in Embodiment 6 of the present application, when a legitimate account or a forged account pretends to be a legitimate account to send a data access request to the first server, the first server checks each data access request received. , that is, the first server determines whether the data access request carries the account context information, and/or whether the context information can pass the verification; when the verification of the data access request passes, the first server allows the data access request to be sent to A third-party system, and then a third-party system, can access the data source based on the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

It should be noted that the first receiving module 1202, the forwarding module 1204, and the second receiving module 1206, corresponding to the steps S702 to S706 in the third embodiment, the examples and applications implemented by the three modules and corresponding steps. The scene is the same, but is not limited to the content disclosed in the third embodiment above. It should be noted that the foregoing module may be implemented in the computer terminal 10 provided in the third embodiment as a part of the device, and may be implemented by software or by using software. Hardware implementation.

The preferred embodiment provided by the foregoing embodiment 6 of the present application is the same as the optional solution and the application scenario provided by the third embodiment, but is not limited to the solution provided by the third embodiment.

Example 7

An access control system for user data is provided according to the embodiment of the present application. FIG. 14 is a schematic structural diagram of an access control system for user data according to Embodiment 7 of the present application.

As shown in Figure 14, the system includes:

The client terminal 141 is configured to initiate a data access request after the account is logged in;

The first server 143 is in communication with the client terminal 141, configured to transparently transmit the data access request after the authentication data access request includes the context information of the account, and/or the verification context information is the legal information;

The third-party system server 145 is in communication with the first server 143, and configured to receive a data access request transparently transmitted by the first server;

The data source server 147 is in communication with the third-party system server 145, and is configured to receive a data access request forwarded by the third-party system server, and determine, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account. When the data access request is a secure access request, the access data corresponding to the data access request is returned to the third-party system server.

The foregoing seventh embodiment of the present application provides a system solution, which can be implemented after the legal account is logged into the client 141, the legal account can send a data access request to the first server 143, and the first server 143 can receive the data access request. Checking, that is, the first server determines whether the data access request carries the account context information, and/or whether the context information can pass the verification. When the verification of the data access request passes, the first server allows the data access. The request is sent to a third-party system, and the third-party system can access the data source based on the data access request. In the above solution, only the data access request initiated by the legal account can pass the verification, and the data access request initiated by the malicious account impersonating the legitimate account does not carry the account context information or the context information carried in the content. Can't pass the check. Through the foregoing solution, the data access request initiated by the legal account with the access right is allowed to be sent to the third-party system, which solves the problem that the prior art uses the third-party system to access the data source, and the security of the account that initiates the access is poor. A technical problem that leads to poor security of data source data.

Optionally, the foregoing system may further include: a login server and a context information server.

When the account is logged in to the client, the login request is initiated to the login server, and the login server calculates the complete context information corresponding to the account (ie, the complete context information), and the login server stores the request. The account password information of the account and the above complete context information, or the context information is sent to the context information server for storage.

The preferred embodiments provided in the foregoing seventh embodiment of the present application are the same as the implementations and application scenarios provided in the first embodiment to the third embodiment, but are not limited to the solutions provided in the first embodiment to the third embodiment.

Example eight

Embodiments of the present application may provide a computer terminal, which may be any one of computer terminal groups. Optionally, in this embodiment, the foregoing computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of the plurality of network devices of the computer network.

In this embodiment, the computer terminal may execute the program code of the following steps in the vulnerability detection method of the application: the first server receives an account-initiated data access request; and the first server verifies whether the data access request carries the Determining context information of the account, and/or verifying context information of the account; the first server includes context information of the account in determining the data access request, and/or in a context of the account In the case where the information verification passes, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, FIG. 15 is a structural block diagram of a computer terminal according to an embodiment of the present application. As shown in FIG. 15, the computer terminal A may include one or more (only one shown in the figure) processor 51, memory 53, and transmission device 55.

The memory 53 can be used to store software programs and modules, such as the security vulnerability detection method and the program instruction/module corresponding to the device in the embodiment of the present application, and the processor 51 executes by executing the software program and the module stored in the memory 53. Various functional applications and data processing, that is, detection methods for implementing the aforementioned system vulnerability attacks. Memory 53 may include high speed random access memory and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 53 may further include memory remotely located relative to processor 51, which may be connected to terminal A via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 55 described above is for receiving or transmitting data via a network. Specific examples of the above network may include a wired network and a wireless network. In one example, the transmission device 55 includes a Network Interface Controller (NIC) that can be connected to other network devices and routers via a network cable to communicate with the Internet or a local area network. In one example, the transmission device 55 is a radio frequency (RF) module. It is used to communicate wirelessly with the Internet.

Specifically, the memory 53 is configured to store preset action conditions and information of the preset rights user, and an application.

The processor 51 may call the information and the application stored by the memory 53 through the transmission device to perform the steps of: the first server receiving an account-initiated data access request; the first server verifying whether the data access request carries the Context information of the account, and/or verification of context information of the account; the first server includes context information of the account in determining the data access request, and/or context information in the account In case the verification is passed, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, the processor 51 may further execute the following steps: after the account is logged in to the client, the login request is initiated to the login server; the client receives the context information returned by the login server, where The context information is a subset of the complete context information generated by the login server according to the login request; the client sends the data access request carrying the context information to the first server.

Optionally, the processor 51 may further execute the following step: the first server reads the context carried in the data access request after determining that the data access request carries the context information The first server matches the context information with the pre-stored complete context information, and if the matching is successful, determining that the context information of the account is legal information; the first server generates the account Legal access identification information, wherein the legal access identification information is used to represent that the account that initiated the data access request is a legitimate account.

Optionally, the processor 51 may further execute the following step: the first server sends the context information to the context information server after determining that the data access request carries the context information; Receiving, by the server, the verification result of the context information by the context information server; if the verification result is that the context information of the account is legal information, the first server receives the location generated by the context information server The legal access identifier information of the account, wherein the legal access identifier information is used to represent the account of the initiated data access request as a legal account; wherein the context information server associates the context information with a pre-existing local The complete context information is matched, and if the matching is successful, the verification result is that the context information of the account is the legal information.

Optionally, the processor 51 may further execute the following steps: the data source server receives the data access request forwarded by the third-party system; and the data source server accesses the first server or the context information a server, if the query obtains the legal access identifier information of the account, determining the legal account The initiated data access request is a secure access request; the data source server returns data to be accessed by the data access request to the third party system.

Optionally, the processor 51 may further execute the following program code: the data source server verifies whether the context information includes online information of the account; and when the context information includes online information of the account The data source server performs the step of returning data to be accessed by the data access request to the third party system.

Optionally, the processor 51 may further execute the following program code: the data source server generates corresponding first access data according to the security privacy level information, and returns the first access data to the first Tripartite system.

Optionally, the processor 51 may further execute the following program code: the data source server generates corresponding second access data according to the security risk status information, and returns the second access data to the first Tripartite system.

Optionally, the processor 51 may further execute the following program code: the first server does not include the context information of the account in determining the data access request, or the context information verification of the account fails. In case, the first server sends the data access request to the third-party system, or the first server prohibits sending the data access request to the third-party system, and sends an alarm message.

With the embodiment of the present application, an access control scheme for user data is provided. Receiving, by the first server, the data access request initiated by the account, verifying whether the data access request carries the context information of the account, and/or verifying the context information of the account, and including the account in determining the data access request by using the first server Context information, and/or in the case that the context information of the account is verified, the data access request is allowed to be sent to the third-party system, so that the third-party system accesses the data source according to the data access request, thereby achieving the Before the three-party system receives the data access, it can identify the technical effect of whether the account that sends the data access request is a legitimate account, thereby solving the problem of the prior art in the process of the user accessing the data source by using the third-party system. Poor performance, resulting in poor technical security of data source data.

A person skilled in the art can understand that the structure shown in FIG. 15 is only for illustration, and the computer terminal can also be a smart phone (such as an Android mobile phone, an iOS mobile phone, etc.), a tablet computer, an applause computer, and a mobile Internet device (Mobile Internet Devices, MID). ), PAD and other terminal devices. Fig. 15 does not limit the structure of the above electronic device. For example, computer terminal A may also include more or fewer components (such as a network interface, display device, etc.) than shown in FIG. 15, or have a different configuration than that shown in FIG.

One of ordinary skill in the art will appreciate that all or part of the various steps of the above embodiments are accessible. The program is executed by instructing the terminal device-related hardware, and the program may be stored in a computer readable storage medium, and the storage medium may include: a flash disk, a read-only memory (ROM), a random access device ( Random Access Memory (RAM), disk or CD.

Example nine

Embodiments of the present application may provide a computer terminal, which may be any one of computer terminal groups. Optionally, in this embodiment, the foregoing computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of the plurality of network devices of the computer network.

In this embodiment, the computer terminal may execute the program code of the following steps in the vulnerability detection method of the application: the client obtains the context information of the account; the client sends the data access request triggered by the account to the first server, where the data access The request includes at least context information; the client receives the access data obtained by the first server according to the data access request; wherein the first server determines that the data access request includes the context information of the account, and/or the context information of the account is verified In this case, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, still a structural block diagram of a computer terminal provided with reference to FIG. As shown in FIG. 15, the computer terminal A may include one or more (only one shown in the figure) processor 51, memory 53, and transmission device 55.

The memory 53 can be used to store software programs and modules, such as the security vulnerability detection method and the program instruction/module corresponding to the device in the embodiment of the present application, and the processor 51 executes by executing the software program and the module stored in the memory 53. Various functional applications and data processing, that is, detection methods for implementing the aforementioned system vulnerability attacks. Memory 53 may include high speed random access memory and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 53 may further include memory remotely located relative to processor 51, which may be connected to terminal A via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 55 described above is for receiving or transmitting data via a network. Specific examples of the above network may include a wired network and a wireless network. In one example, the transmission device 55 includes a Network Interface Controller (NIC) that can be connected to other network devices and routers via a network cable to communicate with the Internet or a local area network. In one example, the transmission device 55 is a Radio Frequency (RF) module for communicating with the Internet wirelessly.

Specifically, the memory 53 is configured to store preset action conditions and information of the preset rights user, and an application.

The processor 51 can call the information and the application stored by the memory 53 through the transmission device to perform the following steps: the client obtains the context information of the account; the client sends the account-triggered data access request to the first server, where the data access request Include at least context information; the client receives the access data obtained by the first server according to the data access request; wherein the first server determines that the data access request includes the context information of the account, and/or the context information of the account is verified In this case, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, the processor 51 may further execute the following program code: after the account is logged in to the client, the login request is initiated to the login server; the client receives the context information returned by the login server, where the context information is the login server according to the login request. A subset of the generated complete context information.

Optionally, the processor 51 may further execute the following program code: the login server receives the login request, generates complete context information of the account that initiates the login request, and returns a subset of the complete context information to the client; The complete context information is sent to the first server and/or the context information server.

Optionally, the processor 51 may further execute the following program code: the first server receives an account initiated data access request; the first server verifies whether the data access request carries the context information of the account, and/or the context of the account The information is verified; the first server includes the context information of the account in determining the data access request, and/or allows the data access request to be sent to the third party system if the context information of the account is verified, so that the third party system A data access request accesses the data source.

Optionally, the processor 51 may further execute the following program code: after determining that the data access request carries the context information, the first server reads the context information carried in the data access request; the first server stores the context information and the pre-stored The complete context information is matched, and if the matching is successful, the context information of the account is determined to be legal information; the first server generates legal access identification information of the account, wherein the legal access identification information is used to represent the account that initiates the data access request is Legal account.

Optionally, the processor 51 may further execute the following program code: after determining that the data access request carries the context information, the first server sends the context information to the context information server; and the first server receives the context information server to verify the context information. The verification result; in the case that the verification result is that the context information of the account is legal information, the first server receives the legal access identification information of the account generated by the context information server, wherein the legal access identification information is used to represent the account of the initiated data access request. Is a legal account; wherein the context information server matches the context information with the pre-existing local complete context information, in case the match is successful Next, the verification result is that the context information of the account is legal information.

Optionally, the processor 51 may further execute the following program code: the data source server receives the data access request forwarded by the third-party system; the data source server accesses the first server or the context information server, and if the query obtains the legal access identifier of the account The information determines that the data access request initiated by the legitimate account is a secure access request; the data source server returns the data to be accessed by the data access request to the third party system.

Optionally, the processor 51 may further execute the following program code: the data source server verifies whether the context information of the account is included in the context information; and when the context information includes the online information of the account, the data source server executes to the third-party system. The step of returning the data to be accessed by the data access request.

Optionally, the processor 51 may further execute the following program code: the data source server generates the corresponding first access data according to the security privacy level information, and returns the first access data to the third-party system.

Optionally, the processor 51 may further execute the following program code: the data source server security risk status information generates the corresponding second access data, and returns the second access data to the third-party system.

Optionally, the processor 51 may further execute the following program code: the first server does not include the context information of the account in determining the data access request, or the first server sends the context information verification failure of the account. The data access request is sent to the third party system, or the first server prohibits sending the data access request to the third party system and issues an alarm message.

With the embodiment of the present application, an access control scheme for user data is provided. Receiving, by the first server, the data access request initiated by the account, verifying whether the data access request carries the context information of the account, and/or verifying the context information of the account, and including the account in determining the data access request by using the first server Context information, and/or in the case that the context information of the account is verified, the data access request is allowed to be sent to the third-party system, so that the third-party system accesses the data source according to the data access request, thereby achieving the Before the three-party system receives the data access, it can identify the technical effect of whether the account that sends the data access request is a legitimate account, thereby solving the problem of the prior art in the process of the user accessing the data source by using the third-party system. Poor performance, resulting in poor technical security of data source data.

A person skilled in the art can understand that the structure shown in FIG. 15 is only for illustration, and the computer terminal can also be a smart phone (such as an Android mobile phone, an iOS mobile phone, etc.), a tablet computer, an applause computer, and a mobile Internet device (Mobile Internet Devices, MID). ), PAD and other terminal devices. Fig. 15 does not limit the structure of the above electronic device. For example, computer terminal A may also include more or fewer components (such as a network interface, display device, etc.) than shown in FIG. 15, or have a different configuration than that shown in FIG.

One of ordinary skill in the art will appreciate that all or part of the various steps of the above embodiments are accessible. The program is executed by instructing the terminal device-related hardware, and the program may be stored in a computer readable storage medium, and the storage medium may include: a flash disk, a read-only memory (ROM), a random access device ( Random Access Memory (RAM), disk or CD.

Example ten

Embodiments of the present application may provide a computer terminal, which may be any one of computer terminal groups. Optionally, in this embodiment, the foregoing computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of the plurality of network devices of the computer network.

In this embodiment, the computer terminal may execute the program code of the following steps in the vulnerability detection method of the application: the third-party system receives the data access request sent by the first server, where the data access request is an account initiated by the account. a request for context information; the third party system forwards the data access request to the data source server; the third party system receives the data to be accessed by the data access request returned by the data source server, wherein the data source server receives the context information included in the data access request When the account that initiates the data access request is determined to be a secure access account, and the data access request is a secure access request, the third-party system is allowed to access the data source according to the data access request.

Optionally, still a structural block diagram of a computer terminal provided with reference to FIG. As shown in FIG. 15, the computer terminal A may include one or more (only one shown in the figure) processor 51, memory 53, and transmission device 55.

The memory 53 can be used to store software programs and modules, such as the security vulnerability detection method and the program instruction/module corresponding to the device in the embodiment of the present application, and the processor 51 executes by executing the software program and the module stored in the memory 53. Various functional applications and data processing, that is, detection methods for implementing the aforementioned system vulnerability attacks. Memory 53 may include high speed random access memory and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 53 may further include memory remotely located relative to processor 51, which may be connected to terminal A via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 55 described above is for receiving or transmitting data via a network. Specific examples of the above network may include a wired network and a wireless network. In one example, the transmission device 55 includes a Network Interface Controller (NIC) that can be connected to other network devices and routers via a network cable to communicate with the Internet or a local area network. In one example, the transmission device 55 is a radio frequency (RF) module. It is used to communicate wirelessly with the Internet.

Specifically, the memory 53 is configured to store preset action conditions and information of the preset rights user, and an application.

The processor 51 can call the information and the application stored by the memory 53 through the transmission device to perform the following steps: the third party system receives the data access request sent by the first server, wherein the data access request is an account initiated by the account. a request for context information; the third party system forwards the data access request to the data source server; the third party system receives the data to be accessed by the data access request returned by the data source server, wherein, when the data source server according to the context information included in the data access request, When the account that initiates the data access request is determined to be a secure access account, and the data access request is a secure access request, the third party system is allowed to access the data source according to the data access request.

Optionally, the processor 51 may further execute the following program code: when the first server determines that the data access request carries the context information of the account, and the context information of the account is legal information, the legal access identifier of the account is generated. Information, wherein the legal access identification information is used to represent the account of the initiated data access request as a legitimate account.

Optionally, the processor 51 may further execute the following program code: the first server verifies whether the data access request carries the context information of the account, and/or checks the context information of the account; the first server determines the data. The access request includes context information of the account, and/or if the context information of the account is verified, the data access request is allowed to be sent to the third-party system, so that the third-party system accesses the data source according to the data access request; the first server is Determining that the data access request does not include context information of the account, and/or in the case that the context information verification of the account fails, the first server still sends the data access request to the third party system, or the first server prohibits sending the data access request to Third-party system and issue an alarm message.

Optionally, the processor 51 may further execute the following steps: the data source server receives the data access request forwarded by the third-party system; the data source server reads the context information carried in the data access request; and the data source server verifies the context. When the information is legal information, the account that initiates the data access request is determined to be a secure access account, and when the query obtains the account with the legal access identifier information, the data access request is determined to be a secure access request.

Optionally, the processor 51 may further execute the following program code: the first server forwards the received data access request to the third-party system, where the specific implementation step of sending the data access request to the first server includes: After logging in to the client, the login request is initiated to the login server; the client receives the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request; the client obtains the context information of the account; The client sends an account-triggered data access request to the first service. Server, wherein the data access request includes at least context information.

With the embodiment of the present application, an access control scheme for user data is provided. Receiving, by the first server, the data access request initiated by the account, verifying whether the data access request carries the context information of the account, and/or verifying the context information of the account, and including the account in determining the data access request by using the first server Context information, and/or in the case that the context information of the account is verified, the data access request is allowed to be sent to the third-party system, so that the third-party system accesses the data source according to the data access request, thereby achieving the Before the three-party system receives the data access, it can identify the technical effect of whether the account that sends the data access request is a legitimate account, thereby solving the problem of the prior art in the process of the user accessing the data source by using the third-party system. Poor performance, resulting in poor technical security of data source data.

A person skilled in the art can understand that the structure shown in FIG. 15 is only for illustration, and the computer terminal can also be a smart phone (such as an Android mobile phone, an iOS mobile phone, etc.), a tablet computer, an applause computer, and a mobile Internet device (Mobile Internet Devices, MID). ), PAD and other terminal devices. Fig. 15 does not limit the structure of the above electronic device. For example, computer terminal 15 may also include more or fewer components (such as a network interface, display device, etc.) than shown in FIG. 15, or have a different configuration than that shown in FIG.

A person of ordinary skill in the art may understand that all or part of the steps of the foregoing embodiments may be completed by a program to instruct terminal device related hardware, and the program may be stored in a computer readable storage medium, and the storage medium may be Including: flash disk, read-only memory (ROM), random access memory (RAM), disk or optical disk.

Embodiment 11

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the foregoing storage medium may be used to save the program code executed by the access control method of the user data provided in the first embodiment.

Optionally, in this embodiment, the foregoing storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: the first server receives an account initiated data access request; the first server verifies whether the data access request is carried Context information of the account, and/or verification of context information of the account; the first server includes context information of the account in determining the data access request, and/or in the account In the case where the context information is verified, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, the storage medium is further configured to store program code for performing the following steps: the account login guest After the client sends a login request to the login server, the client receives the context information returned by the login server, where the context information is in the complete context information generated by the login server according to the login request. a subset; the client sends the data access request carrying the context information to the first server.

Optionally, the storage medium is further configured to store program code for performing the following steps: after the first server carries the context information in the determining the data access request, reading the data access request Context information: the first server matches the context information with the pre-stored complete context information, and if the matching is successful, determining that the context information of the account is legal information; the first server generates The legal access identifier information of the account, wherein the legal access identifier information is used to represent that the account that initiates the data access request is a legal account.

Optionally, the storage medium is further configured to store program code for performing the following steps: after determining that the context information is carried in the data access request, the first server sends the context information to a context information server; Receiving, by the first server, the verification result of the context information by the context information server; if the verification result is that the context information of the account is legal information, the first server receives the context information server Generating the legal access identifier information of the account, wherein the legal access identifier information is used to represent the account of the initiated data access request as a legal account; wherein the context information server compares the context information with The local context information is pre-existing for matching. If the matching is successful, the verification result is that the context information of the account is the legal information.

Optionally, the storage medium is further configured to store program code for performing: the data source server receiving the data access request forwarded by the third party system; the data source server accessing the first server or Determining, by the context information server, the legal access identifier information of the account, determining that the data access request initiated by the legal account is a secure access request; and the data source server returns to the third-party system The data to be accessed by the data access request.

Optionally, the storage medium is further configured to store program code for performing: the data source server verifying whether the context information includes online information of the account; when the context information includes the account The online source server performs the step of returning data to be accessed by the data access request to the third party system.

Optionally, the storage medium is further configured to store program code for: generating, by the data source server, corresponding first access data according to the security privacy level information, and returning the first access data to The third party system.

Optionally, the storage medium is further configured to store program code for performing the following steps: the data source server generates the corresponding second access data by the security risk status information, and returns the second access data to the A third-party system.

Optionally, the storage medium is further configured to store program code for performing: the first server does not include context information of the account in determining the data access request, or context information of the account If the verification fails, the first server sends the data access request to the third-party system, or the first server prohibits sending the data access request to the third-party system, and sends an alarm message.

It should be noted here that any one of the above computer terminal groups can establish a communication relationship with the website server and the scanner, and the scanner can scan the value command of the web application executed by php on the computer terminal.

Example twelve

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the foregoing storage medium may be used to save the program code executed by the access control method of the user data provided in the second embodiment.

Optionally, in this embodiment, the foregoing storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: the client obtains context information of the account; the client sends an account-triggered data access request to the first server, where the data The access request includes at least context information; the client receives the access data acquired by the first server according to the data access request; wherein the first server determines that the data access request includes context information of the account, and/or checks the context information of the account. In the case of passing, the data access request is allowed to be sent to the third party system, so that the third party system accesses the data source according to the data access request.

Optionally, the storage medium is further configured to store program code for performing the following steps: after the account is logged in to the client, the login request is initiated to the login server; the client receives the context information returned by the login server, where the context information is the login server A subset of the complete context information generated from the login request.

Optionally, the storage medium is further configured to store program code for performing the steps of: the login server receiving the login request, generating complete context information of the account initiating the login request, and returning a subset of the complete context information to the client And send the complete context information to the first server and/or the context information server.

Optionally, the storage medium is further configured to store program code for performing the following steps: the first server receives an account initiated data access request; the first server verifies whether the data access request carries context information of the account, and/or The context information of the account is verified; the first server includes the context information of the account in determining the data access request, and/or allows the data access request to be sent to the third party if the context information of the account is verified. The system enables third-party systems to access data sources based on data access requests.

Optionally, the storage medium is further configured to store program code for performing the following steps: after determining that the data access request carries the context information, the first server reads the context information carried in the data access request; the first server sets the context The information is matched with the pre-stored complete context information. If the matching is successful, the context information of the account is determined to be legal information; the first server generates legal access identification information of the account, wherein the legal access identification information is used to represent the originating data access request. The account is a legal account.

Optionally, the storage medium is further configured to store program code for performing the following steps: the first server sends the context information to the context information server after determining that the data access request carries the context information; the first server receives the context information server verification The verification result of the context information; in the case that the verification result is that the context information of the account is legal information, the first server receives the legal access identification information of the account generated by the context information server, wherein the legal access identification information is used to represent the initiated data access. The requested account is a legal account; wherein the context information server matches the context information with the pre-existing local complete context information. If the matching is successful, the verification result is that the context information of the account is legal information.

Optionally, the storage medium is further configured to store program code for performing the following steps: the data source server receives the data access request forwarded by the third party system; the data source server accesses the first server or the context information server, if the query obtains the account If the identification information is legally accessed, it is determined that the data access request initiated by the legal account is a secure access request; and the data source server returns the data to be accessed by the data access request to the third-party system.

Optionally, the storage medium is further configured to store program code for performing the following steps: the data source server verifies whether the context information of the account is included in the context information; and when the context information includes the online information of the account, the data source server performs the The step in which the third-party system returns the data to be accessed by the data access request.

Optionally, the storage medium is further configured to store program code for performing the step of: the data source server generating the corresponding first access data based on the security privacy level information and returning the first access data to the third party system.

Optionally, the storage medium is further configured to store program code for performing the steps of: the data source server security risk status information generating the corresponding second access data and returning the second access data to the third party system.

Optionally, the storage medium is further configured to store program code for performing the following steps: the first server does not include context information of the account in determining the data access request, or in the case that the context information verification of the account fails, A server sends a data access request to a third party system, or the first server prohibits sending a data access request to a third party system and issues an alarm message.

It should be noted here that any one of the above computer terminal groups can establish a communication relationship with the website server and the scanner, and the scanner can scan the value command of the web application executed by php on the computer terminal.

Example thirteen

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the foregoing storage medium may be used to save the program code executed by the access control method of the user data provided in Embodiment 3 above.

Optionally, in this embodiment, the foregoing storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: the third party system receives the data access request sent by the first server, wherein the data access request is initiated by the account. a request for context information of the account; the third party system forwards the data access request to the data source server; the third party system receives data to be accessed by the data access request returned by the data source server, wherein the data source server according to the context included in the data access request The information is determined to be a secure access account when the data access request is initiated, and the third party system is allowed to access the data source according to the data access request when the data access request is a secure access request.

Optionally, the storage medium is further configured to store program code for performing the following steps: in case the first server determines that the data access request carries the context information of the account, and the context information of the account is legal information, the account is generated The legal access identification information, wherein the legal access identification information is used to represent the account of the initiated data access request as a legitimate account.

Optionally, the storage medium is further configured to store program code for performing the following steps: the first server verifies whether the data access request carries context information of the account, and/or verifies the context information of the account; the first server Include context information of the account in determining the data access request, and/or, if the context information of the account is verified, allowing the data access request to be sent to the third party system, so that the third party system accesses the data source according to the data access request; The server does not include the context information of the account in determining the data access request, and/or the first server still sends the data access request to the third party system if the context information verification of the account fails, or the first server prohibits sending the data. Access requests to third-party systems and issue alert messages.

Optionally, the storage medium is further configured to store program code for performing the following steps: the data source server receives the data access request forwarded by the third party system; the data source server reads the context information carried in the data access request; When the server verifies that the context information is legal information, it determines that the account that initiated the data access request is a secure access account, and determines that the data access request is a secure access request when the query obtains the account with the legal access identifier information.

Optionally, the storage medium is further configured to store program code for performing the following steps: the first server forwards the received data access request to the third party system, wherein the specific implementation step of sending the data access request to the first server Including: after the account is logged in to the client, a login request is initiated to the login server; the client receives the login service The context information returned by the server, wherein the context information is a subset of the complete context information generated by the login server according to the login request; the client obtains the context information of the account; and the client sends the data access request triggered by the account to the first server, wherein The data access request includes at least context information.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

In the above-mentioned embodiments of the present application, the descriptions of the various embodiments are different, and the parts that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

In the several embodiments provided by the present application, it should be understood that the disclosed client may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like. .

The above description is only a preferred embodiment of the present application, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present application. It should be considered as the scope of protection of this application.

Claims (23)

An access control method for user data, comprising: The first server receives an account initiated data access request; Determining, by the first server, whether the data access request carries context information of the account, and/or verifying context information of the account; The first server includes context information of the account in determining the data access request, and/or, if the context information of the account is verified, allowing the data access request to be sent to a third-party system, The third party system is caused to access the data source according to the data access request. The method of claim 1, wherein before the first server receives the account initiated data access request, the method further comprises: After logging in to the client, the account initiates a login request to the login server; The client receives the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request; The client sends the data access request carrying the context information to the first server. The method according to claim 2, wherein verifying the context information of the account comprises: After the first server carries the context information, the first server reads the context information carried in the data access request; The first server matches the context information with the pre-stored complete context information, and if the matching is successful, determining that the context information of the account is legal information; The first server generates legal access identifier information of the account, where the legal access identifier information is used to represent that the account that initiates the data access request is a legal account. The method according to claim 2, wherein verifying the context information of the account comprises: After the first server carries the context information in the data access request, the first server sends the context information to the context information server; Receiving, by the first server, the verification result of the context information server to verify the context information; When the verification result is that the context information of the account is legal information, the first server receives the legal access identifier information of the account generated by the context information server, where the legal access identifier information is used. The account for characterizing the initiated data access request is a legitimate account; The context information server matches the context information with the complete context information pre-existing locally. If the matching is successful, the verification result is that the context information of the account is the legal information. The method according to claim 3 or 4, wherein after the data access request is allowed to be sent to the third party system, the method further comprises: Receiving, by the data source server, the data access request forwarded by the third-party system; The data source server accesses the first server or the context information server, and if the query obtains the legal access identifier information of the account, determining that the data access request initiated by the legal account is a secure access request; The data source server returns data to be accessed by the data access request to the third party system. The method according to claim 5, wherein after determining that the account initiating the data access request is a secure access account, the method further comprises: The data source server verifies whether the online information of the account is included in the context information; When the context information includes online information of the account, the data source server performs the step of returning data to be accessed by the data access request to the third party system. The method according to claim 5, wherein when the context information further includes security privacy level information of the account, the data source server returns to the third party system that the data access request is to be accessed. The step of data includes: the data source server generating corresponding first access data according to the security privacy level information, and returning the first access data to the third party system. The method according to claim 5, wherein when the context information further includes security risk status information of the account, the data source server returns to the third-party system that the data access request is to be accessed. The step of data includes: the security risk status information of the data source server generates corresponding second access data, and returns the second access data to the third party system. The method according to claim 1, wherein the first server does not include context information of the account in determining the data access request, or if the context information verification of the account fails, The first server sends the data access request to the third party system, or the first server prohibits sending the data access request to the third party system, and sends an alarm message. An access control method for user data, comprising: The client obtains context information of the account; Sending, by the client, the data access request triggered by the account to a first server, where the data access The request includes at least the context information; Receiving, by the client, access data acquired by the first server according to the data access request; Wherein the first server determines that the data access request includes context information of the account, and/or allows the data access request to be sent to a third party if the context information of the account is verified to pass The system causes the third party system to access the data source in accordance with the data access request. The method according to claim 10, wherein the client obtains context information of the login account, including: After logging in to the client, the account initiates a login request to the login server; The client receives the context information returned by the login server, wherein the context information is a subset of the complete context information generated by the login server according to the login request. An access control method for user data, comprising: Receiving, by the third party system, a data access request sent by the first server, where the data access request is a request initiated by the account that includes context information of the account; Transmitting, by the third party system, the data access request to a data source server; Receiving, by the third party system, data to be accessed by the data access request returned by the data source server, When the data source server determines, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account, and the data access request is a secure access request, The third party system is allowed to access the data source in accordance with the data access request. The method according to claim 12, wherein before the third-party system receives the data access request sent by the first server, the method further includes: And when the first server determines that the data access request carries the context information of the account, and the context information of the account is legal information, generating legal access identifier information of the account, where the legal The access identification information is used to characterize the account of the initiated data access request as a legitimate account. The method according to claim 13, wherein the data source server determines, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account, and The data access request for the secure access request includes: Receiving, by the data source server, the data access request forwarded by the third-party system; The data source server reads the context information carried in the data access request; When the data source server verifies that the context information is legal information, determining that the account that initiates the data access request is a secure access account, and when the query obtains that the account has the legal access identifier information, Determining that the data access request is the secure access request. The method according to claim 12, wherein before the third-party system receives the data access request sent by the first server, the method further includes: Determining, by the first server, whether the data access request carries context information of the account, and/or verifying context information of the account; The first server includes context information of the account in determining the data access request, and/or, if the context information of the account is verified, allowing the data access request to be sent to a third-party system, Causing the third party system to access the data source according to the data access request; The first server does not include the context information of the account in determining the data access request, and/or the first server still sends the data access if the context information verification of the account fails. Requesting to the third party system, or the first server prohibits sending the data access request to the third party system and issuing an alarm message. An access control device for user data, comprising: a receiving module, configured to receive an account-initiated data access request; a verification module, comprising a first verification unit and/or a second verification unit, wherein the first verification unit is configured to verify whether the data access request carries context information of the account, and the second The verification unit checks the context information of the account; And a control module, configured to allow the data access request to be sent to the third-party system if the verification module passes the verification, so that the third-party system accesses the data source according to the data access request. The apparatus according to claim 16, wherein said second verification unit comprises: a reading subunit, configured to read the context information carried in the data access request after determining that the context information is carried in the data access request; a matching subunit, configured to match the context information with pre-stored complete context information, and if the matching is successful, determining that the context information of the account is legal information; And generating a sub-unit, configured to generate legal access identifier information of the account, where the legal access identifier information is used to represent that the account that initiates the data access request is a legal account. The apparatus according to claim 16, wherein said second verification unit comprises: a sending subunit, configured to send the context information to the context information server after determining that the context information is carried in the data access request; a first receiving subunit, configured to receive the verification result that the context information server verifies the context information fruit; a second receiving subunit, configured to receive legal access identification information of the account generated by the context information server, where the verification result is that the context information of the account is legal information, where the legal access The identifier information is used to represent the account of the initiated data access request as a legal account; the context information server matches the context information with pre-existing local complete context information, if the matching is successful, the The verification result is that the context information of the account is the legal information. The apparatus according to claim 16, wherein the control module is further configured to send the data access request to the third-party system or disable sending the check if the verification module fails to pass the verification A data access request is sent to the third party system and an alarm message is issued. An access control device for user data, comprising: An obtaining module, configured to obtain context information of an account; a sending module, configured to send the data access request triggered by the account to the first server, where the data access request includes at least the context information; a receiving module, configured to receive access data acquired by the first server according to the data access request; Wherein the first server determines that the data access request includes context information of the account, and/or allows the data access request to be sent to a third party if the context information of the account is verified to pass The system causes the third party system to access the data source in accordance with the data access request. The device according to claim 20, wherein the obtaining module comprises: a sending unit, configured to initiate a login request to the login server; And a receiving unit, configured to receive the context information returned by the login server, where the context information is a subset of the complete context information generated by the login server according to the login request. An access control device for user data, comprising: a first receiving module, configured to receive a data access request sent by the first server, where the data access request is a request initiated by an account that includes context information of the account; a forwarding module, configured to forward the data access request to a data source server; a second receiving module, configured to receive data to be accessed by the data access request returned by the data source server, When the data source server determines, according to the context information included in the data access request, that the account that initiates the data access request is a secure access account, and the data access request is a secure access request, A third party system is allowed to access the data source based on the data access request. An access control system for user data, comprising: a client terminal, configured to initiate a data access request after the account is logged in; a first server, configured to communicate with the client terminal, configured to transparently transmit the data access request after verifying that the data access request includes context information of the account, and/or verifying that the context information is legal information ; a third-party system server, configured to communicate with the first server, to receive the data access request transparently transmitted by the first server; a data source server, configured to communicate with the third-party system server, to receive the data access request forwarded by the third-party system server, and determine to initiate the according to the context information included in the data access request The account of the data access request is a secure access account, and when the data access request is a secure access request, the access data corresponding to the data access request is returned to the third-party system server.

Images