CN106953738B - Risk control method and device - Google Patents
Risk control method and device Download PDFInfo
- Publication number
- CN106953738B CN106953738B CN201610887634.2A CN201610887634A CN106953738B CN 106953738 B CN106953738 B CN 106953738B CN 201610887634 A CN201610887634 A CN 201610887634A CN 106953738 B CN106953738 B CN 106953738B
- Authority
- CN
- China
- Prior art keywords
- event
- risk
- event information
- information
- security policy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/147—Network analysis or design for predicting network behaviour
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
Abstract
The application relates to the technical field of computers, in particular to a risk control method and a risk control device, wherein in the risk control method, a server can receive event information of a risk event sensed by a client in real time; then analyzing the risk event according to the historical behavior information to determine the category of the risk event; when the type of the risk event is determined to be the risk event, a security policy corresponding to the event information is generated, so that the server side can carry out risk control on the account or the network behavior of the user by combining the automatically generated security policy and a preset security policy, and therefore effective risk control on the account or the network behavior of the user can be realized.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a risk control method and apparatus.
Background
In the traditional technology, when risk control is realized, a server collects historical behavior data of a user from a background database, then carries out risk model modeling according to the historical behavior data, and finally carries out risk identification on an account or a network behavior of the user according to an established risk model; and when the account or the network behavior of the user is recognized to be risky, carrying out risk control on the account or the network behavior of the user according to a preset security policy. However, since the security policy is often written by a developer according to historical behavior data and has no real-time property, risk control cannot be performed on the latest user account or network behavior according to the preset security policy, which affects the effectiveness of risk control on the user account or network behavior, thereby bringing poor experience to the user and further wasting computer resources.
Disclosure of Invention
The application describes a risk control method and a risk control device, which are used for realizing effective risk control of an account or a network behavior of a user.
In a first aspect, a risk control method is provided, the method comprising:
receiving event information corresponding to a risk event sent by a client;
determining the category of the risk event according to the event information and preset historical behavior information;
if the type of the risk event is a risk event, generating a security strategy according to the event information;
and carrying out risk control on the account or the network behavior of the user according to the generated security policy and a preset security policy, wherein the preset security policy is compiled according to the historical behavior information.
In a second aspect, there is provided a risk control device, the device comprising:
the receiving unit is used for receiving event information corresponding to the risk event sent by the client;
the determining unit is used for determining the category of the risk event according to the event information received by the receiving unit and preset historical behavior information;
the generating unit is used for generating a security policy according to the event information if the type of the risk event determined by the determining unit is a risk event;
and the control unit is used for carrying out risk control on the account or the network behavior of the user according to the security policy generated by the generation unit and a preset security policy, wherein the preset security policy is compiled according to the historical behavior information.
According to the risk control method and device, the server can receive event information of the risk event sensed by the client; then analyzing the risk event according to the historical behavior information to determine the category of the risk event; when the type of the risk event is determined to be a risk event, a security policy corresponding to the event information is generated, so that the service end can perform risk control on the account or the network behavior of the user according to the automatically generated security policy and a preset security policy, that is, in the application, the event information of the risk event sent by the client can be received in real time, and under the condition that the event information is effective event information, the corresponding security policy can be automatically generated according to the event information, and then the account or the network behavior of the user is subjected to risk control by combining the generated security policy and the preset security policy, so that the effective risk control on the account or the network behavior of the user can be realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of a risk control method provided in the present application;
FIG. 2 is a flow chart of a risk control method according to an embodiment of the present application;
FIG. 3 is a flow chart of a risk control method according to another embodiment of the present application;
fig. 4 is a schematic view of a risk control device provided in the present application.
Detailed Description
Embodiments of the present invention will be described below with reference to the accompanying drawings.
The risk control method and the risk control device are suitable for a scene of carrying out risk control on the account or the network behavior of the user, wherein the network behavior can comprise login behavior, payment behavior, transaction behavior and the like.
For example, in the application scenario shown in fig. 1, the client may refer to a terminal device that logs in a registered account of a user, or may refer to an application that logs in a registered account of a user, where the application is located in the terminal device; the client can upload the event information of the risk event perceived by the user of the client to the server in real time, that is, the user in the application refers to a user capable of perceiving the risk event, and the event information may include an event name and/or event content.
After receiving event information of a risk event uploaded by a client, a server in fig. 1 may determine a category of the risk event in combination with preset historical behavior information; and under the condition that the category of the risk event is determined to be the risk event, classifying the event information into the following categories: personalized event information and general event information; specifically, if the event information belongs to personalized event information, the event information is directly recorded, and a personalized security policy is generated according to the event information, so that a server can perform risk control on accounts or network behaviors of the user and/or similar users of the client according to the personalized security policy and a preset security policy, thereby being closer to the personal requirements of the user, wherein the preset security policy is compiled by developers according to historical behavior information of the user; if the event information belongs to the general event information, further determining the risk level of the risk event, and generating a general security strategy according to the event information under the condition that the risk level meets a preset condition; and according to the general security policy and the preset security policy, performing risk control on the accounts and network behaviors of the user of the client and other users, thereby achieving the purpose of sharing event information by a plurality of users.
It should be further noted that, under the condition that the event information is valid, the server may store the event information, so that a subsequent server may perform risk control on an account or a network behavior of the user in combination with the preset historical behavior information and the event information, thereby better ensuring the security of the user.
Fig. 2 is a flowchart of a risk control method according to an embodiment of the present application. The execution subject of the method may be a device with processing capabilities: a server or a system or an apparatus, such as a server in fig. 1, as shown in fig. 2, the method may specifically include:
step 210, receiving event information corresponding to the risk event sent by the client.
The client may be a terminal device that has logged in a registered account of the user, or may be an application that has logged in a registered account of the user and is located in the terminal device. Further, the risk events described above may include, but are not limited to, the following: account stolen events, money lost events, infrequent device login events, billing exception events, network underpinning events, login failure events, and drop events, among others.
It should be further noted that, in the present application, the user of the client has the ability to perceive the risk event. Specifically, when the user of the client senses the risk event, the user can fill in the event information of the risk event through an application interface provided by the client, and then trigger the client to upload the event information of the risk event to the server. The event information here may include event names and/or event contents, etc., wherein categories and risk levels may be set according to actual needs, and in one example, the categories may include: both at-risk and no-risk events, the risk levels may include: high, medium and low.
Of course, the above description only shows two categories of risk events and three risk levels by way of example, and is not intended to limit the present application, and in practical applications, the categories of risk events may also be expressed as: risk events and potential risk events occur, or other categories and the like can also be included; in addition, the risk level may also be expressed as a numerical value, or may include other risk levels, etc.
In addition, after receiving the event information sent by the client, the server may also perform preprocessing on the event information, for example, convert the event information into information conforming to a preset format, and the like, where the information in the preset format may be recognized by the server.
For example, it is assumed that the name of the wifi network to which the terminal device of the user is currently connected is "daoyong", and the user logs in the payer client using the registered payer account, and after a period of time, in the case that the user does not perform any payment operation, the payer account of the user has a fund loss, so that the user perceives a risk event, at this time, the user may trigger the payer client to send event information of the risk event to the payer server, and assuming that the event information includes an event name and event content, the event name may be an "account stolen event", and the event content may be a fund loss when the wifi network with the "daoyong" is connected.
And step 220, determining the category of the risk event according to the event information and preset historical behavior information.
Here, the preset historical behavior information may be collected by the server from the background database in advance. Specifically, the event information may be analyzed according to the preset historical behavior information to determine the category of the risk event, where a process of analyzing the event information according to the preset historical behavior information is also referred to as a process of data cleansing. In one implementation, risk model modeling may be performed according to the preset historical behavior information; and analyzing the event information through the risk model to determine the category of the risk event, wherein the event information is analyzed through the risk model to determine that the category of the risk event belongs to the conventional technology, which is not repeated herein.
The categories of the risk events determined in step 220 may include risk events and risk-free events, or may also include risks and risks of potential hazards, etc., and in this specification, the categories of the risk events including risk events and risk-free events are taken as an example.
And step 230, if the type of the risk event is the risk event, generating a security policy according to the event information.
If the server determines that the category of the risk event is a risk event, it indicates that event information corresponding to the risk event is valid information or available data, so that a security policy can be further generated based on the event information, where the security policy refers to a risk control method or rule adopted by the server for an account or a network behavior when the server identifies that the account or the network behavior of a user is at risk, and may include two types, namely a personalized security policy and a general security policy, and the personalized security policy is used for performing risk control on the account or the network behavior of a certain user and/or a similar user; the generic security policy is used for risk control of all users' accounts or network behavior.
It should be noted that, the generating the security policy according to the event information in step 230 further includes:
determining the classification of the event information according to the event information;
if the classification of the event information belongs to the general event information, acquiring the risk level of the risk event according to the event information;
and when the risk level meets a preset condition, generating a safety strategy according to the event information.
In order to perform personalized security protection on the user, when the risk event is determined to be a risk event, the event information can be further classified. In one implementation, the event information may further include classification information, the classification information including: personalized event information and general event information; after receiving the event information, the server determines the classification of the event information according to the classification information in the event information. Specifically, if the classification of the event information belongs to the personalized event information, a personalized security policy is generated directly according to the event information; if the classification of the event information belongs to the general event information, acquiring the risk level of the risk event according to the event information; and generating a general security policy according to the event information under the condition that the risk level meets a preset condition.
In one implementation, before acquiring the risk level of the risk event according to the event information, a storage unit may be preset, where the storage unit is configured to record a corresponding relationship between event information and level information of at least one preset risk event, where the preset risk event may be collected manually in advance.
In one example, the predetermined memory location may be as shown in table 1.
TABLE 1
It should be noted that the content in table 1 is only an exemplary illustration, and in practical applications, table 1 may further include other risk events, and the event information of the risk event may also not be limited to the event name, and may also include event content, event identifier, and the like, which is not limited in this application.
After presetting the storage unit, the obtaining the risk level of the risk event according to the event information may specifically include: and matching the event information with the event information of the preset risk event in the storage unit, and when the event information is matched with the event information of any preset risk event, taking the grade information corresponding to the event information of any preset risk event as the risk grade of the risk event. Here, matching may include coincidence or a similarity value being the largest (or exceeding a preset threshold), and the like. In the case that the event information includes only the event name, the event name of the risk event sent by the paypal client in the foregoing example is "account stolen event", and the event name is consistent with the second name in table 1, so that the name is matched with the second name in table 1, and thus the obtained risk level of the risk event is "medium"; and when the event name of the risk event sent by the client is the "account stolen event", the similarity value between the event name and the second name in table 1 is the largest, so that the name is matched with the second name in table 1, and the acquired risk level of the risk event is also "medium".
The above description has been made by taking an example that the event information only includes an event name, and only the event name is recorded in the storage unit, it can be understood that, when the event information also includes event content and the event content is also recorded in the storage unit, the event name and the event content in the event information sent by the client may be respectively matched with the event name and the event content in the storage unit, and in a case that the event name and the event content are all matched, the level information corresponding to the event name and the event content in the storage unit is acquired.
It should be further noted that when the event information of the risk event sent by the client does not match the event information of each preset risk event in the storage unit, the risk level of the risk event may be manually assigned, and when the risk level meets the preset condition, the event information and the corresponding risk may be equivalently added to the storage unit so as to match the event information subsequently sent by the client.
After determining the risk level of the risk event, and when the risk level satisfies a preset condition, a generic security policy may be generated.
As in the previous example, the risk level of the acquired risk event is "medium", and the preset conditions are assumed to be: and if the risk level is greater than or equal to the middle level, the risk level of the risk event meets the preset condition.
It is understood that the event information is discarded if the risk level does not satisfy the preset condition. Here, since a user of the client may experience a sensing error (for example, a remote login event, the user may forget that the user uses a certain device, and thus the event logged in the device is perceived as a risk event by mistake), when the server receives event information of the risk event, the obtained risk level of the risk event is relatively low (that is, the preset condition is not met), and thus the event information is not used as a basis for generating a security policy.
In one implementation, the generated generic security policy may include:
sending a reminding message to a client of a user; alternatively, the first and second electrodes may be,
prohibiting use of the account or prohibiting execution of the network action.
As in the foregoing example, when the event name is "account stolen event", and the event content is "fund loss occurs when connecting to wifi network with name" daoyong ", the general security policy generated by the paymate server may be: "send a warning message when detecting that the user performs login, payment operation through wifi network named" daoyong "or" prohibit login, payment operation through wifi network named "daoyong" and so on.
And 240, performing risk control on the account or the network behavior of the user according to the generated security policy and a preset security policy, wherein the preset security policy is written according to historical behavior information.
After the server generates the personalized security policy, the server can detect the account or network behavior of the user of the client and/or the similar user according to the personalized security policy and the preset security policy, wherein the similar user refers to a user having similar behavior with the current user obtained by the server through analyzing historical behavior data of the current user and other users; or after the general security policy is generated, the account or network behavior of the user of the client and/or other users may be detected according to the general security policy and the preset security policy. As in the previous example, the pay bank server sends a reminder message when detecting that a pay bank user (including a user using the current client and users of other clients) logs in a pay bank account or performs a payment operation through a wifi network named "daoyong"; or the payment service terminal forbids the login behavior or forbids the payment operation once detecting that the payment user (including the user using the current client and the users of other clients) logs in the payment account or executes the payment operation through the wifi network named as "daoyong".
That is, the risk control can be performed on the accounts or the network behaviors of all the users through the general security policy generated by the application, so that the sharing of data among the users is realized.
Of course, the above steps 210 to 240 are operations executed by the server side when the server side determines that the category of the risk event is a risk event; and when the server judges that the type of the risk event is a risk-free event, discarding the event information uploaded by the client. Here, the risk event is perceived by the user and an error occurs, so that when the server receives the event information sent by the client, the server needs to filter the risk event first to ensure that the risk event is a real risk event and is not a risk event sent by mistake due to a user perception error; and when event information of a risk event of a user perception error is received, a security policy is not generated according to the event information.
It can be understood that the general security policy and the personalized security policy generated by the present application are only supplements to the existing security policy, and are not replacements for the existing security policy, that is, after the general security policy or the personalized security policy of the present application is generated, the existing security policy and the general security policy or the personalized security policy may be combined to perform risk control on an account or a network behavior of a user, so that the effectiveness of risk control may be improved.
Fig. 3 is a flowchart of a risk control method according to another embodiment of the present application. The execution subject of the method may be a device with processing capabilities: a server or a system or an apparatus, such as a server in fig. 1, as shown in fig. 3, the method may specifically include:
and step 310, receiving event information corresponding to the risk event sent by the client.
And step 320, determining the category of the risk event according to the event information and preset historical behavior information.
at step 340, the event information is discarded.
In step 360, if the classification of the event information belongs to the personalized event information, step 370 is executed, otherwise step 390 is executed.
And step 370, generating a personalized security policy according to the event information.
And 380, performing risk control on accounts or network behaviors of the user and/or similar users of the client according to the personalized security policy and the preset security policy.
In step 3100, if the risk level satisfies the predetermined condition, execute step 3120, otherwise execute step 3110.
At step 3110, the event information is discarded.
And 3120, generating a general security policy according to the event information.
3130, performing risk control on accounts or network behavior of the user of the client and/or other users according to the general security policy and the preset security policy.
Therefore, the personalized requirements of the users can be met, and the purpose of sharing data among a plurality of users can be achieved.
In conclusion, the core idea of the application is to change the traditional method that developers write a security policy according to historical behavior data of users and perform risk control on accounts or network behaviors of the users according to the security policy; and the user is allowed to participate in the process, namely, the subject of participatory perception is applied, so that the server can receive the event information of the risk event uploaded by the client in real time, generate a security policy according to the event information, and finally realize risk control on the account or network behavior of the user by combining the generated security policy and a preset security policy, thereby improving the effectiveness of risk control.
Corresponding to the risk control method, an embodiment of the present application further provides a risk control device, as shown in fig. 4, the device includes:
a receiving unit 401, configured to receive event information corresponding to a risk event sent by a client.
A determining unit 402, configured to determine a category of the risk event according to the event information received by the receiving unit 401 and preset historical behavior information.
A generating unit 403, configured to generate a security policy according to the event information if the category of the risk event determined by the determining unit 402 is a risk event.
Optionally, the generating unit 403 is specifically configured to:
determining the classification of the event information according to the event information;
if the classification of the event information belongs to the general event information, acquiring the risk level of the risk event according to the event information;
and when the risk level meets a preset condition, generating a safety strategy according to the event information.
Optionally, the generating unit 403 is further specifically configured to:
matching the event information with event information of preset risk events in a storage unit, wherein the storage unit is used for recording the corresponding relation between the event information of at least one preset risk event and the grade information;
and when the risk level information is matched with the event information of any preset risk event, taking the level information corresponding to the event information of any preset risk event as the risk level of the risk event.
A control unit 404, configured to perform risk control on an account or a network behavior of the user according to the security policy generated by the generating unit 403 and a preset security policy, where the preset security policy is written according to historical behavior information.
Here, the generated general security policy may include:
sending a reminding message to a client of a user; alternatively, the first and second electrodes may be,
prohibiting use of the account or prohibiting execution of the network action.
Optionally, the apparatus may further include: a discarding unit 405, configured to discard the event information if the category of the risk event is a risk-free event.
The functions of the functional modules of the device in the embodiment of the present application may be implemented through the steps in the method embodiment described above, and therefore, the specific working process of the device provided in the present application is not repeated herein.
In the risk control device provided by the application, a receiving unit 401 receives event information corresponding to a risk event sent by a client; the determining unit 402 determines the category of the risk event according to the event information and preset historical behavior information; if the type of the risk event is a risk event, the generating unit 403 generates a security policy according to the event information; the control unit 404 performs risk control on the account or the network behavior of the user according to the generated security policy and the preset security policy. Therefore, effective risk control on the account or the network behavior of the user can be realized.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.
Claims (8)
1. A risk control method, comprising:
receiving event information corresponding to a risk event sent by a client;
determining the category of the risk event according to the event information and preset historical behavior information;
if the type of the risk event is a risk event, generating a security strategy according to the event information;
according to the generated security policy and a preset security policy, performing risk control on an account or a network behavior of a user, wherein the preset security policy is compiled according to the historical behavior information;
wherein, the generating a security policy according to the event information includes:
determining the classification of the event information according to the event information;
if the classification of the event information belongs to general event information, acquiring the risk level of the risk event according to the event information; when the risk level meets a preset condition, generating a general security strategy according to the event information;
if the classification of the event information belongs to the personalized event, a personalized security policy is generated directly according to the event information; the personalized security policy is used for risk control of accounts or network behavior of similar users.
2. The method of claim 1, wherein obtaining the risk level of the risk event based on the event information comprises:
matching the event information with event information of preset risk events in a storage unit, wherein the storage unit is used for recording the corresponding relation between the event information of at least one preset risk event and the grade information;
and when the risk level information is matched with the event information of any preset risk event, taking the level information corresponding to the event information of any preset risk event as the risk level of the risk event.
3. The method according to any one of claims 1 or 2, further comprising:
and if the type of the risk event is a risk-free event, discarding the event information.
4. The method of claim 1 or 2, wherein the generic security policy comprises:
sending a reminding message to the client of the user; alternatively, the first and second electrodes may be,
prohibiting use of the account or prohibiting performance of the network action.
5. A risk control device, comprising:
the receiving unit is used for receiving event information corresponding to the risk event sent by the client;
the determining unit is used for determining the category of the risk event according to the event information received by the receiving unit and preset historical behavior information;
the generating unit is used for generating a security policy according to the event information if the type of the risk event determined by the determining unit is a risk event;
the control unit is used for carrying out risk control on the account or the network behavior of the user according to the security policy generated by the generation unit and a preset security policy, wherein the preset security policy is compiled according to the historical behavior information;
the generating unit is specifically configured to:
determining the classification of the event information according to the event information;
if the classification of the event information belongs to general event information, acquiring the risk level of the risk event according to the event information; when the risk level meets a preset condition, generating a general security strategy according to the event information;
if the classification of the event information belongs to the personalized event, a personalized security policy is generated directly according to the event information; the personalized security policy is used for risk control of accounts or network behavior of similar users.
6. The apparatus according to claim 5, wherein the generating unit is further specifically configured to:
matching the event information with event information of preset risk events in a storage unit, wherein the storage unit is used for recording the corresponding relation between the event information of at least one preset risk event and the grade information;
and when the risk level information is matched with the event information of any preset risk event, taking the level information corresponding to the event information of any preset risk event as the risk level of the risk event.
7. The apparatus of any one of claims 5 or 6, further comprising: and the discarding unit is used for discarding the event information if the type of the risk event is a risk-free event.
8. The apparatus of claim 5 or 6, wherein the generic security policy comprises:
sending a reminding message to the client of the user; alternatively, the first and second electrodes may be,
prohibiting use of the account or prohibiting performance of the network action.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610887634.2A CN106953738B (en) | 2016-10-11 | 2016-10-11 | Risk control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610887634.2A CN106953738B (en) | 2016-10-11 | 2016-10-11 | Risk control method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106953738A CN106953738A (en) | 2017-07-14 |
| CN106953738B true CN106953738B (en) | 2020-12-18 |
Family
ID=59465287
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610887634.2A Active CN106953738B (en) | 2016-10-11 | 2016-10-11 | Risk control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106953738B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109003090A (en) * | 2018-07-05 | 2018-12-14 | 阿里巴巴集团控股有限公司 | risk control method and device |
| CN109327433B (en) * | 2018-09-03 | 2022-05-17 | 北京智游网安科技有限公司 | Threat perception method and system based on operation scene analysis |
| CN109165514B (en) * | 2018-10-16 | 2019-08-09 | 北京芯盾时代科技有限公司 | A kind of risk checking method |
| CN109474515B (en) * | 2018-11-13 | 2022-06-24 | 平安科技（深圳）有限公司 | Risk event mail pushing method and device, computer equipment and storage medium |
| CN110147967B (en) * | 2019-05-28 | 2023-05-30 | 创新先进技术有限公司 | Risk prevention and control method and device |
| CN110381088B (en) * | 2019-08-21 | 2021-11-12 | 牡丹江师范学院 | Data security guarantee method based on Internet of things |
| CN112434214A (en) * | 2020-11-03 | 2021-03-02 | 中国南方电网有限责任公司 | Redis-based operation event pushing method |
| CN113095625B (en) * | 2021-03-17 | 2023-04-07 | 中国民用航空总局第二研究所 | Method and system for grading unsafe events of civil aviation airport |
| CN113992351A (en) * | 2021-09-26 | 2022-01-28 | 五八有限公司 | Detection method and device of communication interface, electronic equipment and readable medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102693384A (en) * | 2012-05-22 | 2012-09-26 | 清华大学 | Method and apparatus for safe self adjustment of browsers |
| CN104598595A (en) * | 2015-01-23 | 2015-05-06 | 安一恒通（北京）科技有限公司 | Fraud webpage detection method and corresponding device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102325062A (en) * | 2011-09-20 | 2012-01-18 | 北京神州绿盟信息安全科技股份有限公司 | Abnormal login detecting method and device |
| CN102722559B (en) * | 2012-05-31 | 2015-09-16 | 北京奇虎科技有限公司 | A kind of course control method of the abnormal page, device and system |
| CN104348810B (en) * | 2013-08-05 | 2019-02-22 | 深圳市腾讯计算机系统有限公司 | The detection method of stolen account number, apparatus and system |
| CN103532797B (en) * | 2013-11-06 | 2017-07-04 | 网之易信息技术（北京）有限公司 | A kind of User logs in method for monitoring abnormality and device |
-
2016
- 2016-10-11 CN CN201610887634.2A patent/CN106953738B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102693384A (en) * | 2012-05-22 | 2012-09-26 | 清华大学 | Method and apparatus for safe self adjustment of browsers |
| CN104598595A (en) * | 2015-01-23 | 2015-05-06 | 安一恒通（北京）科技有限公司 | Fraud webpage detection method and corresponding device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106953738A (en) | 2017-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106953738B (en) | Risk control method and device | |
| CN106656932B (en) | Service processing method and device | |
| CN109600336B (en) | Verification code application method, device and computer readable storage medium | |
| CN104320375B (en) | A kind of method and apparatus for preventing from illegally registering | |
| CN104901936A (en) | Business processing method and device, terminal and server | |
| CN109670931A (en) | Behavioral value method, apparatus, equipment and the storage medium of loan user | |
| US20150150096A1 (en) | Image forming apparatus, image forming system, and method | |
| CN112132687A (en) | Resource exchange wind control method and device, computer equipment and storage medium | |
| CN110135326B (en) | Identity authentication method, electronic equipment and computer readable storage medium | |
| CN111950029A (en) | Financial data query method, device, equipment and medium based on block chain | |
| CN111859320A (en) | Cross-system login-free method, device, equipment and readable storage medium | |
| CN107507086B (en) | Invoice processing method and invoice processing system | |
| CN116302889A (en) | Performance test method and device for functional module and server | |
| CN115967565A (en) | Battlefield situation sensing method, system, terminal equipment and storage medium | |
| CN111784359B (en) | Multi-mode wind control grading disaster recovery method and device | |
| CN103685146A (en) | Data processing device and data processing method for safety information interaction | |
| CN114338703A (en) | Cross-domain message management method and device, electronic equipment and storage medium | |
| CN113890754A (en) | Data transmission method, terminal, system and readable storage medium | |
| CN107483210B (en) | Data verification method and system | |
| KR101456467B1 (en) | Connectting record generation system using packet modulation | |
| CN112559205A (en) | Credit report generation method and system | |
| CN111611473A (en) | Information push processing method and device, storage medium and terminal | |
| CN111091470B (en) | Multi-policy-sum data processing method and device, electronic equipment and storage medium | |
| CN108134656A (en) | Insurance data retransmission method, device, server and storage medium | |
| CN116719751B (en) | Method and system for checking service loss in real time |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201015 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201015 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |