Container arranging and scheduling method and flow control processing method

By dividing security level and matching business services to the cloud platform server resource pool, and implementing traffic control and flow control processing, the problem of lack of physical isolation of container orchestration in the cloud platform is solved, and the security and stability of containers are significantly improved.

CN119071016APending Publication Date: 2024-12-03NO 15 INST OF CHINA ELECTRONICS TECH GRP

Patent Information

Application Number
CN202411005051.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-25
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing cloud platforms lack effective physical isolation in container orchestration, resulting in different dense-level services sharing the same resource pool, increasing the probability and severity of containers being captured.

Method used

By dividing the security level of the server resource pool, servers with different security levels are classified into different resource subpools, and matching them based on the confidentiality and core of the business services, flow control and flow control processing are implemented to ensure that high-security level servers and Isolation of low security level servers.

Benefits of technology

It realizes isolation from the user perception layer to the physical level, improves the security of the container, reduces the probability and severity of being attacked, and quickly responds to deal with security risks through real-time monitoring and alarm mechanisms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071016A_ABST
    Figure CN119071016A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a container arranging and scheduling method and a method for realizing flow control processing, and the method comprises the steps: carrying out the security level division of servers in a server resource pool through employing a preset strategy, and classifying the servers with different security levels into different resource sub-pools, dividing the security levels of different business services based on a preset division rule, and dividing the core degrees of the business services; and matching the different business services to different resource sub-pools based on the security levels of the different business services and the core degrees of the different businesses. According to the embodiment of the invention, the isolation of the user perception layer of the container can be deepened to the isolation of the physical layer, the security level configuration of the business service is combined, different business services are borne by means of different resource sub-pools, and corresponding flow control strategies are configured, so that the isolation level of the container is further improved, and the difficulty of container attack is increased; and the probability that the container is attacked and the severity after the container is attacked are reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the technical field of cloud platforms, and in particular to a container orchestration and scheduling method and a flow control processing method. Background Art

[0002] Container orchestration refers to the deployment and management of multiple service containers. The reason why container orchestration technology exists is mainly related to the increasing business volume and system complexity, which in turn promotes the evolution of service deployment. In actual production environments, coordinating container resources among multiple physical hosts has become the primary problem to be solved. This problem is collectively referred to as container orchestration.

[0003] At present, most clouds are unified resource pools, that is, all reported server resources are treated as a unified schedulable pool. Even if namespace-like isolation is performed, it is only isolation at the user perception layer. The actual physical servers are not isolated and still use a unified resource pool. This undoubtedly expands the attack surface of the service container. Especially for services with different confidentiality levels, isolation at the perception layer alone is far from enough. The physical entities of services with different confidentiality levels are together, which not only increases the probability of the container being compromised, but also makes the consequences of the compromise more serious. Summary of the invention

[0004] The main purpose of the present disclosure is to provide a container orchestration scheduling method, including: dividing the security levels of servers in a server resource pool using a preset strategy, and classifying servers of different security levels into different resource sub-pools, wherein the resource sub-pool level corresponding to a server of a high security level is high, the resource sub-pool level corresponding to a server of a medium security level is medium, and the resource sub-pool level corresponding to a server of a low security level is low; dividing the confidentiality levels of different business services and the coreness of business services based on preset division rules; matching different business services to different resource sub-pools based on the confidentiality levels of different business services and the coreness of different businesses.

[0005] Optionally, after servers of different security levels are grouped into different resource sub-pools, the method further performs traffic control on the resource sub-pools, including: enabling servers in the same resource sub-pool to access each other; between resource sub-pools of different levels, enabling servers in a resource sub-pool of a high security level to access servers in a resource sub-pool of a low security level; and preventing servers in a resource sub-pool of a low security level from accessing servers in a resource sub-pool of a high security level.

[0006] Optionally, based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools, including: business services with high confidentiality levels are preferentially deployed to resource sub-pools with high security levels; business services with low confidentiality levels are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources of a resource sub-pool with a high security level are insufficient, the business services with high confidentiality levels are cross-level deployed to resource sub-pools with low security levels.

[0007] Optionally, based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools, including: core business services with high coreness are preferentially deployed to resource sub-pools with high security levels; edge business services with low coreness are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources in the resource sub-pool with a high security level are insufficient, the core services are cross-level deployed to the resource sub-pool with a low security level.

[0008] Optionally, classifying the confidentiality levels of different business services based on preset classification rules includes: classifying the confidentiality levels based on the sensitivity of the data, the importance of the business, and the potential security risks.

[0009] Optionally, dividing the coreness of the business services includes dividing the coreness of the business services according to business importance, the degree of dependence on system functions, and associations between services.

[0010] Optionally, it includes: obtaining container security monitoring results, wherein the security monitoring results include the presence or absence of vulnerability risks, and when there is a vulnerability risk, the vulnerability risk includes a high risk level, a medium risk level and a low risk level; and performing different flow control processing based on different vulnerability risk levels and different security levels of the server.

[0011] Optionally, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0012] Optionally, container security monitoring results are obtained, wherein the security monitoring results include the presence or absence of vulnerability risks, and when there is a vulnerability risk, the vulnerability risk includes a high risk level, a medium risk level, and a low risk level; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, wherein the servers in the server resource pool are divided into security levels using a preset strategy, the resource subpool level corresponding to the server with a high security level is high, the resource subpool level corresponding to the server with a medium security level is medium, and the resource subpool level corresponding to the server with a low security level is low; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

[0013] Optionally, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0014] In order to achieve the above-mentioned purpose, according to the first aspect of the present disclosure, a container orchestration and scheduling method is provided, including: dividing the security levels of servers in a server resource pool using a preset strategy, and classifying servers of different security levels into different resource sub-pools, wherein the resource sub-pool level corresponding to a server with a high security level is high, the resource sub-pool level corresponding to a server with a medium security level is medium, and the resource sub-pool level corresponding to a server with a low security level is low; dividing the confidentiality levels of different business services and the coreness of business services based on preset division rules; matching different business services to different resource sub-pools based on the confidentiality levels of different business services and the coreness of different businesses.

[0015] Optionally, after servers of different security levels are grouped into different resource sub-pools, the method further performs traffic control on the resource sub-pools, including: enabling servers in the same resource sub-pool to access each other; between resource sub-pools of different levels, enabling servers in a resource sub-pool of a high security level to access servers in a resource sub-pool of a low security level; and preventing servers in a resource sub-pool of a low security level from accessing servers in a resource sub-pool of a high security level.

[0016] Optionally, based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools, including: business services with high confidentiality levels are preferentially deployed to resource sub-pools with high security levels; business services with low confidentiality levels are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources of a resource sub-pool with a high security level are insufficient, the business services with high confidentiality levels are cross-level deployed to resource sub-pools with low security levels.

[0017] Optionally, based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools, including: core business services with high coreness are preferentially deployed to resource sub-pools with high security levels; edge business services with low coreness are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources in the resource sub-pool with a high security level are insufficient, the core services are cross-level deployed to the resource sub-pool with a low security level.

[0018] Optionally, classifying the confidentiality levels of different business services based on preset classification rules includes: classifying the confidentiality levels based on the sensitivity of the data, the importance of the business, and the potential security risks.

[0019] Optionally, dividing the coreness of the business services includes dividing the coreness of the business services according to business importance, the degree of dependence on system functions, and associations between services.

[0020] According to a second aspect of the present disclosure, a method for implementing flow control processing is provided, including obtaining container security monitoring results, wherein the security monitoring results include the presence or absence of vulnerability risks, and when vulnerability risks exist, the vulnerability risks include high risk levels, medium risk levels, and low risk levels; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

[0021] Optionally, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0022] According to a third aspect of the present disclosure, another method for implementing flow control processing is provided, including obtaining container security monitoring results, wherein the security monitoring results include the presence or absence of vulnerability risks, and when there is a vulnerability risk, the vulnerability risk includes a high risk level, a medium risk level and a low risk level; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, wherein the servers in the server resource pool are divided into security levels using a preset strategy, the resource subpool level corresponding to the server with a high security level is high, the resource subpool level corresponding to the server with a medium security level is medium, and the resource subpool level corresponding to the server with a low security level is low; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

[0023] Optionally, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0024] The container orchestration and scheduling method of this embodiment includes dividing the security levels of servers in the server resource pool using a preset strategy, and classifying servers of different security levels into different resource sub-pools, wherein the resource sub-pool level corresponding to the server with a high security level is high, the resource sub-pool level corresponding to the server with a medium security level is medium, and the resource sub-pool level corresponding to the server with a low security level is low; dividing the confidentiality levels of different business services and the coreness of business services based on preset division rules; matching different business services to different resource sub-pools based on the confidentiality levels of different business services and the coreness of different businesses. This embodiment can deepen the user perception layer isolation of the container to the physical layer isolation, and combine the confidentiality level configuration of the business service, by using different resource sub-pools to carry different business services, and configuring corresponding flow control strategies, further improving the isolation level of the container, increasing the difficulty of container attack, and reducing the probability of the container being attacked and the severity after the attack.

[0025] This embodiment implements a method for flow control processing, performs real-time monitoring of the platform's containers, issues risk alerts to notify stakeholders of rapid response in the event of security risks, and takes different measures for different levels of risks. For medium and high-level risks, automatic two-way blocking of traffic is performed to prevent further expansion of risks.

[0026] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0027] Figure 1 is a flowchart of a container orchestration and scheduling method according to an embodiment of the present disclosure;

[0028] Figure 2 This is a schematic diagram of an application scenario of the container orchestration and scheduling method according to an embodiment of the present disclosure;

[0029] Figure 3 is a flow chart of a method for implementing flow control processing according to an embodiment of the present disclosure;

[0030] Figure 4 It is a schematic diagram of an application scenario of the method for implementing flow control processing in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present disclosure, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present disclosure.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0034] According to an embodiment of the present disclosure, a container scheduling method is provided, such as Figure 1 As shown, it includes the following steps 101 to 103:

[0035] Step 101: The servers in the server resource pool are divided into security levels using a preset strategy, and servers of different security levels are classified into different resource sub-pools, wherein the resource sub-pool level corresponding to the server of a high security level is high, the resource sub-pool level corresponding to the server of a medium security level is medium, and the resource sub-pool level corresponding to the server of a low security level is low.

[0036] In this embodiment, the security level of the server is divided by security policies (including intrusion detection and prevention, security patch updates, data encryption and decryption, access control policies, etc.) and its own performance (software and hardware configuration, actual operating environment load, etc.), and different security level labels are added to the server. According to the added security level labels, the server is divided into different security levels, such as high, medium, and low. Thus, the unified resource pool is divided into resource sub-pools of different levels.

[0037] Step 102: Classify the confidentiality levels of different business services and the coreness of the business services based on preset classification rules.

[0038] As an optional implementation of this embodiment, classifying the confidentiality levels of different business services based on preset classification rules includes: classifying the confidentiality levels based on the sensitivity of the data, the importance of the business, and the potential security risks.

[0039] In this optional implementation, when describing the required resources for a service, service confidentiality information is added. Service confidentiality is divided based on the sensitivity of the data, the importance of the business, and potential security risks. Service confidentiality information mainly provides a scheduling basis for container orchestration and scheduling. In the container orchestration system, the scheduler will match the resource sub-pool of the corresponding level according to the confidentiality information of the service. This matching is a mandatory scheduling strategy, that is, if a resource sub-pool that meets the conditions cannot be found, the container deployment will be blocked.

[0040] When describing the resources required for a service, you should add coreness information. The coreness can be determined based on factors such as the business importance of the service, the degree of dependence on system functions, and the relationship between services. For example, services can be divided into multiple levels such as core services and edge services.

[0041] Step 103: Based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools.

[0042] In this embodiment, the business service classification and business coreness division play a vital role in container orchestration and resource scheduling. By clarifying the service classification and service coreness to match the corresponding level of resource sub-pools and implementing cross-level deployment strategies, it can ensure that the security and performance requirements of the service are met, improve the overall resource utilization, and further improve the security and stability of the platform, and enhance user experience and business value.

[0043] As an optional implementation method of this embodiment, after servers of different security levels are classified into different resource sub-pools, the method also performs traffic control on the resource sub-pools, including: enabling servers in the same resource sub-pool to access each other; between resource sub-pools of different levels, enabling servers in a resource sub-pool with a high security level to access servers in a resource sub-pool with a low security level; and preventing servers in a resource sub-pool with a low security level from accessing servers in a resource sub-pool with a high security level.

[0044] In this optional implementation, network tools such as IP tabs are used to control the flow of resource sub-pools of different security levels, so that services in the same security level sub-pool can access each other, ensuring that servers in the same security level can communicate and collaborate normally. Secondly, servers in high-security resource sub-pools are allowed to access servers in low-security resource sub-pools. This access is usually one-way to meet management, monitoring and other requirements. Finally, servers in low-security resource sub-pools are prohibited from accessing servers in high-security resource sub-pools to further prevent potential security threats, such as malicious attacks, data theft, etc. Exemplarily, servers in high-security resource sub-pools accessing servers in low-security resource sub-pools can include high-security servers accessing medium or low-security servers; medium-security servers accessing low-security servers. Similarly, low or medium security servers are prohibited from accessing high-security servers.

[0045] As an optional implementation method of the present embodiment, based on the confidentiality levels of different business services and the coreness of different businesses, different business services are matched to different resource sub-pools, including: business services with high confidentiality levels are preferentially deployed to resource sub-pools with high security levels; business services with low confidentiality levels are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources of a resource sub-pool with a high security level are insufficient, the business services with high confidentiality levels are cross-deployed to resource sub-pools with low security levels (which can be specified by the user through configuration).

[0046] In this optional implementation, high-security services usually contain highly sensitive data or execute critical business logic, so they should be deployed to resource sub-pools with high security levels on a priority basis. These resource sub-pools usually have stronger security protection measures and more stable hardware and software environments to ensure the stable operation and data security of high-security services. Low-security services have relatively low requirements for security and performance, so they can be deployed to resource sub-pools with low security levels. This helps to make full use of resources and improve overall resource utilization. In addition, in some cases, when resources in resource sub-pools with high security levels are insufficient, it may be necessary to allow high-security services to be deployed across levels to resource sub-pools with low security levels (which can be specified by the user through configuration). This strategy needs to be implemented under the premise of ensuring security to avoid potential security risks.

[0047] As an optional implementation method of this embodiment, different business services are matched to different resource sub-pools based on the confidentiality levels of different business services and the coreness of different businesses, including: core business services with high coreness are preferentially deployed to resource sub-pools with high security levels; edge business services with low coreness are preferentially deployed to resource sub-pools with low security levels; wherein, when the resources in the resource sub-pool with a high security level are insufficient, the core services are cross-level deployed to the resource sub-pool with a low security level.

[0048] In this optional implementation, for core services, priority should be given to their deployment location and resource guarantee. During the container orchestration and scheduling process, the scheduler should give priority to deploying them to resource sub-pools with high security levels to ensure the security and stability of core services.

[0049] For edge services, they can be deployed to resource sub-pools with low security levels to avoid waste and overuse of resources. In addition, in some cases, when the resources in the resource sub-pools with high security levels are insufficient, it may be necessary to allow core services to be deployed across levels to resource sub-pools with low security levels. This ensures that the core functions can still operate normally when the platform is under pressure.

[0050] refer to Figure 2 The container orchestration and scheduling diagram in the figure divides the resource pool into resource sub-pools with different security levels. Servers with different security levels and business services with different confidentiality levels and different core degrees are deployed in different resource sub-pools.

[0051] This embodiment isolates the user perception layer of the container and deepens the isolation to the physical layer. In combination with the confidentiality configuration of the business service, different resource sub-pools are used to carry different business services and configure corresponding flow control strategies, which further improves the isolation level of the container, increases the difficulty of container attack, and reduces the probability of container attack and the severity of the attack.

[0052] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0053] According to an embodiment of the present disclosure, a method for implementing flow control processing of a resource pool obtained by orchestration and scheduling is also provided, including obtaining container security monitoring results, wherein the security monitoring results include the presence or absence of vulnerability risks, and when there are vulnerability risks, the vulnerability risks include high risk levels, medium risk levels and low risk levels; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

[0054] In this embodiment, the container is used as a tool for the cloud platform to ultimately deploy service containers. It generally runs on a server and is characterized by resource isolation between containers and between containers and host machines. Its main purpose is to ensure that containers do not interfere with each other and to ensure the security of container data. Compared with virtual machine-level virtualization, it is lighter because it does not use kernel-level virtualization, and the creation and launch of services are also faster. However, due to the advantages of the container itself, its security is not as good as that of a virtual machine. Therefore, when container technology is introduced, it also brings security risks to the container itself, including container image risks, container operation risks, container network risks, and environmental risks of the host machine.

[0055] This embodiment can use commonly used image scanning tools such as Trivy and Clair, as well as container abnormal behavior monitoring tools such as Falco, to perform real-time monitoring of container security; the overall risk level is divided into three levels: high, medium and low. The risk rating is based on the monitoring results combined with the server security level to comprehensively rate the risk, increase the weighted influence of high-security level servers on the risk rating, and further improve the risk level of high-security level servers.

[0056] As an optional implementation method of this embodiment, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0057] In this optional implementation, reference Figure 3 , real-time monitoring of the platform's containers, and risk alert notifications to stakeholders for quick response in the event of security risks. Different measures are taken for different levels of risks. For medium and high-level risks, automated two-way traffic blocking is performed to prevent further expansion of risks.

[0058] In addition to conventional danger warnings, for medium and high-level risks, with the help of IP tables rules, a two-way blocking method at the container level and server level is completed, that is, in addition to cutting off the inlet and outlet traffic of the risk container / the server node where the risk container is located, other normal containers / the server node where the normal container is located also refuse the access of the risk container / the container on the server node where the risk container is located, to prevent the risk from further expanding. Server isolation, container isolation or alarm processing are achieved.

[0059] According to an embodiment of the present disclosure, a method for implementing flow control processing is also provided to obtain container security monitoring results, wherein the security monitoring results include the presence or absence of vulnerability risks, and when there is a vulnerability risk, the vulnerability risk includes a high risk level, a medium risk level and a low risk level; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, wherein the servers in the server resource pool are divided into security levels using a preset strategy, the resource subpool level corresponding to the server with a high security level is high, the resource subpool level corresponding to the server with a medium security level is medium, and the resource subpool level corresponding to the server with a low security level is low; different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

[0060] As an optional implementation method of this embodiment, different flow control processing is performed based on different vulnerability risk levels and different security levels of the server, including: if the security level of the server is a high security level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the server is isolated; if the security level of the server is a medium security level and the vulnerability risk level is a low risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a medium risk level or a high risk level, an alarm is issued and the container is isolated; if the security level of the server is a low security level and the vulnerability risk level is a low risk level, an alarm is issued.

[0061] refer to Figure 3, we use the commonly used security tools in the industry to monitor container security, and perform risk rating based on the monitoring results. Since the severity of security risks in servers with high security levels is higher than that of servers with other levels, the impact of server security levels on ratings is increased compared to conventional risk ratings. Subsequently, for different risk ratings, in addition to conventional risk warnings, we adopted a two-way blocking method at the container and server levels for medium and high-level risks.

[0062] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A container scheduling method, characterized in that: include: The servers in the server resource pool are divided into security levels using a preset strategy, and servers of different security levels are classified into different resource sub-pools, wherein the resource sub-pool level corresponding to the server of high security level is high, the resource sub-pool level corresponding to the server of medium security level is medium, and the resource sub-pool level corresponding to the server of low security level is low; Based on the preset classification rules, the confidentiality level of different business services is divided, and the core degree of business services is divided; Based on the confidentiality level of different business services and the core degree of different businesses, different business services are matched to different resource sub-pools.

2. The container scheduling method according to claim 1, characterized in that: After servers of different security levels are classified into different resource sub-pools, the method further performs flow control on the resource sub-pools, including: Enable servers in the same resource sub-pool to access each other; Among resource sub-pools of different levels, servers in a resource sub-pool with a high security level can access servers in a resource sub-pool with a low security level; and servers in a resource sub-pool with a low security level cannot access servers in a resource sub-pool with a high security level.

3. The container scheduling method according to claim 1, characterized in that: Based on the confidentiality level of different business services and the core degree of different businesses, different business services are matched to different resource sub-pools, including: Business services with high confidentiality levels are preferentially deployed to resource sub-pools with high security levels; Business services with low confidentiality levels are preferentially deployed to resource sub-pools with low security levels; When the resources in the resource sub-pool with a high security level are insufficient, the business services with a high security level are cross-deployed to the resource sub-pool with a low security level.

4. The container scheduling method according to claim 3 is characterized in that: Based on the confidentiality level of different business services and the core degree of different businesses, different business services are matched to different resource sub-pools, including: Core business services with high coreness are preferentially deployed to resource sub-pools with high security levels; Edge business services with low core value are preferentially deployed to resource sub-pools with low security levels; When the resources in the resource sub-pool with a high security level are insufficient, the core services are deployed across levels to the resource sub-pool with a low security level.

5. The container scheduling method according to claim 1, characterized in that: The confidentiality levels of different business services are divided based on preset classification rules, including: classification based on data sensitivity, business importance and potential security risks.

6. The container scheduling method according to claim 5, characterized in that: The core degree of business services is divided into the following categories: core degree of business services is divided according to business importance, the degree of dependence on system functions, and the relationship between services.

7. A method for implementing flow control processing based on a resource pool obtained by scheduling according to any one of claims 1 to 6, characterized in that: include: Obtaining a container security monitoring result, wherein the security monitoring result includes whether a vulnerability risk exists or not, and when a vulnerability risk exists, the vulnerability risk includes a high risk level, a medium risk level, and a low risk level; Different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

8. The method for flow control processing according to claim 7, characterized in that: Different flow control processes are performed based on different vulnerability risk levels and different security levels of the server, including: If the security level of the server is high, an alarm will be issued and the server will be isolated; If the server's security level is medium security level, and the vulnerability risk level is medium risk level or high risk level, an alarm will be issued and the server will be isolated; If the server's security level is medium and the vulnerability risk level is low, an alarm will be issued and the container will be isolated. If the server's security level is low, and the vulnerability risk level is medium or high, an alarm will be issued and the container will be isolated. If the server's security level is low and the vulnerability risk level is low, an alarm will be issued.

9. A method for implementing flow control processing, characterized in that: Obtaining a container security monitoring result, wherein the security monitoring result includes whether a vulnerability risk exists or not, and when a vulnerability risk exists, the vulnerability risk includes a high risk level, a medium risk level, and a low risk level; Different flow control processing is performed based on different vulnerability risk levels and different security levels of servers. Among them, the servers in the server resource pool are divided into security levels using preset policies. The resource sub-pool level corresponding to the server with a high security level is high, the resource sub-pool level corresponding to the server with a medium security level is medium, and the resource sub-pool level corresponding to the server with a low security level is low; Different flow control processing is performed based on different vulnerability risk levels and different security levels of the server.

10. The flow control processing method according to claim 9, characterized in that: Different flow control processes are performed based on different vulnerability risk levels and different security levels of the server, including: If the security level of the server is high, an alarm will be issued and the server will be isolated; If the server's security level is medium security level, and the vulnerability risk level is medium risk level or high risk level, an alarm will be issued and the server will be isolated; If the server's security level is medium and the vulnerability risk level is low, an alarm will be issued and the container will be isolated. If the server's security level is low, and the vulnerability risk level is medium or high, an alarm will be issued and the container will be isolated. If the server's security level is low and the vulnerability risk level is low, an alarm will be issued.

Citation Information

Patent Citations

  • Method and system for deploying services

    CN103428241A

  • Computing pool application method, computing pool application system, cloud management platform, server and authentication platform

    CN105430008A

  • System for parallel access of high-security-level network to low-security-level network

    CN110381040A

  • Network security event processing method

    CN112383503A

  • AI-based server integrated management cloud platform system and management method

    CN116166751A

Cited By

  • Application deployment isolation method and system applied to container cloud scene and medium

    CN119254539A

  • Application Deployment Isolation Method, System and Medium for Container Cloud Scenarios

    CN119254539B

  • Information processing method and device for ensuring safety of operation container environment

    CN119885210A

  • User-oriented multi-tenant security enhancement service isolation system

    CN120151065A