Cloud server security policy configuration methods, devices, electronic equipment and storage media

By unifying semantic parsing and dynamically adjusting, structured instructions are generated and converted into API call sequences for the target cloud platform. This solves the problems of policy fragmentation and frequent manual intervention in hybrid cloud environments, realizes unified management of security policies and consistent execution across platforms, and improves the integrity and real-time response capability of overall security protection.

CN123074822APending Publication Date: 2026-11-10JINAN INSPUR DATA TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611432255.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-15
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing hybrid cloud security policy management methods suffer from fragmented policies and inconsistent execution due to the use of platform-specific APIs. Frequent manual intervention leads to configuration errors, affecting the integrity of overall security protection and real-time response capabilities.

Method used

Structured security policy instructions are generated through unified semantic parsing, converted into API call sequences for the target cloud platform, and their execution status and historical events are recorded. Global security policy rules are dynamically adjusted to achieve cross-platform adaptation and automated management.

Benefits of technology

It enables unified management and consistent execution of security policies across platforms, reduces manual configuration errors, and improves the overall integrity and real-time response capabilities of security protection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074822A_ABST
    Figure CN123074822A_ABST
Patent Text Reader

Abstract

This application discloses a configuration method, apparatus, electronic device, and storage medium for cloud host security policies, relating to the field of computer technology. Through this application, by uniformly semantically parsing the cloud host security policy requirements to generate structured instructions, and then converting them into API call sequences corresponding to the cloud platform to achieve cross-platform adaptation, and simultaneously dynamically adjusting and distributing global security policies based on recorded information, unified management and automatic adaptation of policies are achieved. Therefore, it can solve the technical problems in existing hybrid cloud security policy management methods, such as policy fragmentation and inconsistent execution caused by the use of platform-specific APIs, frequent configuration errors caused by manual intervention, and thus affecting the integrity of overall security protection and real-time response capabilities. It achieves the technical effects of unified management and consistent cross-platform execution of security policies, reducing manual configuration errors, and improving the integrity of overall security protection and real-time response capabilities.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to methods, apparatus, electronic devices and storage media for configuring cloud host security policies. Background Technology

[0002] Hybrid cloud architecture, as a crucial support for enterprise digital transformation, is widely used in industries with extremely high data security requirements, such as finance, government, and healthcare. With the continuous evolution of cloud computing technology, security policy management in hybrid cloud environments has gradually become a core element in ensuring the collaborative operation of multiple clouds. Among related technologies, a preliminary cross-platform security governance system has been constructed through the collaborative operation of security policy abstraction models, natural language processing, and API protocol adaptation. Specifically, this system covers the entire process from policy definition and semantic parsing to API calls, including key aspects such as security-driven deployment, policy distribution, context awareness, and dynamic adjustment.

[0003] In this hybrid cloud security policy management method, directly using platform-specific API interfaces for policy configuration can lead to policy fragmentation, inconsistent execution, and configuration errors caused by frequent manual intervention, thereby affecting the integrity of overall security protection and real-time response capabilities. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for configuring cloud host security policies, in order to at least solve the problem in related technologies where frequent manual intervention leads to configuration errors, thereby affecting the integrity of overall security protection and real-time response capabilities.

[0005] This application provides a method for configuring a cloud host security policy, including:

[0006] Obtain cloud host security policy requirements, perform semantic parsing on the requirements based on a preset model, and generate structured security policy instructions; The security policy instruction is converted into an application programming interface call sequence corresponding to the target cloud platform, and the security policy instruction is sent to the target cloud platform; Record the security policy execution status, cloud host metadata, and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information; The dynamically adjusted security policy rules are converted into a sequence of application programming interface calls for the corresponding cloud platform, and then sent to the cloud host of the corresponding cloud platform.

[0007] Optionally, the step of obtaining cloud host security policy requirements, and generating structured security policy instructions by semantically parsing the requirements based on a preset model, further includes: The security policy requirements input by the user are segmented and the intent is identified to extract at least one of the following: target protocol type, access control object, source Internet protocol address, destination Internet protocol address, port number and access direction. Based on the contextual understanding capabilities of the security big model, and combined with the current operating status of the cloud host and historical security events, the extracted policy requirements are semantically enhanced and compliance verified.

[0008] Optionally, the step of converting the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform and sending the security policy instruction to the target cloud platform further includes: Based on the application programming interface (API) specifications and version information of the target cloud platform, dynamically select the corresponding API call template and generate a request that conforms to the format of the target platform; The generated application programming interface call sequence is subjected to conflict analysis. If a conflict with the existing strategy is detected, conflict resolution suggestions are generated and fed back to the user.

[0009] Optionally, the process of recording the security policy execution status, cloud host metadata, and historical security events, and dynamically adjusting the global security policy rules of the hybrid cloud platform based on the recorded information, further includes: Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate corresponding policy adjustment suggestions. Compare the strategy adjustment recommendations with compliance requirements.

[0010] Optionally, the method further includes: Version control is implemented for policies distributed to various cloud platforms, the context information of each policy change is recorded, and rollback to historical versions is supported.

[0011] Optionally, the method further includes: Based on the platform type of the target cloud platform and the hardware architecture information of the target cloud host, the corresponding security driver is matched from the preset global security image library; The matched security driver is automatically deployed to the target cloud host, and the running status of the security driver is verified to ensure the compatibility of the security driver with the target cloud platform and the target cloud host.

[0012] Optionally, the method further includes: Collect the security policy execution results and real-time security status data of the target cloud host from various cloud platforms, evaluate the protection effect of the global security policy rules of the hybrid cloud platform, and generate a protection effect evaluation report. Based on the protection effectiveness assessment report and the information on changes in business scenarios in the hybrid cloud environment, the global security policy rules are iteratively optimized.

[0013] This application also provides a configuration device for cloud host security policies, including: The acquisition unit is used to acquire the security policy requirements of the cloud host, perform semantic parsing on the requirements based on a preset model, and generate structured security policy instructions. The sending unit is used to convert the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform, and send the security policy instruction to the target cloud platform; The adjustment unit is used to record the security policy execution status, cloud host metadata and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information. The conversion unit is used to convert the dynamically adjusted security policy rules into an application programming interface call sequence for the corresponding cloud platform, and send the dynamically adjusted security policy rules to the cloud host of the corresponding cloud platform.

[0014] Optionally, the acquisition unit is further configured to: The security policy requirements input by the user are segmented and the intent is identified to extract at least one of the following: target protocol type, access control object, source Internet protocol address, destination Internet protocol address, port number and access direction. Based on the contextual understanding capabilities of the security big model, and combined with the current operating status of the cloud host and historical security events, the extracted policy requirements are semantically enhanced and compliance verified.

[0015] Optionally, the sending unit is further configured to: Based on the application programming interface (API) specifications and version information of the target cloud platform, dynamically select the corresponding API call template and generate a request that conforms to the format of the target platform; The generated application programming interface call sequence is subjected to conflict analysis. If a conflict with the existing strategy is detected, conflict resolution suggestions are generated and fed back to the user.

[0016] Optionally, the adjustment unit is further configured to: Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate corresponding policy adjustment suggestions. Compare the strategy adjustment recommendations with compliance requirements.

[0017] Optionally, the device further includes: The recording unit is used to version control the policies issued to various cloud platforms, record the context information of each policy change, and support rollback to historical versions.

[0018] Optionally, the device further includes: The matching unit is used to match the corresponding security driver from the preset global security image library based on the platform type of the target cloud platform and the hardware architecture information of the target cloud host. The deployment unit is used to automatically deploy the matched security driver to the target cloud host and verify the running status of the security driver to ensure the compatibility of the security driver with the target cloud platform and the target cloud host.

[0019] Optionally, the device further includes: The evaluation unit is used to collect the security policy execution results and real-time security status data of the target cloud host from various cloud platforms, evaluate the protection effect of the global security policy rules of the hybrid cloud platform, and generate a protection effect evaluation report. The optimization unit is used to iteratively optimize the global security policy rules based on the protection effect evaluation report and the business scenario change information of the hybrid cloud environment.

[0020] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the configuration method of any of the cloud host security policies described above.

[0021] This application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the configuration method for any of the cloud host security policies described above.

[0022] This application also provides a computer program product, including a computer program, wherein when the computer program is executed by a processor, it implements the configuration method of any of the above-described cloud host security policies.

[0023] This application achieves unified management and automatic adaptation of security policies by uniformly parsing the security policy requirements of cloud hosts to generate structured instructions, which are then converted into API call sequences for the corresponding cloud platforms to achieve cross-platform adaptation. Simultaneously, it dynamically adjusts and distributes global security policies based on recorded information, thus avoiding fragmentation and excessive manual intervention caused by platform-specific APIs. Therefore, it solves the technical problems in existing hybrid cloud security policy management methods, such as policy fragmentation and inconsistent execution caused by platform-specific APIs, and frequent configuration errors due to manual intervention, which affect the integrity of overall security protection and real-time response capabilities. This achieves the technical effect of unified management and consistent cross-platform execution of security policies, reducing manual configuration errors, and improving the integrity of overall security protection and real-time response capabilities. Attached Figure Description

[0024] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart illustrating a method for configuring a cloud host security policy according to an embodiment of this application. Figure 2 A schematic diagram of a cloud host security policy configuration device provided in an embodiment of this application; Figure 3 This is a schematic diagram of the configuration device for another cloud host security policy provided in an embodiment of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0027] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0028] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0029] The embodiments of this application provide a method for configuring a cloud host security policy. The method is described in detail below in conjunction with the execution flow of the cloud host security policy configuration method. Figure 1 This is a flowchart illustrating a method for configuring a cloud host security policy according to an embodiment of this application.

[0030] like Figure 1 As shown, the method includes the following steps: Step 101: Obtain the security policy requirements of the cloud host, perform semantic parsing on the requirements based on the preset model, and generate structured security policy instructions; When orchestrating cloud host security policies in a hybrid cloud environment, the system acquires cloud host security policy requirements and performs semantic parsing of these requirements based on a pre-defined model to generate structured security policy instructions. Acquiring cloud host security policy requirements refers to users describing their security protection needs for cloud hosts in natural language on a unified security management platform. These requirements can cover various security-related needs, such as access control and port protection. For example, users might specify requirements such as allowing only internal network access to MySQL ports or prohibiting external IPs from accessing database ports.

[0031] The preset model is a large-scale security model trained on a hybrid cloud security scenario. By learning from a large number of security policy cases, historical security event logs, and various compliance standard-related data in a hybrid cloud environment, this model has the ability to accurately understand security requirements in natural language form.

[0032] During the semantic parsing stage, the pre-defined model first segments the natural language requirements input by the user, and then uses semantic recognition technology to clarify the core security elements in the requirements, such as operation actions, associated ports, protocol types, access source range, etc., while eliminating ambiguous information in the expression to ensure accurate capture of the user's true security intent.

[0033] After semantic parsing is completed, the preset model will transform the parsing results into structured security policy instructions. These instructions are usually in a format that computers can directly recognize and process, and contain key fields such as action parameters and platform. They can provide clear and accurate instruction basis for the subsequent adaptation and execution of security policies on different cloud platforms.

[0034] Step 102: Convert the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform, and send the security policy instruction to the target cloud platform; The security policy instructions are structured instructions generated in step 101, containing core fields such as action parameters and platform, which clearly reflect security protection requirements. The core component for instruction conversion is the MCP protocol adaptation layer. This adaptation layer pre-stores the API interface specifications and protocol requirements of mainstream cloud platforms and can adapt to the interface characteristics of different target cloud platforms.

[0035] During the conversion process, the MCP protocol adaptation layer first identifies the target cloud platform type specified in the security policy directive, and then, based on the platform's API call rules, decomposes the structured security policy directive and maps it into the corresponding platform's application programming interface call sequence. For example, for the AWS platform, it generates API call sequences related to Security Group rule updates, and for the Azure platform, it generates API call sequences related to NSG configuration, ensuring that the generated call sequences conform to the syntax format and parameter requirements of the target cloud platform.

[0036] The MCP protocol adaptation layer uses the JSON-RPC 2.0 protocol as the communication protocol for interacting with various cloud platforms. This protocol ensures the stability of command transmission and data integrity. After generating the API call sequence, the MCP protocol adaptation layer sends the security policy command in the form of the call sequence to the target cloud platform through a preset communication link. This ensures that the target cloud platform can accurately receive and recognize the command, laying the foundation for the subsequent implementation of the security policy on the target cloud platform. This process effectively solves the problem of significant differences in resource management interfaces of heterogeneous cloud platforms, avoids policy deployment failures due to platform interface incompatibility, and ensures the smooth execution of security policies across different hybrid cloud platforms.

[0037] Step 103: Record the security policy execution status, cloud host metadata, and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information; The recorded security policy execution status covers the distribution results, effectiveness, and any anomalies encountered during the execution process on the target cloud platform. For example, it records whether the policy was successfully implemented on platforms like AWS or Azure via API calls, whether execution failed due to parameter mismatches, and whether the expected protection effect was achieved after implementation. This directly reflects the effectiveness of policy execution. Cloud host metadata includes basic data such as the hybrid cloud platform type to which the cloud host belongs, hardware architecture (e.g., x86 ARM or MIPS), network configuration information (e.g., IP address and port usage), running service types, and resource allocation. This data is crucial for determining the compatibility of cloud host security requirements with the policy.

[0038] Historical security incidents include abnormal traffic access, unauthorized login attempts, port scanning attacks, data access violations, and non-compliance checks encountered by cloud servers in the past, providing data support for discovering security risk patterns and predicting potential threats.

[0039] The recording of the above information is accomplished collaboratively by the MCP protocol adaptation layer and the intelligent policy parsing engine. The MCP protocol adaptation layer synchronizes various data during policy execution in real time, while the intelligent policy parsing engine categorizes, stores, organizes, and performs preliminary analysis on cloud host metadata and historical security events. During the dynamic adjustment phase, the intelligent policy parsing engine's security big model conducts in-depth analysis based on the recorded information. For example, it identifies high-frequency attack paths by combining historical security event logs and automatically adjusts global security policy rules such as firewall rules and encryption algorithm selection for the hybrid cloud platform. Simultaneously, it references recorded cloud host metadata and compliance requirements such as GDPR 2.0 to ensure that the adjusted global rules are adapted to the operating environment and resource characteristics of different cloud hosts while complying with industry compliance standards. Finally, the adjusted global security policy rules are synchronized to each hybrid cloud platform via the MCP protocol, achieving dynamic adaptation and continuous optimization of security protection in the hybrid cloud environment.

[0040] Step 104: Convert the dynamically adjusted security policy rules into the application programming interface call sequence of the corresponding cloud platform, and send the dynamically adjusted security policy rules to the cloud host of the corresponding cloud platform.

[0041] The dynamically adjusted security policy rules are global security policy rules generated in step 103 based on the security policy execution status, cloud host metadata, and historical security events. They cover firewall rules, encryption algorithm configurations, and compliance-related security rules, and have met compliance requirements such as GDPR and Cybersecurity Classified Protection 2.0.

[0042] The core execution component of this step is the MCP protocol adaptation layer, which can perform adaptation processing for the interface characteristics of different corresponding cloud platforms. During the conversion process, the MCP protocol adaptation layer first identifies the target cloud platform types corresponding to the dynamically adjusted security policy rules, and then, based on the API call logic of each platform, decomposes and maps the adjusted rules into application programming interface call sequences that conform to the syntax format and parameter requirements of the corresponding platform. For example, for the AWS platform, it generates API call sequences related to Security Group rule updates, and for the Azure platform, it generates API call sequences related to NSG configuration, ensuring that the converted call sequences can be accurately identified by the corresponding cloud platform.

[0043] Meanwhile, the MCP protocol adaptation layer uses the JSON-RPC 2.0 protocol as the communication protocol. Through a preset stable communication link, it sends the dynamically adjusted security policy rules in the form of the converted API call sequence to the cloud host of the corresponding cloud platform, ensuring the data integrity and stability during the rule transmission process. This ensures that the cloud host can accurately receive and execute the adjusted security policy rules, thereby maintaining the consistency and effectiveness of global security protection in the hybrid cloud environment.

[0044] In some embodiments, the process of obtaining cloud host security policy requirements, including semantic parsing of the requirements based on a preset model to generate structured security policy instructions, further includes: The security policy requirements input by the user are segmented and the intent is identified to extract at least one of the following: target protocol type, access control object, source Internet protocol address, destination Internet protocol address, port number and access direction. Based on the contextual understanding capabilities of the security big model, and combined with the current operating status of the cloud host and historical security events, the extracted policy requirements are semantically enhanced and compliance verified.

[0045] The system performs word segmentation and intent recognition on the user's input security policy requirements in natural language form. Word segmentation breaks down the user's input into keywords or phrases with independent semantics. For example, "Only allow the internal office network to access cloud host port 8080 via TCP protocol" is broken down into semantic units such as "only allow," "internal office network," "TCP protocol," and "cloud host port 8080." Intent recognition uses the semantic analysis capabilities of a pre-defined model to clarify the user's core security requirements, such as determining whether the user's requirement is "allow specific access" or "prohibit external access." Based on this, from the segmented semantic units and the identified core requirements, at least one key piece of information is extracted, including the target protocol type (e.g., TCP / UDP), the access control object (e.g., a specific cloud host or database service), the source internet protocol address (e.g., the 10.0.0.0 / 16 network segment of the internal office network), the destination internet protocol address (i.e., the target cloud host IP), the port number (e.g., 8080 3306), and the access direction (e.g., inbound or outbound access). This information provides data support for the subsequent generation of structured instructions.

[0046] Further processing is performed using the contextual understanding capabilities of a large-scale security model. This model is trained on a large number of security policy cases, operational data, and compliance standards in a hybrid cloud environment. It can combine the current operating status of cloud hosts, such as real-time resource usage, port usage status, and business service types, with historical security events, such as past abnormal access records and attack event logs, to semantically enhance and verify the extracted policy requirements. Semantic enhancement can supplement the security requirements implicit in the user's description. For example, if the user only mentions "protecting the database cloud host," combining the currently running MySQL service on the cloud host and historical attack records, the implicit requirement of "protecting port 3306" can be automatically added. It checks whether the extracted policy requirements comply with compliance requirements such as data security access control and log retention. If there are any non-compliance items, it automatically prompts for adjustments, ensuring that the final generated structured security policy instructions not only meet the user's actual needs but also comply with industry compliance standards.

[0047] In some embodiments, converting the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform and sending the security policy instruction to the target cloud platform further includes: Based on the application programming interface (API) specifications and version information of the target cloud platform, dynamically select the corresponding API call template and generate a request that conforms to the format of the target platform; The generated application programming interface call sequence is subjected to conflict analysis. If a conflict with the existing strategy is detected, conflict resolution suggestions are generated and fed back to the user.

[0048] In the process of converting security policy instructions into an application programming interface call sequence corresponding to the target cloud platform and sending it to the target cloud platform according to claim 1, two key processing steps are also included to ensure the compatibility of the instructions and the effectiveness of the policy. The MCP protocol adaptation layer dynamically selects the corresponding call template to generate compliant requests based on the target cloud platform's application programming interface (API) specifications and version information. Different platforms, and even different API versions within the same platform, have varying requirements for interface parameter formats and request syntax. For example, AWS's Security Group API parameter naming may change from "ip_permissions" to "ip_access_rules" in different versions, and Azure's NSG API's port range parameter restrictions may also change with version updates. The MCP protocol adaptation layer pre-stores API call templates for different versions of various mainstream cloud platforms. These templates include the corresponding version's parameter structure, required fields, and format specifications. During conversion, the MCP protocol adaptation layer first obtains the API version information used by the target cloud platform through its interface detection function. Then, combined with the platform's API specifications, it matches the appropriate API call template from the template library, fills the structured parameters from the security policy instructions into the corresponding fields of the template, and generates request data that conforms to the current version's interface format requirements of the target cloud platform, such as a JSON-formatted API request body. This effectively solves the problem of call failures caused by cloud platform API version iterations and ensures compatibility between instructions and platform interfaces.

[0049] The generated API call sequence is subjected to conflict analysis and resolution suggestions are provided. Specifically, the intelligent policy parsing engine retrieves the security policy data that has been implemented on the target cloud platform, such as the Security Group rules configured in AWS and the existing NSG policies in Azure. The security policy corresponding to the API call sequence to be sent is logically compared with the existing policies to detect whether there are permission conflicts. For example, the policy to be executed may allow external IPs to access the database port 3306, while the existing policy may prohibit external access to this port, or the port range of the policy to be executed may overlap with the port blocking range of the existing policy.

[0050] If a conflict is detected, the intelligent policy parsing engine will generate conflict resolution suggestions based on hybrid cloud security compliance requirements such as GDPR and Cybersecurity Classified Protection 2.0, as well as historical policy operation and maintenance experience. For example, it may suggest prioritizing the retention of policies that meet compliance standards, or prompt the user to choose between retaining a new policy and an existing policy. Subsequently, the conflict information and resolution suggestions will be fed back to the user through the security management platform. The command will be sent to the user only after the user confirms the solution. This avoids security vulnerabilities or policy execution failures caused by policy conflicts, and ensures that the security policies issued to the target cloud platform can stably play a protective role.

[0051] In some embodiments, the process of recording the security policy execution status, cloud host metadata, and historical security events, and dynamically adjusting the global security policy rules of the hybrid cloud platform based on the recorded information, further includes: Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate corresponding policy adjustment suggestions. Compare the strategy adjustment recommendations with compliance requirements.

[0052] In the process of recording the security policy execution status, cloud host metadata and historical security events, and dynamically adjusting the global security policy rules of the hybrid cloud platform based on the recorded information, the method described in claim 1 also includes two key processing steps to improve the foresight and compliance of security protection.

[0053] Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate policy adjustment suggestions. The real-time traffic data of cloud servers includes real-time transmission information such as source Internet Protocol address, destination Internet Protocol address, protocol type used, port access status, and peak traffic fluctuations for both inbound and outbound traffic, reflecting the dynamic characteristics of current network access. The security event logs contain historical security-related data such as abnormal traffic access, unauthorized login attempts, port scanning attacks, and data access violations encountered by the cloud servers in the past.

[0054] The machine learning algorithms used are integrated into the security big model of the intelligent policy parsing engine. Specifically, they may include decision trees, neural networks, and other algorithms. These algorithms identify abnormal access patterns and potential risk trends by analyzing the correlation between real-time traffic data and security event logs. For example, when an external IP is detected to have repeatedly attempted to access the cloud host's database port and the traffic characteristics are similar to historical attack events, it can be predicted that the IP may have an attack path to infiltrate the cloud host through that port. Based on this, corresponding policy adjustment suggestions such as blocking the external IP and restricting the source of database port access are generated.

[0055] The generated policy adjustment suggestions are compared with compliance requirements. During the comparison process, it is checked whether the policy adjustment suggestions comply with the provisions of the compliance standards regarding data access control, security log retention, encryption protection, etc. For example, if the suggestions involve adjustments to the data transmission encryption algorithm, it is necessary to confirm whether the adjusted algorithm meets the encryption strength requirements for data transmission security. This ensures that the final global security policy rules based on the suggestions have both risk protection capabilities and comply with relevant compliance requirements, avoiding security risks and compliance hazards caused by policy adjustments that violate compliance standards.

[0056] In some embodiments, the method further includes: Version control is implemented for policies distributed to various cloud platforms, the context information of each policy change is recorded, and rollback to historical versions is supported.

[0057] The core of this step is to build a complete policy version management mechanism through the collaboration between the intelligent policy parsing engine and the MCP protocol adaptation layer. Each time a policy changes, the system automatically records the complete context information of that change. This context information specifically includes the timestamp of the policy change, the user identity identifier of the user initiating the change (such as an administrator account or automated adjustment module identifier), the triggering reason for the change (whether it was manually initiated by the user based on business needs, or automatically triggered by the intelligent policy parsing engine based on security event logs or risk prediction results), a detailed comparison of the policy content before and after the change (such as records of adding, deleting, or modifying firewall rules, or adjusting port access permissions), and the unique identifier of the target cloud platform type and associated cloud host corresponding to the policy (such as cloud host ID and resource pool information). This information is structured and stored in the security platform's historical version database, forming a traceable policy change chain, facilitating subsequent troubleshooting of policy-related issues or audit compliance by operations and maintenance personnel.

[0058] Meanwhile, the system supports rolling back policies to any historical version. When policy changes cause compatibility conflicts between cloud hosts and business systems, abnormal policy execution affecting normal business operations, or unforeseen security vulnerabilities in the new policy, users can select the target historical version to roll back to based on the context information (such as change time and reason) in the policy version management interface of the security management platform. The system will call the MCP protocol adaptation layer to convert the policy content of the historical version into the application programming interface call sequence of the corresponding target cloud platform, and resend it to the target cloud platform according to the same communication protocol (JSON-RPC 2.0 protocol) as the initial policy issuance, overwriting the currently effective problematic policy version, so that the cloud hosts of the corresponding cloud platform are restored to the historical security policy protection state, effectively reducing the security risks and business impact caused by policy change errors.

[0059] In some embodiments, the method further includes: Based on the platform type of the target cloud platform and the hardware architecture information of the target cloud host, the corresponding security driver is matched from the preset global security image library; The matched security driver is automatically deployed to the target cloud host, and the running status of the security driver is verified to ensure the compatibility of the security driver with the target cloud platform and the target cloud host.

[0060] First, it relies on the preset global security image library to achieve accurate matching of security drivers. The global security image library is a dedicated storage module built into the security platform, which pre-stores security drivers for different target cloud platform types and different target cloud host hardware architectures.

[0061] During the matching process, the system first obtains the platform type information of the target cloud platform through its interface, and reads the metadata of the target cloud host to confirm the hardware architecture information. Then, based on these two types of information, it filters out the fully matching security drivers from the global security image library to avoid the failure of subsequent policy execution due to driver incompatibility with the platform or architecture.

[0062] After the security driver matching is completed, the driver deployment engine performs automatic deployment. The engine calls the target cloud platform's API interface to automatically upload the matched security driver image to the target cloud platform's image repository. Then, it mounts the security driver to the target cloud host via API commands and triggers the deployment command. Specifically, the security driver installation script can be executed through the virtual machine tools built into the target cloud host to install the security driver inside the cloud host and start related services. After deployment, the system further verifies the security driver's running status, including checking whether the driver has started successfully, whether it can interact normally with the target cloud host's operating system, and whether it can respond to commands issued by the security platform (such as policy execution feedback commands). If the verification finds that the driver is running abnormally, it will automatically trigger a retry deployment process or provide error information to the user until the security driver runs normally.

[0063] This process effectively solves the problem of security driver adaptation in heterogeneous cloud environments, providing a foundation for the smooth execution of subsequent security policies on target cloud hosts and ensuring the compatibility of security policies with target cloud platforms and target cloud hosts.

[0064] In some embodiments, the method further includes: Collect the security policy execution results and real-time security status data of the target cloud host from various cloud platforms, evaluate the protection effect of the global security policy rules of the hybrid cloud platform, and generate a protection effect evaluation report. Based on the protection effectiveness assessment report and the information on changes in business scenarios in the hybrid cloud environment, the global security policy rules are iteratively optimized.

[0065] First, data collection is conducted, gathering security policy execution results from various cloud platforms. These results include information such as whether the policy was successfully issued, whether execution anomalies occurred after it took effect on the cloud platform, and whether preset security threats were successfully blocked. For example, AWS reports whether Security Group rules were successfully updated and blocked unauthorized external access, and Azure reports whether NSG configurations effectively blocked abnormal traffic. Simultaneously, the system collects real-time security status data of the target cloud hosts, including real-time network traffic characteristics, vulnerability scan results, unauthorized access attempt records, and compliance check results. This data, along with the security policy execution results, constitutes the foundational data source for evaluating the protection effectiveness.

[0066] The effectiveness of global security policy rules is evaluated. This evaluation compares the policy against preset security indicators for the hybrid cloud environment, such as attack interception rate, compliance rate, and security incident rate. It combines collected execution results with real-time security status data to analyze the global policy's ability to respond to various security threats and determine whether the policy effectively covers security risks in the hybrid cloud environment. For example, it tracks the proportion of successfully intercepted abnormal accesses to total abnormal accesses and checks whether the policy meets GDPR and Cybersecurity Classified Protection 2.0 compliance requirements. A protection effectiveness evaluation report is generated upon completion. The report clearly presents the effective protection items, weak points, and areas for optimization within the global security policy. For instance, it identifies attacks targeting database ports that were effectively intercepted, while vulnerabilities exist in the protection against new business ports.

[0067] Finally, iterative optimizations were conducted based on the protection effectiveness assessment report and information on changes in business scenarios within the hybrid cloud environment. These changes included business expansion in the hybrid cloud environment, the addition of new business modules, and the migration of business to new cloud platform nodes. The system, through its intelligent policy parsing engine, combined the optimization directions in the assessment report with these changes in business scenarios to adjust global security policy rules. For example, corresponding firewall rules were added to address the protection weaknesses identified in the assessment report, and existing port protection policies were optimized based on the network access requirements of newly added business modules. This ensured that the adjusted global security policy rules not only addressed existing protection vulnerabilities but also adapted to changes in business scenarios within the hybrid cloud environment, achieving dynamic matching between security policies and business development and security needs, and continuously enhancing the effectiveness of security protection in the hybrid cloud environment.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0069] Embodiments of this application also provide a configuration device for cloud host security policies, such as... Figure 2 As shown, it includes: The acquisition unit 21 is used to acquire the security policy requirements of the cloud host, perform semantic parsing on the requirements based on a preset model, and generate structured security policy instructions. Sending unit 22 is used to convert the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform, and send the security policy instruction to the target cloud platform; The adjustment unit 23 is used to record the security policy execution status, cloud host metadata and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information. The conversion unit 24 is used to convert the dynamically adjusted security policy rules into the application programming interface call sequence of the corresponding cloud platform, and send the dynamically adjusted security policy rules to the cloud host of the corresponding cloud platform.

[0070] Furthermore, in one possible implementation of this application embodiment, the acquisition unit 21 is further configured to: The security policy requirements input by the user are segmented and the intent is identified to extract at least one of the following: target protocol type, access control object, source Internet protocol address, destination Internet protocol address, port number and access direction. Based on the contextual understanding capabilities of the security big model, and combined with the current operating status of the cloud host and historical security events, the extracted policy requirements are semantically enhanced and compliance verified.

[0071] Furthermore, in one possible implementation of this application embodiment, the sending unit 22 is further configured to: Based on the application programming interface (API) specifications and version information of the target cloud platform, dynamically select the corresponding API call template and generate a request that conforms to the format of the target platform; The generated application programming interface call sequence is subjected to conflict analysis. If a conflict with the existing strategy is detected, conflict resolution suggestions are generated and fed back to the user.

[0072] Furthermore, in one possible implementation of this application embodiment, the adjustment unit 23 is further configured to: Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate corresponding policy adjustment suggestions. Compare the strategy adjustment recommendations with compliance requirements.

[0073] Furthermore, in one possible implementation of the embodiments of this application, such as Figure 3 As shown, the device further includes: Recording unit 25 is used to perform version control on policies issued to various cloud platforms, record the context information of each policy change, and support rollback to historical versions.

[0074] Furthermore, in one possible implementation of the embodiments of this application, such as Figure 3 As shown, the device further includes: The matching unit 26 is used to match the corresponding security driver from the preset global security image library according to the platform type of the target cloud platform and the hardware architecture information of the target cloud host. Deployment unit 27 is used to automatically deploy the matched security driver to the target cloud host and verify the running status of the security driver to ensure the compatibility of the security driver with the target cloud platform and the target cloud host.

[0075] Furthermore, in one possible implementation of the embodiments of this application, such as Figure 3 As shown, the device further includes: Evaluation unit 28 is used to collect the security policy execution results and real-time security status data of the target cloud host from each cloud platform, evaluate the protection effect of the global security policy rules of the hybrid cloud platform, and generate a protection effect evaluation report. The optimization unit 29 is used to iteratively optimize the global security policy rules based on the protection effect evaluation report and the business scenario change information of the hybrid cloud environment.

[0076] For a description of the features in the embodiment corresponding to the configuration device for cloud host security policy, please refer to the relevant description in the embodiment corresponding to the configuration method for cloud host security policy, which will not be repeated here.

[0077] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the cloud host security policy configuration method embodiments described above.

[0078] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in the configuration method embodiments of any of the cloud host security policies described above when running.

[0079] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0080] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in the configuration method embodiments of any of the cloud host security policies described above.

[0081] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the configuration method embodiments of any of the cloud host security policies described above.

[0082] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0083] The foregoing has provided a detailed description of the configuration method, apparatus, electronic device, and storage medium for a cloud host security policy provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for configuring a cloud host security policy, characterized in that, include: Obtain cloud host security policy requirements, perform semantic parsing on the requirements based on a preset model, and generate structured security policy instructions; The security policy instruction is converted into an application programming interface call sequence corresponding to the target cloud platform, and the security policy instruction is sent to the target cloud platform; Record the security policy execution status, cloud host metadata, and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information; The dynamically adjusted security policy rules are converted into a sequence of application programming interface calls for the corresponding cloud platform, and then sent to the cloud host of the corresponding cloud platform.

2. The method according to claim 1, characterized in that, The process of obtaining cloud host security policy requirements, based on a preset model, involves semantic parsing of the requirements to generate structured security policy instructions, and further includes: The security policy requirements input by the user are segmented and the intent is identified to extract at least one of the following: target protocol type, access control object, source Internet protocol address, destination Internet protocol address, port number and access direction. Based on the contextual understanding capabilities of the security big model, and combined with the current operating status of the cloud host and historical security events, the extracted policy requirements are semantically enhanced and compliance verified.

3. The method according to claim 1, characterized in that, The step of converting the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform and sending the security policy instruction to the target cloud platform further includes: Based on the application programming interface (API) specifications and version information of the target cloud platform, dynamically select the corresponding API call template and generate a request that conforms to the format of the target platform; The generated application programming interface call sequence is subjected to conflict analysis. If a conflict with the existing strategy is detected, conflict resolution suggestions are generated and fed back to the user.

4. The method according to claim 1, characterized in that, The process of recording the security policy execution status, cloud host metadata, and historical security events, and dynamically adjusting the global security policy rules of the hybrid cloud platform based on the recorded information, also includes: Based on real-time traffic data and security event logs of cloud servers, machine learning algorithms are used to predict potential attack paths and generate corresponding policy adjustment suggestions. Compare the strategy adjustment recommendations with compliance requirements.

5. The method according to claim 1, characterized in that, The method further includes: Version control is implemented for policies distributed to various cloud platforms, the context information of each policy change is recorded, and rollback to historical versions is supported.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Based on the platform type of the target cloud platform and the hardware architecture information of the target cloud host, the corresponding security driver is matched from the preset global security image library; The matched security driver is automatically deployed to the target cloud host, and the running status of the security driver is verified to ensure the compatibility of the security driver with the target cloud platform and the target cloud host.

7. The method according to any one of claims 1-5, characterized in that, The method further includes: Collect the security policy execution results and real-time security status data of the target cloud host from various cloud platforms, evaluate the protection effect of the global security policy rules of the hybrid cloud platform, and generate a protection effect evaluation report. Based on the protection effectiveness assessment report and the information on changes in business scenarios in the hybrid cloud environment, the global security policy rules are iteratively optimized.

8. A configuration device for cloud host security policies, characterized in that, include: The acquisition unit is used to acquire the security policy requirements of the cloud host, perform semantic parsing on the requirements based on a preset model, and generate structured security policy instructions. The sending unit is used to convert the security policy instruction into an application programming interface call sequence corresponding to the target cloud platform, and send the security policy instruction to the target cloud platform; The adjustment unit is used to record the security policy execution status, cloud host metadata and historical security events, and dynamically adjust the global security policy rules of the hybrid cloud platform based on the recorded information. The conversion unit is used to convert the dynamically adjusted security policy rules into an application programming interface call sequence for the corresponding cloud platform, and send the dynamically adjusted security policy rules to the cloud host of the corresponding cloud platform.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the configuration method for the cloud host security policy as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the configuration method of the cloud host security policy as described in any one of claims 1 to 7.