CN119180030A

CN119180030A - Risk management method, device, storage medium and electronic device

Info

Publication number: CN119180030A
Application number: CN202410117593.3A
Authority: CN
Inventors: 王宝林; 张倞诚; 张云鹏
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2024-01-26
Filing date: 2024-01-26
Publication date: 2024-12-24

Abstract

The disclosure provides a risk management and control method, a device, a storage medium and electronic equipment, wherein the method comprises the steps of obtaining operation data when a target application in the electronic equipment executes at least partial target operation, obtaining pre-stored risk characteristic data, wherein the risk characteristic data are data generated when the target application executes illegal operation by utilizing a system vulnerability in the electronic equipment, and executing management and control on the target operation based on comparison results of the operation data and the risk characteristic data. The method provided by the embodiment of the disclosure is beneficial to improving the safety of the operating system in the electronic equipment.

Description

Risk management and control method and device, storage medium and electronic equipment

Technical Field

The technical scheme of the disclosure relates to the technical field of data security, in particular to a risk management and control method, a risk management and control device, a storage medium and electronic equipment.

Background

The electronic equipment is provided with an application (simply referred to as a system application) of the system, and after the user takes the electronic equipment, the user can additionally install some third-party applications according to own use requirements. For example, when the electronic device is a mobile phone, common system applications include a mobile phone manager, application authority management, short messages, and the like, and common third party applications include short video playing software, picture repair software, and the like.

The system application is an application carried by the electronic equipment when the electronic equipment leaves a factory, the reliability is high, so the system application generally has high authority, the third party application is provided by other manufacturers, the reliability is unknown, and the third party application generally has low authority.

When a user runs a third party application in an electronic device, the third party application is typically granted access to the system application, such as access to an address book, access to a user album, access to user identity information, and so on. This makes it easy for an illegal person to perform some illegal operations using the interactive relationship between the third party application and the system application after discovering the system vulnerability. Based on this, it is desirable to provide a solution.

Disclosure of Invention

In view of this, the disclosure provides a risk management method, a risk management device, a storage medium and an electronic device, which are helpful to improve the security of an operating system in the electronic device.

According to a first aspect of embodiments of the present disclosure, there is provided a risk management method, the method including:

Acquiring operation data when a target application in electronic equipment executes at least part of target operation, and acquiring pre-stored risk characteristic data, wherein the risk characteristic data is data generated when the target application executes illegal operation by utilizing a system vulnerability in the electronic equipment;

And executing control on the target operation based on the comparison result of the operation data and the risk characteristic data.

According to a second aspect of embodiments of the present disclosure, there is provided a risk management and control device, the device comprising:

The system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring operation data when a target application in electronic equipment executes at least partial target operation and acquiring pre-stored risk characteristic data, wherein the risk characteristic data is data generated when the target application executes illegal operation by utilizing a system vulnerability in the electronic equipment;

and the control module is used for executing control on the target operation based on the comparison result of the operation data and the risk characteristic data.

According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:

A processor;

A memory for storing processor-executable instructions;

Wherein the processor is configured to implement the steps of any of the risk management methods of the first aspect by executing the executable instructions.

According to a fourth aspect of embodiments of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of any of the risk management methods of the first aspect described above.

According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program which, when executed by a processor, implements the steps of any of the risk management methods of the first aspect described above.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:

Because the data of the illegal operation executed by the vulnerability of the target application attack system is stored in advance, after the operation data of the target application when executing at least part of the target operation is obtained, the operation data and the risk characteristic data can be compared to obtain a comparison result.

Through the comparison result, whether the target operation of the target application attacks the system vulnerability in the illegal operation mode can be determined, so that corresponding management and control operation is executed on the target operation according to the comparison result.

Therefore, when the system bug exists in the electronic equipment, even if the user does not update the operating system, the method can timely find whether the target operation of the target application is at risk or not, and can timely manage and control the target operation, thereby being beneficial to improving the safety of the operating system in the electronic equipment.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a flow chart of a risk management method according to an exemplary embodiment of the present disclosure;

FIG. 2 is an application framework diagram of a risk management and control method according to an exemplary embodiment of the present disclosure;

FIG. 3 is a flow chart of another risk management method illustrated by the present disclosure according to an exemplary embodiment;

FIG. 4 is an application framework diagram of another risk management method illustrated by the present disclosure according to an exemplary embodiment;

FIG. 5 is an application framework diagram of another risk management method illustrated by the present disclosure according to an exemplary embodiment;

FIG. 6 is an application framework diagram of another risk management method illustrated by the present disclosure according to an exemplary embodiment;

Fig. 7 is a schematic structural view of a risk management device according to an exemplary embodiment of the present disclosure;

fig. 8 is a schematic structural view of an electronic device according to an exemplary embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The term "if" as used herein may be interpreted as "at..once" or "when..once" or "in response to a determination", depending on the context.

When a user runs a third party application in an electronic device, the user typically grants the third party application access to the system application, or allows the third party application to invoke an interface of the system application to perform a specific service. The following is an exemplary illustration:

for example, when a user installs and uses a weather forecast application on a smart phone, the third party weather forecast application may need to access location services (e.g., GPS information) of the system to obtain real-time geographic location information of the user in order to provide accurate local weather forecast. At this time, the system pops up the permission request prompt, inquires whether the user allows the weather forecast application to access the location information, and provides a corresponding access interface and access path after the user allows the weather forecast application to access the location information.

For another example, a user downloads and installs a social media application, and in order to be able to share the photographed photo directly to the social platform, the third party social media application needs to obtain the right to access the device camera and the album, so as to call the system camera interface to photograph, and read or write the picture in the mobile phone album.

As another example, some third party calendar applications require access to a system calendar in order to add, edit, or view a user's schedule. This requires the user to grant the third party calendar application access to the interface of the system calendar application and then edit some calendar in the system calendar via the interface.

This makes it easy for an illegal person to steal data in the user's album, edit schedules in the system calendar, etc. using rights owned by the third party application.

In the prior art, when a vulnerability is to be repaired, a new operating system or security patch is released, a user is prompted to install and wait for confirmation of the installation (the user is not willing to update the new operating system or security patch), so that an illegal molecule can execute illegal operations by utilizing the system vulnerability at any time under the condition that the user does not update the new operating system (or security patch), and information of the user can be stolen illegally.

Therefore, it is necessary to provide a solution that can ensure the security of the electronic device and the operating system in the case that the user does not update the operating system.

The following is a brief description:

It is assumed that a third party application (third party calendar) wants to realize that when adding a target operation of a user schedule in a system calendar, the following partial operations need to be performed:

operation one, send the call request that wants to call the goal interface.

And secondly, after acquiring the information of the target interface, calling a system application (system calendar) through the target interface.

And thirdly, writing the user schedule in the system calendar.

Of the three operations described above, the third operation is most easily utilized by an illegal person to perform an illegal operation.

For example, after the illegal person acquires the access right to the call interface of the system calendar by the operation one and the operation two, the illegal person replaces the operation three with the following illegal operation:

Illegal advertisements, malicious links, sensitive information or other data which infringe the privacy of the user are written in the system calendar, or information which is used by illegal personnel to change the user to write, etc.

Therefore, among the above three operations, the lattice control operation three is required to avoid the corresponding illegal operation by an illegal person. That is, whether the target operation is a risk operation or not may be determined according to the first several operations (e.g., operation one or operation two) of the target operation, and then the target operation is stopped in time when the target operation is not yet executed (operation three is not executed).

That is, by acquiring operation data of at least part of the target operations (for example, the first operation and the second operation) and comparing the operation data with the risk feature data stored in advance, it can be determined whether the target operations are identical to the risk feature data, so that the target operations are controlled to different degrees according to different comparison results.

The following is a detailed description:

Fig. 1 is a flowchart of a risk management method according to an exemplary embodiment of the present disclosure, as shown in fig. 1, the method including the steps of:

Step 101, acquiring operation data when a target application in electronic equipment executes at least part of target operation, and acquiring pre-stored risk characteristic data, wherein the risk characteristic data is data generated when the target application executes illegal operation by utilizing a system vulnerability in the electronic equipment.

The target operation is an operation which can be executed by the target application when the target application needs to call a component of the system application or acquire specific system rights. For example, writing a schedule in a system calendar, editing an image in a system album, and the like.

The risk characteristic data are data which are extracted according to illegal operations after the target application is found to execute the illegal operations by utilizing the system holes in the electronic equipment in advance and are stored in the electronic equipment in advance.

For example, when an illegal person discovers that a system vulnerability exists in a system camera application interface, a third party application invokes the interface to legally obtain the right to take a picture or record a video. However, the vulnerability allows malicious target applications to take advantage of this authority to perform additional illegal operations. For example, after a user authorizes a target application to use the camera function, the application not only takes a normal photograph or video, but also silently uploads the photographed photograph or video to a remote server in the background, which may infringe the privacy of the user.

At this time, the risk characteristic data includes data of a request of the target application to acquire the system camera application interface, an illegal start of the camera in the background after the target application acquires the system camera application interface, illegal modification, deletion, addition of an image in the album, and illegal uploading to the server.

And 102, performing control on the target operation based on the comparison result of the operation data and the risk characteristic data.

It will be appreciated that if the operation data is an illegal operation performed by the target application, the operation data of this illegal operation may be consistent with or similar to the risk feature data, and thus, by comparing the operation data with the risk feature data, it can be determined whether the operation data is at risk.

Therefore, corresponding control can be executed on the target operation according to the comparison result, and the target operation is ensured not to attack the electronic equipment and the operating system of the electronic equipment.

The comparison method can be that two data are in one-to-one correspondence to determine whether the two data are consistent, or operation behaviors which are indicated by the two data and are to be executed by the application are compared one by one to determine whether the two data are consistent, and the specific comparison method is not limited by the scheme.

Optionally, executing step 101 to obtain pre-stored risk feature data includes:

And acquiring risk characteristic data transmitted by a first application in the electronic equipment, wherein the risk characteristic data is sent to the first application by an equipment server after the equipment server determines that the electronic equipment has a system vulnerability, and the target application is not connected to the equipment server.

The first application is a system application installed in the electronic equipment, and is mainly a safety control application used for guaranteeing the safety of the electronic equipment in the system application. In order to ensure that the electronic device can better provide services for users after leaving the factory, the manufacturer can set a device server for providing important services for the electronic device, such as system upgrade, account service and the like. The first application is a system application, so that the first application can communicate with a device server of an operating system of the electronic device, and the third party application is not a system application, can not communicate with the device server, and can only communicate with the third party server.

And after the equipment server discovers that the electronic equipment has the system vulnerability, updating corresponding risk characteristic data in real time, and transmitting the risk characteristic data updated in real time to the first application. In this way, under the condition that the third party server corresponding to the third party application does not update the third party application or the user does not manually update the operating system, the risk characteristic data acquired by the first application can be stored in the electronic device, and corresponding management and control can be executed through the comparison result of the risk characteristic data stored in the electronic device and the operating data of the target application.

Fig. 2 is an application framework diagram of a risk management method according to an exemplary embodiment of the present disclosure, as shown in fig. 2:

The first application communicates with the device server, obtains the risk profile data, and stores the risk profile data in the core service. The target application (third party application) interacts with some service components or interfaces in the core service when performing the target operation, and generates operation data.

At this time, the operation data and the risk feature data can be compared in the core service to obtain a comparison result.

Optionally, fig. 3 is a flowchart of another risk management method according to an exemplary embodiment of the present disclosure, and as shown in fig. 3, when executing step 101 to obtain operation data when a target application in an electronic device performs at least part of a target operation, the method includes the following steps:

step 301, monitoring a plurality of target interfaces in the electronic device.

The target interfaces are component interfaces predetermined from components of the electronic device (e.g., core services) that the target application needs to invoke when performing the target operation. Thus, listening to the target interface may be achieved through a core service in the electronic device.

Step 302, when it is monitored that a target application in the electronic device calls any one of the target interfaces, call information of the target application on the target interfaces and/or system authority information of the target application are obtained.

Wherein, call information including but not limited to:

information of the called application, mainly refers to information (such as identity) of the application program (target application) that initiates the call request.

Uri information (Uniform Resource Identifier ) that points to the location of the data or service to be operated upon, the Uri can be used to represent specific content, data or functional modules to be accessed when communicating across applications.

The call type, the type of ACTION called or the type of request for the called service, e.g. "ACTION _ INSERT" indicates that a new event is to be inserted in the calendar application. The called application package name is the information of the system application to be called.

Information of the invoked application, including, but not limited to, an application component name, a calling behavior name, and/or an application version number. The invoked application component is typically referred to as a core service in the electronic device, and is specified in an agent (a kind of messaging object that is used to describe an interaction request between application components) by a component class name or action. For example, if a specific Activity is to launch another application, the complete class name of the Activity needs to be provided, and if an implicit Intent is used, the target component in the system that can respond to the Intel is matched by action and category (category).

Here, it may be noted that the target interface is an interface where the target application interacts with a second application in the electronic device, where the target operation includes at least one of:

and executing the appointed operation after acquiring the target authority from the second application based on the target interface.

System rights information for the target application including, but not limited to:

the permission list lists a set of system permissions that the target application must obtain in order to perform the target operation, such as reading phone status, accessing external storage, obtaining device location, etc., and a set of system permissions that are already currently owned.

Rights level-indicating whether these rights belong to ordinary rights or dangerous rights. In some operating systems, dangerous rights require explicit authorization by the user at runtime, whereas ordinary rights are automatically granted at installation time.

Rights purpose describes how and how these rights are related to the invoked operation or service, explaining why the target application needs them. For example, if a calendar application requests an "action_insert" ACTION to INSERT a new event, it may require permission to read and write calendar data in order to actually perform the data operation.

The effect of the missing rights is to tell which functions would be limited or not normally used if a particular right was not granted.

Rights management policies-describe how a target application processes and protects user data acquired by rights, and where a user can view or alter the rights that are authorized.

The target application, when invoking any of the target interfaces, generates at least some of the above information, and gathers all of this information as operational data, i.e., performs step 303.

And step 303, determining the call information and/or the system authority information as the operation data.

Fig. 4 is an application framework diagram of another risk management method according to an exemplary embodiment of the present disclosure, as shown in fig. 4:

The core services include a first core service 401, and a second core service 402.

The first core service 401 includes an activity management service and four core services 4011 provided by the activity management service, and when the activity management service receives a call request sent by a target application, the activity management service determines a service that the target application wants to call and an interface corresponding to a service component.

Among them, the four core services 4011 include:

ACTIVITYSTARTER (activity initiation service), ACTIVESERVICES (service management service), contentProviderHelper (content provider management service), broadcastQueue (broadcast queue management service).

Wherein ACTIVITYSTARTER generally refers to the component that initiates the new Activity (a component) related logic. It is responsible for processing the analysis of the Intent, the search of the target Activity and executing the corresponding starting flow, and ensures the correctness and the safety when switching from one Activity to another. ACTIVESERVICES are important components in the operating system responsible for managing the running background services (Background Services) and foreground services (Foreground Services). The system takes charge of life cycle management responsibilities such as starting, binding and stopping of the service, optimizes service scheduling according to the system resource condition, and ensures efficient operation of the service and effective utilization of the system resource. ContentProviderHelper refers to related tool classes or service modules that assist developers or system calls to Content Provider for simplifying access and management of shared data between systems or applications. BroadcastQueue is part of a messaging mechanism that is primarily used to manage broadcast messages sent inside the system and between applications. The method and the device orderly put the received broadcast events into the queue according to the priority, and then distribute the broadcast events to the components registered with the corresponding receivers for processing, thereby ensuring the safe and reliable transmission of the broadcast messages.

The second core service 402 includes:

4021, security manager service, which is used for acquiring risk characteristic data sent by the device server from the first application, and transmitting the risk characteristic data to 4022 for storage.

The defensemmanager (defense management module) stores the risk characteristic data (which can be classified and stored according to different behavior types, for example, classified and stored according to operation duration and operation times, and classified and stored according to set identifiers) acquired from the 4023, and is used for transmitting the risk characteristic data to the 4021 for comparison.

4023, A defensechecker (defense module) is configured to monitor a target interface corresponding to the four core services 4011, store the monitored data as operation data (may use the same storage mode as that in 4022), and compare the operation data with the risk feature data after acquiring the risk feature data transmitted by 4022, so as to obtain a comparison result.

Optionally, the executing step 102 performs control on the target operation based on the comparison result of the operation data and the risk feature data, including the following two control modes:

mode one, for the case where there is a risk for the target operation:

And when the comparison result of the operation data and the risk characteristic data indicates that the target operation has risk, executing first control on the target operation, wherein the first control at least comprises the step of transmitting the operation data of the target operation to a device server.

When the risk exists in the target operation, in order to prevent the target application from attacking the electronic equipment through the target operation again, the operation data needs to be uploaded to the equipment server in time, and the risk reporting is completed. In this way, the risk applications may be taken off-line in the application store, or the applications may be uniformly given lower system permissions, or the user may be prompted to uninstall the applications, etc. The uploading may be forwarded to the device server by the first application.

In addition to the control mode of transmitting the operation data of the target operation to the equipment server, other control modes are included, for example, whether the target application is controlled to stop executing the target operation is determined according to the comparison result, that is, the target application is allowed to continue executing the target operation, or the target application is controlled to stop executing the target operation.

Here, the alignment may be further defined as:

And respectively extracting the characteristics of the operation data and the risk characteristic data, and then obtaining a characteristic similarity value in a characteristic comparison mode. And when the similarity value of the two characteristics is smaller than the first threshold value, the target operation is considered to be free of risk.

That is, when the comparison result of the operation data and the risk feature data indicates that the target operation is at risk, performing a first control on the target operation includes:

and when the feature similarity between the operation data and the risk feature data is larger than or equal to a first threshold value, allowing the target application to continue to execute the target operation or controlling the target application to stop executing the target operation.

By way of example, the first threshold here may be set to 75%.

How to determine whether to allow or not allow the target application to continue execution may be determined by:

And when the feature similarity between the operation data and the risk feature data is larger than or equal to a second threshold value, controlling the target application to stop executing the target operation, wherein the first threshold value is smaller than the second threshold value.

Here, assuming that the second threshold is 100% (merely an exemplary value), when the feature similarity of the two is greater than or equal to 100%, the target operation is deemed to be an illegal operation, the target application is directly controlled to stop executing the target operation (here, generally, when the target application has not executed the target operation yet, if the target application has executed the target operation, it may be set that the target application is not allowed to execute the target operation later).

When the feature similarity of the two is greater than or equal to 75%, but less than 100%, the operation data can be transmitted to the device server, and the target application is allowed to continue to execute the target operation.

By the method, target operation can be prevented in time, or behaviors of illegal personnel attacking the electronic equipment through the target operation can be effectively prevented.

It should be noted that the specific values of the first threshold and the second threshold may be adjusted in conjunction with the actual requirements.

Fig. 5 is an application framework diagram of another risk management method according to an exemplary embodiment of the present disclosure, and as shown in fig. 5, the second core service 402 further includes:

4024 an appsecurityhelper (application security auxiliary module) is configured to control the target application to stop executing the target operation (not allowing the target application to call the second application through an interface provided by the activity management service) when DEFENSECHECKER4023 determines that there is a certain risk in the operation data of the target application through the comparison result. The second application here is also a system application.

Further, controlling the target application to stop executing the target operation includes at least one of:

The method comprises the steps of closing appointed authority of a target application, blocking operation of calling a second application by the target application through a target interface, wherein the target interface is an interface of interaction between the target application and the second application in the electronic equipment, setting that the second application can only be called by the target application, and the risk value of the target application is smaller than an appointed threshold value.

Rights are specified including, but not limited to, rights for performing illegal operations, rights embodied in the risk profile. The second application is set to be invoked only by a trusted application (e.g., a system application), through APPSecurityHelper4024, or the campaign management service blocks the operation of the target application to invoke the second application through the target interface.

In one example of the disclosure, when the first application includes an application capable of performing rights management, the designated rights of closing the target application are completed by the first application. At this time, the following manner may be included:

After the device server sends the illegal feature data to the first application, the first application determines the authority used by the illegal feature data, and directly closes the appointed authority of the target application through the authority management application in the first application. Or, DEFENSECHECKER4023 determines that the comparison result indicates that the target operation is at risk after comparison, and then transmits the result to the first application through 4022-4021, and then closes the designated authority of the target application through the authority management application in the first application. As shown in fig. 6:

the first application 601 includes:

application 6011 PermissionAnagerAPP (rights management application) for setting system rights for managing respective applications.

Application 6012:Security App (security application) for securing electronic devices.

Mode two, for the situation that there is no risk in the target operation:

And when the comparison result of the operation data and the risk characteristic data indicates that the target operation is not at risk, executing second control on the target operation, wherein the second control comprises allowing the target application to continue executing the target operation.

At this time, the second management and control is to neither report nor prevent the target operation of the target application. The risk of the target operation is monitored only by means of comparison.

By way of example, the manner in which the target operation is determined to be risk-free may be such that the operational data has a feature similarity to the risk feature data of less than a first threshold (e.g., 75%).

For the foregoing method embodiments, for simplicity of explanation, the methodologies are shown as a series of acts, but one of ordinary skill in the art will appreciate that the present disclosure is not limited by the order of acts described, as some steps may occur in other orders or concurrently in accordance with the disclosure.

Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required by the present disclosure.

Corresponding to the embodiment of the application function implementation method, the disclosure further provides an embodiment of the risk management and control device and a corresponding terminal.

The present disclosure provides a computer program which, when executed by a processor, implements the steps of any of the risk management methods described above.

Fig. 7 is a schematic structural diagram of a risk management device according to an exemplary embodiment of the present disclosure, and as shown in fig. 7, the risk management device may include:

The acquiring module 701 is configured to acquire operation data when a target application in an electronic device performs at least part of target operations, and acquire pre-stored risk feature data, where the risk feature data is data generated when the target application performs illegal operations by using a system vulnerability in the electronic device.

And the control module 702 is configured to perform control on the target operation based on a comparison result of the operation data and the risk characteristic data.

Optionally, the acquiring module 701, when configured to acquire pre-stored risk feature data, is configured to:

Optionally, the acquiring module 701, when configured to acquire operation data when the target application in the electronic device performs at least part of the target operation, is configured to:

And monitoring a plurality of target interfaces in the electronic equipment.

When the target application in the electronic equipment is monitored to call any one of the target interfaces, call information of the target application on the target interface and/or system authority information of the target application are obtained.

And determining the call information and/or the system authority information as the operation data.

Optionally, the target interface is an interface through which the target application interacts with a second application in the electronic device;

the target operation includes at least one of:

Optionally, the control module 702 is configured to, when configured to perform control on the target operation based on a comparison result of the operation data and the risk feature data, perform:

Optionally, when the comparison result of the operation data and the risk feature data indicates that the target operation is at risk, the management and control module 702 is configured to, when executing the first management and control on the target operation,:

Optionally, the management module 702 is configured to, when configured to control the target application to stop executing the target operation, perform at least one of:

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements described above as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the disclosed solution. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

Accordingly, an embodiment of the disclosure provides an electronic device, including a processor, a memory for storing processor executable instructions, where the processor is configured to implement steps of any of the methods described above by executing the executable instructions.

Fig. 8 is a schematic structural view of an electronic device according to an exemplary embodiment of the present disclosure. For example, electronic device 800 may be a user device, and may be embodied as a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, a wearable device such as a smart watch, smart glasses, smart bracelets, smart running shoes, and the like.

Referring to FIG. 8, an electronic device 800 can include one or more of a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.

The processing component 802 generally controls overall operation of the electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations at the device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply component 806 provides power to the various components of the electronic device 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 800.

The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only a boundary of a touch or a sliding action but also a duration and a pressure related to the touch or the sliding operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the electronic device 800 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, a volume button, an activate button, and a lock button.

The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the electronic device 800. For example, the sensor assembly 814 may detect an on/off state of the electronic device 800, a relative positioning of the components, such as a display and keypad of the electronic device 800, the sensor assembly 814 may also detect a change in position of the electronic device 800 or a component of the electronic device 800, the presence or absence of a user's contact with the electronic device 800, an orientation or acceleration/deceleration of the electronic device 800, and a change in temperature of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate communication between the electronic device 800 and other devices, either wired or wireless. The electronic device 800 may access a wireless network based on a communication standard, such as WiFi,4G or 5G,4G LTE, 5G NR, or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 described above further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer readable storage medium, such as memory 804 including instructions that, when executed by processor 820 of electronic device 800, enable electronic device 800 to perform any one of the methods described above, is also provided.

The non-transitory computer readable storage medium may be a ROM, random-access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A risk management method, the method comprising:

2. The method of claim 1, wherein the acquiring pre-stored risk profile data comprises:

3. The method of claim 1, wherein the obtaining operation data of the target application in the electronic device when performing at least part of the target operation comprises:

monitoring a plurality of target interfaces in the electronic equipment;

when monitoring that any target interface is called by a target application in the electronic equipment, acquiring calling information of the target application on the target interface and/or system authority information of the target application;

4. A method according to claim 3, wherein the target interface is an interface at which the target application interacts with a second application in the electronic device;

the target operation includes at least one of:

Invoking a second application based on the target interface;

And executing the appointed operation after the target interface acquires the target authority from the second application.

5. The method of claim 1, wherein the performing the controlling of the target operation based on the comparison of the operation data and the risk characteristic data comprises:

6.The method of claim 5, wherein performing a first administration of the target operation when the comparison of the operation data and the risk characteristic data indicates that the target operation is at risk comprises:

7. The method of claim 6, wherein the performing a first administration of the target operation when the comparison of the operation data and the risk characteristic data indicates that the target operation is at risk comprises:

8. The method of claim 6 or 7, wherein the controlling the target application to stop performing target operations comprises at least one of:

closing the appointed authority of the target application;

blocking the operation of the target application to call a second application through a target interface, wherein the target interface is an interface of interaction between the target application and the second application in the electronic equipment;

and setting that the second application can only be called by a target application, wherein the risk value of the target application is smaller than a specified threshold.

9. The method of claim 1, wherein the performing the controlling of the target operation based on the comparison of the operation data and the risk characteristic data comprises:

When the comparison result of the operation data and the risk characteristic data indicates that the target operation is free of risk, performing second control on the target operation;

Wherein the second controlling includes allowing the target application to continue performing target operations.

10. A risk management device, the device comprising:

11. An electronic device, comprising:

A processor;

A memory for storing processor-executable instructions;

Wherein the processor is configured to implement the steps of the method of any of claims 1 to 9 by executing the executable instructions.

12. A computer readable storage medium having stored thereon a computer program, characterized in that the program when executed by a processor realizes the steps of the method according to any of claims 1-9.