CN112926049A - Information risk prevention and control method, device and equipment - Google Patents
Information risk prevention and control method, device and equipment Download PDFInfo
- Publication number
- CN112926049A CN112926049A CN202110319550.XA CN202110319550A CN112926049A CN 112926049 A CN112926049 A CN 112926049A CN 202110319550 A CN202110319550 A CN 202110319550A CN 112926049 A CN112926049 A CN 112926049A
- Authority
- CN
- China
- Prior art keywords
- risk
- code
- dynamic code
- target
- target dynamic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
- G06F2221/033—Test or assess software
Abstract
The embodiment of the specification discloses a risk prevention and control method, a risk prevention and control device and risk prevention and control equipment for information, wherein the method comprises the following steps: when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded; risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained; and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for risk prevention and control of information.
Background
With the rapid development of internet technology, an application installed in a terminal device (especially an APP installed in a mobile phone) and a service running in the application are more and more sufficient to the life of a user, the terminal device (especially a mobile terminal device, an IoT device, and the like) provides convenience for the user, and meanwhile, a series of related problems such as security and user privacy are brought, one of the outstanding security and user privacy problems is that a large amount of second party and third party codes are introduced due to the open ecology of the application, and therefore the probability of malicious code execution is improved.
For malicious third party SDKs, risk scanning is typically performed on the third party SDK before the third party SDK is integrated into the application. However, since some of the malicious third-party SDKs still bypass the risk scanning by means of dynamic codes, so as to implement loading of malicious codes, there is a need to provide a mechanism for performing real-time risk scanning when codes are dynamically loaded.
Disclosure of Invention
It is an object of embodiments of the present specification to provide a mechanism for real-time risk scanning when code is dynamically loaded.
In order to implement the above technical solution, the embodiments of the present specification are implemented as follows:
the embodiment of the specification provides a risk prevention and control method for information, which comprises the following steps: and when detecting that an interface used for loading the dynamic code in the terminal equipment is called, acquiring the target dynamic code to be loaded. And carrying out risk scanning on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result. And if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
The embodiment of this specification provides a risk prevention and control device of information, the device includes: and the dynamic code acquisition module is used for acquiring the target dynamic code to be loaded when detecting that the interface used for loading the dynamic code in the terminal equipment is called. And the risk scanning module is used for carrying out risk scanning on the target dynamic code so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result. And the loading canceling module cancels the loading of the target dynamic code if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation.
The embodiment of this specification provides a risk prevention and control equipment of information, includes: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to: and when detecting that an interface used for loading the dynamic code in the terminal equipment is called, acquiring the target dynamic code to be loaded. And carrying out risk scanning on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result. And if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
Embodiments of the present specification also provide a storage medium, where the storage medium is used to store computer-executable instructions, and the executable instructions, when executed, implement the following processes: and when detecting that an interface used for loading the dynamic code in the terminal equipment is called, acquiring the target dynamic code to be loaded. And carrying out risk scanning on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result. And if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a block diagram illustrating an embodiment of a method for risk prevention and control of information;
FIG. 2 is a schematic diagram of a risk prevention and control process for information;
FIG. 3 is a block diagram of another embodiment of a method for risk prevention and control of information according to the present disclosure;
FIG. 4 is an embodiment of a risk prevention and control device for information according to the present disclosure;
fig. 5 is an embodiment of a risk prevention and control device for information according to the present disclosure.
Detailed Description
The embodiment of the specification provides a risk prevention and control method, device and equipment for information.
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
Example one
As shown in fig. 1, an execution subject of the method may be a server or a terminal device, where the terminal device may be a computer device such as a notebook computer or a desktop computer, or may be a mobile terminal device such as a mobile phone or a tablet computer. The server may be a server for performing risk prevention and control on a certain service (such as a transaction service or a financial service) or a code included in a designated application program, and specifically, the server may be a server for a payment service, or a server for a service related to finance, instant messaging, or the like. The execution main body in this embodiment is described by taking a terminal device as an example, and for the case where the execution main body is a server, the following related contents may be referred to, and details are not described here. The method may specifically comprise the steps of:
in step S102, when it is detected that the interface for loading the dynamic code in the terminal device is called, the target dynamic code to be loaded is acquired.
The terminal device may be any terminal device, specifically, the terminal device may be a mobile terminal device such as a mobile phone, a tablet computer, or a personal computer, and may be specifically set according to an actual situation, which is not limited in this description embodiment. The dynamic code may be a code which is connected to a code storage unit such as a database, and the content of the code in the dynamic code may be changed, that is, the content of the code in the dynamic code may be changed by performing a specified operation on the code storage unit such as the database. The target dynamic code may be any dynamic code, for example, a dynamic code for displaying some type of recommendation information (specifically, an advertisement of a game class or an advertisement of a video class), or a dynamic code for displaying some specified data, which may be specifically set according to an actual situation, and this is not limited in this embodiment of the specification.
In implementation, with the rapid development of internet technology, an application installed in a terminal device (especially, an APP installed in a mobile phone) and a service running in the application are more and more sufficient to permeate the life of a user, and the terminal device (especially, a mobile terminal device, an IoT device, and the like) provides convenience for the user and brings a series of related problems such as security and user privacy, wherein one of the outstanding security and user privacy problems is that a large amount of second party and third party codes are introduced due to the open ecology of the application, so that the probability of malicious code execution is improved. As shown in fig. 2, for a malicious third-party SDK, before the third-party SDK is integrated into an application, risk scanning is performed on the third-party SDK, that is, risk scanning or risk detection is performed on the main program code to be loaded or being loaded as shown in fig. 2. However, as shown in fig. 2, because some malicious third parties SDKs still bypass the risk scanning in a dynamic code manner, so as to implement loading of malicious codes, a mechanism for performing real-time risk scanning when dynamically loading codes needs to be provided. An embodiment of the present specification provides a risk detection mechanism for code loading, which may specifically include the following contents:
the terminal device may be installed with an application program, the application program may include a plurality of different codes, different codes may implement different functions through compiling, the same function may also be implemented by a plurality of different codes through compiling, generally, the codes may include static codes and dynamic codes, the static codes are codes whose source codes are set in the application program, the code content of the static codes is often not changed at will, but the dynamic codes are often changeable at any time, so risk prevention and control and risk detection of the dynamic codes become the difficulty of risk prevention and control. In practical applications, an interface for loading dynamic codes may be modified (or an interface for loading dynamic codes is subjected to a HOOK process), so that a detection mechanism for loading dynamic codes may be set at the interface, and thus, whether the interface is called or not is detected, so as to implement management and control of loading dynamic codes, specifically, when a terminal device runs the application program, the terminal device may run the detection mechanism, and when the application program or the terminal device needs to call and load a certain dynamic code (i.e., a target dynamic code) in a running process, a call or load request for the target dynamic code may be sent to an interface for loading dynamic codes in the terminal device, at this time, the terminal device may detect that the interface is called, and may intercept the call or load request, and may determine that the application program needs to call and load dynamic codes at the same time, at this time, in order to ensure the security of the application program, the security of the terminal device, and the security of the user information, a preset dynamic code obtaining mechanism may be operated, so as to obtain a dynamic code (i.e. a target dynamic code to be loaded) that the application program or the terminal device needs to call and load.
In step S104, a risk scan is performed on the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation, and a corresponding risk scan result is obtained.
The risk operation may be an operation capable of triggering or causing a specified risk, specifically, such as an operation of acquiring user privacy data (that is, private information that a user does not want to be acquired by others without authorization, specifically, a facial image of the user, fingerprint data of the user, or identity information of the user, or the like), or an operation of tampering a specified parameter in an application or a terminal device, and the like, which may be specifically set according to an actual situation, and this is not limited in this specification.
In implementation, after the target dynamic code to be loaded is obtained in the above manner, the target dynamic code may be read, and security analysis and risk scanning may be performed on the read target dynamic code, so as to determine whether the target dynamic code can trigger a predetermined risk operation, for example, whether the target dynamic code can trigger an operation of obtaining user privacy data or an operation of tampering a specified parameter in an application or a terminal device, and if it is detected that the target dynamic code can trigger the risk operation, a risk scanning result that the target dynamic code can trigger the risk operation may be obtained, and if it is detected that the target dynamic code does not trigger the risk operation, a risk scanning result that the target dynamic code does not trigger the risk operation may be obtained.
In step S106, if the risk scanning result indicates that the target dynamic code can trigger a predetermined risk operation, the target dynamic code is not loaded.
In implementation, if the risk scanning result indicates that the target dynamic code can trigger a predetermined risk operation, it may be determined that the target dynamic code has a risk, and at this time, the terminal device or the application program may be rejected or cancelled to load the target dynamic code, so as to ensure the security of the terminal device, the application program, or the user information.
In addition, if the risk scanning result indicates that the target dynamic code cannot trigger a predetermined risk operation, it may be determined that the target dynamic code has no risk, and at this time, the terminal device or the application program may be allowed to load the target dynamic code, so as to implement a corresponding operation or function.
The embodiment of the specification provides an information risk prevention and control method, which includes the steps of acquiring a target dynamic code to be loaded when it is detected that an interface used for loading the dynamic code in a terminal device is called, then performing risk scanning on the target dynamic code to determine whether the target dynamic code can trigger a preset risk operation, and thus in the process of needing to load the dynamic code in an application program, performing risk detection and risk scanning on the dynamic code contained in the application program to judge whether the dynamic code can trigger a specified risk operation, and further performing risk prevention and control on the corresponding dynamic code based on a risk scanning result.
Example two
As shown in fig. 3, an execution subject of the method may be a server or a terminal device, where the terminal device may be a computer device such as a notebook computer or a desktop computer, or may be a mobile terminal device such as a mobile phone or a tablet computer. The server may be a server for performing risk prevention and control on a certain service (such as a transaction service or a financial service) or a code included in a designated application program, and specifically, the server may be a server for a payment service, or a server for a service related to finance, instant messaging, or the like. The execution main body in this embodiment is described by taking a terminal device as an example, and for the case where the execution main body is a server, the following related contents may be referred to, and details are not described here. The method may specifically comprise the steps of:
in step S302, a main program code necessary for the operation of the target application program is acquired.
The target application may be an applet installed in a host program, or the target application may also be the host program integrated with a third-party software development kit SDK, where the host program may be an APP installed in a mobile terminal device or a PC or an APP on an IoT, and the host program may be specifically set according to an actual situation, and this is not limited in this embodiment of the specification.
In implementation, when a third-party SDK is not integrated in an application (i.e., a target application) installed in a terminal device, risk scanning may be performed on a static code included in the target application to find a risk existing in the static code in time.
In step S304, risk scanning is performed on the main program code to obtain a risk scanning result corresponding to the main program code.
In implementation, the risk scan results may include two cases: in a case where the main program code cannot trigger a predetermined risky operation, it may be determined that there is no risk in the main program code of the target application, and the process of step S306 described below may be continuously performed. In another case, the main program code can trigger a predetermined risky operation, and at this time, it may be determined that the main program code of the target application program is risky, and the terminal device may record the target application program, and when the target application program runs, may prevent the target application program from running based on the recorded related information of the target application program, thereby preventing the main program code from being executed.
In step S306, if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger a predetermined risk operation, the main program code is loaded and executed when it is detected that the target application program is running.
In step S308, the dynamic code included in the target application is added to a queue that needs to be managed and controlled by the preset risk protection rule based on the profile.
The section in the risk protection rule based on the section may be Aspect, Aspect-Oriented Programming (AOP), and the section is a Programming paradigm that dynamically adds functions to a program without modifying source codes by means of pre-compiling, run-time dynamic proxy, or injection. AOP pursues decoupling between caller and callee, providing cross-module function convergence. AOP is suitable for solving cross-cut (cross-cut) related system functions in programs, which are often difficult to solve by either procedural or object-oriented programming. The risk protection rule based on the tangent plane can construct a corresponding tangent plane defense system, the tangent plane defense system can be a safety defense system, the core of the tangent plane defense system is a safety integration framework, codes can be analyzed and controlled, the core thought of the tangent plane defense system is to establish a set of safety layers which are interwoven with and parallel to the service, the safety can go deep into service logic, careful observation and attack and defense are realized, meanwhile, decoupling of the service and the safety is guaranteed, and the service and the safety are independent. The section defense system can be embedded into the framework of the whole application program (such as APP) through the security section defense layer, meanwhile, the independently running rule engine and the upgrading capability are kept, and the important security-related interface contained in the APP can be protected through the section. In addition, when the risk protection rule or the tangent plane defense system based on the tangent plane judges whether a certain call is reasonable, the called link information is traced and checked, and the call risk of the link is subjected to perspective so as to make accurate and comprehensive judgment.
In implementation, the dynamic code included in the target application may be managed and controlled by the risk protection rule based on the profile, and for this reason, the dynamic code included in the target application may be added to a queue that needs to be managed and controlled by the preset risk protection rule based on the profile.
In step S310, when it is detected that the interface for loading the dynamic code in the terminal device is called, the target dynamic code to be loaded is acquired.
The target dynamic code includes a dynamic code provided in a target application, and the target application may be an applet installed in a host program, or the target application may also be the above-mentioned host program integrated with a third-party software development kit SDK, and the host program may be an APP installed in a mobile terminal device or a PC or an APP on an IoT, which may be specifically set according to an actual situation, and this is not limited in this description embodiment.
It should be noted that, when the target application program runs, risk scanning may be performed on the main program code, which may specifically include the following: and when the target application program is detected to run, risk scanning is carried out on the main program code required by the running of the target application program, and a risk scanning result corresponding to the main program code is obtained. For the specific processing procedure of the above steps, reference may be made to the related contents, which are not described herein again.
Further, based on the above processing, the processing of step S310 may also be realized by: and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger the preset risk operation, acquiring the target dynamic code to be loaded when detecting that an interface for loading the dynamic code in the terminal equipment is called. For the specific processing procedure of the above steps, reference may be made to the related contents, which are not described herein again.
In step S312, risk scanning is performed on the target dynamic code according to the risk protection rule based on the section to determine whether the target dynamic code can trigger a predetermined risk operation, and a corresponding risk scanning result is obtained.
The predetermined risk operations may include risk operations related to the operation security of the application program (specifically, operations for tampering with the operation parameters in the application program or operations for tampering with address information of a service provider of a specific service provided in the application program, etc.), and risk operations related to the user privacy data (specifically, operations for stealing the user privacy data or operations for tampering with the user privacy data, etc.).
In step S314, if the risk scan result indicates that the target dynamic code can trigger a predetermined risk operation, the target dynamic code is not loaded.
In step S316, a first notification message that the target dynamic code can trigger a predetermined risk operation is sent to the preset management device, and/or a second notification message that the target dynamic code is cancelled is sent to the preset management device.
The management device may be a device of a risk management and control party, specifically, a mobile terminal device such as a mobile phone or a tablet computer, or a terminal device such as a personal computer, which may be specifically set according to an actual situation, and this is not limited in this specification.
The embodiment of the specification provides an information risk prevention and control method, which includes the steps of acquiring a target dynamic code to be loaded when it is detected that an interface used for loading the dynamic code in a terminal device is called, then performing risk scanning on the target dynamic code to determine whether the target dynamic code can trigger a preset risk operation, and thus in the process of needing to load the dynamic code in an application program, performing risk detection and risk scanning on the dynamic code contained in the application program to judge whether the dynamic code can trigger a specified risk operation, and further performing risk prevention and control on the corresponding dynamic code based on a risk scanning result.
EXAMPLE III
Based on the same idea, the information risk prevention and control method provided in the embodiments of the present specification further provides an information risk prevention and control device, as shown in fig. 4.
The risk prevention and control device of the information comprises: a dynamic code acquisition module 401, a risk scanning module 402, and a cancel load module 403, wherein:
the dynamic code obtaining module 401 is configured to obtain a target dynamic code to be loaded when detecting that an interface for loading a dynamic code in a terminal device is called;
a risk scanning module 402, configured to perform risk scanning on the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation, and obtain a corresponding risk scanning result;
and a load canceling module 403, configured to cancel loading the target dynamic code if the risk scanning result indicates that the target dynamic code can trigger a predetermined risk operation.
In an embodiment of this specification, the apparatus further includes:
the dynamic code management and control module is used for adding the dynamic codes contained in the target application program into a queue which needs to be managed and controlled by preset risk protection rules based on a section;
the risk scanning module 402 performs risk scanning on the target dynamic code according to the risk protection rule based on the tangent plane to determine whether the target dynamic code can trigger a predetermined risk operation, and obtains a corresponding risk scanning result.
In an embodiment of this specification, the apparatus further includes:
the first main code scanning module is used for scanning risks of a main program code required by the running of a target application program when the running of the target application program is detected, and obtaining a risk scanning result corresponding to the main program code;
the dynamic code obtaining module 401, if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger a predetermined risk operation, obtains a target dynamic code to be loaded when detecting that an interface for loading a dynamic code in a terminal device is called.
In an embodiment of this specification, the apparatus further includes:
the main code acquisition module is used for acquiring a main program code required by the running of the target application program;
the second main code scanning module is used for carrying out risk scanning on the main program code to obtain a risk scanning result corresponding to the main program code;
and the main code loading module is used for loading and running the main program code when the running of the target application program is detected if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger the preset risk operation.
In an embodiment of the present specification, the target dynamic code includes dynamic code provided in the target application.
In the embodiment of the present specification, the target application is an applet installed in a host program.
In an embodiment of the present specification, the target application is the host program integrated with a third party software development kit SDK.
In the embodiment of the specification, the predetermined risk operation comprises a risk operation related to the running safety of the application program and a risk operation related to user privacy data.
In an embodiment of this specification, the apparatus further includes:
and the notification module is used for sending a first notification message that the target dynamic code can trigger a preset risk operation to a preset management device and/or sending a second notification message for cancelling the loading of the target dynamic code to the preset management device.
An embodiment of the present specification provides an information risk prevention and control apparatus, where when it is detected that an interface used for loading a dynamic code in a terminal device is called, a target dynamic code to be loaded is acquired, and then risk scanning is performed on the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation, so that in a process of needing to load the dynamic code in an application program, risk detection and risk scanning may be performed on the dynamic code included in the application program to determine whether the dynamic code can trigger a specified risk operation, and then risk prevention and control may be performed on a corresponding dynamic code based on a risk scanning result, which may not only ensure security of operation of the application program and the terminal device, but also effectively prevent private data of a user from being stolen.
Example four
Based on the same idea, the information risk prevention and control device provided in the embodiments of the present specification further provides an information risk prevention and control apparatus, as shown in fig. 5.
The risk prevention and control device of the information may be the terminal device or the server provided in the above embodiments.
The risk prevention and control device of information may have a large difference due to different configurations or performances, and may include one or more processors 501 and a memory 502, and the memory 502 may store one or more stored applications or data. Memory 502 may be, among other things, transient or persistent storage. The application program stored in memory 502 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a risk prevention and control device for information. Still further, processor 501 may be configured to communicate with memory 502 to execute a series of computer-executable instructions in memory 502 on the information risk prevention device. The risk prevention and control apparatus of information may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input-output interfaces 505, and one or more keyboards 506.
In particular, in this embodiment, an information risk prevention and control device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the information risk prevention and control device, and the one or more programs configured to be executed by one or more processors include computer-executable instructions for:
when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded;
risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained;
and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
In the embodiment of this specification, the method further includes:
adding the dynamic code contained in the target application program into a queue which needs to be preset and is controlled based on the risk protection rule of the section;
the risk scanning the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation and obtain a corresponding risk scanning result includes:
and risk scanning is carried out on the target dynamic code through the risk protection rule based on the section so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result.
In the embodiment of this specification, the method further includes:
when the running of a target application program is detected, risk scanning is carried out on a main program code required by the running of the target application program, and a risk scanning result corresponding to the main program code is obtained;
when detecting that an interface used for loading dynamic codes in the terminal equipment is called, acquiring target dynamic codes to be loaded, including:
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, acquiring a target dynamic code to be loaded when detecting that an interface for loading the dynamic code in the terminal equipment is called.
In this embodiment of this specification, before acquiring a target dynamic code to be loaded when it is detected that an interface for loading a dynamic code in a terminal device is called, the method further includes:
acquiring a main program code required by the running of a target application program;
risk scanning is carried out on the main program code, and a risk scanning result corresponding to the main program code is obtained;
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, loading and running the main program code when the running of the target application program is detected.
In an embodiment of the present specification, the target dynamic code includes dynamic code provided in the target application.
In the embodiment of the present specification, the target application is an applet installed in a host program.
In an embodiment of the present specification, the target application is the host program integrated with a third party software development kit SDK.
In the embodiment of the specification, the predetermined risk operation comprises a risk operation related to the running safety of the application program and a risk operation related to user privacy data.
In the embodiment of this specification, the method further includes:
and sending a first notification message that the target dynamic code can trigger a preset risk operation to a preset management device, and/or sending a second notification message that the target dynamic code is cancelled to the preset management device.
The embodiment of the present specification provides an information risk prevention and control device, which acquires a target dynamic code to be loaded when it is detected that an interface for loading a dynamic code in a terminal device is called, and then performs risk scanning on the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation, so that in a process of needing to load the dynamic code in an application program, risk detection and risk scanning may be performed on the dynamic code included in the application program to determine whether the dynamic code can trigger a specified risk operation, and then performs risk prevention and control on a corresponding dynamic code based on a risk scanning result, which not only can ensure the security of the operation of the application program and the terminal device, but also can effectively prevent private data of a user from being stolen.
EXAMPLE five
Further, based on the methods shown in fig. 1 to fig. 3, one or more embodiments of the present specification further provide a storage medium for storing computer-executable instruction information, in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, or the like, and when the storage medium stores the computer-executable instruction information, the storage medium implements the following processes:
when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded;
risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained;
and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
In the embodiment of this specification, the method further includes:
adding the dynamic code contained in the target application program into a queue which needs to be preset and is controlled based on the risk protection rule of the section;
the risk scanning the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation and obtain a corresponding risk scanning result includes:
and risk scanning is carried out on the target dynamic code through the risk protection rule based on the section so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result.
In the embodiment of this specification, the method further includes:
when the running of a target application program is detected, risk scanning is carried out on a main program code required by the running of the target application program, and a risk scanning result corresponding to the main program code is obtained;
when detecting that an interface used for loading dynamic codes in the terminal equipment is called, acquiring target dynamic codes to be loaded, including:
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, acquiring a target dynamic code to be loaded when detecting that an interface for loading the dynamic code in the terminal equipment is called.
In this embodiment of this specification, before acquiring a target dynamic code to be loaded when it is detected that an interface for loading a dynamic code in a terminal device is called, the method further includes:
acquiring a main program code required by the running of a target application program;
risk scanning is carried out on the main program code, and a risk scanning result corresponding to the main program code is obtained;
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, loading and running the main program code when the running of the target application program is detected.
In an embodiment of the present specification, the target dynamic code includes dynamic code provided in the target application.
In the embodiment of the present specification, the target application is an applet installed in a host program.
In an embodiment of the present specification, the target application is the host program integrated with a third party software development kit SDK.
In the embodiment of the specification, the predetermined risk operation comprises a risk operation related to the running safety of the application program and a risk operation related to user privacy data.
In the embodiment of this specification, the method further includes:
and sending a first notification message that the target dynamic code can trigger a preset risk operation to a preset management device, and/or sending a second notification message that the target dynamic code is cancelled to the preset management device.
The embodiment of the present specification provides a storage medium, which acquires a target dynamic code to be loaded when it is detected that an interface for loading a dynamic code in a terminal device is called, and then performs risk scanning on the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation, so that in a process of needing to load the dynamic code in an application program, risk detection and risk scanning can be performed on the dynamic code included in the application program to determine whether the dynamic code can trigger a designated risk operation, and then risk prevention and control can be performed on the corresponding dynamic code based on a risk scanning result, which not only can ensure the operating security of the application program and the terminal device, but also can effectively prevent private data of a user from being stolen.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present description are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable fraud case serial-parallel apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable fraud case serial-parallel apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable fraud case to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable fraud case serial-parallel apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (16)
1. A method of risk prevention and control of information, the method comprising:
when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded;
risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained;
and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
2. The method of claim 1, further comprising:
adding the dynamic code contained in the target application program into a queue which needs to be preset and is controlled based on the risk protection rule of the section;
the risk scanning the target dynamic code to determine whether the target dynamic code can trigger a predetermined risk operation and obtain a corresponding risk scanning result includes:
and risk scanning is carried out on the target dynamic code through the risk protection rule based on the section so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result.
3. The method of claim 1, further comprising:
when the running of a target application program is detected, risk scanning is carried out on a main program code required by the running of the target application program, and a risk scanning result corresponding to the main program code is obtained;
when detecting that an interface used for loading dynamic codes in the terminal equipment is called, acquiring target dynamic codes to be loaded, including:
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, acquiring a target dynamic code to be loaded when detecting that an interface for loading the dynamic code in the terminal equipment is called.
4. The method according to claim 1, before the target dynamic code to be loaded is acquired when it is detected that the interface for loading the dynamic code in the terminal device is called, the method further comprises:
acquiring a main program code required by the running of a target application program;
risk scanning is carried out on the main program code, and a risk scanning result corresponding to the main program code is obtained;
and if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger preset risk operation, loading and running the main program code when the running of the target application program is detected.
5. The method of claim 4, the target dynamic code comprising dynamic code provided in the target application.
6. The method of claim 5, the target application being an applet hosted by a host program.
7. The method of claim 6, the target application being the host program integrated with a third party Software Development Kit (SDK).
8. The method of claim 1, the predetermined risk operations comprising risk operations related to operational security of an application and risk operations related to user privacy data.
9. The method of claim 1, further comprising:
and sending a first notification message that the target dynamic code can trigger a preset risk operation to a preset management device, and/or sending a second notification message that the target dynamic code is cancelled to the preset management device.
10. An apparatus for risk prevention and control of information, the apparatus comprising:
the dynamic code acquisition module is used for acquiring a target dynamic code to be loaded when detecting that an interface used for loading the dynamic code in the terminal equipment is called;
the risk scanning module is used for carrying out risk scanning on the target dynamic code so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result;
and the loading canceling module cancels the loading of the target dynamic code if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation.
11. The apparatus of claim 10, the apparatus further comprising:
the dynamic code management and control module is used for adding the dynamic codes contained in the target application program into a queue which needs to be managed and controlled by preset risk protection rules based on a section;
and the risk scanning module carries out risk scanning on the target dynamic code through the risk protection rule based on the section so as to determine whether the target dynamic code can trigger preset risk operation or not and obtain a corresponding risk scanning result.
12. The apparatus of claim 10, the apparatus further comprising:
the first main code scanning module is used for scanning risks of a main program code required by the running of a target application program when the running of the target application program is detected, and obtaining a risk scanning result corresponding to the main program code;
and the dynamic code acquisition module acquires a target dynamic code to be loaded when detecting that an interface for loading the dynamic code in the terminal equipment is called if a risk scanning result corresponding to the main program code indicates that the main program code cannot trigger a preset risk operation.
13. The apparatus of claim 10, the apparatus further comprising:
the main code acquisition module is used for acquiring a main program code required by the running of the target application program;
the second main code scanning module is used for carrying out risk scanning on the main program code to obtain a risk scanning result corresponding to the main program code;
and the main code loading module is used for loading and running the main program code when the running of the target application program is detected if the risk scanning result corresponding to the main program code indicates that the main program code cannot trigger the preset risk operation.
14. The apparatus of claim 13, the target dynamic code comprising dynamic code provided in the target application, the target application being an applet hosted by a host program, or the target application being the host program integrated with a third party Software Development Kit (SDK).
15. A risk prevention and control device for information, the risk prevention and control device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded;
risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained;
and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
16. A storage medium for storing computer-executable instructions, which when executed implement the following:
when detecting that an interface used for loading dynamic codes in terminal equipment is called, acquiring target dynamic codes to be loaded;
risk scanning is carried out on the target dynamic code to determine whether the target dynamic code can trigger preset risk operation or not, and a corresponding risk scanning result is obtained;
and if the risk scanning result indicates that the target dynamic code can trigger the preset risk operation, cancelling the loading of the target dynamic code.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110319550.XA CN112926049A (en) | 2021-03-25 | 2021-03-25 | Information risk prevention and control method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110319550.XA CN112926049A (en) | 2021-03-25 | 2021-03-25 | Information risk prevention and control method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112926049A true CN112926049A (en) | 2021-06-08 |
Family
ID=76175992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110319550.XA Pending CN112926049A (en) | 2021-03-25 | 2021-03-25 | Information risk prevention and control method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112926049A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103714290A (en) * | 2013-12-26 | 2014-04-09 | 北京工业大学 | Software behavior obtaining, monitoring and verifying method |
| CN105493470A (en) * | 2013-08-28 | 2016-04-13 | 亚马逊科技公司 | Dynamic application security verification |
| CN108196833A (en) * | 2018-01-09 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Implementation method, storage medium, electronic equipment and the system of AOP agent frameworks |
| CN108710801A (en) * | 2018-05-29 | 2018-10-26 | 北京迪诺益佳信息科技有限公司 | A kind of behavior management-control method of mobile application dynamic load code |
| CN109871681A (en) * | 2019-02-28 | 2019-06-11 | 天津大学 | Android malware detection method is loaded towards dynamic code based on hybrid analysis |
| CN110362459A (en) * | 2019-06-18 | 2019-10-22 | 中国平安人寿保险股份有限公司 | A kind of system performance monitoring method and device, electronic equipment based on SpringAop |
| CN110460583A (en) * | 2019-07-15 | 2019-11-15 | 中国平安人寿保险股份有限公司 | A kind of sensitive information recording method and device, electronic equipment |
| CN111191246A (en) * | 2019-12-19 | 2020-05-22 | 杭州安恒信息技术股份有限公司 | Spring annotation based security development verification method |
| CN111914251A (en) * | 2020-07-03 | 2020-11-10 | 上海理想信息产业（集团）有限公司 | Intelligent terminal safety protection method and system based on hybrid control technology |
| CN112035858A (en) * | 2020-08-28 | 2020-12-04 | 中国建设银行股份有限公司 | API access control method, device, equipment and medium |
-
2021
- 2021-03-25 CN CN202110319550.XA patent/CN112926049A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105493470A (en) * | 2013-08-28 | 2016-04-13 | 亚马逊科技公司 | Dynamic application security verification |
| CN103714290A (en) * | 2013-12-26 | 2014-04-09 | 北京工业大学 | Software behavior obtaining, monitoring and verifying method |
| CN108196833A (en) * | 2018-01-09 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Implementation method, storage medium, electronic equipment and the system of AOP agent frameworks |
| CN108710801A (en) * | 2018-05-29 | 2018-10-26 | 北京迪诺益佳信息科技有限公司 | A kind of behavior management-control method of mobile application dynamic load code |
| CN109871681A (en) * | 2019-02-28 | 2019-06-11 | 天津大学 | Android malware detection method is loaded towards dynamic code based on hybrid analysis |
| CN110362459A (en) * | 2019-06-18 | 2019-10-22 | 中国平安人寿保险股份有限公司 | A kind of system performance monitoring method and device, electronic equipment based on SpringAop |
| CN110460583A (en) * | 2019-07-15 | 2019-11-15 | 中国平安人寿保险股份有限公司 | A kind of sensitive information recording method and device, electronic equipment |
| CN111191246A (en) * | 2019-12-19 | 2020-05-22 | 杭州安恒信息技术股份有限公司 | Spring annotation based security development verification method |
| CN111914251A (en) * | 2020-07-03 | 2020-11-10 | 上海理想信息产业（集团）有限公司 | Intelligent terminal safety protection method and system based on hybrid control technology |
| CN112035858A (en) * | 2020-08-28 | 2020-12-04 | 中国建设银行股份有限公司 | API access control method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180060569A1 (en) | Detection and Prevention of Malicious Shell Exploits | |
| CN111291374B (en) | Application program detection method, device and equipment | |
| US10986103B2 (en) | Signal tokens indicative of malware | |
| US20160217029A1 (en) | Data Flow Tracking Via Memory Monitoring | |
| CN108763951B (en) | Data protection method and device | |
| CN110889691B (en) | Information display method, device and equipment | |
| CN109684795B (en) | Method and device for anti-debugging of application program and electronic equipment | |
| CN112651040A (en) | Permission application method, component, device and computer readable storage medium | |
| CN114896603A (en) | Service processing method, device and equipment | |
| CN112948824B (en) | Program communication method, device and equipment based on privacy protection | |
| US11349658B2 (en) | Blockchain data processing method, apparatus, and device | |
| CN112926089B (en) | Data risk prevention and control method, device and equipment based on privacy protection | |
| CN111259374B (en) | Authority abnormity detection method and device, computer equipment and storage medium | |
| CN110581921B (en) | Control method and device for folding screen equipment | |
| CN113467981A (en) | Exception handling method and device | |
| CN115495777A (en) | Data protection method and device, storage medium and electronic equipment | |
| CN116820668A (en) | Container escape detection method and system based on fanotify | |
| CN112926049A (en) | Information risk prevention and control method, device and equipment | |
| Kaur et al. | PeMo: Modifying application's permissions and preventing information stealing on smartphones | |
| CN107392010B (en) | Root operation execution method and device, terminal equipment and storage medium | |
| CN111488569B (en) | Authority determining and managing method, device, equipment and medium | |
| CN106203087B (en) | Injection protection method, system, terminal and storage medium | |
| CN111882321A (en) | Identity verification processing method, device and system | |
| CN111859461A (en) | Data isolation method and device and electronic equipment | |
| CN113239851B (en) | Privacy image processing method, device and equipment based on privacy protection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |