CN116107912A - Security detection method and system based on application software - Google Patents
Security detection method and system based on application software Download PDFInfo
- Publication number
- CN116107912A CN116107912A CN202310362356.9A CN202310362356A CN116107912A CN 116107912 A CN116107912 A CN 116107912A CN 202310362356 A CN202310362356 A CN 202310362356A CN 116107912 A CN116107912 A CN 116107912A
- Authority
- CN
- China
- Prior art keywords
- application software
- architecture
- dangerous
- security
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
- G06F21/566—Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Quality & Reliability (AREA)
- General Health & Medical Sciences (AREA)
- Virology (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a security detection method and a security detection system based on application software, which belong to the technical field of security detection, and the method comprises the following steps: according to the functional dangers and the application dangers of each sub-architecture in the software architecture of the current application software, and establishing a first dangerous constraint relation; determining a security failed result of the current application software in different application environments, and establishing a second dangerous constraint relation; according to the software execution logic of the current application software, matching a corresponding safety detection mode to carry out safety detection, and when a safety detection result is related to random failure of a component, screening a first matching relation from all first dangerous constraint relations to construct a first protection mechanism to carry out first protection; and otherwise, screening the second matching relation from all the second dangerous constraint relations to construct a second protection mechanism for second protection. The method is convenient for realizing high-efficiency detection and targeted protection, can effectively reduce the use waiting time of the application and improves the safety detection efficiency.
Description
Technical Field
The invention relates to the technical field of safety detection, in particular to a safety detection method and system based on application software.
Background
Application software (Application) corresponds to system software, and is a collection of various programming languages that can be used by users and Application programs programmed in various programming languages, and is divided into Application packages and user programs. An application software package is a collection of programs designed to solve a class of problems with a computer, and is used by users in many cases.
In the prior art, before application software is used, security detection of viruses and the like is performed on the application software to ensure the use security of the application software, but at present, many detection modes are that whether all contents of the application software need to be detected again or not is automatically detected by a window such as whether the user continues to access or not, and the detection process is that all contents need to be detected again or not after the user accesses, and only when no invasion is determined, whether follow-up starting or not is determined, that is, in the mode, in the process of determining whether the invasion exists or not, repeated detection and repeated abnormal repair are performed on the application software for a plurality of times to ensure the use security of the application software, which can definitely improve the use waiting time of the application.
Therefore, the invention provides a security detection method and system based on application software.
Disclosure of Invention
The invention provides a safety detection method and system based on application software, which are used for solving the technical problems.
The invention provides a security detection method based on application software, which comprises the following steps:
step 1: according to the normal behavior and possible abnormal behavior of each sub-architecture in the software architecture of the current application software, determining the functional risk and the application risk of the corresponding sub-architecture, and establishing a first risk constraint relation of the corresponding sub-architecture;
step 2: determining a security failing result of the current application software under different application environments according to the application environments of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environments;
step 3: according to the software execution logic of the current application software, matching a corresponding safety detection mode to carry out safety detection, and when a safety detection result is related to random failure of a component, screening a first matching relation from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
Step 4: and when the safety detection result is irrelevant to the random failure of the component, screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism so as to carry out second protection on the current application software.
Preferably, determining the functional risk and the application risk of each sub-architecture in the software architecture of the current application software according to the normal behavior and the possible abnormal behavior of the corresponding sub-architecture includes:
calling a behavior data packet consistent with the current application software from an application software database, and carrying out packet disassembly to obtain normal behavior and possible abnormal behavior of a corresponding sub-architecture;
performing a first assignment of the function weight and a second assignment of the application weight according to the first behavior type of each normal behavior and the second behavior type of each possible abnormal behavior;
and obtaining the functional risk of the corresponding subframe according to the first assignment result, and obtaining the application risk of the corresponding subframe according to the second assignment result.
Preferably, establishing a first dangerous constraint relation of the corresponding sub-architecture includes:
determining a building mode of the current application software based on a software attribute database;
According to the architecture type of each sub-architecture, and combining the building modes, determining building weight d1 of the corresponding sub-architecture based on the current application software;
establishing a first hazard function Y1 (d 1, g1, Y1) of the corresponding sub-architecture, wherein g1 represents the functional hazard of the corresponding sub-architecture; y1 represents the application risk of the corresponding sub-architecture;
acquiring a dangerous boundary S1 related to a corresponding sub-architecture from a dangerous database, and constructing a first dangerous constraint relation: y1 (d 1, g1, Y1) < Y1 (S1).
Preferably, determining a security failed result of the current application software under different application environments according to the application environment of the current application software and a security detection mechanism of each application environment includes:
matching the security detection mechanism with the current application software in different application environments from an application-environment-security database;
based on the safety detection mechanism, carrying out safety detection on current application software in a corresponding application environment, and carrying out result standardized consistency analysis on a safety detection result according to safety detection indexes of the safety detection mechanism;
and obtaining inconsistent indexes according to the consistent analysis results, and taking the results of the inconsistent indexes as safe failed results in the corresponding application environment.
Preferably, establishing a second dangerous constraint relation corresponding to the application environment includes:
acquiring all inconsistent indexes under the same application environment, and establishing an index constraint relation corresponding to the inconsistent indexes according to a detection result y3 of the inconsistent indexes:
wherein->
Representing standard detection results corresponding to the inconsistent indexes; />
Representing a first constraint constant; />
Representing a second constraint constant;
and establishing and obtaining a second dangerous constraint relation under the corresponding application environment based on all index constraint relations under the same application environment.
Preferably, according to the software execution logic of the current application software, the security detection is performed by matching with a corresponding security detection mode, including:
acquiring a software execution flow of the current application software, and logically operating each execution block in the software execution flow;
if the logic operation passes, judging that the corresponding execution block meets the execution requirement, and performing first locking on the corresponding execution block;
if the logic operation does not pass, obtaining error indication of a corresponding execution block, and obtaining an effective detection factor aiming at the error indication from an indication-detection mapping table;
acquiring all effective detection factors of the software execution flow, and matching from a factor-detection database to obtain a detection set;
And acquiring a first locked execution block, performing similar matching with the detection set according to the block attribute, and acquiring a detection mode with highest similarity as a matched safety detection mode to perform safety detection on the current application software.
Preferably, when the security detection result is related to random failure of the component, a first protection mechanism is constructed by screening a first matching relationship from all first dangerous constraint relationships, so as to perform first protection on the current application software, including:
acquiring component attributes of a random failure component, and locking a failure sub-architecture;
screening and obtaining a first matching relation consistent with a failure sub-architecture and a current dangerous relation of the failure sub-architecture from all first dangerous constraint relations;
retrieving first security measures consistent with each first matching relationship and the current dangerous relationship of each failure sub-architecture from a relationship-security database;
and constructing a first protection mechanism based on the first security measure, and performing first protection on the current application software.
Preferably, when the security detection result is irrelevant to the random failure of the component, screening the second matching relationship from all the second dangerous constraint relationships to construct a second protection mechanism, so as to perform the second protection on the current application software, including:
Determining a dangerous application environment of the current application software according to a safety detection result;
screening and obtaining a second matching relation consistent with the dangerous application environment from all second dangerous constraint relations, and determining a current dangerous relation of the dangerous application environment;
retrieving second security measures consistent with each second matching relationship and the current dangerous relationship of the dangerous application environment from the relationship-security database;
and constructing a second protection mechanism based on all the second security measures, and performing second protection on the current application software.
The invention provides a safety detection system based on application software, which comprises:
the first relation establishing module is used for determining the functional risk and the application risk of the corresponding sub-architecture according to the normal behavior and the possible abnormal behavior of each sub-architecture in the software architecture of the current application software, and establishing a first risk constraint relation of the corresponding sub-architecture;
the second relation establishing module is used for determining a security failing result of the current application software under different application environments according to the application environment of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environment;
The first protection module is used for matching a corresponding safety detection mode to carry out safety detection according to the software execution logic of the current application software, and when a safety detection result is related to random failure of a component, a first matching relation is screened from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
and the second protection module is used for screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism to carry out second protection on the current application software when the safety detection result is irrelevant to the random failure of the component.
Compared with the prior art, the beneficial effects of the application are as follows:
the analysis of the sub-architecture of the application software and the analysis of the software based on the application environment effectively establish a dangerous constraint relation, and then the high-efficiency detection of the application software is realized in a targeted detection mode through the software execution logic of the current application software, and the targeted protection is conveniently realized by acquiring protection mechanisms under different conditions, so that the use waiting time of the application can be effectively reduced, and the safety detection efficiency is improved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
FIG. 1 is a flowchart of a security detection method based on application software according to an embodiment of the present invention;
FIG. 2 is a block diagram of a security detection system based on application software in an embodiment of the present invention;
fig. 3 is a block diagram of a software architecture in an embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are for illustration and explanation of the present invention only, and are not intended to limit the present invention.
The invention provides a security detection method based on application software, as shown in figure 1, comprising the following steps:
step 1: according to the normal behavior and possible abnormal behavior of each sub-architecture in the software architecture of the current application software, determining the functional risk and the application risk of the corresponding sub-architecture, and establishing a first risk constraint relation of the corresponding sub-architecture;
Step 2: determining a security failing result of the current application software under different application environments according to the application environments of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environments;
step 3: according to the software execution logic of the current application software, matching a corresponding safety detection mode to carry out safety detection, and when a safety detection result is related to random failure of a component, screening a first matching relation from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
step 4: and when the safety detection result is irrelevant to the random failure of the component, screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism so as to carry out second protection on the current application software.
In this embodiment, the software architecture refers to various components for the application software, as shown in fig. 3, each software architecture includes several components, and each component can be regarded as a sub-architecture, that is, a component application that implements interface skip by clicking a component in each application software, for example, a search component, a query component, and so on.
In this embodiment, the normal behavior and possible abnormal behavior of the sub-architecture refer to abnormal behavior of the corresponding component, such as a flashing behavior, or a behavior of automatically jumping to a non-corresponding interface, which is existed in the application software in the history application process, and the normal behavior refers to a behavior of the component in which a vulnerability never occurs, for example, a search keyword can be consistently input for the search component, and the input behavior is the normal behavior.
In this embodiment, the functional risk is related to the function of the sub-architecture, and when the sub-architecture is aimed at the search component, the function is to meet the search requirement according to the search, and the picture search, the text search and the like which can be realized by the keywords, that is, the search program corresponding to the search program in the search process has search attack loopholes, such as virus attack and the like, so that the search process jumps to the non-required interface, and at the moment, the functional risk is caused.
In this embodiment, the application risk is related to the application object corresponding to the software, the risk brought by different application objects is different, the user 1 is a network quality user, the user 2 is a network non-quality user, and at this time, the risk brought by the user 2 to the current application software is greater than the risk brought by the user 1 to the current application software, where the current application software refers to any app software.
In this embodiment, the first risk constraint is built for the application risk and the functional risk of the same application software.
In this embodiment, the application environment refers to the use condition of the application software under different network connection conditions, and the security of the corresponding application software is determined according to the security of the network environment, and the security detection mechanisms corresponding to different security network environments are different, so that the worse the network environment is, the higher the detection level of the corresponding security detection mechanism is, and the security use condition under different application environments is guaranteed to the greatest extent.
In this embodiment, the security failed result is determined based on comparing the security detection result under the same application environment with the standard detection result, and then a second dangerous constraint relationship is established, where each security detection mechanism is a standard detection result that is especially existing, and the security detection mechanism is determined in advance by an expert, mainly for security detection using different application software in the network environment.
In this embodiment, the software execution logic refers to software code of the application software, and the software code is executed in a certain order, and the execution purpose of the software code is not the same, and thus, is referred to as software execution logic.
In this embodiment, the security detection mode is obtained by matching from a corresponding mapping table, so as to ensure the security detection of the application software to the greatest extent, where the security detection mode includes a plurality of detection indexes, and further obtains the final detection values of different detection indexes according to the security detection result.
In this embodiment, the random failure of the component refers to that a related security exception problem exists because of a fault exception of the component itself, so that a matching relationship is obtained from a relationship related to the function itself, and a first protection mechanism is constructed.
In this embodiment, the software execution logic refers to the execution code of the application software, for example, including: execution blocks 1, 2 and 3, wherein execution block 1 and execution block 2 meet execution requirements, and execution block 3 does not meet execution requirements, and at this time, a relevant instruction (an error is automatically alarm and indicated in the process of code running) for execution block 3 needs to be acquired, and at this time, a relevant valid detection factor needs to be matched from a mapping table according to the instruction, and the valid detection factor is required to exist in a security detection mode acquired later, so that security detection is realized.
In this embodiment, the first hazard constraint relationship comprises: and the relationships 1, 2 and 3, wherein the security detection relationship is related to the random failure of the component, the randomly failed component is related to the relationships 1 and 2, at this time, the relationships 1 and 2 can be regarded as a first matching relationship to construct a first protection mechanism, wherein the dangerous constraint relationship related to the randomly failed component is a relationship established according to the normal behavior and the possible abnormal behavior corresponding to the component, the acquisition of the relationship and the construction of the mechanism are convenient, and the constructed first protection mechanism is used for carrying out security protection on the randomly failed component to prevent the randomly failed component from being attacked to realize the security detection of the randomly failed component.
In this embodiment, when the security detection result is unrelated to the random failure of the component, it is determined that the security detection result is related to the application environment, and at this time, a related second matching relationship needs to be called from all second dangerous constraint relationships to construct a second protection mechanism, for example, related to the application environment 1, and at this time, a second matching relationship for the application environment 1 needs to be acquired to construct a second protection mechanism for the application environment 1, where the second protection mechanism is the acquired method for coping with the existing network security environment, so as to avoid the attack of the current application software under the condition that the network environment is unsafe, and further ensure the security detection of the application software.
The beneficial effects of the technical scheme are as follows: the analysis of the sub-architecture of the application software and the analysis of the software based on the application environment effectively establish a dangerous constraint relation, and then the high-efficiency detection of the application software is realized in a targeted detection mode through the software execution logic of the current application software, and the targeted protection is conveniently realized by acquiring protection mechanisms under different conditions, so that the use waiting time of the application can be effectively reduced, and the safety detection efficiency is improved.
The invention provides a security detection method based on application software, which determines the functional danger and the application danger of the corresponding sub-architecture according to the normal behavior and the possible abnormal behavior of each sub-architecture in the software architecture of the current application software, and comprises the following steps:
calling a behavior data packet consistent with the current application software from an application software database, and carrying out packet disassembly to obtain normal behavior and possible abnormal behavior of a corresponding sub-architecture;
performing a first assignment of the function weight and a second assignment of the application weight according to the first behavior type of each normal behavior and the second behavior type of each possible abnormal behavior;
and obtaining the functional risk of the corresponding subframe according to the first assignment result, and obtaining the application risk of the corresponding subframe according to the second assignment result.
In this embodiment, the application software database is constructed after the application software is built and put into use to perform various security tests on the application software, where the database includes various behavior data packets of the application software, and the data packets include normal behaviors and possible abnormal behaviors of different components, where the normal behaviors are aimed at the possibility that the same component will not be attacked during use, or even if the possibility that the application software is attacked exists, the possibility that the application software is never attacked during testing is successful, and the possible abnormal behaviors are aimed at the possibility that the application software will be attacked and the attack will be successful during use of the same component.
In this embodiment, for example, for the behavior of flashing, or automatic jump to a non-corresponding interface, the two behaviors are regarded as possible abnormal behaviors, and the corresponding behavior types are respectively: the flashing is of a type and a jump failure behavior type, the search behavior aiming at the search component can be regarded as normal behavior, and the corresponding behavior types are as follows: search behavior types.
In this embodiment, for example, the subframe is a search component, and the normal behavior determined based on the search component includes: behaviors 1 and 2, the determined possible abnormal behaviors include: the behavior 3, 4 and 5 are constructed to obtain a behavior sequence [ behavior 1, behavior 2, behavior 3, behavior 4 and behavior 5] aiming at the same sub-architecture, and for the sequence, a first assignment aiming at each behavior is obtained from a behavior-function weight database, and the behavior-function database contains different behavior sequences and assignment conditions matched with the behavior sequences, so that a corresponding first assignment result can be directly obtained.
In this embodiment, since the dangerous situation caused by the access situation of each behavior for different users is different, the assignment of different users for the same behavior is obtained from the behavior-application database, and the assignment is averaged to implement the second assignment, where the behavior-application database includes different behavior sequences and the dangerous situation of the user access matched with the behavior sequences to match and obtain the assignment result of each behavior.
The calculation process of the second assignment is as follows:
wherein F0 represents a second assignment corresponding to the same behavior;
representing the assignment result of the same behavior based on the i1 st user; />
Representing the maximum assignment of n1 users to the same behavior; />
Representing the minimum assignment of n1 users to the same behavior;
in this embodiment, the calculation of the functional risk is as follows:
wherein g1 represents a corresponding functional risk;
the number of normal behaviors contained in the same application software is represented;
the number of possible abnormal behaviors contained in the same application software is represented; />
A first assignment representing the j1 st normal behavior under the same application software; />
A first assignment representing the j2 nd possible abnormal behavior under the same application software; / >
Representing the maximum assignment in the first assignments corresponding to all possible abnormal behaviors under the same application software; />
The first set constant for possible abnormal behavior in the function danger determining process is generally 0.8; />
A second setting representing the possible abnormal behavior corresponding to the maximum assignment in the function danger determination processConstant, generally 0.2.
In this embodiment, the calculation process of the application risk is as follows:
wherein, the liquid crystal display device comprises a liquid crystal display device,
a second assignment representing the j1 st normal behavior under the same application software; />
A second assignment representing the j2 nd possible abnormal behavior under the same application software; />
Representing the maximum assignment in the second assignments corresponding to all possible abnormal behaviors under the same application software; />
3 represents a third set constant for possible abnormal behavior in the application risk determination process, and the value is generally 0.9; />
4 represents a fourth set constant for possible abnormal behaviors corresponding to the maximum assignment in the application risk determination process, and the value is generally 0.1; y1 represents the corresponding application risk.
The beneficial effects of the technical scheme are as follows: through the first assignment of the function weight and the second assignment of the application weight, the function dangers and the application dangers are obtained through effective calculation, a basis is provided for the follow-up construction of the first dangerous constraint condition, and the effectiveness of follow-up safety detection and the effectiveness of safety protection are guaranteed.
The invention provides a security detection method based on application software, which establishes a first dangerous constraint relation of a corresponding sub-architecture and comprises the following steps:
determining a building mode of the current application software based on a software attribute database;
according to the architecture type of each sub-architecture, and combining the building modes, determining building weight d1 of the corresponding sub-architecture based on the current application software;
establishing a first hazard function Y1 (d 1, g1, Y1) of the corresponding sub-architecture, wherein g1 represents the functional hazard of the corresponding sub-architecture; y1 represents the application risk of the corresponding sub-architecture;
acquiring a dangerous boundary S1 related to a corresponding sub-architecture from a dangerous database, and constructing a first dangerous constraint relation: y1 (d 1, g1, Y1) < Y1 (S1).
In this embodiment, the software attribute database comprises different software types and software build modes matching the software types, wherein a software build mode refers to a build mode of the software, i.e. in which way the different components are built, e.g. in which the important component is built before the secondary component.
In this embodiment, the architecture type of the sub-architecture refers to the type of the component, such as the search type, the message type, etc., mainly depends on the implementation function of the corresponding component, and thus, the different components play different roles in the corresponding software, so that the corresponding building weights are different, and the weights of the first-built components are determined to be greater than the weights of the later-built components according to the building mode.
In this embodiment, the cumulative sum of all the building weights for the same application is 1.
In this embodiment, the building weights are initial building weights for each sub-architecture, which are determined primarily from a pattern-weight database based on the building pattern, and then the initial building weights are adjusted according to the architecture type of each sub-architecture, so as to obtain the building weights based on the current application software, where the pattern-weight database includes different building patterns and weights of different application software and sub-architectures of the application software in the building pattern, so that the initial building weights can be obtained.
In this embodiment, because the architecture type of the sub-architecture may have a slight variation in the actual use process, for example, in the process of adjusting the program, at this time, a certain influence is caused on the weight of the sub-architecture, so that the initial building weight needs to be adjusted to obtain the corresponding building weight d1, for example, the initial building weight of the sub-architecture 1 is g01, after the adjustment according to the architecture type, the product of g02, g02=g01 and the relevant adjustment coefficient is obtained, and the value range of the adjustment coefficient is [0.8,1.2], but the sum of the weights after all adjustments is 1, and the sum of the initial building weights before the adjustment is also 1.
In this embodiment, the hazard database is a maximum functional hazard boundary containing different applications and sub-frameworks contained in the applications
Maximum application risk boundary +.>
Internally, S1 can thus be acquired, i.e. comprising a maximum functional risk boundary and a minimum application risk boundary.
Wherein the first dangerous constraint relationship, i.e. the determined first dangerous function of the sub-architecture, is to have a constraint boundary relationship, i.e.
And y->
2, wherein S1 includes S01 and S02.
The beneficial effects of the technical scheme are as follows: according to the construction mode of the application software and the construction type of the sub-architecture, construction weight is determined, and then a basis is provided for subsequent safety detection and the reliability of subsequent safety protection is ensured by establishing a dangerous function and dangerous constraint conditions.
The invention provides a security detection method based on application software, which determines the security failing result of the current application software in different application environments according to the application environment of the current application software and the security detection mechanism of each application environment, and comprises the following steps:
matching the security detection mechanism with the current application software in different application environments from an application-environment-security database;
Based on the safety detection mechanism, carrying out safety detection on current application software in a corresponding application environment, and carrying out result standardized consistency analysis on a safety detection result according to safety detection indexes of the safety detection mechanism;
and obtaining inconsistent indexes according to the consistent analysis results, and taking the results of the inconsistent indexes as safe failed results in the corresponding application environment.
In this embodiment, the application-environment-security database includes different application software, security detection mechanisms under different network environments where different application software is located, and standard detection results of the application software using the security detection mechanisms, and the security detection mechanisms are mainly used for security detection of the application software, because the network environments are different, attacks suffered by the same application software are different, and therefore, the security detection mechanism with the best match is obtained to perform security detection on the application software.
In this embodiment, the detection index of the security detection mechanism in the relatively unsafe network environment for the same application software is more than the detection index of the security detection mechanism in the relatively safe network environment for the same application software.
In this embodiment, after the security detection mechanism is adopted to perform security detection on the current application software, a security detection result 01 of the security detection index 1 and a security detection result 02 of the security detection index 2 are obtained, and at this time, a standard detection result 03 of the security detection index 1 corresponding to the security detection mechanism and a standard detection result 04 of the security detection index 2 are respectively compared with the corresponding security detection result 01 and the security detection result 02 to obtain a consistent analysis result.
In this embodiment, when the security detection result 01 does not coincide with the standard detection result 03, the existing inconsistency is the security detection index 1 as a security failed result, and when the security detection result 02 does not coincide with the standard detection result 04, the existing inconsistency is the security detection index 2 as a security failed result.
The beneficial effects of the technical scheme are as follows: the security detection mechanism under different application environments is matched to realize the security detection of the application software, and the security failed result existing at the position is effectively determined through the result consistency analysis, so that the basis is provided for not subsequently establishing the second dangerous constraint condition.
The invention provides a security detection method based on application software, which establishes a second dangerous constraint relation corresponding to an application environment and comprises the following steps:
acquiring all inconsistent indexes under the same application environment, and establishing an index constraint relation corresponding to the inconsistent indexes according to a detection result y3 of the inconsistent indexes:
wherein->
Representing standard detection results corresponding to the inconsistent indexes; />
Representing a first constraint constant; />
Representing a second constraint constant;
and establishing and obtaining a second dangerous constraint relation under the corresponding application environment based on all index constraint relations under the same application environment.
In this embodiment, the first constraint constant is generally 0, and the second constraint constant is generally 1.
In this embodiment, since a plurality of inconsistent indexes exist in the same application environment and each inconsistent index has an index constraint relationship existing therein, all the index constraint relationships in the same application environment are the corresponding second dangerous constraint relationships.
In this embodiment, the detection result may be a detection value for the relevant index, that is, the detection value of the corresponding index may be directly obtained in the detection process using the detection index.
The beneficial effects of the technical scheme are as follows: by acquiring the index constraint relation of each inconsistent index, the second dangerous constraint relation aiming at the application environment is conveniently established and obtained, and a foundation is provided for subsequent safety detection and safety protection.
The invention provides a security detection method based on application software, which matches a corresponding security detection mode for security detection according to software execution logic of the current application software, and comprises the following steps:
acquiring a software execution flow of the current application software, and logically operating each execution block in the software execution flow;
if the logic operation passes, judging that the corresponding execution block meets the execution requirement, and performing first locking on the corresponding execution block;
if the logic operation does not pass, obtaining error indication of a corresponding execution block, and obtaining an effective detection factor aiming at the error indication from an indication-detection mapping table;
acquiring all effective detection factors of the software execution flow, and matching from a factor-detection database to obtain a detection set;
and acquiring a first locked execution block, performing similar matching with the detection set according to the block attribute, and acquiring a detection mode with highest similarity as a matched safety detection mode to perform safety detection on the current application software.
In this embodiment, the software execution flow refers to all program codes existing in the software, because the extent codes are different in positions of the whole code page, and the execution of codes in different block positions is realized based on the code design, and the codes are realized based on the matched code running interfaces, and in the process of running the codes, the error of which line of codes is automatically indicated, or the logic condition of how to cause problems occurs, so that whether the corresponding execution block runs through is determined by logically running each execution block.
In the embodiment, the error indication is directly displayed in the code running process, the existing error condition can be intuitively obtained, the indication-detection mapping table comprises different error indications and effective detection factors matched with the error indications, the follow-up effective direct detection of the application software in the detection process according to the effective detection factors is ensured, and the pertinence and the high efficiency of the detection are ensured.
In this embodiment, for example, during the running process, an error indication occurs in the interface jump code in the execution block 1, and then during the subsequent detection process, the jump condition of different components in the application software needs to be detected safely, so as to effectively and doubly ensure the jump security of the components.
In this embodiment, for example, there are valid detection factors 1, 2, 3, at which time all security detection modes including valid detection factors 1, 2, 3 are matched from the factor-detection database.
In this embodiment, the block attribute refers to the main execution content of the execution block corresponding to the first lock, that is, what kind of parameters in the main execution content need to be detected, so that the detection mode with the highest similarity is obtained by performing similar matching with each security detection mode in the set.
The beneficial effects of the technical scheme are as follows: the execution blocks related to the process are subjected to logic operation detection to be matched through error indication, and the similar matching is carried out again through the block attributes of the locked execution blocks, so that a safety detection mode is obtained, and safety detection is realized.
The invention provides a security detection method based on application software, when a security detection result is related to random failure of a component, a first protection mechanism is constructed by screening first matching relations from all first dangerous constraint relations, so as to carry out first protection on the current application software, and the security detection method comprises the following steps:
acquiring component attributes of a random failure component, and locking a failure sub-architecture;
Screening and obtaining a first matching relation consistent with a failure sub-architecture and a current dangerous relation of the failure sub-architecture from all first dangerous constraint relations;
retrieving first security measures consistent with each first matching relationship and the current dangerous relationship of each failure sub-architecture from a relationship-security database;
and constructing a first protection mechanism based on the first security measure, and performing first protection on the current application software.
In this embodiment, the randomly disabled component refers to a security problem of the corresponding component due to an abnormality of the component code itself and the like, and the security problem is aimed at the abnormality of the component code itself.
In this embodiment, the component attribute refers to the component type, so as to determine the failure sub-architecture, and in fact, the component corresponds to the sub-architecture one by one, or may be said to be the sub-architecture.
In this embodiment, all sub-architectures have the first dangerous constraint relationship, so that the relationship consistent with the failed sub-architecture can be directly called from the first dangerous constraint relationship as the first matching relationship.
In this embodiment, the relationship-security database includes different first dangerous constraint relationships and security protection measures corresponding to dangerous differences between the first dangerous constraint relationships and current dangerous relationships corresponding to the failure sub-architecture, so that the software is prevented from being damaged to the greatest extent, and therefore, in the determining process, the first security measures are invoked, where the first security measures are related to functional security protection and application security protection, and if the functional security protection is, for example, security protection for jumping to an interface with no need (if problematic code is for a jump problem), if the application security protection is, for example, access to the failure sub-architecture by a network non-quality user brings a certain danger, at this time, the security measures for the danger need to be invoked, so that the failure sub-architecture satisfies the first dangerous constraint relationships to the greatest extent, and reliable protection of the current application software is achieved.
In this embodiment, the first protection mechanism is constituted by all the first security measures.
In this embodiment, the first security measure is to realize that the failure sub-architecture can maximally satisfy the corresponding first matching relationship, so as to ensure the effectiveness of the subsequent protection.
In this embodiment, the following dangerous relationship of the failure sub-architecture is: y1 (d 1, g11, Y11), at this time, it is necessary to satisfy: y1 (d 1, g11, Y11)<Y1（d1,d1
g1,d1/>
y 1), wherein g11 represents the current functional risk corresponding to the failed sub-architecture, and y11 represents the current application risk corresponding to the failed sub-architecture.
The beneficial effects of the technical scheme are as follows: the matching relation is called through locking the failure sub-architecture, so that a safety measure of the matching relation is obtained, and the safety measure can maximally realize that the failure sub-architecture meets the corresponding matching relation, so that the effectiveness of software protection is ensured.
The invention provides a security detection method based on application software, when a security detection result is irrelevant to random failure of a component, a second protection mechanism is constructed by screening second matching relations from all second dangerous constraint relations, so as to carry out second protection on the current application software, and the security detection method comprises the following steps:
Determining a dangerous application environment of the current application software according to a safety detection result;
screening and obtaining a second matching relation consistent with the dangerous application environment from all second dangerous constraint relations, and determining a current dangerous relation of the dangerous application environment;
retrieving second security measures consistent with each second matching relationship and the current dangerous relationship of the dangerous application environment from the relationship-security database;
and constructing a second protection mechanism based on all the second security measures, and performing second protection on the current application software.
In this embodiment, the dangerous application environment refers to an unsafe network environment.
In this embodiment, each network environment has its corresponding second risk constraint relationship, and therefore, a second matching relationship that matches the network environment can be obtained.
In this embodiment, the relationship-security database is comprised of security measures that match the difference in relationship between the second, different, dangerous constraint relationship and the current dangerous relationship of the dangerous application environment, and is primarily for the purpose of securing the current dangerous relationship to the current network environment.
In this embodiment, the second protection mechanism is a combination of all the second security measures.
The beneficial effects of the technical scheme are as follows: the security measures are effectively called by determining dangerous application environments and determining the relationship difference between the dangerous application environments and the dangerous application environments, so that the second protection of the software is realized, and the effectiveness of protection and the effectiveness of security detection are ensured.
The invention provides a security detection system based on application software, as shown in fig. 2, comprising:
the first relation establishing module is used for determining the functional risk and the application risk of the corresponding sub-architecture according to the normal behavior and the possible abnormal behavior of each sub-architecture in the software architecture of the current application software, and establishing a first risk constraint relation of the corresponding sub-architecture;
the second relation establishing module is used for determining a security failing result of the current application software under different application environments according to the application environment of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environment;
the first protection module is used for matching a corresponding safety detection mode to carry out safety detection according to the software execution logic of the current application software, and when a safety detection result is related to random failure of a component, a first matching relation is screened from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
And the second protection module is used for screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism to carry out second protection on the current application software when the safety detection result is irrelevant to the random failure of the component.
The beneficial effects of the technical scheme are as follows: the analysis of the sub-architecture of the application software and the analysis of the software based on the application environment effectively establish a dangerous constraint relation, and then the high-efficiency detection of the application software is realized in a targeted detection mode through the software execution logic of the current application software, and the targeted protection is conveniently realized by acquiring protection mechanisms under different conditions, so that the use waiting time of the application can be effectively reduced, and the safety detection efficiency is improved.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (9)
1. A security detection method based on application software, comprising:
step 1: according to the normal behavior and possible abnormal behavior of each sub-architecture in the software architecture of the current application software, determining the functional risk and the application risk of the corresponding sub-architecture, and establishing a first risk constraint relation of the corresponding sub-architecture;
Step 2: determining a security failing result of the current application software under different application environments according to the application environments of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environments;
step 3: according to the software execution logic of the current application software, matching a corresponding safety detection mode to carry out safety detection, and when a safety detection result is related to random failure of a component, screening a first matching relation from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
step 4: and when the safety detection result is irrelevant to the random failure of the component, screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism so as to carry out second protection on the current application software.
2. The application software-based security detection method according to claim 1, wherein determining the functional risk and the application risk of each sub-architecture in the software architecture of the current application software based on the normal behavior and the possible abnormal behavior of the corresponding sub-architecture comprises:
calling a behavior data packet consistent with the current application software from an application software database, and carrying out packet disassembly to obtain normal behavior and possible abnormal behavior of a corresponding sub-architecture;
Performing a first assignment of the function weight and a second assignment of the application weight according to the first behavior type of each normal behavior and the second behavior type of each possible abnormal behavior;
and obtaining the functional risk of the corresponding subframe according to the first assignment result, and obtaining the application risk of the corresponding subframe according to the second assignment result.
3. The application-based security detection method of claim 2, wherein establishing a first risk constraint relationship for the corresponding sub-architecture comprises:
determining a building mode of the current application software based on a software attribute database;
according to the architecture type of each sub-architecture, and combining the building modes, determining building weight d1 of the corresponding sub-architecture based on the current application software;
establishing a first hazard function Y1 (d 1, g1, Y1) of the corresponding sub-architecture, wherein g1 represents the functional hazard of the corresponding sub-architecture; y1 represents the application risk of the corresponding sub-architecture;
acquiring a dangerous boundary S1 related to a corresponding sub-architecture from a dangerous database, and constructing a first dangerous constraint relation: y1 (d 1, g1, Y1) < Y1 (S1).
4. The application software-based security detection method according to claim 1, wherein determining a security failed result of the current application software in different application environments according to an application environment of the current application software and a security detection mechanism of each application environment comprises:
Matching the security detection mechanism with the current application software in different application environments from an application-environment-security database;
based on the safety detection mechanism, carrying out safety detection on current application software in a corresponding application environment, and carrying out result standardized consistency analysis on a safety detection result according to safety detection indexes of the safety detection mechanism;
and obtaining inconsistent indexes according to the consistent analysis results, and taking the results of the inconsistent indexes as safe failed results in the corresponding application environment.
5. The application-based security detection method of claim 4, wherein establishing a second risk constraint relationship corresponding to the application environment comprises:
acquiring all inconsistent indexes under the same application environment, and establishing an index constraint relation corresponding to the inconsistent indexes according to a detection result y3 of the inconsistent indexes:
wherein->
Representing standard detection results corresponding to the inconsistent indexes; />
Representing a first constraint constant; />
Representing a second constraint constant;
and establishing and obtaining a second dangerous constraint relation under the corresponding application environment based on all index constraint relations under the same application environment.
6. The application software-based security detection method according to claim 1, wherein the matching the corresponding security detection mode for security detection according to the software execution logic of the current application software comprises:
acquiring a software execution flow of the current application software, and logically operating each execution block in the software execution flow;
if the logic operation passes, judging that the corresponding execution block meets the execution requirement, and performing first locking on the corresponding execution block;
if the logic operation does not pass, obtaining error indication of a corresponding execution block, and obtaining an effective detection factor aiming at the error indication from an indication-detection mapping table;
acquiring all effective detection factors of the software execution flow, and matching from a factor-detection database to obtain a detection set;
and acquiring a first locked execution block, performing similar matching with the detection set according to the block attribute, and acquiring a detection mode with highest similarity as a matched safety detection mode to perform safety detection on the current application software.
7. The application software-based security detection method according to claim 1, wherein when the security detection result relates to random failure of the component, screening the first matching relationship from all the first dangerous constraint relationships to construct a first protection mechanism for performing first protection on the current application software, comprising:
Acquiring component attributes of a random failure component, and locking a failure sub-architecture;
screening and obtaining a first matching relation consistent with a failure sub-architecture and a current dangerous relation of the failure sub-architecture from all first dangerous constraint relations;
retrieving first security measures consistent with each first matching relationship and the current dangerous relationship of each failure sub-architecture from a relationship-security database;
and constructing a first protection mechanism based on the first security measure, and performing first protection on the current application software.
8. The application software-based security detection method according to claim 1, wherein when the security detection result is independent of random failure of the component, screening second matching relationships from all second dangerous constraint relationships to construct a second protection mechanism, so as to perform second protection on the current application software, comprising:
determining a dangerous application environment of the current application software according to a safety detection result;
screening and obtaining a second matching relation consistent with the dangerous application environment from all second dangerous constraint relations, and determining a current dangerous relation of the dangerous application environment;
retrieving second security measures consistent with each second matching relationship and the current dangerous relationship of the dangerous application environment from the relationship-security database;
And constructing a second protection mechanism based on all the second security measures, and performing second protection on the current application software.
9. A security detection system based on application software, comprising:
the first relation establishing module is used for determining the functional risk and the application risk of the corresponding sub-architecture according to the normal behavior and the possible abnormal behavior of each sub-architecture in the software architecture of the current application software, and establishing a first risk constraint relation of the corresponding sub-architecture;
the second relation establishing module is used for determining a security failing result of the current application software under different application environments according to the application environment of the current application software and a security detection mechanism of each application environment, and establishing a second dangerous constraint relation of the corresponding application environment;
the first protection module is used for matching a corresponding safety detection mode to carry out safety detection according to the software execution logic of the current application software, and when a safety detection result is related to random failure of a component, a first matching relation is screened from all first dangerous constraint relations to construct a first protection mechanism so as to carry out first protection on the current application software;
And the second protection module is used for screening second matching relations from all second dangerous constraint relations to construct a second protection mechanism to carry out second protection on the current application software when the safety detection result is irrelevant to the random failure of the component.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310362356.9A CN116107912B (en) | 2023-04-07 | 2023-04-07 | Security detection method and system based on application software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310362356.9A CN116107912B (en) | 2023-04-07 | 2023-04-07 | Security detection method and system based on application software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116107912A true CN116107912A (en) | 2023-05-12 |
| CN116107912B CN116107912B (en) | 2023-07-04 |
Family
ID=86265808
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310362356.9A Active CN116107912B (en) | 2023-04-07 | 2023-04-07 | Security detection method and system based on application software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116107912B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105787366A (en) * | 2016-02-16 | 2016-07-20 | 上海交通大学 | Android software visualization safety analysis method based on module relations |
| CN109167754A (en) * | 2018-07-26 | 2019-01-08 | 北京计算机技术及应用研究所 | A kind of network application layer security protection system |
| CN110502875A (en) * | 2019-07-25 | 2019-11-26 | 安徽易百互联科技有限公司 | A kind of security of computer software guard system |
| CN110990903A (en) * | 2019-11-29 | 2020-04-10 | 腾讯科技（深圳）有限公司 | Cloud system and cloud system protection method |
| CN112487434A (en) * | 2020-11-05 | 2021-03-12 | 杭州孝道科技有限公司 | Application software self-adaptive safety protection method |
| CN112685737A (en) * | 2020-12-24 | 2021-04-20 | 恒安嘉新（北京）科技股份公司 | APP detection method, device, equipment and storage medium |
| CN113051581A (en) * | 2021-04-25 | 2021-06-29 | 中航机载系统共性技术有限公司 | Highly-integrated complex software security analysis method |
| CN113111347A (en) * | 2021-02-26 | 2021-07-13 | 全球能源互联网研究院有限公司 | Threat disposal method and safety monitoring probe for Android application |
| CN114968761A (en) * | 2022-04-11 | 2022-08-30 | 杭州德适生物科技有限公司 | Software operating environment safety supervision system based on internet |
| CN115174192A (en) * | 2022-06-29 | 2022-10-11 | 中国电信股份有限公司 | Application security protection method and device, electronic equipment and storage medium |
| CN115774872A (en) * | 2021-09-08 | 2023-03-10 | 中国电力科学研究院有限公司 | Platform region fusion type terminal software safety detection method based on sandbox |
-
2023
- 2023-04-07 CN CN202310362356.9A patent/CN116107912B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105787366A (en) * | 2016-02-16 | 2016-07-20 | 上海交通大学 | Android software visualization safety analysis method based on module relations |
| CN109167754A (en) * | 2018-07-26 | 2019-01-08 | 北京计算机技术及应用研究所 | A kind of network application layer security protection system |
| CN110502875A (en) * | 2019-07-25 | 2019-11-26 | 安徽易百互联科技有限公司 | A kind of security of computer software guard system |
| CN110990903A (en) * | 2019-11-29 | 2020-04-10 | 腾讯科技（深圳）有限公司 | Cloud system and cloud system protection method |
| CN112487434A (en) * | 2020-11-05 | 2021-03-12 | 杭州孝道科技有限公司 | Application software self-adaptive safety protection method |
| CN112685737A (en) * | 2020-12-24 | 2021-04-20 | 恒安嘉新（北京）科技股份公司 | APP detection method, device, equipment and storage medium |
| CN113111347A (en) * | 2021-02-26 | 2021-07-13 | 全球能源互联网研究院有限公司 | Threat disposal method and safety monitoring probe for Android application |
| CN113051581A (en) * | 2021-04-25 | 2021-06-29 | 中航机载系统共性技术有限公司 | Highly-integrated complex software security analysis method |
| CN115774872A (en) * | 2021-09-08 | 2023-03-10 | 中国电力科学研究院有限公司 | Platform region fusion type terminal software safety detection method based on sandbox |
| CN114968761A (en) * | 2022-04-11 | 2022-08-30 | 杭州德适生物科技有限公司 | Software operating environment safety supervision system based on internet |
| CN115174192A (en) * | 2022-06-29 | 2022-10-11 | 中国电信股份有限公司 | Application security protection method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 孙鸿青: "《Android应用安全检测分析技术研究》", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 3 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116107912B (en) | 2023-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106991324B (en) | Malicious code tracking and identifying method based on memory protection type monitoring | |
| RU2487405C1 (en) | System and method for correcting antivirus records | |
| CN100527147C (en) | Web page safety information detecting system and method | |
| US10162966B1 (en) | Anti-malware system with evasion code detection and rectification | |
| US20120317645A1 (en) | Threat level assessment of applications | |
| CN100492300C (en) | System and method for executing a process on a microprocessor-enabled device | |
| KR100951144B1 (en) | System and Method for Vulnerability Assessment of Network based on Business Model | |
| CN108183897B (en) | Safety risk assessment method for information physical fusion system | |
| CN101599113A (en) | Driven malware defence method and device | |
| CN102156834A (en) | Method for realizing program killing prevention | |
| CN116107912B (en) | Security detection method and system based on application software | |
| Laranjeiro et al. | A learning-based approach to secure web services from SQL/XPath Injection attacks | |
| CN116319421A (en) | Fault detection method and device based on cloud platform, fault detection system and medium | |
| CN116010963A (en) | Kernel vulnerability detection method, device, equipment and readable storage medium | |
| CN117093999A (en) | Remote code execution vulnerability detection method, device, equipment, medium and product | |
| CN112491813B (en) | Instruction transmission control method and device and computer readable storage medium | |
| CN105631317B (en) | A kind of system call method and device | |
| CN113779589A (en) | Android smart phone application misconfiguration detection method | |
| WO2023029835A1 (en) | Method for protecting kernel thread, and terminal and computer readable storage medium | |
| WO2007092524A2 (en) | Systems, methods, and media for repairing the state of constrained data items in an application | |
| CN114880668A (en) | Database security protection method and device, electronic equipment and storage medium | |
| CN112231710B (en) | QNX BSP starting verification method and starting verification module | |
| CN110378116B (en) | Method and device for preventing operating system from being attacked based on native code | |
| Khalili et al. | Software engineering issues regarding securing ICS: an industrial case study | |
| CN111523115B (en) | Information determining method, function calling method and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |