CN106953738A - Risk control method and device - Google Patents
Risk control method and device Download PDFInfo
- Publication number
- CN106953738A CN106953738A CN201610887634.2A CN201610887634A CN106953738A CN 106953738 A CN106953738 A CN 106953738A CN 201610887634 A CN201610887634 A CN 201610887634A CN 106953738 A CN106953738 A CN 106953738A
- Authority
- CN
- China
- Prior art keywords
- event information
- risk
- event
- risk case
- information
- 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.)
- Granted
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application is related to field of computer technology, more particularly to a kind of risk control method and device, in a kind of risk control method, the event information for the risk case that service end can be perceived with real-time reception client；Afterwards according to historical behavior information, the risk case is analyzed, to determine the classification of the risk case；When it is determined that the classification of the risk case is risky event, the generation security strategy corresponding with event information, the security strategy and default security strategy that can be automatically generated so as to service end with reference to this, to carry out risk control to the account or network behavior of user, effective risk control is carried out to the account or network behavior of user thus, it is possible to realize.
Description
Technical field
The application is related to field of computer technology, more particularly to a kind of risk control method and device.
Background technology
In conventional art, when realizing risk control, server collects the history row of user from background data base first
For data, risk model modeling is carried out according to historical behavior data afterwards, finally according to the risk model of foundation, to user's
Account or network behavior carry out risk identification；When the account or risky network behavior for recognizing user, according to default
Security strategy, account to user or network behavior carry out risk control.However, due to above-mentioned security strategy often by
Developer writes according to historical behavior data, without real-time, so that according to above-mentioned default security strategy, often not
Risk control can be carried out to the account or network behavior of newest user, this have impact on the account or network behavior to user
The validity of risk control is carried out, poor experience is thus brought to user, and then waste computer resource.
The content of the invention
This application describes a kind of risk control method and device, had with the account or network behavior of realizing user
The risk control of effect.
First aspect includes there is provided a kind of risk control method, this method：
Receive the corresponding event information of risk case that client is sent；
According to the event information and default historical behavior information, the classification of the risk case is determined；
If the classification of the risk case is risky event, according to the event information, security strategy is generated；
According to the security strategy of generation and default security strategy, account or network behavior to user carry out risk
Control, wherein, the default security strategy is according to the historical behavior message composition.
Second aspect includes there is provided a kind of risk control device, the device：
Receiving unit, the corresponding event information of risk case for receiving client transmission；
Determining unit, for the event information and the default historical behavior information received according to the receiving unit,
Determine the classification of the risk case；
Generation unit, if the classification of the risk case determined for the determining unit is risky event, root
According to the event information, security strategy is generated；
Control unit, for the security strategy and default security strategy generated according to the generation unit, to user
Account or network behavior carry out risk control, wherein, the default security strategy is according to the historical behavior information
Write.
Risk control method and device that the application is provided, service end can receive the thing of the risk case of client perception
Part information；Afterwards according to historical behavior information, the risk case is analyzed, to determine the classification of the risk case；True
When the classification of the fixed risk case is risky event, the security strategy corresponding with event information is generated, so that service end can
With the security strategy and default security strategy automatically generated according to this, sector-style is entered come account or network behavior to user
Danger control, namely in the application, the event information for the risk case that can be sent with real-time reception client, and in the event information
In the case of for validity event information, corresponding security strategy can be automatically generated, and then combine the life according to the event information
Into security strategy and default security strategy, account to user or network behavior carry out risk control, thus, it is possible to
Realize and effective risk control is carried out to the account or network behavior of user.
Brief description of the drawings
Technical scheme in order to illustrate more clearly the embodiments of the present invention, below will be to that will use needed for embodiment description
Accompanying drawing be briefly described, it should be apparent that, drawings in the following description are only some embodiments of the present invention, for this
For the those of ordinary skill of field, on the premise of not paying creative work, it can also obtain other according to these accompanying drawings
Accompanying drawing.
The application scenarios schematic diagram for the risk control method that Fig. 1 provides for the application；
The risk control method flow chart that Fig. 2 provides for a kind of embodiment of the application；
The risk control method flow chart that Fig. 3 provides for another embodiment of the application；
The risk control schematic device that Fig. 4 provides for the application.
Embodiment
Below in conjunction with the accompanying drawings, embodiments of the invention are described.
The risk control method and device that the embodiment of the present application is provided are applied to enter the account or network behavior of user
The scene of row risk control, wherein, network behavior can include login behavior, payment behavior and trading activity etc..
Such as, it is adaptable in application scenarios as shown in Figure 1, in Fig. 1, client can both refer to the registration for having logged in user
The terminal device of account or refer to the application program for having logged in the login account of user, the application program is set positioned at terminal
In standby；The event information for the risk case that the user that above-mentioned client can upload client to service end in real time perceives, namely
User in the application refers to can be with the user of Perceived Risk event, and above-mentioned event information can include event title and/thing
Part content etc..
Service end in Fig. 1 can be combined default after the event information of risk case of client upload is received
Historical behavior information, to determine the classification of risk case；And it is determined that the classification of risk case is the situation of risky event
Under, event information is classified, is such as divided into：Personalized event information and general purpose event information；Specifically, if above-mentioned event is believed
Breath belongs to personalized event information, then directly records the event information, and generates personalized secure strategy according to the event information,
So as to service end can according to the personalized secure strategy and default security strategy, user to above-mentioned client and/or
The account or network behavior of similar users carry out risk control, so that closer to the demands of individuals of user, it is above-mentioned default
Security strategy is the historical behavior message composition according to user by developer；If above-mentioned event information belongs to general purpose event letter
Breath, then further determine that the risk class of the risk case, in the case where risk class meets preparatory condition, according to above-mentioned thing
Part information, generates communication security policy；And according to the communication security policy and default security strategy, to above-mentioned client
The account and network behavior of user and other users carry out risk control, thus achieve multiple users to share event informations
Purpose.
It should also be noted that, in the case of event information is effective, service end can be stored to the event information,
So that follow-up service end can combine default historical behavior information and above-mentioned event information, to the account or net of user
Network behavior carries out risk control, so as to preferably ensure the safety of user.
The risk control method flow chart that Fig. 2 provides for a kind of embodiment of the application.The executive agent of methods described can be with
For the equipment with disposal ability：Server or system or device, e.g., the service end in Fig. 1, as shown in Fig. 2 the side
Method can specifically include：
Step 210, the corresponding event information of risk case that client is sent is received.
Client herein can refer to log in the terminal device of the login account of user or referred to have logged in use
The application program of the login account at family, the application program is located in terminal device.In addition, above-mentioned risk case can be included but not
It is limited to following event：Account is stolen event, the event that loses money, the equipment that is of little use log-in events, bill anomalous event, network state not
Good event, login failure event and the event etc. that goes offline.
It should also be noted that, in the application, the user of client has the ability for perceiving above-mentioned risk case.Specifically
Ground, the user of client is when perceiving above-mentioned risk case, and the application interface that can be provided by client fills in risk thing
The event information of part, triggers client and the event information of risk case is uploaded into service end afterwards.Event information herein can
With including event title and/or event content etc., wherein, classification and risk class can be set according to the actual requirements, at one
In example, classification can include：Risky two kinds of event and devoid of risk event, risk class can include：High, medium and low three kinds.
Certainly, the above-mentioned simply exemplary classification and three kinds of risk class for illustrating two kinds of risk cases, is not intended as
Restriction to the application, in actual applications, the classification of risk case can also be expressed as：Occurrence risk event and hidden danger wind
Dangerous event, or other classifications etc. can also be included；In addition, risk class can also be expressed as numerical value, or it can also wrap
Include other risk class etc..
In addition, service end is after the event information of client transmission is received, the event information can also be carried out pre-
Processing, e.g., event information is converted to information for meeting preset format etc., the information of the preset format can be known with being serviced end
Not.
As an example it is assumed that entitled " daoyong " of the wifi network that the terminal device of user is currently connected, and the use
Family has logged in Alipay client using registered Alipay account, and after a period of time, is not carried out in the user any
In the case of delivery operation, the Alipay account of the user occurs in that the situation of monetary losses, so that user has perceived risk
Event, now, user can trigger the event information that Alipay client sends risk case to Alipay service end, it is assumed that should
Event information includes event title and event content, then its event title can be " account is stolen event ", and event content can be with
For " when connection name is the wifi network of " daoyong ", occurring in that the situation of monetary losses ".
Step 220, according to event information and default historical behavior information, the classification of risk case is determined.
Herein, default historical behavior information can be collected in advance from background data base by service end.Specifically, may be used
With according to the default historical behavior information, to analyze event information, to determine the classification of risk case, wherein, root
According to default historical behavior information, the process of data cleansing is also referred to as the process analyzed event information.A kind of real
In existing mode, risk model modeling can be carried out according to the default historical behavior information；Afterwards by risk model come to thing
Part information is analyzed, to determine the classification of risk case, event information is analyzed here by risk model, with true
The classification for determining risk case belongs to conventional art, does not repeat again herein.
The classification of the risk case determined in step 220 can include risk case and devoid of risk event, or also may be used
With including occurrence risk and hidden danger risk etc., in this description, with the classification of risk case include risk case and
Illustrated exemplified by two kinds of devoid of risk event.
Step 230, if the classification of risk case is risky event, according to event information, security strategy is generated.
If service end judges that the classification of risk case, for risky event, illustrates the corresponding event information of the risk case
As effective information or data available, so as to based on the event information, further to generate security strategy, wherein, peace
Full strategy refers to service end when identifying the account of user or risky network behavior, for the account or network behavior
The risk control method or rule taken, it can include two kinds of personalized secure strategy and communication security policy, personalized
Security strategy is used to carry out risk control to the account or network behavior of some user and/or similar users；Universal safety plan
Slightly it is used to carry out risk control to the account or network behavior of all users.
It should be noted that in step 230 according to event information, generation security strategy can further include：
According to event information, the classification of event information is determined；
If the classification of event information belongs to general purpose event information, according to event information, risk of risk case etc. is obtained
Level；
When risk class meets preparatory condition, according to event information, security strategy is generated.
In order to carry out personalized secure protection to user, the application, can be with when it is determined that risk case is risky event
Further event information is classified.In one implementation, the event information can also include classification information, the classification
Information includes：Personalized event information and general purpose event information；Service end is after event information is received, according to event information
In classification information, determine the classification of event information.Specifically, if the classification of event information belongs to personalized event information,
Directly according to event information, personalized secure strategy is generated；If the classification of event information belongs to general purpose event information, according to thing
Part information, obtains the risk class of risk case；In the case where risk class meets preparatory condition, generated according to event information
Communication security policy.
In one implementation, according to event information, before the risk class for obtaining risk case, it can set in advance
Memory cell is put, the memory cell is used for the event information pass corresponding with class information for recording at least one default risk case
System, default risk case herein can be by artificially collecting in advance.
In one example, default memory cell can be as shown in table 1.
Table 1
It should be noted that the content in table 1 is exemplary illustration, in actual applications, it can also be included in table 1
Its risk case, and the event information of risk case can also be not limited to event title, can also include event content and
Event identifier etc., the application is not construed as limiting to this.
After default memory cell, above-mentioned according to event information, obtaining the risk class of risk case can specifically wrap
Include：By event information with memory cell preset risk case event information matched, when with any default risk case
Event information when matching, using the corresponding class information of event information of any default risk case as risk case wind
Dangerous grade.Herein, consistent or Similarity value maximum (or more than predetermined threshold value) etc. can be included by matching.Believed with event
Breath is only included for the entitled example of event, and the event for the risk case that Alipay client is sent is entitled in such as previous example
" account is stolen event ", the event title is consistent with second title in table 1, therefore, the title and second title in table 1
Match, thus obtain the risk case risk class for " in "；And the event name of the risk case when client transmission
Referred to as " account is stolen event " when, second title Similarity value is maximum in the event title and table 1, therefore, the title and table 1
In second title match, therefore obtain the risk case risk class be similarly " in ".
Above-mentioned is to only include event title with event information, and the entitled example of event is only have recorded in memory cell carries out
Explanation, it is to be understood that when event information also includes being also recorded for event content in event content, and memory cell, then
Event title and event content in the event information that client can be sent respectively with the event title in memory cell and
Event content is matched, in the case where event title and event content all match, with thing in acquisition memory cell
Part title and the corresponding class information of event content.
It should also be noted that, client send risk case event information and memory cell in each default risk
When the event information of event is mismatched, then the risk class of the risk case can be artificially distributed, meet pre- in risk class
If during condition, the event information can be added in memory cell with corresponding risk equivalent, so as to supervention after client
The event information sent is matched.
It is determined that after the risk class of risk case, and when risk class meets preparatory condition, it can generate general
Security strategy.
Such as previous example, the risk class of the risk case of acquisition for " in ", and assume that preparatory condition is：" >=in ", then
The risk class of risk case meets preparatory condition.
If it is understood that risk class is unsatisfactory for preparatory condition, abandoning event information.Herein, due to client
User it is possible that perceive mistake situations such as (such as, different-place login event, user may have forgotten it and be set using excessively a certain
It is standby, so as to be by mistake risk case by the event perception for logging in the equipment), now service end is believed in the event for receiving risk case
During breath, the risk class of the risk case of acquisition is than relatively low (being unsatisfactory for preparatory condition), so that will not be by the event information
It is used as the foundation of generation security strategy.
In one implementation, the communication security policy of generation can include：
Reminder message is sent to the client of user；Or,
Prohibit the use of the account or forbid performing the network behavior.
Such as previous example, entitled " account is stolen event " in event, event content is " connection name is " daoyong "
Wifi network when, occur in that the situation of monetary losses " when, Alipay service end generation communication security policy can be："
When detecting user and performing login, delivery operation by the wifi network of entitled " daoyong ", reminder message is sent " or
" wifi network that no thoroughfare entitled " daoyong " performs login, delivery operation " etc..
Step 240, according to the security strategy of generation and default security strategy, to the account or network behavior of user
Risk control is carried out, wherein, default security strategy is according to historical behavior message composition.
Service end, can be according to the personalized secure strategy and default safety after generation personalized secure strategy
Strategy, the account or network behavior of user and/or similar users to client detect that similar users herein refer to
By service end by analyzing the historical behavior data of active user and other users, there is similar row to active user obtained from
For user；Or generation communication security policy after, can according to the communication security policy and default security strategy,
The account or network behavior of user and/or other users to client are detected.Such as previous example, Alipay service end
Alipay user (user and the user of other clients including the use of active client) is being detected by entitled
When the wifi network of " daoyong " logs in Alipay account or performs delivery operation, reminder message is sent；Or Alipay clothes
Business end once detects Alipay user (user and the user of other clients including the use of active client) by name
When referred to as the wifi network of " daoyong " logs in Alipay account or performs delivery operation, forbid the login behavior or taboo
Only delivery operation etc..
Namely the communication security policy generated by the application, the account or network behavior of all users can be carried out
Risk control, it is achieved thereby that between user data it is shared.
Certainly, above-mentioned steps 210- steps 240 are to judge feelings of the classification of risk case for risky event in service end
Under condition, the operation performed by service end；When service end judges the classification of risk case for devoid of risk event, then client is abandoned
The event information of upload.Herein, above-mentioned risk case is perceived by user, it may appear that error, so that service end is being received
, it is necessary to first be filtered to risk case, to ensure that the risk case is real risk during the event information that client is sent
Event, rather than because user perceives risk case that is wrong and sending by mistake；Wrong risk case is perceived receiving user
Event information when, then not according to the event information generate security strategy.
It is understood that the communication security policy and personalized secure strategy of the application generation are intended only as existing safety
The supplement of strategy, not as the replacement of existing security strategy, namely the communication security policy in generation the application or personalization
After security strategy, existing security strategy can be combined with communication security policy or personalized secure strategy, to user
Account or network behavior carry out risk control, thus, it is possible to improve the validity of risk control.
The risk control method flow chart that Fig. 3 provides for another embodiment of the application.The executive agent of methods described can
Think the equipment with disposal ability：Server or system or device, e.g., the service end in Fig. 1, as shown in figure 3, described
Method can specifically include：
Step 310, the corresponding event information of risk case that client is sent is received.
Step 320, according to event information and default historical behavior information, the classification of risk case is determined.
Step 330, if the classification of risk case is risky event, step 350 is performed, step 340 is otherwise performed；
Step 340, the event information is abandoned.
Step 350, according to event information, the classification of event information is determined.
Step 360, if the classification of event information belongs to personalized event information, step 370 is performed, step is otherwise performed
390。
Step 370, according to event information, personalized secure strategy is generated.
Step 380, according to personalized secure strategy and default security strategy, user to client and/or similar
The account or network behavior of user carries out risk control.
Step 390, according to event information, the risk class of risk case is obtained.
Step 3100, if risk class meets preparatory condition, step 3120 is performed, step 3110 is otherwise performed.
Step 3110, the event information is abandoned.
Step 3120, according to event information, communication security policy is generated.
Step 3130, according to communication security policy and default security strategy, user and/or other use to client
The account or network behavior at family carry out risk control.
Thus, the individual demand of user can be both met, the mesh of shared data between a plurality of users can also be realized
's.
To sum up, the core concept of the application be exactly change it is traditional by developer according to the historical behavior data of user come
Security strategy is write, and according to the security strategy, account or network behavior to user carry out risk control；But allow use
Family is participated in during this, namely applies the subject of participatory perception, so that service end can be with real-time reception client
The event information of the risk case of biography, and security strategy is generated according to the event information, finally with reference to the security strategy of the generation
And default security strategy, to realize that account or network behavior to user carry out risk control, so as to improve wind
The validity of danger control.
With above-mentioned risk control method accordingly, a kind of risk control device that the embodiment of the present application is also provided, such as Fig. 4 institutes
Show, the device includes：
Receiving unit 401, the corresponding event information of risk case for receiving client transmission.
Determining unit 402, for the event information that is received according to receiving unit 401 and default historical behavior information, really
Determine the classification of risk case.
Generation unit 403, for if it is determined that the classification for the risk case that unit 402 is determined is risky event, then basis
Event information, generates security strategy.
Alternatively, generation unit 403 specifically for：
According to event information, the classification of event information is determined；
If the classification of event information belongs to general purpose event information, according to event information, risk of risk case etc. is obtained
Level；
When risk class meets preparatory condition, according to event information, security strategy is generated.
Alternatively, generation unit 403 also particularly useful for：
Event information is matched with presetting the event information of risk case in memory cell, wherein, memory cell is used
In the event information and the corresponding relation of class information that record at least one default risk case；
When the event information with any default risk case matches, by the event information pair of any default risk case
The class information answered as risk case risk class.
Control unit 404, for the security strategy and default security strategy generated according to generation unit 403, to
The account or network behavior at family carry out risk control, wherein, default security strategy is according to historical behavior message composition.
Herein, the communication security policy of generation can include：
Reminder message is sent to the client of user；Or,
Prohibit the use of the account or forbid performing the network behavior.
Alternatively, described device can also include：Discarding unit 405, if the classification for risk case is devoid of risk thing
Part, then abandon event information.
The function of each functional module of the embodiment of the present application device, can be by each step of above method embodiment come real
Existing, therefore, the specific work process for the device that the application is provided is not repeated again herein.
The risk control device that the application is provided, receiving unit 401 receives the corresponding thing of risk case that client is sent
Part information；Determining unit 402 determines the classification of risk case according to event information and default historical behavior information；If risk
The classification of event is risky event, and generation unit 403 generates security strategy according to event information；Control unit 404 is according to life
Into security strategy and default security strategy, account to user or network behavior carry out risk control.Thus, it is possible to
Realize and effective risk control is carried out to the account or network behavior of user.
Those skilled in the art are it will be appreciated that in said one or multiple examples, work(described in the invention
It is able to can be realized with hardware, software, firmware or their any combination.When implemented in software, can be by these functions
It is stored in computer-readable medium or is transmitted as one or more instructions on computer-readable medium or code.
Above-described embodiment, has been carried out further to the purpose of the present invention, technical scheme and beneficial effect
Describe in detail, should be understood that the embodiment that the foregoing is only the present invention, be not intended to limit the present invention
Protection domain, it is all technical scheme basis on, any modifications, equivalent substitutions and improvements done etc. all should
It is included within protection scope of the present invention.
Claims (10)
1. a kind of risk control method, it is characterised in that including：
Receive the corresponding event information of risk case that client is sent；
According to the event information and default historical behavior information, the classification of the risk case is determined；
If the classification of the risk case is risky event, according to the event information, security strategy is generated；
According to the security strategy of generation and default security strategy, account or network behavior to user carry out risk control
System, wherein, the default security strategy is according to the historical behavior message composition.
2. according to the method described in claim 1, it is characterised in that described according to the event information, generate security strategy, bag
Include：
According to the event information, the classification of the event information is determined；
If the classification of the event information belongs to general purpose event information, according to the event information, the risk case is obtained
Risk class；
When the risk class meets preparatory condition, according to the event information, security strategy is generated.
3. method according to claim 2, it is characterised in that described according to the event information, obtains the risk case
Risk class, including：
The event information is matched with presetting the event information of risk case in memory cell, wherein, the storage is single
Member is used to record the event information of at least one default risk case and the corresponding relation of class information；
When the event information with any default risk case matches, by the event information pair of any default risk case
The class information answered as the risk case risk class.
4. the method according to claim any one of 1-3, it is characterised in that also include：
If the classification of the risk case is devoid of risk event, the event information is abandoned.
5. the method according to claim any one of 1-4, it is characterised in that the communication security policy includes：
Reminder message is sent to the client of the user；Or,
Prohibit the use of the account or forbid performing the network behavior.
6. a kind of risk control device, it is characterised in that including：
Receiving unit, the corresponding event information of risk case for receiving client transmission；
Determining unit, for the event information and the default historical behavior information received according to the receiving unit, it is determined that
The classification of the risk case；
Generation unit, if the classification of the risk case determined for the determining unit is risky event, according to institute
Event information is stated, security strategy is generated；
Control unit, for the security strategy and default security strategy generated according to the generation unit, to the account of user
Family or network behavior carry out risk control, wherein, the default security strategy is according to the historical behavior message composition
's.
7. device according to claim 6, it is characterised in that the generation unit specifically for：
According to the event information, the classification of the event information is determined；
If the classification of the event information belongs to general purpose event information, according to the event information, the risk case is obtained
Risk class；
When the risk class meets preparatory condition, according to the event information, security strategy is generated.
8. device according to claim 7, it is characterised in that the generation unit also particularly useful for：
The event information is matched with presetting the event information of risk case in memory cell, wherein, the storage is single
Member is used to record the event information of at least one default risk case and the corresponding relation of class information；
When the event information with any default risk case matches, by the event information pair of any default risk case
The class information answered as the risk case risk class.
9. the device according to claim any one of 6-8, it is characterised in that described device also includes：Discarding unit, is used for
If the classification of the risk case is devoid of risk event, the event information is abandoned.
10. the device according to claim any one of 6-9, it is characterised in that the communication security policy includes：
Reminder message is sent to the client of the user；Or,
Prohibit the use of the account or forbid performing the network behavior.
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 true CN106953738A (en) | 2017-07-14 |
| CN106953738B 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) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109003090A (en) * | 2018-07-05 | 2018-12-14 | 阿里巴巴集团控股有限公司 | risk control method and device |
| CN109165514A (en) * | 2018-10-16 | 2019-01-08 | 北京芯盾时代科技有限公司 | A kind of risk checking method |
| CN109327433A (en) * | 2018-09-03 | 2019-02-12 | 北京智游网安科技有限公司 | Threat cognitive method and system based on Run-time scenario analysis |
| CN109474515A (en) * | 2018-11-13 | 2019-03-15 | 平安科技（深圳）有限公司 | Mail push method, device, computer equipment and the storage medium of risk case |
| CN110147967A (en) * | 2019-05-28 | 2019-08-20 | 阿里巴巴集团控股有限公司 | Risk prevention system method and device |
| CN110381088A (en) * | 2019-08-21 | 2019-10-25 | 牡丹江师范学院 | A kind of data safety support method based on Internet of Things |
| CN112434214A (en) * | 2020-11-03 | 2021-03-02 | 中国南方电网有限责任公司 | Redis-based operation event pushing method |
| CN113095625A (en) * | 2021-03-17 | 2021-07-09 | 中国民用航空总局第二研究所 | 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 (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102325062A (en) * | 2011-09-20 | 2012-01-18 | 北京神州绿盟信息安全科技股份有限公司 | Abnormal login detecting method and device |
| CN102693384A (en) * | 2012-05-22 | 2012-09-26 | 清华大学 | Method and apparatus for safe self adjustment of browsers |
| CN102722559A (en) * | 2012-05-31 | 2012-10-10 | 奇智软件（北京）有限公司 | Method, device and system for controlling processes of abnormal pages |
| CN103532797A (en) * | 2013-11-06 | 2014-01-22 | 网之易信息技术（北京）有限公司 | Abnormity monitoring method and device for user registration |
| WO2015018314A1 (en) * | 2013-08-05 | 2015-02-12 | Tencent Technology (Shenzhen) Company Limited | Method, device and system for detecting whether account is stolen |
| CN104598595A (en) * | 2015-01-23 | 2015-05-06 | 安一恒通（北京）科技有限公司 | Fraud webpage detection method and corresponding device |
-
2016
- 2016-10-11 CN CN201610887634.2A patent/CN106953738B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102325062A (en) * | 2011-09-20 | 2012-01-18 | 北京神州绿盟信息安全科技股份有限公司 | Abnormal login detecting method and device |
| CN102693384A (en) * | 2012-05-22 | 2012-09-26 | 清华大学 | Method and apparatus for safe self adjustment of browsers |
| CN102722559A (en) * | 2012-05-31 | 2012-10-10 | 奇智软件（北京）有限公司 | Method, device and system for controlling processes of abnormal pages |
| WO2015018314A1 (en) * | 2013-08-05 | 2015-02-12 | Tencent Technology (Shenzhen) Company Limited | Method, device and system for detecting whether account is stolen |
| CN103532797A (en) * | 2013-11-06 | 2014-01-22 | 网之易信息技术（北京）有限公司 | Abnormity monitoring method and device for user registration |
| CN104598595A (en) * | 2015-01-23 | 2015-05-06 | 安一恒通（北京）科技有限公司 | Fraud webpage detection method and corresponding device |
Cited By (13)
| 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 |
| CN109327433A (en) * | 2018-09-03 | 2019-02-12 | 北京智游网安科技有限公司 | Threat cognitive method and system based on Run-time scenario analysis |
| CN109165514A (en) * | 2018-10-16 | 2019-01-08 | 北京芯盾时代科技有限公司 | A kind of risk checking method |
| CN109165514B (en) * | 2018-10-16 | 2019-08-09 | 北京芯盾时代科技有限公司 | A kind of risk checking method |
| CN109474515A (en) * | 2018-11-13 | 2019-03-15 | 平安科技（深圳）有限公司 | Mail push method, device, computer equipment and the storage medium of risk case |
| CN109474515B (en) * | 2018-11-13 | 2022-06-24 | 平安科技（深圳）有限公司 | Risk event mail pushing method and device, computer equipment and storage medium |
| CN110147967A (en) * | 2019-05-28 | 2019-08-20 | 阿里巴巴集团控股有限公司 | Risk prevention system method and device |
| CN110381088A (en) * | 2019-08-21 | 2019-10-25 | 牡丹江师范学院 | A kind of data safety support method based on Internet of Things |
| 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 |
| CN113095625A (en) * | 2021-03-17 | 2021-07-09 | 中国民用航空总局第二研究所 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106953738B (en) | 2020-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106953738A (en) | Risk control method and device | |
| CN104519032B (en) | A kind of security strategy and system of internet account number | |
| CN106549902A (en) | A kind of recognition methods of suspicious user and equipment | |
| CN104519018A (en) | Method, device and system for preventing malicious requests for server | |
| CN106302308B (en) | Trust login method and device | |
| CN104937909A (en) | User authentication | |
| CN103888255A (en) | Identity authentication method, device and system | |
| CN105516133A (en) | User identity verification method, server and client | |
| CN106790129A (en) | A kind of identity authentication method and device | |
| CN103745538A (en) | Password protection method and system of financial account | |
| CN104469768A (en) | User identity verifying method and device based on application software | |
| CN106685940A (en) | Password processing method and server | |
| CN110750784B (en) | Security prevention and control method and system for automatic vending equipment | |
| CN104618322B (en) | Data processing method and device based on immediate communication tool | |
| CN112511484A (en) | U shield safety control management system | |
| CN111859320A (en) | Cross-system login-free method, device, equipment and readable storage medium | |
| CN103841081A (en) | Capability scheduling method and system | |
| CN104702647A (en) | Information request method and information request system | |
| CN110232270A (en) | A kind of method of safety certification, unit and storage medium | |
| CN110135190B (en) | Data management method, server and computer storage medium | |
| CN115987675B (en) | Illegal external connection detection method and device, mobile terminal and storage medium | |
| CN115967565A (en) | Battlefield situation sensing method, system, terminal equipment and storage medium | |
| CN105279414A (en) | Verification device based on fingerprint application and verification method based on fingerprint application | |
| US8818432B2 (en) | Method and integrated routing device for controlling remote systems via short messages | |
| CN109768967A (en) | A kind of credible platform connection system |
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 |