Application system security auditing method and system
By judging the connection information and usage information of the API interface, temporarily closed the interface that has not been used for a long time, and grading the business data according to the user level and classification standard library, combined with mirror traffic analysis, it solves the problem that traditional API security tools cannot identify hackers at low frequency The problem of multi-source API access requests has achieved refined security protection and normal transmission of business data.
Patent Information
- Application Number
- CN202411111405.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2024-11-29
AI Technical Summary
Traditional API security tools cannot recognize low-frequency multi-source API access requests made by hackers through legal identity login, resulting in easy intrusion during business data monitoring, affecting normal business processes, and being unable to effectively defend against API attacks.
By obtaining the connection information and usage information of the API interface, setting a judgment threshold to temporarily close the long-term unused API interface, and classifying and grading the business data according to the user level classification and classification standard library, and using the bypass deployment method to capture mirror traffic Perform analysis, identify risk data and close the abnormal API interface.
It realizes blockade of long-term API interfaces, only allows access by the highest authorized user. Through data classification and grading and mirror traffic analysis, it realizes automated business data content identification and refined security protection, ensuring the normal transmission and security of business data. sex.
Smart Images

Figure CN119046834A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of system security auditing, and in particular to an application system security auditing method and system. Background Art
[0002] With the development of Internet technology, various organizations and enterprises have inevitably introduced various office systems and data systems at many business levels to help improve operational efficiency. The use of API is particularly important. API serves as a bridge to connect systems and systems, and systems and application data transmission. It carries the heavy responsibility of connecting services and data transmission, involving a large amount of user sensitive information and business data, and is widely used in finance, technology, Internet medical care, government affairs and other fields. With the increase in API interface calls, risk exposure has opened up, and API has quickly become a new target of attack. API attacks have become the number one risk of data leakage, and information security construction is becoming increasingly important. However, judging from the current information construction environment, the situation of API security governance is severe and faces tremendous pressure.
[0003] The terminal security audit method and system with patent publication number CN101833621A can configure each security audit item and its audit standard according to the terminal security requirements, conduct a comprehensive audit of the terminal's hardware, system and software security according to the audit standard, determine the overall risk level of the terminal, and control the terminal's operation according to the determined risk level, which can effectively ensure the terminal's operational security. In addition, the embodiment uses an information digest algorithm to process the terminal's hardware information and software information, avoiding the plain text storage of private data in the terminal's memory, and also avoiding the plain text transmission of private data in the bus, so that private data is not easily intercepted or modified by software, thereby improving the terminal's information security. The embodiment can be applied to ATM terminals to avoid ATM terminals being attacked by software or hardware and facing security issues such as data leakage, system crash, and hardware loss of control, thereby effectively ensuring the operational security of ATM terminals.
[0004] During the use of the above and similar technical solutions, since traditional API security tools are more focused on identity authentication, permission control, request content verification and filtering, and API traffic speed limit protection, traditional API gateways ensure that identity authentication is legal, but it does not mean that the access behavior is legal. Especially in ToC business, facing hackers logging in with legitimate identities, simulating normal operations, and multi-source low-frequency API access requests, traditional API gateways cannot identify such seemingly "safe" user behaviors. When monitoring business data, it is easy to cause business intrusion, affect the normal business process, and cause failures in the transmission of business data. Summary of the invention
[0005] The purpose of the present invention is to provide an application system security audit method and system to solve the problems raised in the above background technology.
[0006] To achieve the above object, the present invention provides the following technical solution: an application system security audit method and system, comprising:
[0007] Interface information determination: obtain the connection information and usage information of the API interface, set the judgment threshold, set the API interface below the judgment threshold as a temporarily closed interface, obtain a temporarily closed interface set, the temporarily closed interface set includes at least one temporarily closed interface, and set the enabling conditions;
[0008] Interface restart: Set the enabling conditions. Based on the temporarily closed interface set, when the temporarily closed interface meets the enabling conditions, the temporarily closed interface will be re-enabled.
[0009] Data classification and grading: users are classified into different levels based on the classification method, and a classification standard library is created. Business data stored in the cloud is classified into multiple different levels of classification standards. The user level classification corresponds to the classification standard library.
[0010] Data detection: Deploy the analysis module based on the deployment mode and analyze and detect the business data, and complete the detection of business data without affecting the normal transmission of business data;
[0011] The deployment methods include:
[0012] Step 1: Determine the deployment location, take the location of the analysis module as the first feature point, obtain the transmission direction and feedback direction of the business data, and take the data switch and the classification standard library as the second feature point and the third feature point respectively, determine the location of the first feature point between the second feature point and the third feature point, and establish the analysis module;
[0013] Step 2: Mirror traffic acquisition, based on the capture device, the service data transmitted between the second characteristic point and the third characteristic point is acquired to obtain a mirror traffic set;
[0014] Step 3: Mirror traffic analysis, obtaining feedback information of the service data in the second feature point, judging whether the user level in the feedback information matches the level of the service data, and judging that the service data is normal when the user level is higher than or equal to the level of the service data, and judging that the service data is abnormal when the user level is lower than the level of the service data, and obtaining an abnormal data feedback signal;
[0015] Step 4: Business data truncation: based on the abnormal data feedback signal, the API interface corresponding to the feedback information of the business data in the second feature point is closed.
[0016] Furthermore, the division method includes:
[0017] S1: User level division, dividing the user level into at least two levels, each level corresponds to different access rights, and obtaining user level items;
[0018] S2: Business data monitoring: Based on the user level item, the number of business data used by users at different levels is monitored to obtain a business data usage set;
[0019] S3: Creating a classification standard library: Creating a classification standard library based on the target method, and creating classification standards of different levels in the classification standard library. The classification standard levels correspond to the user level items.
[0020] S4: Business data division: based on the business data usage set, a usage threshold is set, and the business data that reaches the usage threshold in the business data usage set corresponding to the user level item is divided into corresponding classification standards.
[0021] Furthermore, the division method also includes:
[0022] S5: Assigning classification definitions, assigning different classification definitions to different levels of classification standards in the classification standard library;
[0023] S6: Business data division: divide the business data based on the classification definition corresponding to each level.
[0024] Furthermore, the evaluation threshold includes:
[0025] M1: Setting the first time threshold, setting the first time threshold, determining the API interfaces that have not been connected and used within the first time threshold as pre-selected interfaces, and obtaining the pre-selected interface set;
[0026] M2: Setting the second time threshold. Set the second time threshold, and concentrate the pre-selected interfaces. The API interfaces that have not been connected and used within the second time threshold are determined as the screened interfaces, and the remaining API interfaces are determined as the interfaces to be selected, and the interface set to be selected is obtained. Repeat the steps of M1-M2 to screen out all the screened interfaces and obtain the temporarily closed interface set.
[0027] Furthermore, the evaluation threshold also includes: using a threshold setting, setting a usage threshold, and in the processes of M1 and M2, determining the API interface that does not reach the usage threshold as a substandard interface, and filtering out the interface and combining the substandard interface to obtain a temporarily closed interface set.
[0028] Furthermore, the enabling conditions include:
[0029] X1: Enable item setting, set the first startup item in advance, the first startup item includes setting the highest and only authorized user, and obtaining the highest user item;
[0030] X2: The first enabled item detection obtains the IP address of the highest user item and obtains the secure IP item. When the highest user item uses the temporarily closed interface, the IP address is detected. When the IP address matches the secure IP item, the target temporarily closed interface is set as the re-enabled interface.
[0031] Furthermore, the enabling conditions also include:
[0032] X3: Enable location setting, set the second startup item in advance, the second startup item includes setting at least two visiting users, obtaining a visiting user set, and assigning fixed coordinate location items to the visiting users based on the visiting user set;
[0033] X4: The second startup item detection obtains the coordinate position item of the access user set. When the target coordinate position item matches the fixed coordinate position item, the target temporarily closed interface is set to a re-enabled interface.
[0034] Furthermore, an application system security audit system uses an application system security audit method described in any one of the above.
[0035] Compared with the prior art, the present invention has the following beneficial effects:
[0036] This application system security audit method and system blocks some API interfaces that have not been used for a long time based on the connection information and usage information of the API interfaces, allowing only the highest authorized user to access them, and classifies and grades the data. By creating multiple levels of classification standards, business data is acquired and divided into different classification standards according to the access information of the business data, thereby realizing automatic business data content recognition, focusing on promoting data asset sorting and data classification and grading, and thus realizing refined security protection.
[0037] At the same time, through the bypass deployment method, the mirror traffic is captured to analyze the http protocol and the transmitted business data, and then the risk data is identified. By capturing and detecting the mirror traffic, it will not interfere with the normal flow of business data, thereby ensuring the normal transmission of business data. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 A schematic diagram of the relationship between interface information determination, interface restart, data classification and grading, and detection according to the present invention;
[0039] Figure 2 It is a schematic diagram of the deployment method flow of the present invention;
[0040] Figure 3 This is a schematic diagram of the installation position of the analysis module of the present invention;
[0041] Figure 4 It is a schematic diagram of the relationship between user levels and classification standard libraries of the present invention. DETAILED DESCRIPTION
[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0043] With the development of cloud computing technology, more and more SaaS is being migrated to the cloud, and APIs are also exposed to the cloud. Compared with the single-point call of traditional data centers, both east-west and north-south directions may become attack surfaces of APIs. In addition, R&D personnel often open APIs to the outside world for inadvertent reasons such as testing convenience, enabling third-party developers to access, and demonstrating to partners. Insecure APIs will continue to expand the attack surface of applications, making it easier for hackers to conduct reconnaissance, collect configuration information, and plan network attacks. APIs are an important way to obtain various high-value services and sensitive data. Although the traffic of some APIs is very low, they are the core part of the business, and these types of APIs are likely to carry sensitive data. This requires security personnel to clearly understand whether the API should carry these sensitive data, whether its data processing method is legal, and whether the sensitive data is used maliciously. There are many kinds of API vulnerabilities. Traditional security tools, such as API gateways and Web Application Firewalls (WAFs) and traditional API security governance methods, are currently unable to accurately perceive and defend against API risks, and in the process of analyzing and detecting business data, they are likely to interfere with the normal transmission of business data. The technical solution provided by this application is used according to the API. The connection information and usage information of the I interface are collected, and some API interfaces that have not been used for a long time are blocked, allowing only the highest authorized user to access them. The data is classified and graded, and business data is acquired by creating multiple levels of classification standards. Business data is divided into different classification standards according to the access information of business data, and automatic business data content recognition is realized. The focus is on promoting data asset sorting and data classification and grading, so as to achieve refined security protection. In the bypass deployment mode, the mirror traffic is captured to analyze the http protocol and the transmitted business data, and then the risk data is identified. By capturing and detecting the mirror traffic, the normal flow of business data will not be interfered with, thereby ensuring the normal transmission of business data.
[0044] like Figure 1-Figure 4As shown, the present invention provides a technical solution: a method for security auditing of an application system, comprising: interface information determination: obtaining connection information and usage information of an API interface, setting a judgment threshold, setting an API interface below the judgment threshold as a temporarily closed interface, obtaining a temporarily closed interface set, the temporarily closed interface set including at least one temporarily closed interface, and setting an enabling condition; interface restart: setting an enabling condition, based on the temporarily closed interface set, when the temporarily closed interface meets the enabling condition, the temporarily closed interface is re-enabled; data classification and grading: dividing users into levels based on the division method, creating a classification standard library at the same time, and dividing the business data stored in the cloud into a plurality of different levels of classification standards, the division of user levels corresponds to the classification standard library; data detection: deploying an analysis module based on the deployment method and analyzing and detecting business data, and completing the detection of business data without affecting the normal transmission of business data; the deployment method comprises: step one: determining the deployment position, taking the position of the analysis module as the first feature point, obtain the transmission direction and feedback direction of the business data, and use the data switch and the classification standard library as the second feature point and the third feature point respectively, determine the position of the first feature point between the second feature point and the third feature point, and establish an analysis module; Step 2: Mirror traffic acquisition, based on the capture device, obtain the business data transmitted between the second feature point and the third feature point, and obtain the mirror traffic set; Step 3: Mirror traffic analysis, obtain the feedback information of the business data in the second feature point, determine whether the user level in the feedback information matches the level of the business data, when the user level is higher than or equal to the level of the business data, determine that the business data is normal, when the user level is lower than the level of the business data, determine that the business data is abnormal, and obtain an abnormal data feedback signal; Step 4: Business data truncation, based on the abnormal data feedback signal, close the API interface corresponding to the feedback information of the business data in the second feature point.
[0045] It should be noted that due to the large number and rapid growth of API assets, many companies are not clear about how many APIs they have and the status of the APIs. In the case of a large number of API interfaces not being sorted out, API assets are not clear, security responsibilities cannot be divided and implemented, and the life safety cycle of API assets cannot be effectively managed.
[0046] It should be noted that by obtaining the connection information and usage information of the API interface, the API interface below the judgment threshold is set as a temporarily closed interface by setting the judgment threshold. When the API interface has not been used for a long time, it may be in a forgotten or abandoned state. At this time, the API interface in this state is temporarily closed, and a restart condition is set. When the restart condition is met, the temporarily closed interface is reused. This method can effectively protect business data and prevent malicious programs or personnel from stealing business data through forgotten API interfaces. By setting the enabling conditions, when the closed API interface needs to be reused, the API interface can be re-enabled by relying on the set enabling conditions, which makes it more convenient to enable. By dividing the user level and the business data level, the stored business data is classified and stored. Users of different levels correspond to business data of different levels. When business data needs to be obtained, the business data is obtained from the classification standards of the corresponding level. While the security is higher, the business data can be obtained faster.
[0047] It should be noted that the analysis module is deployed through a special deployment method, and an analysis module is established between the data switch and the classification standard library. When the data switch generates a demand and the classification standard library provides business data, the mirror traffic of the transmitted business data is obtained, and the mirror traffic is analyzed without affecting the transmission of business data, thereby realizing the demand analysis of the transmitted business data and the data switch.
[0048] like Figure 4 As shown, the division methods include: S1: user level division, dividing the user level into at least two levels, each level corresponds to different access rights, and obtaining user level items; S2: business data monitoring, based on the user level items, monitoring the number of business data connected and used by users at different levels, and obtaining a business data usage set; S3: classification standard library creation, creating a classification standard library based on the target method, and creating classification standards of different levels in the classification standard library, and the classification standard levels correspond to the user level items; S4: business data division, based on the business data usage set, setting a usage threshold, and dividing the business data that reaches the usage threshold in the business data usage set corresponding to the user level item into the corresponding classification standard.
[0049] It should be noted that users are divided into three levels, namely advanced users, intermediate users and regular users. Each user has different access rights, and users of each level have access to different business data. The number of times business data is connected and used by users at different levels is monitored, and classification standards corresponding to user levels are set, namely important data, secondary data and regular data. By setting usage thresholds, business data corresponding to user level items and whose usage concentration reaches the usage threshold are classified into corresponding classification standards.
[0050] In the specific implementation process, the usage threshold is set at 10 times. When advanced users, intermediate users and regular users connect and use business data, there are usage times, and the usage times are monitored. When the business data connected and used by advanced users reaches the usage threshold, the target business data is determined to be important data. Similarly, the business data is divided into important data, secondary data and regular data respectively.
[0051] The division method also includes: S5: assigning classification definitions, assigning different classification definitions to classification standards of different levels in the classification standard library; S6: business data division, dividing the business data based on the classification definition corresponding to each level.
[0052] In the specific implementation process, different classification definitions are assigned to different levels of classification standards. The classification definition of important data is data that is critical to business operations, and the leakage or loss of which will result in significant losses, legal liabilities or damage to customer trust, including customer personal information, financial records, trade secrets and proprietary technologies, contracts and legal documents; secondary data is data that has a certain impact on business operations but will not cause significant losses, such as internal investigations and reports, general business communications, marketing information and data; routine data is data that has little impact on company operations, and the leakage or loss will not cause significant consequences, including public resources and information, general market analysis, and low-sensitivity statistical data. Business data is divided by assigning different classification definitions.
[0053] The evaluation thresholds include: M1: setting the first time threshold, setting the first time threshold, determining the API interfaces that have not been connected and used within the first time threshold as pre-selected interfaces, and obtaining a pre-selected interface set; M2: setting the second time threshold, setting the second time threshold, determining the pre-selected interfaces that have not been connected and used within the second time threshold as filtered interfaces, and determining the remaining API interfaces as candidate interfaces, and obtaining a candidate interface set, repeating steps M1-M2, filtering out all filtered interfaces, and obtaining a temporarily closed interface set.
[0054] In the specific implementation process, the first time threshold is set as one month, and the API interfaces that have not been connected and used within one month are determined as pre-selected interfaces, and the second time threshold is also set as one month. The API interfaces among the pre-selected interfaces that have not been connected and used within the second time threshold are determined as screened interfaces, and the remaining API interfaces are determined as interfaces to be selected. This step is repeated to screen out all the screened interfaces, and the screened interfaces are closed to obtain a temporarily closed interface set.
[0055] The evaluation threshold also includes: setting the usage threshold. In setting the usage threshold, during the M1 and M2 processes, the API interfaces that do not reach the usage threshold are judged as substandard interfaces, and the interfaces are screened out and combined with the substandard interfaces to obtain a temporarily closed interface set.
[0056] In the specific implementation process, the usage threshold is the number of uses, which is 10 times. In the processes of M1 and M2, when an API interface is determined to have been used 10 times, this type of API interface is also determined as a substandard interface. Both the screened interfaces and the substandard interfaces are closed to obtain a temporarily closed interface set.
[0057] The enabling conditions include: X1: enabling item setting, setting the first enabling item in advance, the first enabling item includes setting the highest and only authorized user to obtain the highest user item; X2: first enabling item detection, obtaining the IP address of the highest user item, obtaining the secure IP item, and when the highest user item uses a temporarily closed interface, detecting the IP address, and when the IP address matches the secure IP item, setting the target temporarily closed interface to the re-enabled interface.
[0058] The enabling conditions also include: X3: enabling location setting, setting the second startup item in advance, the second startup item includes setting at least two access users, obtaining an access user set, and assigning fixed coordinate location items to the access users based on the access user set; X4: second startup item detection, obtaining the coordinate location item of the access user set, when the target coordinate location item matches the fixed coordinate location item, setting the target temporarily closed interface to a re-enabled interface.
[0059] In the specific implementation process, the second startup item includes three access users, and the fixed coordinate positions of the three access users are obtained respectively. When the API interface needs to be restarted, the target coordinate position is obtained to determine whether the target coordinate position is consistent with the fixed coordinate position.
[0060] An application system security audit system uses any one of the above application system security audit methods.
[0061] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is limited by the attached embodiments and their equivalents.
Claims
1. A method for security auditing of an application system, characterized in that: include: Interface information determination: obtain the connection information and usage information of the API interface, set the judgment threshold, set the API interface below the judgment threshold as a temporarily closed interface, obtain a temporarily closed interface set, the temporarily closed interface set includes at least one temporarily closed interface, and set the enabling conditions; Interface restart: Set the enabling conditions. Based on the temporarily closed interface set, when the temporarily closed interface meets the enabling conditions, the temporarily closed interface will be re-enabled. Data classification and grading: users are classified into different levels based on the classification method, and a classification standard library is created. Business data stored in the cloud is classified into multiple different levels of classification standards. The user level classification corresponds to the classification standard library. Data detection: Deploy the analysis module based on the deployment mode and analyze and detect the business data, and complete the detection of business data without affecting the normal transmission of business data; The deployment methods include: Step 1: Determine the deployment location, take the location of the analysis module as the first feature point, obtain the transmission direction and feedback direction of the business data, and take the data switch and the classification standard library as the second feature point and the third feature point respectively, determine the location of the first feature point between the second feature point and the third feature point, and establish the analysis module; Step 2: Mirror traffic acquisition, based on the capture device, the service data transmitted between the second characteristic point and the third characteristic point is acquired to obtain a mirror traffic set; Step 3: Mirror traffic analysis, obtaining feedback information of the service data in the second feature point, judging whether the user level in the feedback information matches the level of the service data, and judging that the service data is normal when the user level is higher than or equal to the level of the service data, and judging that the service data is abnormal when the user level is lower than the level of the service data, and obtaining an abnormal data feedback signal; Step 4: Business data truncation: based on the abnormal data feedback signal, the API interface corresponding to the feedback information of the business data in the second feature point is closed.
2. The method for security auditing of an application system according to claim 1, characterized in that: The division methods include: S1: User level division, dividing the user level into at least two levels, each level corresponds to different access rights, and obtaining user level items; S2: Business data monitoring: Based on the user level item, the number of business data used by users at different levels is monitored to obtain a business data usage set; S3: Creating a classification standard library: Creating a classification standard library based on the target method, and creating classification standards of different levels in the classification standard library. The classification standard levels correspond to the user level items. S4: Business data division: based on the business data usage set, a usage threshold is set, and the business data that reaches the usage threshold in the business data usage set corresponding to the user level item is divided into corresponding classification standards.
3. The method for security auditing of an application system according to claim 2, characterized in that: The division method also includes: S5: Assigning classification definitions, assigning different classification definitions to different levels of classification standards in the classification standard library; S6: Business data division: divide the business data based on the classification definition corresponding to each level.
4. The method for security auditing of an application system according to claim 1, characterized in that: The evaluation thresholds include: M1: setting the first time threshold, setting the first time threshold, determining the API interface that has not been connected and used within the first time threshold as the pre-selected interface, and obtaining the pre-selected interface set; M2: Setting the second time threshold. Set the second time threshold, and concentrate the pre-selected interfaces. The API interfaces that have not been connected and used within the second time threshold are determined as the screened interfaces, and the remaining API interfaces are determined as the interfaces to be selected, and the interface set to be selected is obtained. Repeat the steps of M1-M2 to screen out all the screened interfaces and obtain the temporarily closed interface set.
5. The method for security auditing of an application system according to claim 4, characterized in that: The evaluation threshold also includes: using a threshold setting, setting a usage threshold, and in the process of M1 and M2, determining the API interface that does not reach the usage threshold as a substandard interface, and filtering out the interface and combining the substandard interface to obtain a temporarily closed interface set.
6. The method for security auditing of an application system according to claim 1, characterized in that: The enabling conditions include: X1: Enable item setting, set the first startup item in advance, the first startup item includes setting the highest and only authorized user, and obtaining the highest user item; X2: The first enabled item detection obtains the IP address of the highest user item and obtains the secure IP item. When the highest user item uses the temporarily closed interface, the IP address is detected. When the IP address matches the secure IP item, the target temporarily closed interface is set as the re-enabled interface.
7. The method for security auditing of an application system according to claim 6, characterized in that: The enabling conditions also include: X3: Enable location setting, set the second startup item in advance, the second startup item includes setting at least two visiting users, obtaining a visiting user set, and assigning fixed coordinate location items to the visiting users based on the visiting user set; X4: The second startup item detection obtains the coordinate position item of the access user set. When the target coordinate position item matches the fixed coordinate position item, the target temporarily closed interface is set to a re-enabled interface.
8. An application system security audit system, characterized by: An application system security audit method as described in any one of claims 1-7 is used.
