WO2016008414A1 - 一种安卓***Activity的安全性确定方法及装置 - Google Patents
一种安卓***Activity的安全性确定方法及装置 Download PDFInfo
- Publication number
- WO2016008414A1 WO2016008414A1 PCT/CN2015/084141 CN2015084141W WO2016008414A1 WO 2016008414 A1 WO2016008414 A1 WO 2016008414A1 CN 2015084141 W CN2015084141 W CN 2015084141W WO 2016008414 A1 WO2016008414 A1 WO 2016008414A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- activity
- target activity
- application
- determining
- interface
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
Definitions
- the present invention relates to the field of mobile terminals, and in particular, to a security method and apparatus for determining an Activity of an Android system.
- an Activity is one of the most basic and most commonly used components of the Android system component (Activity, Service Service, Content Provider Content Provider, Broadcast Receiver Broadcast Receiver), which is mainly responsible for the interaction between the system and the user.
- an Activity is equivalent to an interface, which is used to display various contents to the user on the one hand, and to monitor and respond to the user's operation behavior on the other hand.
- the application provides a security method and device for determining an Activity of an Android system, which is used to determine whether the Activity is running in the foreground is safe.
- the technical solution is as follows:
- a method for determining the security of an Android system activity may include:
- the interface of the application When the interface of the application is detected to be displayed at the forefront of the screen, the interface is corresponding
- the Activity is set as the target Activity, and the feature information of the target Activity is extracted;
- the determining, according to the determination result, whether the target activity is safe includes:
- the target activity is determined to be secure.
- the method further includes: notifying the user that the interface corresponding to the target activity is secure.
- the manner of notifying the user that the interface corresponding to the target activity is secure is:
- a floating icon is displayed on the interface corresponding to the target activity.
- the determining, according to the determination result, whether the target activity is safe includes:
- the feature information of the application corresponding to the target activity is further extracted
- the application corresponding to the target activity is determined to be a non-malicious program.
- the method further includes: notifying the user that the interface corresponding to the target activity is insecure.
- the manner of notifying the user that the interface corresponding to the target activity is insecure is:
- the method further includes: deleting the application.
- the user after determining that the application corresponding to the target activity is a malicious program, the user is asked whether to delete the application, and after receiving the confirmation deletion operation of the user, executing the deletion The steps of the application.
- the feature information includes: a component name of the Activity, a package name of the Activity, and a class name of the Activity.
- the white list is a white list stored locally on the mobile terminal or a white list obtained in advance from the network side.
- the application also provides a security determining device for the Android system activity, which may include:
- a feature information extraction module configured to set an activity corresponding to the interface as a target activity and extract feature information of the target activity when the interface of the application is detected at the forefront of the screen;
- a judging module configured to determine whether the feature information of the extracted activity exists in a pre-built white list
- the determining module is configured to determine whether the target activity is safe according to the determination result.
- the determining module is specifically configured to:
- the target activity is determined to be secure.
- the notification module is further configured to notify the user that the interface corresponding to the target activity is secure if the determining module determines that the Activity is secure.
- the notification module notifies the user that the interface corresponding to the target activity is secure:
- a floating icon is displayed on the interface corresponding to the target activity.
- the device further includes: a malicious program determining module, where the determining module is specifically configured to:
- the application corresponding to the target activity is determined to be a non-malicious program.
- the notification module is further configured to notify the user that the interface corresponding to the target activity is insecure after the malicious program determining module determines that the application corresponding to the target activity is a malicious program.
- the notification module notifies the user that the interface corresponding to the target activity is unsafe:
- the malicious program deletion module is further configured to delete the application after the malicious program determining module determines that the application corresponding to the target activity is a malicious program.
- the method further includes: an inquiry module, configured to: after the malicious program determination module determines that the application corresponding to the target activity is a malicious program, ask the user whether to delete the application, and receive After the user confirms the deletion operation, the malicious program deletion module is triggered to delete the application.
- an inquiry module configured to: after the malicious program determination module determines that the application corresponding to the target activity is a malicious program, ask the user whether to delete the application, and receive After the user confirms the deletion operation, the malicious program deletion module is triggered to delete the application.
- the feature information is specifically: a component name of the Activity, a package name of the Activity, and a class name of the Activity.
- the white list is a white list stored locally on the mobile terminal or a white list obtained in advance from the network side.
- an electronic device including:
- processor a memory, a communication interface, and a bus
- the processor, the memory, and the communication interface are connected by the bus and complete each other Communication between
- the memory stores executable program code
- the processor by reading the executable program code stored in the memory, runs a program corresponding to the executable program code for performing security of any Android system activity provided by the embodiment of the present application. Determine the method.
- the embodiment of the present application further provides a storage medium for storing an application, and the application is used to perform the security determination method of any Android system activity provided by the embodiment of the present application.
- the embodiment of the present application further provides an application program for performing the security determination method of any Android system activity provided by the embodiment of the present application.
- the activity when the interface of the application is displayed at the forefront of the screen, whether the feature information of the corresponding Activity exists in the pre-built white list to determine the security of the Activity, when the feature information of the Activity exists in the When the pre-built whitelist is in place, the activity is determined to be secure. Simple to implement and practical.
- FIG. 1 is a flowchart of a method for determining security of an Android system activity according to an embodiment of the present application
- FIG. 2 is a flowchart of a preferred implementation manner of a method for determining security of an Android system activity according to an embodiment of the present application
- FIG. 3 is a schematic structural diagram of an apparatus for determining security of an Android system activity according to an embodiment of the present application
- FIG. 4 is a schematic structural diagram of a preferred embodiment of an apparatus for determining security of an Android system activity according to an embodiment of the present application.
- the embodiment of the present application provides a method for determining the security of an Android system activity, which may include:
- the activity corresponding to the interface is set as the target activity, and the feature information of the target activity is extracted;
- the execution body of the security determination method of the Android system activity may be a security determining device of an activity in a mobile device installed with an Android system, and the device may be an independent functional entity or may be installed on a mobile device.
- a functional module in the device, the mobile device referred to herein generally refers to a mobile phone, a tablet computer, etc., and the specific form thereof is not required to be limited.
- a method for determining the security of an Android system activity includes:
- the Android system manages the Activity through the Activity stack. It is managed as follows:
- Activity(I) When Activity(I) is started, it is pushed onto the top of the stack of the Activity stack, and its corresponding interface (I) is displayed at the front of the screen. At this time, the interface (I) can interact with the user.
- Activity(II) When started, Activity(II) is pushed onto the top of the stack of the Activity stack, and the Activity(I) is pushed into the second layer of the Activity stack; at this time, the interface corresponding to Activity(II) (II) covers the interface (I) ), displayed at the front of the screen, at this time the interface (II) can interact with the user.
- this management method will bring security risks to users.
- the payment interface is displayed at the forefront of the screen, and the activity corresponding to the payment interface is pushed onto the top of the stack of the Activity stack, and the user can input relevant information on the payment interface to complete the payment.
- the malicious program starts a service (Service) in the background during the running of the system, and the function of the service is to monitor all the processes running in the system, when it listens to the activity corresponding to the payment interface is When pressed into the top of the stack of the Activity stack, it will start a malicious Activity, and push the malicious Activity into the top of the stack of the Activity stack, so that the Activity corresponding to the payment interface is pushed into the second layer of the Activity Stack.
- the pseudo-payment interface corresponding to the malicious activity will cover the real payment interface and be displayed at the forefront of the screen.
- the user will see the pseudo-payment interface corresponding to the malicious activity.
- the pseudo-payment interface is designed to be very similar or even the same as the real payment interface, and the user generally cannot distinguish the authenticity of the payment interface by using the naked eye.
- the time for the pseudo-payment interface to cover the real payment interface is extremely short, and the user cannot perceive the process with the naked eye.
- users often regard the pseudo-payment interface as a real payment interface, and input personal information on the pseudo-payment interface. After confirming the click, the personal information may be sent to the attacker, causing the user's personal information to leak. .
- the process of this malicious activity counterfeiting the real payment interface is hidden and difficult for users to discover.
- the top of the stack of the Activity stack may be first monitored. Because, when the interface of the application is displayed at the front end of the screen, the activity corresponding to the interface is located at the top of the stack of the Activity stack.
- the monitoring can be performed after the user manually starts the security determining device of the activity. It is also possible to set the activity security determining device of the Activity to automatically run every time the booting is performed, so that the security determining device of the Activity automatically monitors the top of the stack of the Activity stack after each booting.
- the specific implementation of this step can be implemented by using various related technical solutions in the prior art, and the present application is not specifically limited herein.
- the Activity When an Activity is monitored and enters the top of the stack of the Activity stack, the Activity is set as the target Activity, and the feature information of the target Activity is extracted.
- the management mode of the Activity stack whenever a new Activity is started, it will be pushed onto the top of the stack. At this time, the device for determining the security of the activity on the top of the stack of the Activity Stack will be this new.
- the Activity is set to the target Activity, and the feature information of the target Activity is extracted.
- the feature information of the Activity mentioned here refers to the feature information that can distinguish an Activity from other Activity. For example, when the component name, package name and class name of an Activity are determined, the Activity can be uniquely determined. Therefore, the component name of the Activity, the package name of the Activity, and the class name of the Activity can be used as the feature information of the Activity.
- the method for extracting the feature information of the target activity is the prior art, and the present application does not describe it in detail herein, and those skilled in the art can implement the related technical solutions in the prior art.
- the white list mentioned here pre-stores the feature information of at least one Activity.
- the security determining device of the Activity extracts the feature information of the target Activity, the feature information is compared with the feature information in the pre-built white list, and is determined. Whether the feature information of the target activity is the same as a feature information in the white list.
- the white list mentioned here may be stored locally on the mobile terminal, or may be stored on the network side, such as a network server.
- the activity security determining device obtains the white list from the network side before comparing, and then compares.
- the advantage of storing the whitelist on the network side is that it can save local disk capacity and also help to update the whitelist in time.
- the comparison can be performed. Therefore, an acquisition time is added as compared with the local storage of the mobile terminal, which results in a relatively long execution time of this step.
- the specific storage method is adopted by a person skilled in the art, and the present invention does not make a selection according to the actual situation. Body definition.
- the target activity is determined to be secure.
- the target activity security can be determined.
- the purpose of determining the target activity security here is specifically that the target activity is the activity that the program starts when the user uses an application, rather than the malicious activity initiated by a malicious program. Since the activity corresponding to a certain feature information in the target activity is the same, and one feature information can uniquely determine an Activity, the target activity can be determined.
- the feature information of the application corresponding to the target activity is further extracted;
- the application corresponding to the target activity is determined to be a non-malicious program.
- the method further includes: S104, after the determining the security of the target activity, notifying the user that the interface corresponding to the target activity is secure.
- the manner of notifying the user that the interface corresponding to the target activity is secure is: displaying a floating icon on the interface corresponding to the target activity.
- a floating icon is displayed on the interface corresponding to the target activity and does not affect the user's viewing and operation.
- the position of the floating icon can be set by the activity security determining device of the Activity, or can be specified by the user.
- the user can be notified of the interface security corresponding to the target activity by using other methods, for example, the interface security corresponding to the target activity can be used by the voice reminder.
- the method is used to notify the user of the interface security corresponding to the target activity, and the person skilled in the art may select according to the actual situation, which is not specifically limited herein.
- the user after determining that the application corresponding to the target activity is a malicious program, the user is notified that the interface corresponding to the target activity is insecure.
- the manner of notifying the user that the interface corresponding to the target activity is unsafe is: displaying prompt information on the interface corresponding to the target activity.
- the content of the prompt information is not limited herein, as long as the content can serve as a warning user.
- the user may be notified that the interface corresponding to the target activity is not secure, for example, the interface corresponding to the target activity may be insecure by means of voice reminding.
- the application may also be deleted.
- an anti-virus software may be triggered to detect and kill the malicious program.
- the application further provides a security determining device for the Android system activity, as shown in FIG. 3, including:
- the feature information extraction module 101 is configured to: when the interface of the application is detected to be displayed at the front end of the screen, set the activity corresponding to the interface as the target activity, and extract feature information of the target activity;
- the determining module 102 is configured to determine whether the feature information of the extracted activity exists in a pre-built white list
- the determining module 103 is configured to determine whether the target activity is safe according to the determination result.
- the feature information of the Activity refers to feature information that can distinguish an Activity from other activities, for example, when the component name, package name, and class name of an Activity are determined, Activity can be uniquely determined. Therefore, the component name of the Activity, the package name of the Activity, and the class name of the Activity can be used as the feature information of the Activity.
- the whitelist may be stored locally on the mobile terminal, or may be stored on the network side, such as a network server or the like.
- the activity security determining device obtains the white list from the network side before comparing, and then compares.
- the advantage of storing the whitelist on the network side is that it can save local disk capacity and also help to update the whitelist in time.
- the comparison can be performed. Therefore, an acquisition time is added as compared with the local storage of the mobile terminal, which results in a relatively long execution time of this step.
- the storage method is specifically selected by a person skilled in the art, and the present invention is not limited thereto.
- the notification module 104 is configured to notify the user that the interface corresponding to the target activity is secure if the determining module determines that the activity is secure.
- the manner in which the notification module 104 notifies the user that the interface corresponding to the target activity is secure may be: displaying a floating icon on the interface at the forefront of the screen.
- the device may further include:
- determining module is specifically configured to:
- the application corresponding to the target activity is determined to be a non-malicious program.
- the notification module 104 is further configured to notify the user that the interface corresponding to the target activity is not after the malicious program determining module determines that the application corresponding to the target activity is a malicious program. Safety.
- the notification module 104 notifies the user that the interface corresponding to the target activity is unsafe, and may display the prompt information on the interface corresponding to the target activity.
- the device may further include a malicious program deletion module, configured to delete the application after the malicious program determining module determines that the application corresponding to the target activity is a malicious program.
- the apparatus may further include an inquiry module, configured to ask the user whether to delete the application after the malicious program determination module determines that the application corresponding to the target activity is a malicious program After receiving the confirmation deletion operation of the user, the malicious program deletion module is triggered to delete the application.
- the feature information is specifically: a component name of the Activity, a package name of the Activity, and a class name of the Activity.
- the white list is a white list stored locally on the mobile terminal or a white list obtained in advance from the network side.
- an electronic device which may include:
- processor a memory, a communication interface, and a bus
- the processor, the memory, and the communication interface are connected by the bus and complete communication with each other;
- the memory stores executable program code
- the processor runs a program corresponding to the executable program code by reading executable program code stored in the memory, and is used to perform security determination of an Android system activity provided by an embodiment of the present application.
- the method for determining the security of an Android system activity provided by the embodiment of the present application may include:
- the activity corresponding to the interface is set as the target activity, and the feature information of the target activity is extracted;
- the embodiment of the present application further provides a storage medium for storing an application, where the application is used to perform a security determination method for an Android system activity provided by an embodiment of the present application;
- the method for determining the security of an Android system activity provided by the example may include:
- the activity corresponding to the interface is set as the target activity, and the feature information of the target activity is extracted;
- the embodiment of the present application further provides an application for executing the security determination method of the Android system activity provided by the embodiment of the present application; wherein the Android system activity provided by the embodiment of the present application is
- the security determination method may include:
- the activity corresponding to the interface is set as the target activity, and the feature information of the target activity is extracted;
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Virology (AREA)
- Telephone Function (AREA)
Abstract
一种安卓***Activity的安全性确定方法及装置,该方法包括:当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息(S101);判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中(S102);并依据判断结果,确定所述目标Activity是否安全(S103)。上述方法通过判断应用程序的界面显示在屏幕最前端时,其对应的Activity的特征信息是否存在于预先构建的白名单中,来确定该Activity的安全性,当该Activity的特征信息存在于预先构建的白名单中时,就确定该Activity安全。实现简单,实用性强。
Description
本申请要求于2014年07月18日提交中国专利局、申请号为201410344495.X发明名称为“一种安卓***Activity的安全性确定方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及移动终端领域,特别涉及一种安卓***Activity的安全性确定方法及装置。
Activity是Android***组件中最基本也是最为常用的四大组件(Activity,Service服务,Content Provider内容提供者,Broadcast Receiver广播接收器)之一,主要负责***与用户之间的交互操作。在Android***中,一个Activity相当于一个界面,该界面一方面用于向用户显示各种内容,另一方面还用于监听并响应用户的操作行为。
在Android***运行过程中,各种***服务或应用程序可能会创建多个Activity,而在某一时刻,***仅允许一个Activity在前台运行,该Activity处于激活状态,其他Activity则处于暂停或停止状态。利用Android***的这一特性,恶意程序可以通过创建Activity来实现以伪造界面替换真实界面,这种手段被称为Activity劫持,利用伪造界面,可以达到骗取点击、甚至盗取用户私有信息等目的。更为严重的是,这种手段利用了Android***的Activity管理机制,具有很强的隐蔽性,不易被发现。因此,如何能确定正在前台运行Activity是否安全是一个亟待解决的问题。
发明内容
本申请提供了一种安卓***Activity的安全性确定方法及装置,用于确定正在前台运行Activity是否安全,技术方案如下:
一种安卓***Activity的安全性确定方法,可以包括:
当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的
Activity设定为目标Activity,并提取目标Activity的特征信息;
判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;
并依据判断结果,确定所述目标Activity是否安全。
在本申请的一种优选实施方式中,所述依据判断结果,确定所述目标Activity是否安全,包括:
在判断结果为是的情况下,确定所述目标Activity安全。
在本申请的一种优选实施方式中,在所述确定所述目标Activity安全后,进一步包括:通知用户所述目标Activity对应的界面安全。
在本申请的一种优选实施方式中,所述通知用户所述目标Activity对应的界面安全的方式为:
在所述目标Activity对应的界面上显示浮动图标。
在本申请的一种优选实施方式中,所述依据判断结果,确定所述目标Activity是否安全,包括:
在判断结果为否的情况下,进一步提取所述目标Activity对应的应用程序的特征信息;
判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;
在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;
在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
在本申请的一种优选实施方式中,在确定所述目标Activity对应的应用程序为恶意程序后,进一步包括:通知用户所述目标Activity对应的界面不安全。
在本申请的一种优选实施方式中,所述通知用户所述目标Activity对应的界面不安全的方式为:
在所述目标Activity对应的界面上显示提示信息。
在本申请的一种优选实施方式中,在确定所述目标Activity对应的应用程序为恶意程序后,进一步包括:删除所述应用程序。
在本申请的一种优选实施方式中,在确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,执行所述删除所述应用程序的步骤。
在本申请的一种优选实施方式中,所述特征信息包括:Activity的组件名、Activity的包名及Activity的类名。
在本申请的一种优选实施方式中,所述白名单为存储于移动终端本地的白名单或预先从网络侧获取的白名单。
本申请同时还提供了一种安卓***Activity的安全性确定装置,可以包括:
特征信息提取模块,用于当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断模块,用于判断所提取的Activity的特征信息是否存在于预先构建的白名单中;
确定模块,用于依据判断结果,确定所述目标Activity是否安全。
在本申请的一种优选实施方式中,所述确定模块具体用于:
在判断结果为是的情况下,确定所述目标Activity安全。
在本申请的一种优选实施方式中,还包括通知模块,用于在所述确定模块确定所述Activity安全的情况下,通知用户所述目标Activity对应的界面安全。
在本申请的一种优选实施方式中,所述通知模块通知用户所述目标Activity对应的界面安全的方式为:
在所述目标Activity对应的界面上显示浮动图标。
在本申请的一种优选实施方式中,该装置还包括:恶意程序判断模块,所述确定模块具体用于:
在判断结果为否的情况下,触发所述恶意程序判断模块进一步提取所述目标Activity对应的应用程序的特征信息;
判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;
在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;
在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
在本申请的一种优选实施方式中,所述通知模块还用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,通知用户所述目标Activity对应的界面不安全。
在本申请的一种优选实施方式中,通知模块通知用户所述目标Activity对应的界面不安全的方式为:
在所述目标Activity对应的界面上显示提示信息。
在本申请的一种优选实施方式中,还包括恶意程序删除模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,删除所述应用程序。
在本申请的一种优选实施方式中,还包括询问模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,触发所述恶意程序删除模块删除所述应用程序。
在本申请的一种优选实施方式中,所述特征信息具体为:Activity的组件名、Activity的包名及Activity的类名。
在本申请的一种优选实施方式中,所述白名单为存储于移动终端本地的白名单或预先从网络侧获取的白名单。
另外,本申请还提供了一种电子设备,包括:
处理器、存储器、通信接口和总线;
所述处理器、所述存储器和所述通信接口通过所述总线连接并完成相互
间的通信;
所述存储器存储可执行程序代码;
所述处理器通过读取所述存储器中存储的可执行程序代码来运行与所述可执行程序代码对应的程序,以用于执行本申请实施例所提供的任意一种安卓***Activity的安全性确定方法。
另外,本申请实施例还提供了一种存储介质,用于存储应用程序,所述应用程序用于执行本申请实施例所提供的任意一种安卓***Activity的安全性确定方法。
另外,本申请实施例还提供了一种应用程序,用于执行本申请实施例所提供的任意一种安卓***Activity的安全性确定方法。
本申请实施例通过判断应用程序的界面显示在屏幕最前端时,其对应的Activity的特征信息是否存在于预先构建的白名单中,来确定该Activity的安全性,当该Activity的特征信息存在于预先构建的白名单中时,就确定该Activity安全。实现简单,实用性强。
为了更清楚地说明本申请实施例和现有技术的技术方案,下面对实施例和现有技术中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本申请实施例一种安卓***Activity的安全性确定方法的流程图;
图2为本申请实施例一种安卓***Activity的安全性确定方法一种优选实施方式的流程图;
图3为本申请实施例一种安卓***Activity的安全性确定装置的结构示意图;
图4为本申请实施例一种安卓***Activity的安全性确定装置的一种优选实施方式的结构示意图。
本申请实施例提供了一种安卓***Activity的安全性确定方法,可以包括:
当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;
并依据判断结果,确定所述目标Activity是否安全。
通过判断应用程序的界面显示在屏幕最前端时,其对应的Activity的特征信息是否存在于预先构建的白名单中,来确定该Activity的安全性,当该Activity的特征信息存在于预先构建的白名单中时,就确定该Activity安全。实现简单,实用性强。
上述一种安卓***Activity的安全性确定方法的执行主体,可以是一个安装有安卓***的移动设备中的Activity的安全性确定装置,该装置可以是一个独立的功能实体,也可以是安装于移动设备中的一个功能模块,这里所说的移动设备,一般指手机、平板电脑等,其具体形式本申请并不需要进行限定。
为了使本领域技术人员更好地理解本申请中的技术方案,下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行详细地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都应当属于本申请保护的范围。
如图1所示,一种安卓***Activity的安全性确定方法,包括:
S101,当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息。
在现有技术中,Android***是通过Activity栈来管理Activity的。其管理方式如下:
当Activity(Ⅰ)被启动时,它被压入Activity栈的栈顶,其对应的界面(Ⅰ)显示在屏幕最前端,此时界面(Ⅰ)可以和用户进行交互。当一个新的Activity(Ⅱ)
被启动时,Activity(Ⅱ)被压入Activity栈的栈顶,并将Activity(Ⅰ)压入到Activity栈的第二层;此时,Activity(Ⅱ)对应的界面(Ⅱ)覆盖界面(Ⅰ),显示在屏幕最前端,此时界面(Ⅱ)可以和用户进行交互。但是,这种管理方式会给用户带来安全隐患。
例如,当用户打开支付界面进行支付时,支付界面显示在屏幕的最前端,支付界面对应的Activity被压入Activity栈的栈顶,用户可以在支付界面上输入相关信息,完成支付。
如果移动终端中存在一个恶意程序,该恶意程序在***运行期间在后台启动一个服务(Service),该服务的作用是对***中运行的所有进程进行监听,当它监听到支付界面对应的Activity被压入Activity栈的栈顶时,它会启动一个恶意Activity,并将该恶意Activity压入Activity栈的栈顶,从而将支付界面对应的Activity压入到Activity栈的第二层。相应的,该恶意Activity对应的伪支付界面将覆盖真正的支付界面,显示在屏幕的最前端。
此时,用户看到的将是该恶意Activity对应的伪支付界面,一般情况下,伪支付界面设计成与真正的支付界面非常相似甚至相同,用户使用肉眼一般无法分辨支付界面的真伪。而且伪支付界面覆盖真正的支付界面的时间极短,用户肉眼无法感知这一过程。正是由于上述两种原因,用户往往将伪支付界面当成真正的支付界面,并在伪支付界面上输入个人信息,确认点击后,个人信息就可能被发送到了攻击者处,造成用户个人信息泄露。这种恶意Activity仿造真正的支付界面的过程很隐蔽,用户难以发现。
根据上述的描述,在本步骤的具体实施过程中,可以首先要对Activity栈的栈顶进行监听。因为,当应用程序的界面显示在屏幕最前端时,此界面对应的Activity是位于Activity栈的栈顶的。
监听可以在用户手动启动Activity的安全性确定装置后进行。也可以将Activity的安全性确定装置设置为每次开机自动运行,这样,每次开机后,Activity的安全性确定装置就会自动对Activity栈的栈顶进行监听。本步骤的具体实施方案可以采用现有技术中各种相关的技术方案实现,本申请在这里不作具体限制。
当监听到一个Activity进入所述Activity栈的栈顶时,将该Activity设定为目标Activity,并提取所述目标Activity的特征信息。
根据Activity栈的管理方式,每当一个新的Activity被启动,它会被压入栈的栈顶,此时,正在对Activity栈的栈顶进行监听的Activity安全性的确定装置就会将这个新的Activity设定为目标Activity,并提取目标Activity的特征信息。
这里所说的Activity的特征信息指的是能将一个Activity与其它Activity区分开的特征信息,例如,当一个Activity的的组件名、包名及类名确定时,该Activity就可以被唯一确定。所以,可以将Activity的组件名、Activity的包名及Activity的类名一起作为Activity的特征信息。
当然,可以理解的是,其它能将一个Activity与其它Activity区分开的特征信息都可以应用在本申请的技术方案中,本申请在此不一一列举,本领域技术人员可以根据实际情况进行选择。
由于提取目标Activity的特征信息的方法为现有技术,本申请在此不作详细描述,本领域技术人员可以根据现有技术中的相关技术方案实现。
S102,判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中。
这里所说的白名单会预先存储至少一个Activity的特征信息,当Activity的安全性确定装置提取目标Activity的特征信息后,将此特征信息与预先构建的白名单中的特征信息进行比较,并判断目标Activity的特征信息是否与白名单中的某个特征信息相同。
这里所说的白名单可以存储于移动终端本地,也可以存储于网络侧,例如网络服务器等。当白名单存储于网络侧时,Activity的安全性确定装置在进行比较之前,先从网络侧获取白名单,然后再进行比较。白名单存储于网络侧的好处是可以节省本地磁盘容量,也有利于及时更新白名单。但是由于需要先从网络侧获取白名单后,才能进行比较,所以与存储于移动终端本地相比,要增加一个获取时间,导致本步骤的执行时间相对较长。具体采用哪种存储方式,本领域技术人员可以根据实际情况进行选择,本申请在此不作具
体限定。
S103,并依据判断结果,确定所述目标Activity是否安全。
在判断结果为是的情况下,确定所述目标Activity安全。
即当判断的结果为目标Activity的特征信息与白名单中的某个特征信息完全一致时,就可以确定目标Activity安全。
这里所说的确定目标Activity安全,具体指的是目标Activity是用户在使用一个应用程序时,该程序启动的Activity,而不是某个恶意程序启动的恶意Activity。由于目标Activity与白名单中所述某个特征信息对应的Activity是相同的,且一个特征信息可以唯一的确定一个Activity,因此可以确定目标Activity安全。
当比较的结果为目标Activity的特征信息与白名单中的某个特征信息不完全一致时,就无法确定目标Activity是不否安全。
针对上述问题,在本申请的一种优选实施方式中,在判断结果为否的情况下,进一步提取所述目标Activity对应的应用程序的特征信息;
判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;
在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;
在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
在本申请的一种优选实施方式中,如图2所示,还包括S104,在所述确定所述目标Activity安全后,通知用户所述目标Activity对应的界面安全。
通知用户所述目标Activity对应的界面安全的方式为:在所述目标Activity对应的界面上显示浮动图标。
具本来说,当确定所述目标Activity安全后,在目标Activity对应的界面上且不影响用户观看和操作的位置上显示浮动图标。浮动图标的位置可以由Activity的安全性确定装置自行设定,也可以由用户指定。当用户看到当前界
面上显示出所述示浮动图标后,就知道当前显示的界面是其正在使用的应用程序中的一个Activity对应的界面,并不是由恶意程序伪造的界面。这样,用户就可以放心的在该界面上进行相应的操作。
当然,可以理解的是,还可以采用其它的方式来通知用户所述目标Activity对应的界面安全,例如可以通过声音提醒的方式来户所述目标Activity对应的界面安全。
具体采用何种方式来通知用户所述目标Activity对应的界面安全,本领域技术人员可能根据实际情况进行选择,本申请在此不作具体限定。
在本申请的一种优选实施方式中,在确定所述目标Activity对应的应用程序为恶意程序后,通知用户所述目标Activity对应的界面不安全。
通知用户所述目标Activity对应的界面不安全的方式为:在所述目标Activity对应的界面上显示提示信息。
其中,提示信息的内容本申请在此不需要进行限定,只要该内容能起到警示用户的作用即可。
当然,可以理解的是,还可以采用其它的方式来通知用户所述目标Activity对应的界面不安全,例如可以通过声音提醒的方式来户所述目标Activity对应的界面不安全。
在本申请的一种优选实施方式中,在确定所述目标Activity对应的应用程序为恶意程序后,还可以删除所述应用程序。
在具体实施过程中,在确定所述目标Activity对应的应用程序为恶意程序后,可以触发一个杀毒软件对该恶意程序进行查杀。
当然,为了防误杀的情况发生,在确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,再执行所述删除所述应用程序的步骤。
需要说明的是,上述方法的各实施方式,既可以单独实施,也可以组合在一起实施,具体采用何种实施方式,本领域技术人员可以根据实际情况进行选择,本申请在此不作具体限定。
相应于上面的方法实施例,本申请还提供了一种安卓***Activity的安全性确定装置,如图3所示,包括:
特征信息提取模块101,用于当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断模块102,用于判断所提取的Activity的特征信息是否存在于预先构建的白名单中;
确定模块103,用于依据判断结果,确定所述目标Activity是否安全。
在本申请的一种优选实施方式中,Activity的特征信息指的是能将一个Activity与其它Activity区分开的特征信息,例如,当一个Activity的的组件名、包名及类名确定时,该Activity就可以被唯一确定。所以,可以将Activity的组件名、Activity的包名及Activity的类名一起作为Activity的特征信息。
在本申请的一种优选实施方式中,白名单可以存储于移动终端本地,也可以存储于网络侧,例如网络服务器等。当白名单存储于网络侧时,Activity的安全性确定装置在进行比较之前,先从网络侧获取白名单,然后再进行比较。白名单存储于网络侧的好处是可以节省本地磁盘容量,也有利于及时更新白名单。但是由于需要先从网络侧获取白名单后,才能进行比较,所以与存储于移动终端本地相比,要增加一个获取时间,导致本步骤的执行时间相对较长。具体采用哪种存储方式,本领域技术人员可以根据实际情况进行选择,本申请在此不作具体限定。
在本申请的一种优选实施方式中,图如4还所示,包括通知模块104,用于在所述确定模块确定所述Activity安全的情况下,通知用户所述目标Activity对应的界面安全。
在实际应用中,所述通知模块104通知用户所述目标Activity对应的界面安全的方式可以为:在所述屏幕最前端的界面上显示浮动图标。
在本申请的一种优选实施方式中,该装置还可以包括:
恶意程序判断模块,所述确定模块具体用于:
在判断结果为否的情况下,触发所述恶意程序判断模块进一步提取所述目标Activity对应的应用程序的特征信息;
判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;
在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;
在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
在本申请的一种优选实施方式中,所述通知模块104还用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,通知用户所述目标Activity对应的界面不安全。
在实际应用中,所述通知模块104通知用户所述目标Activity对应的界面不安全的方式可以为:在所述目标Activity对应的界面上显示提示信息。
在本申请的一种优选实施方式中,该装置还可以包括恶意程序删除模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,删除所述应用程序。
在本申请的一种优选实施方式中,该装置还可以包括询问模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,触发所述恶意程序删除模块删除所述应用程序。
在本申请的一种优选实施方式中,所述特征信息具体为:Activity的组件名、Activity的包名及Activity的类名。
在本申请的一种优选实施方式中,所述白名单为存储于移动终端本地的白名单或预先从网络侧获取的白名单。
可以理解的是,上述装置的各实施方式,既可以单独实施,也可以组合在一起实施,具体采用何种实施方式,本领域技术人员可以根据实际情况进行选择,本申请在此不作具体限定。
另外,本申请实施例还提供了一种电子设备,可以包括:
处理器、存储器、通信接口和总线;
所述处理器、所述存储器和所述通信接口通过所述总线连接并完成相互间的通信;
所述存储器存储可执行程序代码;
所述处理器通过读取所述存储器中存储的可执行程序代码来运行与所述可执行程序代码对应的程序,以用于执行本申请实施例所提供的一种安卓***Activity的安全性确定方法;其中,本申请实施例所提供的一种安卓***Activity的安全性确定方法可以包括:
当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;
并依据判断结果,确定所述目标Activity是否安全。
另外,本申请实施例还提供了一种存储介质,用于存储应用程序,所述应用程序用于执行本申请实施例所提供的一种安卓***Activity的安全性确定方法;其中,本申请实施例所提供的一种安卓***Activity的安全性确定方法可以包括:
当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;
并依据判断结果,确定所述目标Activity是否安全。
另外,本申请实施例还提供了一种应用程序,用于执行本申请实施例所提供的一种安卓***Activity的安全性确定方法;其中,本申请实施例所提供的一种安卓***Activity的安全性确定方法可以包括:
当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;
判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;
并依据判断结果,确定所述目标Activity是否安全。
需要说明的是,在本文中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述,各个实施例之间相同相似的部分互相参见即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于装置实施例而言,由于其基本相似于方法实施例,所以描述的比较简单,相关之处参见方法实施例的部分说明即可。
本领域普通技术人员可以理解实现上述方法实施方式中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,所述的程序可以存储于计算机可读取存储介质中,这里所称得的存储介质,如:ROM/RAM、磁碟、光盘等。
以上所述仅为本申请的较佳实施例而已,并不用以限制本申请,凡在本申请的精神和原则之内,所做的任何修改、等同替换、改进等,均应包含在本申请保护的范围之内。
Claims (22)
- 一种安卓***Activity的安全性确定方法,其特征在于,包括:当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;判断所提取的目标Activity的特征信息是否存在于预先构建的白名单中;并依据判断结果,确定所述目标Activity是否安全。
- 如权利要求1所述的方法,其特征在于,所述依据判断结果,确定所述目标Activity是否安全,包括:在判断结果为是的情况下,确定所述目标Activity安全。
- 如权利要求2所述的方法,其特征在于,在所述确定所述目标Activity安全后,进一步包括:通知用户所述目标Activity对应的界面安全。
- 如权利要求3所述的方法,其特征在于,所述通知用户所述目标Activity对应的界面安全的方式为:在所述目标Activity对应的界面上显示浮动图标。
- 如权利要求1所述的方法,其特征在于,所述依据判断结果,确定所述目标Activity是否安全,包括:在判断结果为否的情况下,进一步提取所述目标Activity对应的应用程序的特征信息;判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
- 如权利要求5所述的方法,其特征在于,在确定所述目标Activity对应的应用程序为恶意程序后,进一步包括:通知用户所述目标Activity对应的界 面不安全。
- 如权利要求6所述的方法,其特征在于,所述通知用户所述目标Activity对应的界面不安全的方式为:在所述目标Activity对应的界面上显示提示信息。
- 如权利要求5所述的方法,其特征在于,在确定所述目标Activity对应的应用程序为恶意程序后,进一步包括:删除所述应用程序。
- 如权利要求8所述的方法,其特征在于,在确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,执行所述删除所述应用程序的步骤。
- 如权利要求1-4中任意一项所述的方法,其特征在于,所述特征信息包括:Activity的组件名、Activity的包名及Activity的类名。
- 如权利要求1-4中任意一项所述的方法,其特征在于,所述白名单为存储于移动终端本地的白名单或预先从网络侧获取的白名单。
- 一种安卓***Activity的安全性确定装置,其特征在于,包括:特征信息提取模块,用于当检测到应用程序的界面显示在屏幕最前端时,将所述界面对应的Activity设定为目标Activity,并提取目标Activity的特征信息;判断模块,用于判断所提取的Activity的特征信息是否存在于预先构建的白名单中;确定模块,用于依据判断结果,确定所述目标Activity是否安全。
- 如权利要求12所述的装置,其特征在于,所述确定模块具体用于:在判断结果为是的情况下,确定所述目标Activity安全。
- 如权利要求12所述的装置,其特征在于,还包括通知模块,用于在所述确定模块确定所述Activity安全的情况下,通知用户所述目标Activity对应的界面安全。
- 如权利要求14所述的装置,其特征在于,所述通知模块通知用户所 述目标Activity对应的界面安全的方式为:在所述目标Activity对应的界面上显示浮动图标。
- 如权利要求12所述的装置,其特征在于,还包括:恶意程序判断模块,所述确定模块具体用于:在判断结果为否的情况下,触发所述恶意程序判断模块进一步提取所述目标Activity对应的应用程序的特征信息;判断所提取的应用程序的特征信息是否存在于预先构建的黑名单中;在判断结果为是的情况下,确定所述目标Activity对应的应用程序为恶意程序;在判断结果为否的情况下,确定所述目标Activity对应的应用程序为非恶意程序。
- 如权利要求16所述的装置,其特征在于,所述通知模块还用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,通知用户所述目标Activity对应的界面不安全。
- 如权利要求17所述的装置,其特征在于,通知模块通知用户所述目标Activity对应的界面不安全的方式为:在所述目标Activity对应的界面上显示提示信息。
- 如权利要求16所述的装置,其特征在于,还包括恶意程序删除模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,删除所述应用程序。
- 如权利要求19所述的装置,其特征在于,还包括询问模块,用于在所述恶意程序判断模块确定所述目标Activity对应的应用程序为恶意程序后,询问用户是否删除所述应用程序,在接收到用户的确认删除操作后,触发所述恶意程序删除模块删除所述应用程序。
- 如权利要求12-15中任意一项所述的装置,其特征在于,所述特征信息具体为:Activity的组件名、Activity的包名及Activity的类名。
- 如权利要求12-15中任意一项所述的装置,其特征在于,所述白名单为存储于移动终端本地的白名单或预先从网络侧获取的白名单。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410344495.XA CN104123498B (zh) | 2014-07-18 | 2014-07-18 | 一种安卓***Activity的安全性确定方法及装置 |
CN201410344495.X | 2014-07-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016008414A1 true WO2016008414A1 (zh) | 2016-01-21 |
Family
ID=51768906
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/084141 WO2016008414A1 (zh) | 2014-07-18 | 2015-07-15 | 一种安卓***Activity的安全性确定方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN104123498B (zh) |
WO (1) | WO2016008414A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105930720A (zh) * | 2016-05-05 | 2016-09-07 | 北京元心科技有限公司 | 一种实现与设备安全人机交互的方法和*** |
CN114489841A (zh) * | 2022-01-14 | 2022-05-13 | 湖南小算科技信息有限公司 | 一种快速检测安卓***幽灵进程限制的方法 |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104123498B (zh) * | 2014-07-18 | 2017-12-05 | 广州猎豹网络科技有限公司 | 一种安卓***Activity的安全性确定方法及装置 |
CN104598822A (zh) * | 2015-01-15 | 2015-05-06 | 百度在线网络技术(北京)有限公司 | 应用程序的检测方法及装置 |
US9904783B2 (en) | 2015-02-09 | 2018-02-27 | Lenovo (Beijing) Co., Ltd. | Information processing method and electronic device |
CN104700032B (zh) * | 2015-02-09 | 2018-11-13 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
CN105119903B (zh) * | 2015-07-21 | 2019-03-08 | 北京奇虎科技有限公司 | 在局域网中处理恶意程序的方法及装置 |
CN105160212B (zh) * | 2015-09-29 | 2018-10-12 | 上海斐讯数据通信技术有限公司 | 应用的安全保护方法及*** |
CN105611046B (zh) * | 2015-12-17 | 2016-11-23 | 福建六壬网安股份有限公司 | 一种策略定制的安卓手机安全保护***及其保护方法 |
CN106227585B (zh) * | 2016-05-31 | 2020-02-14 | 北京金山安全软件有限公司 | 一种应用程序启动方法、装置及设备 |
CN106650442B (zh) * | 2016-10-31 | 2020-06-23 | 维沃移动通信有限公司 | 一种信息的安全控制方法及移动终端 |
CN108197462A (zh) * | 2016-12-08 | 2018-06-22 | 武汉安天信息技术有限责任公司 | 一种安卓***下勒索应用检测***及方法 |
CN106778248B (zh) * | 2016-12-26 | 2020-07-14 | 北京奇虎科技有限公司 | 应用程序Activity启动的方法和装置 |
CN107995156A (zh) * | 2017-10-18 | 2018-05-04 | 东软集团股份有限公司 | 页面劫持处理方法及装置、存储介质、电子设备 |
CN107992745A (zh) * | 2017-11-29 | 2018-05-04 | 暨南大学 | 一种基于安卓平台的界面劫持应对方法 |
CN108133137B (zh) * | 2017-12-13 | 2021-11-23 | 北京奇虎科技有限公司 | 智能终端中的界面安全性检测方法和装置 |
CN110414226A (zh) * | 2018-04-28 | 2019-11-05 | 北京安天网络安全技术有限公司 | 一种基于关键目标防护的安全维护方法及*** |
CN114397982A (zh) | 2018-11-26 | 2022-04-26 | 华为技术有限公司 | 一种应用显示方法及电子设备 |
CN110020530B (zh) * | 2018-12-24 | 2023-07-04 | ***股份有限公司 | 用于确定应用程序在运行时的安全性的方法及其装置 |
CN110896540A (zh) * | 2019-11-21 | 2020-03-20 | 国网辽宁省电力有限公司电力科学研究院 | 移动互联网客户端安全评估工具、方法、计算机设备及存储介质 |
CN113157377B (zh) * | 2021-05-20 | 2023-06-27 | 读书郎教育科技有限公司 | 一种Android***实现对应用部分管控的方法及设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120096519A1 (en) * | 2009-06-24 | 2012-04-19 | Nokia Corporation | Methods and Apparatuses for Avoiding Denial of Service Attacks By Rogue Access Points |
CN102710645A (zh) * | 2012-06-06 | 2012-10-03 | 珠海市君天电子科技有限公司 | 一种钓鱼网站检测方法及其检测*** |
CN103065092A (zh) * | 2012-12-24 | 2013-04-24 | 公安部第一研究所 | 一种拦截可疑程序运行的方法 |
CN103617387A (zh) * | 2013-11-25 | 2014-03-05 | 北京奇虎科技有限公司 | 一种防止自动安装应用程序的方法及装置 |
CN104123498A (zh) * | 2014-07-18 | 2014-10-29 | 广州金山网络科技有限公司 | 一种安卓***Activity的安全性确定方法及装置 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102831338B (zh) * | 2012-06-28 | 2015-09-30 | 北京奇虎科技有限公司 | 一种Android应用程序的安全检测方法及*** |
-
2014
- 2014-07-18 CN CN201410344495.XA patent/CN104123498B/zh not_active Expired - Fee Related
-
2015
- 2015-07-15 WO PCT/CN2015/084141 patent/WO2016008414A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120096519A1 (en) * | 2009-06-24 | 2012-04-19 | Nokia Corporation | Methods and Apparatuses for Avoiding Denial of Service Attacks By Rogue Access Points |
CN102710645A (zh) * | 2012-06-06 | 2012-10-03 | 珠海市君天电子科技有限公司 | 一种钓鱼网站检测方法及其检测*** |
CN103065092A (zh) * | 2012-12-24 | 2013-04-24 | 公安部第一研究所 | 一种拦截可疑程序运行的方法 |
CN103617387A (zh) * | 2013-11-25 | 2014-03-05 | 北京奇虎科技有限公司 | 一种防止自动安装应用程序的方法及装置 |
CN104123498A (zh) * | 2014-07-18 | 2014-10-29 | 广州金山网络科技有限公司 | 一种安卓***Activity的安全性确定方法及装置 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105930720A (zh) * | 2016-05-05 | 2016-09-07 | 北京元心科技有限公司 | 一种实现与设备安全人机交互的方法和*** |
CN114489841A (zh) * | 2022-01-14 | 2022-05-13 | 湖南小算科技信息有限公司 | 一种快速检测安卓***幽灵进程限制的方法 |
CN114489841B (zh) * | 2022-01-14 | 2023-07-25 | 湖南小算科技信息有限公司 | 一种快速检测安卓***幽灵进程限制的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN104123498A (zh) | 2014-10-29 |
CN104123498B (zh) | 2017-12-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016008414A1 (zh) | 一种安卓***Activity的安全性确定方法及装置 | |
CN104092542B (zh) | 一种账号登录方法、装置及*** | |
US11055406B2 (en) | Application security protection method, terminal, and storage medium | |
WO2016101384A1 (zh) | 基于双***切换的数据安全处理方法及装置 | |
TWI516972B (zh) | 應用安全驗證方法、應用伺服器、應用用戶端及系統 | |
US20060101128A1 (en) | System for preventing keystroke logging software from accessing or identifying keystrokes | |
WO2012142938A1 (zh) | 一种保证用户网络安全性的方法及客户端 | |
CN104268475B (zh) | 一种运行应用程序的*** | |
US20150101055A1 (en) | Method, system and terminal device for scanning virus | |
JP2015523663A (ja) | メッセージを処理するための方法およびデバイス | |
WO2017036345A1 (zh) | 一种信息输入方法和装置 | |
WO2017166689A1 (zh) | 一种隐私保护的方法及装置 | |
US9378374B2 (en) | Method and device for prompting program uninstallation | |
CN105930726A (zh) | 一种恶意操作行为的处理方法及用户终端 | |
CN106600279A (zh) | 一种基于指纹识别的安全支付方法及*** | |
CN104243708A (zh) | 一种移动终端及其防盗方法和装置 | |
WO2016197827A1 (zh) | 一种恶意捆绑软件的处理方法和装置 | |
CN108108618B (zh) | 伪造攻击的应用界面检测方法及装置 | |
CN106778173B (zh) | 一种基于智能操作***的应用锁设置的方法及装置 | |
WO2016180234A1 (zh) | 一种安全环境构建方法和装置 | |
US8677495B1 (en) | Dynamic trap for detecting malicious applications in computing devices | |
CN104298924A (zh) | 确保***安全的方法、确保***安全的装置和终端 | |
CN106102011A (zh) | 一种终端定位处理的方法、装置以及终端 | |
CN104125130A (zh) | 一种安全提醒方法、装置及通信*** | |
CN108989298B (zh) | 一种设备安全监控方法、装置及计算机可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15821479 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 23/05/2017 ) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15821479 Country of ref document: EP Kind code of ref document: A1 |