Web page access processing method, device, storage medium, and program product
By generating login files and combining portrait data for trust testing, the degree of trust of the target device is identified, and the issue of account theft behavior that cannot be recognized frequently in the target account in the prior art is solved, which improves the recognition rate of account theft behavior and the security of user accounts .
Patent Information
- Application Number
- CN202210233962.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-10
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2042-03-10
AI Technical Summary
When the existing network service platform recognizes theft, it cannot effectively identify the frequent login of the target account, which makes the account theft difficult to identify, affecting the security of the user account and the normal operation of the network services.
By receiving the login request from the target device, generating a login file and obtaining characteristic data, and performing trust tests based on the image data of the account. If the target device is a non-trusted device, human-computer interaction verification is performed to determine whether to respond to the login request and use the unique device ID Weighted average calculations are performed with historical login data to determine the level of trust of the device.
It improves the recognition rate of account theft behavior during web page access, enhances the security of user accounts, and ensures the normal operation of the network service platform.
Smart Images

Figure CN114448645B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security technology. Specifically, the present application relates to a method, device, computer device, computer-readable storage medium and computer program product for processing web page access. Background Art
[0002] With the development of Internet services, the scale of users of network service platforms has been greatly increased. In order to facilitate the provision of exclusive services to users and the retention of user information, many network service platforms have adopted the account registration method. However, in order to achieve certain purposes, some account thefts have gradually emerged. In order to prevent the account thefts from damaging the interests of users, network service platforms will take some measures to identify the account thefts of user accounts. Currently, the identification is generally achieved by identifying the login geographical location.
[0003] When solving the problem of account theft, some of the thefts come from web page access. The login location of the account theft is often displayed or leaked to the user's regular login location, and the corresponding account theft violations are carried out. Especially on the live broadcast platform, when the user account is stolen, it will be used to steal and broadcast pornographic content and other illegal and illegal activities, which will cause trouble to the normal activities of users on the network service platform and greatly affect the normal web page access operation service of the network service platform. Summary of the invention
[0004] The embodiments of the present application provide a method, device, computer device, computer-readable storage medium and computer program product for processing web page access, which are used to solve the technical problem that the existing web page access operation service is affected by the phenomenon of account theft.
[0005] According to a first aspect of an embodiment of the present application, a method for processing web page access is provided, the method comprising the following steps:
[0006] Receiving a login request for a target account initiated through a web page, and generating a login file for a target device that initiated the login request;
[0007] Obtaining the portrait data of the target account, and obtaining characteristic data for trust testing from the login file;
[0008] When the target device is determined to be an untrusted device based on the portrait data and the feature data, a human-computer interaction verification operation is performed to determine whether to respond to the login request.
[0009] In an optional embodiment of one aspect, the step of receiving a login request for a target account initiated through a web page and generating a login file for a target device that initiated the request includes:
[0010] The target account is detected when the target device logs in for the first time, the target device ID is obtained, and a prefix is added to the target device ID to form a unique device ID of the target device.
[0011] In an optional embodiment of one aspect, the characteristic data includes a first unique device ID;
[0012] The step of determining that the target device is an untrusted device according to the portrait data and the feature data comprises:
[0013] The first unique device ID is matched with the second unique device ID of the historical login device of the portrait data. If the match is unsuccessful, the target device is an abnormal login device, and the abnormal login device is determined to be an untrusted device.
[0014] In an optional embodiment of one aspect, the characteristic data further includes login IP and login time;
[0015] The step of determining that the target device is an untrusted device according to the portrait data and the feature data comprises:
[0016] Obtain the current login IP and login time of the target device, and match them with the frequently logged-in locations and frequently logged-in time periods in the corresponding target account's portrait data;
[0017] Obtaining a score for each of the feature data according to the matching result, and performing a weighted average calculation on the scores of all the login feature data;
[0018] When the result of the weighted average calculation does not meet a preset detection value, the target device is determined to be an untrusted device.
[0019] In an optional embodiment of one aspect, the step of obtaining the portrait data of the target account includes:
[0020] Collect the login files within the preset time period, obtain the characteristic data of each historical login request, and form a historical message queue;
[0021] The historical message queue is cleaned to obtain the portrait data of the target account.
[0022] In an optional embodiment of one aspect, the step of cleaning and obtaining the portrait data of the target account according to the historical message queue includes:
[0023] The login location and login time of each historical login are obtained from the portrait data to form a corresponding login location-time distribution graph; wherein the value of the login location and login time of each login is represented by a numerical point in the location-time distribution graph;
[0024] Based on the distribution of the numerical points in the location-time distribution graph, the range of the frequently logged-in locations and frequently logged-in times of the target account in historical logins is determined.
[0025] In an optional embodiment of one aspect, the method for processing web page access further includes:
[0026] Obtaining a unique device ID of the untrusted device;
[0027] Based on the unique device ID of the untrusted device, obtain an associated user account that has logged in using the untrusted device;
[0028] Acquire characteristic data of corresponding historical login requests of each associated user account to form a historical message queue;
[0029] Confirm whether the most recent login location and / or login time of each associated user account corresponds to a frequently logged-in location and / or frequently logged-in time; wherein the associated user account is another user account that has been logged in by the untrusted device;
[0030] If not, the corresponding associated user account performs a temporary disabling operation.
[0031] According to another aspect of an embodiment of the present application, a device for processing web page access is provided, including:
[0032] A login file generation module, configured to receive a login request for a target account initiated via a web page, and generate a login file for a target device that initiates the login request;
[0033] A device trust test module, used to obtain the portrait data of the target account and obtain characteristic data for trust testing from the login file;
[0034] The login request verification module is used to perform a human-computer interaction verification operation to determine whether to respond to the login request when the target device is determined to be an untrusted device based on the portrait data and the feature data.
[0035] According to another aspect of an embodiment of the present application, a computer device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to perform the steps of any of the aforementioned methods for processing web page access.
[0036] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored, characterized in that when the computer program is executed by a processor, the steps of the method for processing web page access described in any one of the above are performed.
[0037] According to another aspect of an embodiment of the present application, a computer program product is provided, including a computer program, characterized in that when the computer program is executed by a processor, the steps of the method for processing web page access described in any one of the above are performed.
[0038] The beneficial effects of the technical solution provided by the embodiment of the present application are:
[0039] The processing scheme for web page access provided by the present application is that when the server receives a login request for a target account sent by a target device through a web page and forms a corresponding login file, characteristic data is obtained from the login file. Determine whether the target device is an untrusted device based on the characteristic data and the portrait data of the target account. When it is determined that the target device is an untrusted device, determine whether to respond to the login request of the target device based on the result of the confirmation. Based on the technical scheme provided by the present application, the technical problem that the original means of identifying theft behavior based on the login geographic location cannot identify theft behavior in the target account's frequent login location is overcome, thereby improving the recognition rate of theft behavior in web page access, contributing to the security level of user accounts, and ensuring the normal operation of the network service platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in describing the embodiments of the present application.
[0041] Figure 1 A flowchart of a method for processing web page access provided by an embodiment disclosed in the present application;
[0042] Figure 2 A diagram showing a verification interface for a login request on a live broadcast platform provided in an embodiment disclosed in this application;
[0043] Figure 3 A login location-time distribution diagram provided for the embodiments disclosed in this application;
[0044] Figure 4 A schematic diagram of the structure of a web page access processing device provided in an embodiment disclosed in the present application;
[0045] Figure 5 A schematic diagram of the structure of another web page access processing device provided by the embodiment disclosed in the present application;
[0046] Figure 6 A schematic diagram of the structure of a computer device for processing web page access provided in an embodiment disclosed in the present application. DETAILED DESCRIPTION
[0047] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.
[0048] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the presented features, information, data, steps, operations, but do not exclude the implementation as other features, information, data, steps, operations, elements, components and / or combinations thereof supported by the technical field. It should be understood that when we say that an element is "connected" or "coupled" to another element, the one element may be directly connected or coupled to the other element, or it may refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein indicates at least one of the items defined by the term, for example, "A and / or B" indicates that it is implemented as "A", or is implemented as "A", or is implemented as "A and B".
[0049] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0050] In the existing network service platform services, in addition to using applications for access, in order to achieve a better experience of network services, especially using web pages for login and access, such as in fixed places such as residences or offices. However, with the background of the network service platform's strengthened management of user accounts, some account thefts have appeared on the network service platform in order to achieve illegal purposes. The account theft phenomenon usually obtains user account and user login information through collection or network crawling, and uses the obtained information to perform illegal operations. What's more, in order to avoid the existing means of identifying account theft by using the login geographic location, web pages are accessed based on the frequently logged-in locations displayed or leaked when the user account is normally logged in, thereby posing new challenges to the network service platform's identification of account theft.
[0051] In the example where the user account of the current live broadcast webpage is stolen and used to commit illegal acts, the hacker can steal the account by collecting, grabbing or stealing the user's account's frequent login locations, and then commit illegal acts such as stealing, broadcasting pornographic content, or sending barrage content in the live broadcast room that disrupts the host's live broadcast, etc.
[0052] Figure 1A flowchart of a method for processing web page access provided by an embodiment disclosed in the present application.
[0053] In order to solve the above-mentioned technical problems, the present application provides a method for processing web page access.
[0054] refer to Figure 1 , the method comprises at least the following steps:
[0055] S110, receiving a login request for a target account initiated through a web page, and generating a login file for a target device that initiated the login request;
[0056] S120, obtaining the portrait data of the target account, and obtaining characteristic data for trust testing from the login file;
[0057] S140. When it is determined that the target device is an untrusted device based on the portrait data and the feature data, a human-computer interaction verification operation is performed to determine whether to respond to the login request.
[0058] The embodiment corresponding to the above steps S110-S140 may occur between a server and a terminal device that currently issues a login request. A communication connection is established between the server and the terminal device, and data interaction can be achieved according to instructions or response instructions. In the embodiment corresponding to the above steps, the execution subject is the server. The following is a detailed description of how the above steps are executed between the server and the terminal device.
[0059] The terminal device can use a browser to send a login request instruction to the network service platform using a user account of a specific network service platform. In this embodiment, the user account is set as the target account, and the terminal device that sends the login request is the target device. In the subsequent processing execution process, it is determined whether the target device is an untrusted device for the target account. The above-mentioned login request instruction can be input by controlling the terminal device, or can be input according to the login program setting that pre-acquires and carries the user account of the target account.
[0060] The target device sends a login request to the server according to the login request instruction. In this embodiment, the target device can input the login link of the network service platform through the browser according to the login request instruction, so that the browser interface jumps to the login page of the network service platform, and inputs the account information of the target account into the account control of the login page, and sends a login request to the network service platform for the target account, so that the target device can enter the login page corresponding to the login URL of the network service platform according to the response message fed back by the server.
[0061] After receiving the login request, the server obtains the target device ID according to the login request and generates a login file, wherein the login file carries the target device ID.
[0062] In this embodiment, the server feeds back the login file of the target site from the network service platform to the target device. The target device extracts information including the target device ID and the cookie setting data established under the domain name of the above-mentioned input login link from the received login file, and according to the cookie setting data, the target device carries the cookie established under the domain name of the above-mentioned input login link in its login interface by default. Continuing with the above-mentioned embodiment, the cookie setting data includes the login URL of the network service platform requested to log in. Based on the target device ID and cookie setting data carried in the login file, the target device can re-initiate the target device ID corresponding to the current login request for the target account through the web page, so as to subsequently confirm whether the target device is an untrusted device.
[0063] In addition to feeding back the target device the login file of the target site of the network service platform, the server also records in the login file characteristic data that can determine whether the target device is an untrusted device. Based on the characteristic data, the server can perform a trust test on the target device that sends a login request to the target account.
[0064] The server obtains the login history portrait data of the target account based on the historical login records of the target account. The portrait data includes the historical records formed by at least one type of data formed by the target account at each historical login request, and / or the processed data obtained after further data processing of the historical records. In addition, the portrait data can also reflect the attribute information, historical login track and other information of the target account. For example, in a live broadcast platform, it can be obtained through the target account whether the corresponding registered user is a host user or an audience user, the geographical track and time track of the user's historical login, etc.
[0065] When the server determines that the target device is an untrusted device based on the above-mentioned portrait data and feature data, it further performs a human-computer interaction verification operation. The specific verification operation can be confirmed by the server based on the verification result obtained by the verification operation to confirm whether to respond to the login request issued by the target device. If the target device is an untrusted device according to the verification result, the login request currently issued by the target device will not be responded to; otherwise, the login request will be responded to so that the target device can log in and access the target account.
[0066] In this embodiment, the verification operation of human-computer interaction can be that the server obtains the user number corresponding to the target account according to the verification result of the untrusted device, and sends the verification information of the current login request to the terminal device using the user number, and determines whether to respond to the login request based on the detection result of whether the user confirms the verification information. If an operation to confirm the verification information is detected, the login request is responded to when the confirmation information is correct; if no operation to confirm the verification information is detected or the confirmation information is wrong, the login request is prohibited from being executed.
[0067] Figure 2 This is a diagram showing the verification interface for a login request on a live broadcast platform provided in an embodiment disclosed in this application.
[0068] refer to Figure 2 , continuing to use the above-mentioned embodiment of the live broadcast platform, the above-mentioned human-computer interaction verification operation can be that according to the login request, the server sends the verification information to the terminal device of the user number registered by the target account, and also pushes the submission control of the verification information to the operation interface of the target device that issued the login request. By detecting the matching between the verification information and the verification information sent to the terminal device of the user number within the set time, it is determined whether to respond to the login request.
[0069] According to the above analysis, the processing method for web page access provided by the present application, when the server receives a login request for a target account sent by a target device through a web page and forms a corresponding login file, obtains feature data from the login file. Determine whether the target device is an untrusted device based on the feature data and the portrait data of the target account. When it is determined that the target device is an untrusted device, determine whether to respond to the login request of the target device based on the result of the confirmation. Based on the technical solution provided by the present application, the technical problem that the original means of identifying theft behavior based on the login geographic location cannot identify theft behavior in the target account's frequent login location is overcome, thereby improving the recognition rate of theft behavior in web page access, contributing to the security level of user accounts, and ensuring the normal operation of the network service platform.
[0070] Based on the above-mentioned embodiment, the step of generating a login file for the target device initiating the request in step S120 includes:
[0071] The target account is detected when the target device logs in for the first time, the target device ID is obtained, and a prefix is added to the target device ID to form a unique device ID of the target device.
[0072] In this embodiment, the server obtains the target device ID from the login file carrying the target device. The server can determine whether the target device is the first login for the target account from the historical login record of the target account corresponding to the login request based on the target device ID. If so, the target device ID is obtained and a prefix is added to it to obtain the unique device ID of the target device for the target account.
[0073] The prefix can be added according to the preset setting. For example: In this embodiment, according to the situation of logging in through a web page, the prefix is represented by "w", and the corresponding unique device ID is: w_482599900584255488, and "482599900584255488" is the target device ID of the target device for the first login of the target account. Based on the prefix "w", other login methods other than the web page, such as applications, can be distinguished.
[0074] In this embodiment, the target device ID can generate a globally unique ID for the target device through a snowflake algorithm. The snowflake algorithm is used to obtain the time frame in which the target device logs into the target account, as well as the device information of the target device, and the globally unique ID is formed according to the pre-set rules. In addition, the globally unique ID of the target device ID can also be obtained by other methods such as database auto-increment and UUID.
[0075] The unique device ID obtained in the above embodiment can be used to detect whether the target device is a non-trusted test. The characteristic data includes the first unique device ID. That is, the login method, login IP, and device information of the target device when the target account first logs in to the target device can be obtained based on the first unique device ID. Among them, the login IP is an Internet protocol address that can reflect the login geographic location when the terminal device issues a login request.
[0076] On this basis, determining that the target device is an untrusted device according to the portrait data and the feature data in the above step S140 includes:
[0077] The first unique device ID is matched with the second unique device ID of the historical login device of the portrait data. If the match is unsuccessful, the target device is an abnormal login device, and the abnormal login device is determined to be an untrusted device.
[0078] The portrait data records the historical login information of the target account, including the terminal device ID and historical login IP of the historical login; it may also include statistical data of the historical login information, such as the frequency of occurrence of the historical login IP corresponding to each terminal device. According to the statistical data of the frequency of occurrence of the historical login IP, the common login location of the corresponding target account can be obtained. If the login IP of the current login obtained by parsing the first unique device ID is matched with the historical login IP in the second unique device ID of the portrait data or the common login location obtained by statistics of the frequency of occurrence of the historical login IP. If the match fails, the target device is confirmed as an unusual login device, and the unusual login device is determined to be an untrusted device. In this embodiment, the common login location can be confirmed according to the frequency of occurrence of the second unique device ID of the corresponding target account, and the common login location can be represented by the login IP that issued the login request in the historical login record.
[0079] Before determining that the non-permanent login device is an untrusted device, the non-permanent login device may also be labeled. Based on the labeling of the non-permanent login device, the server directly confirms the corresponding target device as an untrusted device. Alternatively, when it is determined that the target device is a non-permanent login device, it is confirmed whether the current target device is an untrusted device based on the type of the logged-in web page. For example, the type of the logged-in web page is a service page of a government service outlet, and the historical logins corresponding to the portrait data of the target account may be at other government service outlets or addresses. Therefore, for the current login web page confirmed as a service page of a government service outlet, it is normal for the target account to change different terminal devices to log in at different login times. At this time, the current target device will not be treated as an untrusted device.
[0080] The characteristic data involved in the above embodiments may further include login IP and login time.
[0081] On this basis, the step of determining that the target device is an untrusted device according to the portrait data and the feature data in step S140 includes:
[0082] Obtain the current login IP and login time of the target device, and match them with the frequently logged-in locations and frequently logged-in time periods in the corresponding target account's portrait data;
[0083] Obtaining a score for each of the feature data according to the matching result, and performing a weighted average calculation on the scores of all the login feature data;
[0084] When the result of the weighted average calculation does not meet a preset detection value, the target device is determined to be an untrusted device.
[0085] In this embodiment, the target device's current login data, including the target device's login IP and login time, are matched item by item with the corresponding target account's profile data's frequently logged-in locations and frequently logged-in times, and each feature data item is scored based on the matching result.
[0086] For the login IP in the feature data, it can reflect the specific login location of the target device, such as Room E, Street D, District C, City B, Province A. For example, the score range for the specific login location is 0-10 points. If the specific login location of the current login is consistent with the specific location of the frequent login in the portrait data, the highest score is 10 points.
[0087] If the specific login location of the current login is inconsistent with the specific location of the frequently logged-in place in the portrait data, the corresponding score ratio is set according to the geographical level corresponding to each geographical information in the specific location. For example, the specific login location mentioned above includes 5 geographical levels, namely province, city, district, street and house number. The levels are arranged from high to low according to the size of the corresponding geographical range, and the geographical levels from high to low are: province, city, district, street and house number. The higher the geographical level, the greater the score ratio. In this embodiment, the score ratios of province, city, district, street and house number are: 4, 3, 2, 1, 0.
[0088] If the specific login location of the current login is compared with the specific location of the frequent login in the portrait data, the corresponding score is deducted according to different geographical levels to obtain the score corresponding to the specific login location of the current login. For example, if the specific login location of the current login is Room E1, D1 Street, C1 District, B City, Province A, then the corresponding score is 7 points. Based on this score, the specific login location of the target device can be reflected in the form of data, which is more convenient to provide a data basis for trust testing.
[0089] In addition, for the login IP in the feature data, a score value can be preset for each area on the map. Specifically, on the map with regional score settings, confirm the login IP to obtain the location corresponding to the current login address of the target device, and obtain the score corresponding to the login IP currently logged in by the target device.
[0090] For the login time in the feature data, the login time of the target device is divided into time periods according to the similarity of the time periods corresponding to the user's general living habits. The specific login time is scored according to the similarity with the living habits of the usual login time.
[0091] For example, the target account's usual login time is 19:40PM, and according to general living habits, this time is generally the time period for study and entertainment after meals. According to general living habits, the time period for study and entertainment after meals is generally between 19-22PM. If the specific login time of the target device is 21PM, the corresponding score can get the highest score of 10. If it is beyond the time range of 19-22PM, the corresponding score is determined according to the specific login time of the target device and the time interval between it.
[0092] After obtaining each feature data currently logged in by the target device, the weighted ratio of each feature data can be determined according to the type corresponding to the logged in web page.
[0093] The total score obtained by the weighted average is compared with a preset detection value for the type corresponding to the webpage, and when the total score does not meet the preset detection value, the target device is determined to be an untrusted device. The preset detection value can be a numerical value or a range of preset detection values.
[0094] In order to clearly explain how to determine whether the target device is an untrusted device, the above-mentioned live broadcast platform implementation example is continued to further explain the implementation of the solution in different situations.
[0095] In the case where the webpage is a webpage of a live broadcast platform, the weighted ratio of the login time will be higher than the weighted ratio of the login IP, such as 6:4. The specific scores corresponding to the current login time and login IP of the target device can be obtained according to the above specific examples or other methods, and the total score corresponding to the current login of the target device can be obtained according to the weighted ratio of the type corresponding to the login webpage.
[0096] Furthermore, the embodiment of the live broadcast platform described above is continued, and the weighted ratio of the characteristic data can also be based on the type of the live broadcast room and / or the live broadcast history data. For example, the type of live broadcast room A is domestic tourism, and the target account is the anchor account. Since the anchor usually needs to switch to different live broadcast scenes, in this embodiment, the weighted ratio of the login time is much higher than that of the login IP.
[0097] If the target account is a viewer account, its historical login information is obtained based on its portrait data, and the geographical location range corresponding to its login IP is determined based on its historical login information. For example, for office workers, the geographical location range corresponding to the login IP of the viewer account is basically in the office area or the address of their own residence, that is, its historical login address is relatively stable. In this case, the weighted ratio of the login IP of the target device can be increased to be higher than the login time, so that the total score corresponding to the current login of the target device can more easily determine whether the target device is an untrusted device.
[0098] If the type of the live broadcast room B is knowledge sharing, and the target account is a live broadcast account, since the historical login IP obtained from the portrait information of the live broadcast account is usually stable in one place, the weighted ratio of the login IP is much higher than the login time. When the login IP can match the historical login IP more, the corresponding sub-item score of the login IP is low, which affects the final total score and cannot meet the preset detection value, making it easier for the server to determine that the target device is an untrusted device.
[0099] In the above embodiment, the portrait data is obtained by the operation of obtaining the portrait data of the target account in step S120, and this operation may further include:
[0100] Collecting login files within a preset historical time period, obtaining the characteristic data of each login request, and forming a historical message queue;
[0101] The historical message queue is cleaned to obtain the portrait data of the target account.
[0102] In the server, for each login request received for the target account, a corresponding login file is generated, and characteristic data is obtained from the generated login file. The collected characteristic data can be stored item by item to form a historical message queue based on the historical preset time period of the target account.
[0103] The sub-items of the characteristic data collected above at least include the sub-items required for statistics of the formed portrait data, so as to form statistics of the sub-items required for statistics of the portrait data in the historical message queue.
[0104] After obtaining the historical message queue, according to the statistical requirements of the sub-item content of the target account's portrait data, or the pre-set sub-item statistics, the feature data corresponding to each login that does not meet the pre-set sub-item content is cleaned. The feature data corresponding to the pre-set sub-item content that failed to be collected in the historical message queue can also be deleted as a whole to avoid the waste of data computing resources due to the increase in data volume in subsequent trust tests.
[0105] For the above step: according to the historical message queue, data cleaning to obtain the portrait data of the target account may further include:
[0106] The login location and login time of each historical login are obtained from the historical message queue to form a login location-time distribution graph; wherein the value of the login location and login time of each login is represented by a numerical point in the location-time distribution graph;
[0107] Based on the density of the numerical points in the location-time distribution graph, the range of the frequently logged-in locations and frequently logged-in times of the target account in historical logins is determined.
[0108] Figure 3 A login location-time distribution diagram provided for the embodiments disclosed in this application.
[0109] refer to Figure 3 In this embodiment, the login time score and the login location score are used as the horizontal axis and the vertical axis of the login location-time distribution graph respectively. The numerical values of the scores obtained for the login location and login time of the characteristic data corresponding to each historical login are recorded in the form of points on the login location-time distribution graph to obtain a login portrait of the target account.
[0110] In the login portrait in the location-time distribution graph, the range of the target account's frequent login locations and login times in historical logins is determined based on the distribution of multiple data points representing the scores of the corresponding historical login locations and login times.
[0111] The distribution may include the density of data points, or at least one of the contents in the closed loop formed by the connection of multiple data points or the connection. Moreover, the concentrated area of multiple data points can be obtained according to the distribution. The frequently logged-in locations and frequently logged-in times corresponding to the target account in the historical logins are directly obtained from the concentrated area reflected by the multiple data points of the location-time distribution diagram. If the login IP and login time corresponding to the current login are both within the range of the frequently logged-in locations and frequently logged-in times reflected on the location-time distribution diagram, the target device of the current login target account is a trusted device; otherwise, it is a non-trusted device.
[0112] like Figure 3 In the diagram, a closed loop H formed by multiple data points concentrated in a certain area of the distribution graph is used as the basis for the common login location and common login time corresponding to the target account in the historical login. In this embodiment, the geometric center point is obtained from the closed loop H, and the login location and login time corresponding to the data point corresponding to the historical record closest to the geometric center point are used as the common login location and common login time.
[0113] In the above implementation, if it is determined that the target device is an untrusted device, a unique device ID of the untrusted device is obtained.
[0114] Based on the unique device ID of the untrusted device, the method for processing web page access provided by the present application further includes:
[0115] Based on the unique device ID of the untrusted device, obtain an associated user account that has logged in using the untrusted device;
[0116] Acquire characteristic data of corresponding historical login requests of each associated user account to form a historical message queue;
[0117] Confirm whether the most recent login location and / or login time of each associated user account corresponds to a frequently logged-in location and / or frequently logged-in time; wherein the associated user account is another user account that has been logged in by the untrusted device;
[0118] If not, the corresponding associated user account performs a temporary disabling operation.
[0119] In this embodiment, other user accounts involved in the historical login records of the untrusted device are obtained based on the unique device ID of the untrusted device, and the records of the other user accounts are obtained from the login file generated by the login request sent from the target device. In this embodiment, the other user account is defined as: the associated user account when the target device is an untrusted device.
[0120] Each associated user account generates a feature data each time it logs into the target device, and the feature data generated for an associated user account forms a corresponding historical message queue. Each historical message queue includes: the login location and / or login time generated for the same associated user account logging into the target device.
[0121] Obtain from the historical message queue whether the corresponding target account's most recent login location and / or login time on the target device corresponds to the frequently logged-in location and / or login time, and determine whether the frequently logged-in location and / or login time are the frequently logged-in locations and / or login times that can be reflected by the portrait data of the target account.
[0122] If not, the associated user account is confirmed as an untrusted account, a temporary disabling operation is performed on the associated user account, and the target device is confirmed as an untrusted device.
[0123] In the above process, the sub-items of the profile data statistics can be determined in combination with the type of web page logged in by the associated user account. For example, if the web page is a network service web page of a government service outlet, then the weighted proportion corresponding to the login location is small, or even unnecessary to consider. At this time, the login time is mainly used as one of the main considerations for the profile data, and the associated user account is tested for trust. If the login time exceeds the normal government service time, the associated user account can be directly confirmed as an untrusted account, and the target device can be confirmed as an untrusted device.
[0124] Figure 4 A schematic diagram of the structure of a web page access processing device provided in an embodiment disclosed in the present application.
[0125] The present application embodiment provides a processing device for web page access, such as Figure 4 As shown, the web page access processing device 200 may include:
[0126] A login file generating module 210, configured to receive a login request for a target account initiated via a web page, and generate a login file for a target device that initiated the login request;
[0127] The device trust test module 220 is used to obtain the portrait data of the target account and obtain the characteristic data used for trust testing from the login file;
[0128] The login request verification module 230 is used to perform a human-computer interaction verification operation to determine whether to respond to the login request when the target device is determined to be an untrusted device based on the portrait data and the feature data.
[0129] The web page access processing device 200 of this embodiment can execute the web page access processing method shown in the above embodiments of the present application. The implementation principle is similar and will not be repeated here.
[0130] The processing device 200 for web page access provided in the present application, when the server receives a login request for a target account sent by a target device through a web page and forms a corresponding login file, obtains feature data from the login file. Determine whether the target device is an untrusted device based on the feature data and the portrait data of the target account. When it is determined that the target device is an untrusted device, determine whether to respond to the login request of the target device based on the result of the confirmation. Based on the technical solution provided in the present application, the technical problem that the original means of identifying theft behavior based on the login geographic location cannot identify theft behavior in the target account's frequent login location is overcome, thereby improving the recognition rate of theft behavior in web page access, contributing to the security level of user accounts, and ensuring the normal operation of the network service platform.
[0131] The login file generation module 210 is further used to detect that the target account is logging into the target device for the first time, obtain the target device ID, and add a prefix to the target device ID to form a unique device ID of the target device.
[0132] The characteristic data includes a first unique device ID and a login request verification module 230, and is also used to match the first unique device ID with the second unique device ID of the historical login device of the portrait data. If the match is unsuccessful, the target device is an abnormal login device, and the abnormal login device is determined to be an untrusted device.
[0133] The characteristic data also includes a login IP and a login time. The login request verification module 230 is further used to obtain the current login IP and login time of the target device, and match them with the frequently logged-in locations and frequently logged-in time periods in the portrait data of the corresponding target account;
[0134] Obtaining a score for each of the feature data according to the matching result, and performing a weighted average calculation on the scores of all the login feature data;
[0135] When the result of the weighted average calculation does not meet a preset detection value, the target device is determined to be an untrusted device.
[0136] The device trust test module 220 is used to collect login files within a preset historical time period, obtain feature data of each historical login request, and form a historical message queue;
[0137] The historical message queue is cleaned to obtain the portrait data of the target account.
[0138] The device trust test module 220 is further used to obtain the login location and login time of each historical login from the portrait data to form a corresponding login location-time distribution graph; wherein the value of the login location and login time of each login is represented by a numerical point in the location-time distribution graph;
[0139] Based on the distribution of the numerical points in the location-time distribution graph, the range of the frequently logged-in locations and frequently logged-in times of the target account in historical logins is determined.
[0140] Figure 5 A schematic diagram of the structure of another web page access processing device provided by the embodiment disclosed in the present application.
[0141] like Figure 5 As shown, the apparatus of this embodiment further includes: an account trust testing module 240 associated with a user account.
[0142] The account trust testing module 240 of the associated user account is used to obtain the unique device ID of the untrusted device;
[0143] Based on the unique device ID of the untrusted device, obtain an associated user account that has logged in using the untrusted device;
[0144] Acquire characteristic data of corresponding historical login requests of each associated user account to form a historical message queue;
[0145] Confirm whether the most recent login location and / or login time of each associated user account corresponds to a frequently logged-in location and / or frequently logged-in time; wherein the associated user account is another user account that has been logged in by the untrusted device;
[0146] If not, the corresponding associated user account performs a temporary disabling operation.
[0147] Another corresponding description of the device and method:
[0148] The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.
[0149] In an embodiment of the present application, a computer device is provided, including a memory, a processor, and a computer program stored in the memory, and the processor executes the above-mentioned computer program to implement the steps of the processing method for web page access. Compared with the prior art, it can be achieved that: when the server receives a login request for a target account sent by a target device through a web page and forms a corresponding login file, characteristic data is obtained from the login file. Determine whether the target device is an untrusted device based on the characteristic data and the portrait data of the target account. When it is determined that the target device is an untrusted device, determine whether to respond to the login request of the target device based on the result of the confirmation. Based on the technical solution provided by the present application, the technical problem that the original means of identifying theft behavior based on the login geographical location cannot identify theft behavior in the target account's frequent login location is overcome, thereby improving the recognition rate of theft behavior of web page access, contributing to the security level of user accounts, and ensuring the normal operation of the network service platform.
[0150] In an alternative embodiment, a computer device is provided, such as Figure 6 As shown, Figure 6 The computer device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the computer device 4000 may also include a transceiver 4004, which may be used for data exchange between the computer device and other computer devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the computer device 4000 does not constitute a limitation on the embodiments of the present application.
[0151] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0152] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0153] The memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.
[0154] The memory 4003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the above method embodiment.
[0155] The computer device includes but is not limited to: a desktop computer device, a mobile computer or a portable mobile terminal such as a mobile phone, a tablet computer, etc.
[0156] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned processing method embodiment for accessing a web page can be implemented.
[0157] The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned web page access processing method embodiment when executed by a processor.
[0158] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.
[0159] The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.
Claims
1. A method for processing web page access, characterized in that: The following steps are involved: Receiving a login request for a target account initiated through a web page, and generating a login file for a target device that initiated the login request; Obtaining the portrait data of the target account, and obtaining characteristic data for trust testing from the login file; When it is determined that the target device is an untrusted device according to the portrait data and the feature data, performing a human-computer interaction verification operation to determine whether to respond to the login request; Obtaining a unique device ID of the untrusted device; Based on the unique device ID of the untrusted device, obtain an associated user account that has logged in using the untrusted device; Confirm whether the most recent login location and / or login time of each associated user account corresponds to the frequently logged-in location and / or frequently logged-in time; if not, the corresponding associated user account is temporarily disabled; wherein the associated user account is other user account that has been logged in by the untrusted device.
2. The method for processing web page access according to claim 1, characterized in that: The step of receiving a login request initiated for a target account via a web page and generating a login file for a target device that initiated the request includes: The target account is detected when the target device logs in for the first time, the target device ID is obtained, and a prefix is added to the target device ID to form a unique device ID of the target device.
3. The method for processing web page access according to claim 2, characterized in that: The characteristic data includes a first unique device ID; The step of determining that the target device is an untrusted device according to the portrait data and the feature data comprises: The first unique device ID is matched with the second unique device ID of the historical login device of the portrait data. If the match is unsuccessful, the target device is an abnormal login device, and the abnormal login device is determined to be an untrusted device.
4. The method for processing web page access according to claim 1 or 3, characterized in that: The characteristic data also includes login IP and login time; The step of determining that the target device is an untrusted device according to the portrait data and the feature data comprises: Obtain the current login IP and login time of the target device, and match them with the frequently logged-in locations and frequently logged-in time periods in the corresponding target account's portrait data; Obtaining a score for each of the feature data according to the matching result, and performing weighted average calculation on the scores of all the feature data; When the result of the weighted average calculation does not meet a preset detection value, the target device is determined to be an untrusted device.
5. The method for processing web page access according to claim 4, characterized in that: The step of obtaining the portrait data of the target account includes: Collect the login files within the preset time period, obtain the characteristic data of each historical login request, and form a historical message queue; The historical message queue is cleaned to obtain the portrait data of the target account.
6. The method for processing web page access according to claim 5, characterized in that: The step of cleaning and obtaining the portrait data of the target account according to the historical message queue includes: The login location and login time of each historical login are obtained from the portrait data to form a corresponding login location-time distribution graph; wherein the values of the login location and login time of each login are represented by a numerical point in the location-time distribution graph; Based on the distribution of the numerical points in the location-time distribution graph, the range of the frequently logged-in locations and frequently logged-in times of the target account in historical logins is determined.
7. The method for processing web page access according to claim 1, characterized in that: Also includes: Acquire characteristic data of corresponding historical login requests of each associated user account to form a historical message queue; The last login location and / or login time of the corresponding associated user account is obtained from the historical message queue.
8. A web page access processing device, characterized in that: include: A login file generation module, configured to receive a login request for a target account initiated via a web page, and generate a login file for a target device that initiates the login request; A device trust test module, used to obtain the portrait data of the target account and obtain characteristic data for trust testing from the login file; A login request verification module, configured to perform a human-computer interaction verification operation to determine whether to respond to the login request when the target device is determined to be an untrusted device based on the portrait data and the feature data; An account trust test module, used to obtain a unique device ID of the untrusted device; Based on the unique device ID of the untrusted device, obtain an associated user account that has logged in using the untrusted device; Confirm whether the most recent login location and / or login time of each associated user account corresponds to the frequently logged-in location and / or frequently logged-in time; if not, the corresponding associated user account is temporarily disabled; wherein the associated user account is other user account that has been logged in by the untrusted device.
9. A computer device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the method for processing web page access according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method for processing web page access described in any one of claims 1 to 7 are implemented.
11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method for processing web page access described in any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
User account login method and apparatus, electronic device and storage medium
CN109039987A
Web service account theft real-time monitoring method and system based on Flink
CN110138791A
