Asset management method based on SOAR automated orchestration and response
Through SOAR automated orchestration and response methods, users can orchestrate and manage asset management processes, solving the problem that existing asset security management platforms cannot be customized, and achieving flexible and automated asset management.
Patent Information
- Application Number
- CN202111244407.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-25
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-10-25
AI Technical Summary
The existing asset security management platform is difficult to develop customized processes according to the specific needs of users, and cannot meet the dynamic adjustment of enterprise business processes and the flexibility of asset management rules.
Using SOAR-based automated orchestration and response methods, including security capability module, orchestration engine module and application layer module, through scripted API interface calls and graphical interfaces, users can orchestrate and manage asset management processes to achieve customization and flexibility.
It realizes customized asset management process development and rule arrangement according to user needs, and provides more automated and flexible asset management solutions to meet the dynamic management needs of enterprises.
Smart Images

Figure CN113946833B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of asset management technology, and in particular to an asset management method based on SOAR automated orchestration and response. Background Art
[0002] As enterprises continue to develop, their asset types are becoming more and more diversified, and their quantity is growing. Asset information management and security issues are also constantly emerging, making asset management more and more challenging. Existing asset management methods are relatively traditional and fixed. Many new types of assets need to be managed through manual sorting, which is time-consuming and labor-intensive. The asset security management platform has become a powerful tool for major companies to manage their assets.
[0003] Since each enterprise has different needs for asset security management, the actual business process is not static. The asset security management platforms currently developed by manufacturers on the market are all finished products. It is difficult to develop customized processes based on the actual needs of users. They can only be executed according to the business processes and security management processes designed by the manufacturers themselves. However, client companies will make adjustments over time and as the company develops, the asset management platform needs to meet basic management requirements and be able to arrange different and adjustable asset management rules and methods according to customer requirements in a relatively automated manner. This urgently requires a management platform that can meet customer customization needs so that customers can manage according to their actual business processes. Summary of the invention
[0004] In view of the deficiencies in the prior art, the purpose of the present invention is to provide an asset management method based on SOAR automated orchestration and response, which introduces SOAR to standardize various asset management needs and means in the three core stages of trigger conditions, analysis and judgment, and response and disposal. It can develop customized processes according to the actual needs of users, and arrange different asset management rules that can be adjusted at any time, which is easy to promote and use.
[0005] In order to achieve the above-mentioned purpose, the present invention is implemented through the following technical solution: an asset management method based on SOAR automated orchestration and response, including a security capability module, an orchestration engine module and an application layer module.
[0006] The security capability module is a functional module that provides security services to assets, including but not limited to IP detection, port discovery, host vulnerability scanning, website vulnerability scanning, baseline compliance check, and website content monitoring. Each of the above security technology functional modules will generate corresponding data. IP detection discovers surviving IP addresses; port discovery discovers open ports and fingerprint information of surviving IPs; host vulnerability scanning discovers vulnerability information of host IPs; website vulnerability scanning discovers vulnerability information of website IPs; baseline compliance checks are used to discover non-compliant configurations; and website content monitoring is used to monitor and discover sensitive information.
[0007] The orchestration engine module calls each API interface application through scripts. The orchestration engine module consists of data source capture, script parser and controller. The script parser parses a series of asset security management scripts formulated by users according to needs into recognizable codes and passes them into the controller for execution. The controller then makes decisions and takes corresponding actions based on the result data after the data capture module runs each security engine in the security capability.
[0008] The script is a user's arrangement of various API applications according to his own thinking logic, and finally generates a set of business processes that can be automatically executed. The rules of the script are: start action → IP detection → port discovery → host vulnerability scan → DingTalk push → end action; the specific execution idea of the script is: if a surviving IP host is found, the port discovery step will be executed next. If a surviving port is found, the host vulnerability scan step will be performed. When relevant vulnerability information is found, relevant alarm information will be pushed by DingTalk.
[0009] The application layer module displays a graphical interface to the user, and the application layer module includes a message module and a business operation module; the message module refers to the DingTalk push user feedback function; the business operation module includes a script management module and an asset management module. Users can use the script management module to write and manage scripts that meet their needs, that is, set the asset management script rule content and logical flow that the user wants to achieve the purpose of automated orchestration management and response.
[0010] Preferably, the actions of the script are divided into restrictive actions and non-restrictive actions, the restrictive actions are API interfaces that can produce response data, and the restrictive actions include but are not limited to IP detection, vulnerability scanning, and content monitoring; the non-restrictive actions are API interfaces that cannot produce response data, and the non-restrictive actions include but are not limited to DingTalk message push, platform alarms, SMS notifications, and WeChat public account push; the selection of the next restrictive action type is limited by the data type of the previous restrictive action, and the next non-restrictive action is not limited to the previous restrictive action, but after the non-restrictive action, restrictive actions and non-restrictive actions cannot be added, and the first action cannot add non-restrictive actions.
[0011] Preferably, the restrictive action has one or more restrictive conditions, each restrictive condition is a new branch, and when the first restrictive condition is met, it will no longer be determined whether the second and other restrictive conditions are met; the non-restrictive action has no restrictive conditions; only when the previous restrictive action meets the restrictive conditions, the next restrictive action or non-restrictive action will continue to execute, otherwise the currently triggered script task will be terminated.
[0012] Preferably, the script task is the first restrictive action of the script manually triggered by the user. In this case, all scripts that meet the first action will be regarded as script tasks and passed into the task queue in the controller to wait for execution. Among them, restrictive actions that are not automatically triggered by the user will not trigger scripts that meet the first action, that is, they will not be placed in the task queue of the controller.
[0013] Preferably, the same restrictive action will only be executed once, and the data output after the restrictive action is completed can be used to judge the same or different restrictive conditions of the same restrictive action in multiple scripts; the same non-restrictive action can be executed multiple times.
[0014] Beneficial effects of the present invention: This method introduces security orchestration automation and response SOAR to standardize various asset management needs and means with three core stages: trigger conditions, analysis and judgment, and response and disposal. It can develop customized processes according to the actual needs of users, orchestrate different asset management rules that can be adjusted at any time, and provide users with more liberal choices at the trigger conditions. It has broad application prospects. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments;
[0016] Figure 1 It is a structural schematic diagram of the present invention;
[0017] Figure 2 This is a flow chart of Embodiment 1 of the present invention;
[0018] Figure 3 This is a flow chart of Embodiment 2 of the present invention;
[0019] Figure 4 This is a flow chart of Example 3 of the present invention. DETAILED DESCRIPTION
[0020] In order to make the technical means, creative features, objectives and effects achieved by the present invention easy to understand, the present invention is further explained below in conjunction with specific implementation methods.
[0021] Reference Figure 1-4 This specific implementation adopts the following technical solution: an asset management method based on SOAR automated orchestration and response, including a security capability module, an orchestration engine module and an application layer module.
[0022] The security capability module is a functional module that provides security services to assets, including but not limited to IP detection, port discovery, host vulnerability scanning, website vulnerability scanning, baseline compliance checking, website content monitoring, etc. Each of the above security technology functional modules will generate corresponding data. The IP detection discovers the living IP address; the port discovery discovers the open port and fingerprint information of the living IP; the host vulnerability scanning discovers the vulnerability information of the host IP; the website vulnerability scanning discovers the vulnerability information of the website IP; the baseline compliance check is used to discover non-compliant configurations; and the website content monitoring is used to monitor and discover sensitive information.
[0023] The orchestration engine module calls various API interface applications through scripts. The orchestration engine module consists of data source capture, script parser and controller. The script parser parses a series of asset security management scripts formulated by users according to their needs into recognizable codes and passes them into the controller for execution. The controller then makes decisions and takes corresponding actions based on the result data after the data capture module runs various security engines in the security capabilities.
[0024] The application layer module displays a graphical interface to the user, that is, the user platform display and interaction interface; the application layer module includes a message module and a business operation module; the message module refers to user feedback functions such as DingTalk push, and its working logic is to provide feedback to the user in the form of message text on the results provided by the orchestration engine; the business operation module includes a script management module and an asset management module. Users can use the script management module to write and manage scripts that meet their needs, that is, set the asset management script rule content and logical flow that the user wants to achieve the purpose of automated orchestration management and response.
[0025] The script is a user's arrangement of various API applications according to his own thinking logic, and finally generates a set of business processes that can be automatically executed. For example, the rules of the script are: start action → IP detection → port discovery → host vulnerability scan → DingTalk push → end action; the specific execution idea of the script is: if a surviving IP host is found, the port discovery step will be executed next; if a surviving port is found, the host vulnerability scan step will be performed again; when relevant vulnerability information is found, relevant alarm information will be pushed by DingTalk.
[0026] It is worth noting that the script's actions are divided into restrictive actions and non-restrictive actions. The restrictive actions are API interfaces that can produce response data. Restrictive actions include but are not limited to IP detection, vulnerability scanning, and content monitoring. The non-restrictive actions are API interfaces that cannot produce response data. Non-restrictive actions include but are not limited to DingTalk message push, platform alarms, SMS notifications, and WeChat public account push. The selection of the next restrictive action type is limited by the data type of the previous restrictive action. The next non-restrictive action is not limited to the previous restrictive action. However, after the non-restrictive action, restrictive actions and non-restrictive actions cannot be added, and the first action cannot add non-restrictive actions. For example, the data output by the restrictive action IP detection is IP, and the restrictive actions associated with the industrial P are port discovery, baseline compliance check, etc., then the next action can be selected from these two restrictive actions and all non-restrictive actions.
[0027] Each restrictive action has one or more restrictive conditions, and each restrictive condition is a new branch. When the first restrictive condition is met, it will not be judged whether the second and other restrictive conditions are met; the non-restrictive action has no restrictive conditions. For example, the restrictive condition of IP detection is the IP range, the restrictive condition of port discovery is the port range and service type, and the restrictive condition of host vulnerability scanning is the vulnerability type range, etc. Only when the previous restrictive action meets the restrictive condition, the next restrictive action or non-restrictive action will continue to execute, otherwise the currently triggered script task will end. The script task is the first restrictive action of the script manually triggered by the user. All scripts that meet the first action will be regarded as script tasks and will be passed to the task queue in the controller to wait for execution. Among them, restrictive actions that are not automatically triggered by the user will not trigger scripts that meet the first action, that is, they will not be placed in the task queue of the controller.
[0028] It is worth noting that the same restrictive action will only be executed once, and the data output after the completion of the restrictive action can be used to judge the same or different restrictive conditions of the same restrictive action in multiple scripts; the same non-restrictive action can be executed multiple times.
[0029] In addition, scripts are not limited to functional processes, but can also be applied to the script arrangement of business processes. For example, after a host vulnerability scan, a work order is automatically created and sent to the corresponding person in charge, and pushed via DingTalk messages; if a vulnerability is ignored, it is automatically added to the vulnerability whitelist, etc.
[0030] This specific implementation method takes asset security management into consideration, introduces security orchestration automation and SOAR response methods, and standardizes various asset management needs and means in three core stages: trigger conditions, analysis and judgment, and response and disposal, and provides users with more liberal choices at trigger conditions. This solution manages asset security through a combination of fixed restrictive actions and non-restrictive actions. Users can customize asset security management and business processes to write scripts, and then use the orchestration engine to call various API-interfaced applications to implement the script process, thereby solving the problem that the asset security management platform cannot be managed according to the company's internal needs, allowing customers to manage according to their actual business processes and meet customers' customized needs. It has broad market application prospects.
[0031] Example 1: Asset management method based on SOAR automated orchestration and response, such as script 1 ( Figure 2 ), the first restrictive action is IP liveness detection, the restrictive condition of this restrictive action is ip in192.168.1.0 / 24, and the non-restrictive action is DingTalk push.
[0032] When the user triggers the restrictive action IP detection, and the IP address output by the action is 192.168.1.22, which meets the restrictive conditions of the restrictive action, the subsequent non-restrictive action DingTalk push will continue to be executed. The system will automatically push "Found living IP-192.168.1.22-from Script 1" to the previously set DingTalk account through the message module interface.
[0033] Example 2: Asset management method based on SOAR automated orchestration and response, such as Script 2 ( Figure 3 ), the first restrictive action is IP liveness detection, and the restrictive condition is that all surviving IPs must pass. The second restrictive action is port discovery, and this restrictive action has two restrictive conditions, that is, two branches. The first restrictive condition is the existence of ports 80, 443, and 8080, and the second restrictive condition is the existence of ports 22, 23, and 3306. The subsequent actions of the two branches are DingTalk push, which is a non-restrictive action.
[0034] When the user triggers the first restrictive action and meets the current restrictive conditions, the port discovery action will be triggered. When the action is completed, the output port information includes ports 80, 443, 8080, 22, 23, 3306, 8081, and 8082, which meet the restrictive conditions of the first action and the second action. However, since only one path will be taken in the same script, when it is determined that the restrictive conditions of the first action are met, the website vulnerability scanning action will be directly triggered instead of the host vulnerability scanning action. Finally, when a website vulnerability is discovered, the system will automatically push "It is discovered that xx vulnerability risks exist in the surviving IP-192.168.1.22 - from script 2" to the previously set DingTalk account through the message module interface.
[0035] Example 3: Asset management method based on SOAR automated orchestration and response, such as multiple scripts ( Figure 4 ), when script 3 and script 4 exist at the same time, the first restrictive action and restrictive condition of the two scripts are consistent, both of which are IP exploration action and all IPs, that is, when the user operates an IP exploration action and outputs a surviving IP-192.168.1.25 after completing the action, the first restrictive action and restrictive condition of script 3 and script 4 can be satisfied, and both will trigger the next restrictive action-port scanning. Since it is the same IP and the subsequent actions are all port discovery actions, the action will only be executed once, but the final output result of the action will be used by script 3 and script 4 as the judgment of the restrictive condition. When the port scanning action is completed and the list of ports 80, 443, 8080, 22, 23, 3306, 8081, and 8082 is output, the second restrictive condition of the two scripts is satisfied, that is, the restrictive action-website vulnerability scanning of script 3 and the host vulnerability scanning of script 4 will be triggered; when the current two restrictive actions of the two scripts are completed and the restrictive conditions are met, the relevant information will be pushed to the relevant person in charge through DingTalk respectively.
[0036] The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention. It should be understood by those skilled in the art that the present invention is not limited to the above embodiments. The above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention to be protected. The scope of protection of the present invention is defined by the attached claims and their equivalents.
Claims
1. An asset management method based on SOAR automated orchestration and response, characterized in that: It includes security capability module, orchestration engine module and application layer module; The security capability module is a functional module that provides security services to assets, including an IP detection module, a port discovery module, a host vulnerability scanning module, a website vulnerability scanning module, a baseline compliance check module, and a website content monitoring module. Each functional module of the security technology will generate corresponding data. The IP detection module is used to discover live IP addresses; the port discovery module is used to discover open ports and fingerprint information of live IPs; the host vulnerability scanning module is used to discover vulnerability information of host IPs; the website vulnerability scanning module is used to discover vulnerability information of website IPs; the baseline compliance check module is used to discover non-compliant configurations; and the website content monitoring module is used to monitor and discover sensitive information. The orchestration engine module calls each API application through a script. The orchestration engine module consists of a data source capture module, a script parser, and a controller. The script parser parses a series of asset security management scripts formulated by the user according to the needs into recognizable codes and passes them to the controller for execution. The controller then makes decisions and takes corresponding actions based on the result data after the data source capture module runs each security engine in the security capability module. The script is a user's arrangement of various API applications according to their own thinking logic, and finally generates a set of business processes that can be automatically executed. The rules of the script are: start action → IP detection → port discovery → host vulnerability scan → DingTalk push → end action; The application layer module displays a graphical interface to the user, and includes a message module and a business operation module; the message module has the function of pushing user feedback on DingTalk; the business operation module includes a script management module and an asset management module. Users can use the script management module to write and manage scripts that meet their needs, that is, set the asset management script rule content and logical flow that the user wants, so as to achieve the purpose of automated orchestration management and response; The specific execution idea of the script is: if a live IP host is found, the port discovery step will be executed next. If a live port is found, the host vulnerability scanning step will be performed. When relevant vulnerability information is found, relevant alarm information will be pushed to DingTalk. The actions of the script are divided into restrictive actions and non-restrictive actions. The restrictive actions can produce response data, including IP detection, vulnerability scanning, and content monitoring; the non-restrictive actions cannot produce response data, including DingTalk message push, platform alarm, SMS notification, and WeChat public account push; the selection of the next restrictive action type is limited by the data type of the previous restrictive action, and the next non-restrictive action is not limited by the previous restrictive action, but after the non-restrictive action, restrictive actions and non-restrictive actions cannot be added, and the first action cannot add non-restrictive actions; The restrictive action has one or more restrictive conditions, each of which is a new branch. When the first restrictive condition is met, the second and other restrictive conditions will not be judged. The non-restrictive action has no restrictive conditions. Only when the previous restrictive action meets the restrictive conditions, the next restrictive action or non-restrictive action will continue to execute, otherwise the currently triggered script task will end. The script task is the first restrictive action of the script manually triggered by the user. All scripts that meet the first restrictive action will be regarded as script tasks and will be passed to the task queue in the controller to wait for execution. Among them, the restrictive action that is not automatically triggered by the user will not trigger the script that meets the first restrictive action, that is, it will not be put into the task queue of the controller; The same restrictive action will only be executed once, and the data output after the restrictive action is completed can be used to judge the same or different restrictive conditions of the same restrictive action in multiple scripts; the same non-restrictive action can be executed multiple times.
