WO2019095449A1 - Method and apparatus for preventing personal information leakage - Google Patents

Abstract

The present invention provides a method for preventing personal information leakage, and in particular a method and apparatus for preventing personal information leakage applied to the field of Internet teaching. The method and apparatus of the present invention select to determine, after a core event is triggered, whether to execute the core event, instead of performing identity authentication when starting a program, cancel the identity authentication every time the program is started, and improve user experience. In addition, a successful identity authentication for the program does not represent that personal information leakage would not occur when sharing a device, and lending the device during use. Therefore, only a series of determinations during the triggering of a core event can effectively monitor and intercept the personal information leakage.

Description

Method and device for preventing leakage of personal information Technical field

The present invention relates to the field of online education technology, and in particular, to a method and apparatus for preventing personal information leakage during an online education process of the Internet.

Background technique

With the development of current communication technologies and the popularization of intelligent devices, the manufacturing costs of intelligent computing devices such as smart phones, tablets, laptops, etc. have generally been reduced, and have become an indispensable part of the daily lives of most ordinary people. component. The use of mobile devices for online learning and further education is becoming more and more popular. It has the characteristics of flexible learning places, personalized learning content, and personalized learning modes. And with the increasing social functions of learning programs, online learning programs are also It also has instant online calls, communication and other functions, and the social itself is private and should be classified as personal sensitive information. Therefore, the function of the online learning program is divided into two parts, one is the course category, this part of the function is not private, and the other is the personal information category, such as academic scores, social learning friends, virtual currency information, and so on. A typical online learning mode in the commuting process in the city allows students to learn online through mobile devices. In the learning process, mobile devices may be loaned to peers who share the same learning hobby. In the process of lending, the course is The function of the class is to allow peers to watch, but personal information is not intended to be leaked. We will conduct unauthorized access or acquisition of personally sensitive information of device owners as personal information disclosure. How to prevent online devices from protecting personal information during lending or sharing is a variety of A technical problem faced by intelligent computing devices.

There is also a need to protect personal information in response to malicious programs (also known as "malware"), which are programs that, when executed by a computer, adversely affect the performance and/or hazard of the computer. Unauthorized instructions for the integrity of the data. As an example, a malicious program can gain access to an application; disrupt computer operations; erase files stored on the computer; collect sensitive information (such as passwords or other personal information); track the behavior of the user of the computer; use the computer for non- Expected operations and so on.

One prior art is to provide a mobile computing device having multiple access modes, the mobile device A lock screen page for accessing the device in the primary access mode or the secondary access mode is displayed on the touch screen display of the device. The primary access mode provides access to several applications of the device, and the secondary access mode provides access to a limited set of applications. The mobile device receives a touch input on the lock screen page to access the device in the secondary access mode. The mobile device unlocks the device to the secondary access mode by allowing access to the set of applications and restricting access to the remaining applications of the plurality of applications. However, this kind of device relies on the device owner's advanced setting of the device, and actively switches the device between the first-level access mode and the second-level access mode, but in real life, many information leaks occur when the device owner is not prepared. If there is no defense, if the primary access mode is not switched to the secondary access mode, sensitive information is leaked from device sharing or borrowing. In addition, this technology can only classify programs at different levels of privacy, but does not distinguish between different levels of privacy within the program. That is to say, the protection function of such devices for personal information is still defective.

There is also a prior art, which is a monitoring method and device for malicious behavior, belonging to the field of monitoring. The method includes: detecting whether an event is triggered; if the detected event is triggered, comparing the detected event with each behavior in the behavior list, and determining whether the detected event conforms to the behavior in the behavior list; The event is detected to be consistent with the behavior in the behavior list, and the behavior is matched with the malicious behavior pre-stored in the behavior library; if the behavior matches the malicious behavior pre-stored in the behavior library, the behavior is determined to be malicious behavior, and the detected behavior is detected. The event is a malicious event; the malicious event in the malicious behavior is intercepted. By adopting a method of automatically intercepting malicious events in malicious behavior, the invention can automatically and effectively identify malicious behaviors and intercept them in real time during the malicious behavior monitoring process. However, this kind of matching behavior is difficult to adapt to rapid changes in malicious behavior. A monitoring device cannot include all kinds of malicious behaviors, and the technology is only theoretically feasible.

Still another prior art provides an application protection method and apparatus for improving application security and improving user experience. The protection method of the application includes receiving first information input by a user, the first information is used to start a first application, and determining whether the first application belongs to a preset application to be spoofed; When the first application belongs to a preset application to be disguised, a preset camouflage interface is displayed to the user, and the camouflage interface is used to indicate that the application is abnormal. This approach improves application security and improves the user experience. Of course, according to the startup mode set by different applications, the first information is not limited to click information, for example. For example, it can also be double-click, select, etc. The biggest problem with this protection method is that it generates a disguised interface that is indistinguishable from any program visitor, which also causes great trouble to the device owner. Each time the selected program is opened, a camouflage interface is generated, and the decryption information needs to be input. It is very inconvenient to carry out the next step, and as the analysis above, most of the functions of many programs do not involve personal information. For the learning program itself, most of the functions are not private, such as specific courses. Content, course schedules, etc., only the part that involves personal information is private. If the program itself is set to a strict level of confidentiality, it is neither necessary nor convenient to operate.

Still another prior art provides an implicit identity authentication method based on natural interaction, the steps comprising: 1) implicitly triggering and enabling an implicit identity authentication process; 2) enabling multiple collection devices to implicitly collect the user's a plurality of biometric information; 3) determining whether biometric information is available for use, and if no biometric information is available, prompting implicit guiding information within the preset number of acquisitions and opening the information related to the guiding information The collecting device collects the biometric information of the user, and continues to determine whether the biometric information that is available is collected; if the biometric information that is available is collected, the collected biometric information is used as the user to be authenticated The feature information is verified and matched with the corresponding pre-stored biometric information; 4) if the matching is consistent, the user is allowed to perform a specific operation; if the matching is inconsistent, the user is prompted not to pass the identity authentication and display the identity authentication. This method can perform natural and high security authentication on the user identity through the implicit identity authentication method in the natural interaction process. Compared with the existing dynamic identity authentication mode, the authentication process is naturally not rigid, without disturbing the user. The implicitly extracting the biometric information to be authenticated for identity authentication, or prompting the user to generate a specific natural reaction through simple implicit guiding prompt information, and then implicitly extracting the biometric information to be authenticated for identity authentication. This technology has greatly improved compared to the existing verification methods, but there are still major flaws, that is, the implicit authentication method is not enough "implicit" because when a series of biological information is collected, if Explicit verification can be started without verification. Explicit verification is essentially a reminder to the operator. This is what the device owner does not want to see. It is more desirable that the entire process be completed under implicit conditions.

In the prior art, there is also a method for identifying a user identity recognition system, which includes the following steps: the system collects user history operation information and operation information and uploads the operation information to the cloud platform, and the cloud platform analyzes and learns the user history operation information to find a user operation habit set. Stored as flag information; the historical operating habit set is iteratively updated as the number of uses of the user increases; when used, the system pairs the user The identity information is verified. If the verification fails, the user access is denied. If the verification is passed, the user operation information is compared with the stored flag information, and if the comparison is successful, the user access is run, otherwise the user access is denied. Suitable for identification. However, according to the recorded user A, the online payment function of the mobile phone is used to open a payment APP, and the user draws a circle on the touch screen of the mobile phone before the payment operation, and then performs a payment operation. The system records this operating habit as a contrast operation in the future, but the accuracy of this gesture is very low, and it is very easy to be observed and imitated. In addition, the gesture itself has no practical significance, it is only now There are technical gesture verifications. For the timing of activation verification, it is also a kind of implicit authentication before the program is started, and it is also indistinguishable. It will be verified every time, which will bring inconvenience to the normal use of the user.

In summary, it can be known that in the prior art, for the protection method of sensitive personal information in the standby device, one is artificially switched in the first state of normal use and the second state of restrictive use, and is restrictive. Use includes a reduced number of programs available, removes programs that include sensitive information, and a restrictive use is a camouflage interface that simply cannot be used, or needs to be decrypted before use, or, in contrast to human switching, is advanced Preset specific programs. Once such a program is triggered, the camouflage interface is automatically opened and can only be further used by human decryption, which makes implicit authentication become dominant and is not desired by the device owner.

Summary of the invention

The object of the present invention is to provide a method and a device for protecting personal information and having sufficient protection against personal information leakage, and the method or device does not significantly increase the burden on the user or the device owner, and throughout the verification process. In, all are implicit verification.

It is an object of the present invention to provide a method for preventing leakage of personal information, the method comprising:

A method of preventing the disclosure of personal information, including:

S1: Start;

S2: start the program;

S3: determining whether a core event is triggered, and if so, entering S4;

S4: determining the operation occurring before the triggering of the core event and the first reservation pre-stored in the behavior library Whether the operation events match, if yes, enter S5, if not enter S6;

S5: Execution of core events;

S6: generating a camouflage interface to provide camouflage information;

S7: End.

Preferably, the step S6 includes:

S601: Generate a first camouflage interface according to the core event, and provide camouflage information;

S602: Determine whether a second predetermined operation event occurs on the first masquerading interface, if yes, execute S5; if not, execute S603:

S603: Generate a second camouflage interface.

Preferably, the step S6 includes:

S601': generating a first camouflage interface according to the core event, and providing camouflage information;

S602': determining whether a second predetermined operation event occurs on the first masquerading interface, and if so, executing 604'; if not, executing S603':

S603': generating a second camouflage interface;

S604': Exit the first camouflage interface and execute S3.

Preferably, performing the core event enables obtaining information requiring protection, and the pre-stored first predetermined operational event is an operation of an actual function possessed by the program.

Preferably, performing the core event enables obtaining information requiring protection, and the pre-stored first predetermined operational event is a combination of operations of actual functions possessed by the program.

A device that prevents disclosure of personal information, including:

a first receiving module, configured to receive a user startup program instruction;

a second receiving module, configured to receive a user trigger core event instruction, a first determining module, configured to determine whether a core event is triggered, and a second determining module, configured to determine an operation and a pre-stored in the behavior library before the triggering of the core event Whether the first predetermined operational event matches;

Storage medium for storing behavior libraries.

Preferably, the method further includes: a third determining module, configured to determine whether a second predetermined operation event occurs on the first camouflage interface.

Beneficial effects:

1. The method for preventing personal information leakage of the present application does not perform identity verification when the program is started, but chooses to judge whether to execute the core event after the core event is triggered, and cancels the verification of the identity every time the startup program is performed. The user's experience, on the other hand, the successful authentication of the program does not mean that the personal information is not leaked when the device is shared and used during the use of the device. Therefore, a series of judgments when triggering the core event can be effective. Monitor and block personal information disclosure.

2. The "predetermined operation" in this application is essentially that the owner of the device habitually records and saves other functions before triggering the core event. When the owner of the device wishes to execute the core event, due to the operational habits Perform the scheduled operation first. If the device is judged to have such a predetermined operation before triggering the core event, it is considered that the owner of the device is performing the corresponding operation to perform the core event normally, otherwise it is considered to be a personal information leak. "Scheduled operation" is a function with substantial functions. It is not a simple gesture operation. The gesture operation is easy to be imitated, but the combination of the function of the essential function, especially the continuous functional operation, is not easily found by others because others cannot The artificially set connection between operations is seen in the use of seemingly normal programs.

3. The application also proposes a scientific method for generating a camouflage interface. Because the implicit identity verification is combined with the first camouflage interface, the device owner himself/herself generates a first camouflage interface due to a misoperation during normal use. Can not be effectively identified, therefore, in order to avoid misleading the normal use of the device owner, here in the environment of the first camouflage interface, a second predetermined operational event is also preset, the second predetermined operational event and device possession The operation of the core event is completely consistent, and the device owner's operating habits are still used for identity verification, and no explicit authentication is performed, and the entire verification process is embodied as implicit verification. The first camouflage interface is placed between two predetermined operational event judgments, which greatly avoids the probability of the device owner's misoperation, and effectively protects the device owner's personal privacy.

DRAWINGS

Figure 1 is a flow chart showing the core operation of the conventional technology;

2 is a flow chart of a first embodiment for preventing leakage of personal information in the present invention;

3 is a flow chart of a second embodiment of preventing personal information leakage in the present invention;

4 is a flow chart of a third embodiment of preventing personal information leakage in the present invention;

5 is a first label menu interface of an example online learning program in the present invention;

6 is a second tab menu interface of an example online learning program in the present invention;

Figure 7 is a third tab menu interface of an exemplary online learning program in the present invention.

Reference numerals: 1, the first label menu; 2, the second label menu; 3, the third label menu.

Detailed ways

Specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It is understood that the embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. Various changes and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention.

In this context, a program represents an application that includes personally sensitive information, and the application includes a variety of functions, the execution of which is called an event, and the core event represents a function in the execution of the application to obtain personally sensitive information. In the prior art, the user generally needs to unlock the device when the device is started or when the screen saver is released. The unlocking operation generally includes verification of the identity. FIG. 1 is a typical operation flow of the prior art. After starting the device, a series of startup programs are executed to execute core events. When the device is shared and the device is borrowed during use, the leakage of personal sensitive information occurs after the identity verification. In this embodiment, the authentication is not performed in the startup program, but the core event is triggered. It is judged whether to execute the core event. This is because verifying the identity every time the program is started is a very complicated operation, which is easy to cause user dissatisfaction. On the other hand, the successful authentication of the program does not mean that the device is shared and used. The leakage of personal information does not occur when the device is borrowed in the process. Only a series of judgments when triggering a core event can effectively monitor and intercept personal information disclosure.

In this embodiment, a logic for forward verification is proposed for the judgment after the core event is triggered. The general verification is to see whether the behavior matches the data in the personal information disclosure behavior database, and if so, it is recognized as personal information. Leakage behavior, so the device can only judge according to the data of the existing database. If it can neither be judged to be legal nor judged to be malicious, it can only be released. But this judgment is very inefficient, and devices often need to update the database frequently to cope with a growing variety of malicious behavior.

This kind of setting is of great significance in practice. It can not only exclude other people's behaviors that trigger core events, but more importantly, it can effectively control the core events of malicious programs in the background. Currently, malicious virus updates are frequent, new viruses. There are endless streams, so many malicious viruses are not collected in the database in time. If only a certain triggering behavior is not recorded in the database, the device will release it. In this way, the possibility that personal sensitive information will be obtained by malicious programs is brought about. In the present invention, the determination as to whether or not to execute the core event is limited to determining whether it satisfies the occurrence of a preset event. This greatly reduces the burden on the device to judge the operation.

Referring to FIG. 2, a method for preventing leakage of personal information includes:

S1: Start; this method of preventing personal information leakage is generally initiated when the device is started or when the device owner releases the lock screen. Because there are many programs in the device that involve sensitive personal information, such as various online learning programs, as long as these programs are launched, it is necessary to prevent personal information from being leaked.

S2: Start the program; as long as any one of the programs involving personal sensitive information is activated, it is necessary to enter the subsequent judgment.

S3: judging whether a core event is triggered, and if so, entering S4; for the above program, many functions do not involve personal information, and the information may be a function of a large number of repeated use by the operator, such as Figure 5-7. It is a typical online learning program in the 1-3 label menu interface, wherein the third tab menu interface involves personal information and is a core event. The "General Function 1", "General Function 2", and "Common Function 3" in the first tab menu interface do not involve personal sensitive information. The common functions can be online search, course search, push news, etc. The function of the information, if the system performs judgment or authentication every time the user uses the first tab menu interface, it will greatly affect the user experience. But for the third tab menu world, this includes the user's big Amount of personal information, such as learning interest friends, friends messages, virtual property and triggering online payment programs, etc., are sensitive personal information. If you want to trigger the third tab menu interface, the system should determine if the device owner is using this feature. Therefore, in S3, if an event involving personal sensitive information is triggered, it will enter the subsequent judgment. If not, the system will not interrupt the user's operation and keep the program running smoothly.

S4: judging whether the operation occurring before the triggering of the core event matches the first predetermined operation event pre-stored in the behavior library, if yes, entering S5, if not entering S6; it needs to be stated that the pre-stored predetermined operation here has It is not a simple hand-scheduled gesture to enter a password or input a fingerprint. In some prior art, the operating habits may include, but are not limited to, an application used by the user,

The user's screen unlock gesture/password, the user's habitual gesture, the user's habitual continuous operation gesture. However, the collection of operating habits in these prior art methods cannot solve the problem of personal information leakage. First, if other applications are used as a precondition for triggering core events, then the core event is also a parallel application, but as mentioned earlier, it is complicated to verify each shipment, and information leakage occurs in a program. Specific functions, rather than the entire program, involve the disclosure of personal information, increasing the level of security or expanding the protection of information can cause a decline in user experience. Entering passwords is explicit; gestures are easy to imitate; fingerprint verification is not an operating habit and is still part of biological information.

Step S4 is intended to be judged in a manner that does not interrupt the user's operation. A predetermined operational event refers to the execution of other functions in an open program or a collection of such functions performed, such as general functions, such as course information. As long as the operator performs a series of predetermined program functions before triggering the core event, the device can determine that the operator is the owner of the device, so that it can enter the next S5, otherwise, the behavior of triggering the core event is considered It is a personal information leak. To further explain, the pre-determined operation in this application corresponds to the function of the actual application. When the user performs this operation, the actual function is completed by the program, which is different from using other programs as pre-operations or using gesture fingerprints, etc. No practical operation.

In the prior art, few techniques pay attention to the operator's habitual operation of the functionality of the application or the connection between the consistency operation and the authentication of the operator identity. Many programs provide more for the operator's habits. User-friendly settings, on the one hand, these programs are designed to allow operators Adjust the UI interface, for example, the operator can delete the buttons that are not used normally, and then add new and commonly used buttons. This reflects the thinking of customizing the UI interface according to personal style. After adjustment, the buttons on the UI interface are more suitable for the operator. On the other hand, many programs actively push information to users. For example, Baidu will push news according to the reader's reading habits. Tmall will push specific types of products according to the operator's search habits. The improved user's reading efficiency can be seen, and the intelligent setting or modification of the program itself according to the operator's habit can improve the operator's user experience. Similarly, in the present embodiment, the "predetermined operation" is essentially that the owner of the device habitually records and saves other functions before triggering the core event. These functions have their own substantive meanings, but there is no mutual relationship between them. Any logical connection, therefore, the combination of these functions or functions as a predetermined operation enables both the operator to perform substantial operations and good implicit authentication, when the owner of the device wishes to perform core events. At the time, the predetermined operation is performed first due to the habit of operation. If the device is judged to have such a predetermined operation before triggering the core event, it is considered that the owner of the device is performing the corresponding operation to enter S5, otherwise it is considered to be a personal information leak. For habitual pre-operations, this does not increase the burden on the user, because it is not used as a determination condition, and the user also uses the function of operating the program in this way. As an example, for FIG. 5, a user is accustomed to trigger a general function in the first tab menu interface, for example, to learn about the latest course introduction, and then trigger the general function 1 to understand the examination time of the corresponding subject, and then enter the third tab menu interface. Trigger personal information 2, such as checking the account balance to decide whether to recharge. Then execute the general function 2 and then execute the general function 1 to enter the "predetermined operation" of the core event of the third tab menu interface. For the "predetermined operation" setting, it can be flexible and variable, which is closely related to the habits of the device owner.

Of course, if necessary, the owner of the device can artificially develop a unique operating habit based on the needs of information security, and then trigger a qualification for the core event for a new type of authentication. This new authentication is different from existing password or fingerprint authentication. The latter is purely authentication, but uses a predetermined operation to verify identity. It is itself a service that can provide the operator with the functions of the program. In addition, it There is no obvious discontinuity in the procedure.

S5: Execute the core event; after a series of judgments, the program will execute the core event, such as displaying various information under the third tab menu interface.

S6: Generate a camouflage interface to provide camouflage information. The significance of generating a camouflage interface is that it will be the whole The operations are performed in an implicit manner, and no prompts or information about the pass or fail of authentication are provided to the person in use. The provision of camouflage interface or camouflage information is prior art, which has been mentioned in the prior art, but in the prior art, the startup or triggering of the camouflage interface is very unscientific, and the first is as long as it is started. A program directly generates a camouflage interface that needs to be decrypted and then used, which will cause great inconvenience to the user. Second, artificially trigger the camouflage interface, but this design can not effectively protect personal information. It can be seen that the generation of the camouflage interface in S6 has a premise. It is not a blind startup program to generate a camouflage interface, nor is it a manual switch. Instead, in the process of using the program, the identity verification is performed without traces, and then the camouflage interface is generated. It is difficult for others to find that they are not the owner of the device when they use the program normally. In the case of implicit authentication, the camouflage interface is also generated after the verification, which is confused by the camouflage interface.

Optionally, executing the core event can obtain information that needs to be protected, and the predetermined operation event is any other function in the program except the core event. Optionally, executing the core event can obtain information that needs to be protected, and the predetermined operation event is a combination of any other function in the program except the core event.

S7: End

As shown in FIG. 3, the step S6 includes:

S601: Generate a first camouflage interface according to the core event, and provide camouflage information;

S602: determining whether a second predetermined operation event occurs on the first masquerading interface, if yes, executing S5; if not, executing S603;

S603: Generate a second camouflage interface.

The second predetermined operational event corresponds to a functional operation of the core event.

Optionally, the implicit authentication can be further performed according to the operation of the operator on the first camouflage interface. In the prior art, there is no technology for using implicit authentication and camouflage interfaces. The inventor found in actual operation that such implicit authentication is too confusing, sometimes even the real device owner is mishandling. In the case, it will be confused by the generated first camouflage interface. To sum up, it is because there is no interaction between the implicit authentication and the user, which is a one-way process of information transmission. In order to eliminate this misuse of the first camouflage interface caused by misoperation, the party The method further includes comparing whether the operation in the environment of the first camouflage interface matches the second predetermined operational event, and if so, the operation before the core operation can be considered as not consistent with the first predetermined operational event, but It's just a misuse. Therefore, S5 can be executed to execute the core event. However, if it fails again in the second implicit authentication, the system will generate a second masquerading interface to provide false information.

For example, if the online learning program is found, if you lend the mobile phone to a friend, let him take a look at the "course information 2" in Figure 6, but the friend accidentally touched the "third label menu interface", and the result is seen. His personal information 2, this happens from time to time but there is no way to protect personal information. However, according to S601-603, first, the owner of the device sets the "third tab menu interface" as the core event, and when the mobile phone lends to the friend, the friend triggers the "second tab menu interface" to be fully usable. However, once a friend clicks on the "3rd tab menu interface", since the predetermined operation is not performed in advance, clicking the "3rd tab menu interface" will generate a false first camouflage interface, when his friend does not know that this is camouflage. The page, all validations are performed in an implicit verification mode.

However, as mentioned above, if the owner of the investment himself becomes the first camouflage interface by mistake, it is difficult for him to discover, but this does not affect the normal use. He only needs to follow the interface at the core event. The habit of operating the corresponding function in the first camouflage interface, or being able to switch back to the real core event in S5. This eliminates the problem of misuse of implicit authentication. Therefore, it is only necessary to design the first camouflage interface according to the interface of the core operation, and check the operation of the user on the first camouflage interface.

As shown in FIG. 4, optionally, the step S6 includes:

S601': generating a first camouflage interface according to the core event, and providing camouflage information;

S602': determining whether a second predetermined operation event occurs on the first masquerading interface, and if so, executing 604'; if not, executing S603':

S603': generating a second camouflage interface;

S604': Exit the first camouflage interface and execute S3.

In this case, if the pass is obtained in the implicit verification of the second predetermined operation event, and then returns to S3, the first predetermined operation event is re-operated. This further enhances the effectiveness of the verification, but the disadvantage is that this non-conformity of the jump is a reminder to remind the user of the device The program did not follow the usual process. However, the inventive concept of the present application is mainly embodied by a combination of a first predetermined operational event, a first masquerading interface, and a second predetermined operational event, such that the completely implicit authentication allows all verification actions to be unknown to the user. In the case of love.

A device that prevents disclosure of personal information, including:

a first receiving module, configured to receive a user startup program instruction;

a second receiving module, configured to receive a user trigger core event instruction, a first determining module, configured to determine whether a core event is triggered, and a second determining module, configured to determine an operation and a pre-stored in the behavior library before the triggering of the core event Whether the first predetermined operational event matches;

Storage medium for storing behavior libraries.

Preferably, the method further includes: a third determining module, configured to determine whether a second predetermined operation event occurs on the first camouflage interface.

Optionally, the method further includes: displaying, by the display module, the first fake interface to the operator when the second determining module is authenticated.

Optionally, the first fake interface is generated according to the core event interface.

You can also apply the method to the field of financial software. When a user uses Alipay, he lists “My” as a core event. He will first click on “Yuebao” and then click “Billbook” as the scheduled event, so that every time he If you want to know the balance information, bank card information, etc. in "My", you should first read "Yuebao" and the bookkeeping book, then click "My" to open "My" smoothly; if it is other People use this device, they can use "Yuebao", "bookkeeping" and other functions, but when you click "My", because there is no pre-requisite for the first scheduled event, the system will generate according to the "My" interface. The first camouflage interface.

However, if the user erroneously operates to generate the first masquerading interface, it is only necessary to perform the "my" corresponding function on the first masquerading interface, that is, the second predetermined event, and then can switch back to the core event or The verification of the first predetermined event is resumed.

Hardware equipment and practical environment

In each of the above examples, the user of the device performs a touch gesture to select the determination. The user can trigger the core event by a touch gesture or an action-based gesture to direct the device. For example, a user taps and presses a function button of an application icon, and those skilled in the art will understand that these are merely exemplary gestures. Other gestures can be used to perform the same function. Different touch gestures (eg, single tap, two taps, single tap, tap and press (ie, press), drag, pinch, stretch press, rotate, etc.) can be exchanged to provide similar Features. Unlike a rotating computing device, the device can be placed face down or face up on a surface, the device can be flipped, or any other motion-based gesture can be passed through one or more orientation/motion detection components of the computing device, such as a gyroscope And accelerometer detected.

In many of the above examples, it is not limited to touch screen type smart computing devices. One of ordinary skill in the art will also recognize that other embodiments for performing on a device having a cursor and cursor controller or other input mechanism may use a cursor controller or other input device to be shown in these examples. The controls interact. Unlike the way in which the application icons are pressed, such devices may allow the user to use the keyboard in conjunction with the cursor controller. These are all mature prior art.

The application described above is implemented as a program that specifies a set of instructions recorded on a computer readable storage medium (also referred to as a computer readable medium). When the instructions are executed by one or more computing or processing units (eg, one or more processors, a processor's core, or other processing unit), the instructions enable one or more processing units to perform the action. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, random access memory (RAM) chips, hard disk drives, erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM) )Wait. The computer readable medium does not include carrier and electrical signals that are transmitted wirelessly or through a wired connection.

In the present specification, the term "program" is intended to include firmware residing in a read-only memory or an application stored in a magnetic storage device, which can be read into a memory for processing by Processing. Moreover, in some embodiments, multiple program inventions can be implemented as sub-portions of larger programs while preserving different program inventions. In some embodiments, multiple program inventions may also be implemented as separate programs.

The devices in this specification include, by way of example, a smart phone, a tablet, a laptop, and the like. The mobile computing device includes one or more processing units, a memory interface, and a peripheral device interface.

The peripheral device interface is coupled to various sensors and subsystems including a camera subsystem, one or more wireless communication subsystems, an audio subsystem, an input/output (I/O) subsystem, and the like. The peripheral device interface enables communication between the processing unit and various peripheral devices. For example, orientation sensing A device (eg, a gyroscope) and an acceleration sensor (eg, an accelerometer) are coupled to the peripheral device interface to facilitate orientation and acceleration functions.

The camera subsystem is coupled to one or more optical sensors (eg, charge coupled device (CCD) optical sensors, complementary metal oxide semiconductor (CMOS) optical sensors, etc.). A camera subsystem coupled to the optical sensor facilitates camera functions, such as image and/or video data capture. The wireless communication subsystem is used to facilitate communication functions. In some embodiments, the wireless communication subsystem includes a radio frequency receiver and transmitter, and an optical receiver and transmitter. These receivers and transmitters of some embodiments are implemented to operate on one or more communication networks, such as a GSM network, a Wi-Fi network, a Bluetooth network, and the like. The audio subsystem is coupled to the speaker to output audio. Additionally, the audio subsystem is coupled to a microphone to facilitate voice-enabled functions such as voice recognition, digital recording, and the like.

The I/O subsystem involves the transfer of input/output peripherals (such as displays, touch screens, etc.) and the processing unit's data bus through a peripheral interface. The input/output subsystem includes a touch screen controller and other input controllers to facilitate transfer between the input/output peripherals and the data bus of the processing unit. As shown, the touch screen controller is coupled to the touch screen. The touch-screen controller uses any multi-touch technology to detect contact and movement on the touch screen. Other input controllers are coupled to other input/control devices, such as one or more buttons. Some embodiments include a proximity touch screen and a corresponding controller that can detect an alternate touch interaction or a proximity touch interaction other than a touch interaction.

The memory interface is coupled to the memory. In some embodiments, the memory includes a combination of volatile memory (eg, high-speed random access memory), non-volatile memory (eg, flash memory), volatile memory, and non-volatile memory and/or Or any other type of memory. The memory stores an operating system (OS). The OS includes instructions for processing basic system services and for performing hardware related tasks.

The memory also includes: communication instructions to facilitate communication with one or more additional devices; graphical user interface instructions to facilitate graphical user interface processing; image processing instructions to facilitate image related processing and functions; facilitate input related (eg, touch input) Process and function input processing instructions; audio processing instructions that facilitate audio-related processes and functions; and camera instructions that facilitate camera-related processes and functions. The above instructions are merely exemplary, and in some embodiments, the memory includes additional and/or other instructions. For example, a memory for a smart phone can include phone instructions that facilitate phone related processes and functions. The above identified instructions do not need to be used as separate programs or modules. Implementation. The various functions of the mobile computing device can be implemented in hardware and/or a program, including in one or more signal processing and/or application specific integrated circuits.

While the illustrated components are shown as separate components, one of ordinary skill in the art will recognize that two or more components can be integrated into one or more integrated circuits. Additionally, two or more components may be coupled together by one or more communication buses or signal lines. Additionally, while a number of functions have been described as being performed by one component, those skilled in the art will recognize that the functionality described above can be split into two or more integrated circuits.

Some embodiments embodying the present invention utilize an electronic system that can be a computer (eg, a desktop computer, a personal computer, a tablet, etc.), a telephone, a PDA, or any other kind of electronic or computing device. Such electronic systems include various types of computer readable media and interfaces for various other types of computer readable media. Electronic systems include buses, processing units, graphics processing units (GPUs), system memories, networks, read-only memories, persistent storage devices, input devices, and output devices.

The bus generally represents all of the systems, peripherals, and chipset buses that are communicatively coupled to many of the internal devices of electronic system 6800. For example, the bus can communicatively connect one or more processing units to read only memory, GPUs, system memory, and persistent storage devices.

The processing unit retrieves the instructions to be executed and the data to be processed from these various memory units in order to perform the processes of the present invention. In various embodiments, one or more of the processing units can be a single processor or a multi-core processor. Some instructions are passed to and executed by the GPU. The GPU can offload various computing instructions or supplement the image processing provided by the processing unit.

A read only memory (ROM) stores static data and instructions required by one or more processing units and other modules of the electronic system. Permanent storage devices, on the other hand, are read and write memory devices. The device is even in an electronic system

Non-volatile memory locations that store instructions and data when closed. Some embodiments of the present invention use mass storage devices, such as magnetic or optical disks and their corresponding hard drives, as permanent storage devices.

As used in this specification and any claims of this patent application, the terms "computer," "server," "processor," and "memory" mean electronic or other technical device. These terms exclude people or Group of people. For the purposes of this specification, the term display or display is meant to be displayed on an electronic device. As used in this specification and any claims of this patent application, the terms "computer readable medium" and "machine readable medium" are fully limited to tangible physical objects that store information in a form readable by a computer. These terms do not include any wireless signals, cable download signals, and any other ephemeral signals.

The preferred embodiments of the present invention have been described above, and are intended to provide a further understanding of the embodiments of the present invention. It is intended to be included within the scope of the appended claims.

Industrial applicability

The method for preventing personal information leakage of the present invention does not perform identity verification when the program is started, but selects whether to perform core events after the core event is triggered, and cancels the authentication of the identity every time the startup program is performed. The experience, on the other hand, the successful authentication of the program does not mean that the personal information is not leaked when the device is shared and used during the use of the device. Therefore, a series of judgments when triggering the core event can be effective for the individual. Information disclosure is monitored and intercepted.

Claims (10)

1. A method for preventing leakage of personal information, comprising:

   S1: Start;

   S2: start the program;

   S3: determining whether a core event is triggered, and if so, entering S4;

   S4: determining whether the operation occurring before the triggering of the core event matches the first predetermined operation event pre-stored in the behavior library, if yes, entering S5, if not entering S6;

   S5: Execution of core events;

   S6: generating a camouflage interface to provide camouflage information;

   S7: End.
2. The method according to claim 1, wherein the step S6 specifically comprises:

   S601: Generate a first camouflage interface according to an interface of the core event, and provide camouflage information;

   S602: determining whether a second predetermined operation event occurs on the first masquerading interface, if yes, executing S5; if not, executing S603;

   S603: Generate a second camouflage interface.

   The second predetermined operational event corresponds to a functional operation of the core event.
3. The method according to claim 1, wherein the step S6 specifically comprises:

   S601': generating a first camouflage interface according to an interface of the core event, and providing camouflage information;

   S602': determining whether a second predetermined operation event occurs on the first masquerading interface, and if so, executing 604'; if not, executing S603':

   S603': generating a second camouflage interface;

   S604': exiting the first camouflage interface, executing S3;

   The second predetermined operational event corresponds to a functional operation of the core event.
4. The method of claim 1 wherein performing said core event enables obtaining information requiring protection, said pre-stored first predetermined operational event being an operation of an actual function of the program.
5. The method of claim 1 wherein performing said core event enables obtaining information requiring protection, said pre-stored first predetermined operational event being a combination of operations of actual functions possessed by the program.
6. A device for preventing leakage of personal information, comprising:

   a first receiving module, configured to receive a user startup program instruction;

   a second receiving module, configured to receive a user trigger core event instruction, a first determining module, configured to determine whether a core event is triggered, and a second determining module, configured to determine an operation and a pre-stored in the behavior library before the triggering of the core event Whether the first predetermined operational event matches;

   Storage medium for storing behavior libraries.
7. The device of claim 6 further comprising:

   The third determining module is configured to determine whether a second predetermined operation event occurs on the first camouflage interface.
8. The device according to claim 6, further comprising: a display module, configured to feed back a first fake interface to the operator when the identity verification of the second determining module is negative.
9. The device according to claim 8, further comprising: the display module generating the first fake interface according to the interface of the core event.
10. The device according to claim 9, further comprising: a display module, configured to: when the third judging module is authenticated to be no, to feed back the second spurious interface to the operator.

Images