Enabling Container Protection
Scenarios
The HSS container edition protects containers throughout their lifecycles. This section describes how to enable protection for container nodes.
Prerequisites
- HSS can be billed in yearly/monthly or pay-per-use mode. To use yearly/monthly billing, ensure you have purchased sufficient protection quotas. For details, see Purchasing an HSS Quota. If you use the pay-per-use billing mode, you do not need to purchase quotas in advance.
- Ensure that the agent has been installed on the container node and is online. For details about how to install the agent on a single node, see Installing the Agent on Huawei Cloud Servers and Installing the Agent on Third-party Servers. For details about how to install the agent on a cluster, see Installing an Agent in a Cluster.
Constraints
HSS can only protect Docker, Containerd, CRI-O, Podman, and iSulad containers.
Enabling the Container Edition
- Log in to the management console.
- In the upper left corner of the page, select a region, click
, and choose Security & Compliance > Host Security Service.
- In the navigation pane, choose Asset Management > Containers & Quota.
- In the row of a server, click Enable Protection in the Operation column. The confirmation dialog box is displayed.
By default, only the Linux servers where the agent is installed (that is, the servers eligible for the container edition) are displayed in the list. To install the agent on a server, perform the operations in Installing the Agent on Servers and Installing an Agent in a Cluster.Figure 1 Enabling container protection
- Confirm the node information and select a billing mode.
You can buy quota in pay-per-use or yearly/monthly mode.
- Yearly/Monthly
- Billing Mode: Select Yearly/Monthly.
- Select Quota: Select a quota allocation mode.
- Random quota: Let the system allocate the quota with the longest remaining validity to the server.
- Select a quota ID and allocate it to a server.
- Pay-per-use
- Billing Mode: Select Pay-per-use.
- Tags: Select a tag if you want to use it to identify multiple types of cloud resources.
- A container security quota protects one cluster node.
- If the version of the agent installed on the Linux server is 3.2.10 or later or the version of the agent installed on the Windows server is 4.0.22 or later, ransomware prevention is automatically enabled with the container edition. Deploy honeypot files on servers and automatically isolate suspicious encryption processes (there is a low probability that processes are incorrectly isolated). You are also advised to enable backup so that you can restore data in the case of a ransomware attack to minimize losses. For details, see Enabling Ransomware Backup.
- Yearly/Monthly
- Read the Host Security Service Disclaimer and select I have read and agree to the Container Guard Service Disclaimer.
- Click OK. If the Protection Status of the node changes to Protected, protection has been enabled.
Viewing Scan Details
After server protection is enabled, HSS will immediately perform a comprehensive scan on the server. It may take a long time. After the scan is complete, you can check its details.
- Choose Servers tab page. . Locate the server on the
- Check the Risk Level column of the server.
Table 1 Risk status Status
Description
Pending risk detection
The server is neither protected nor scanned.
Safe
No risks were found in the comprehensive scan on the server; or the protection has just been enabled, and no risks have been found yet.
Risky
The server has security risks.
- Hover the cursor over the risk status to view the risk distribution.
You can click a value to go to the details page.
Follow-up Operations
HSS provides container protection functions for you to enable as needed. For more information, see Manual configuration.
Type |
Function |
Reference |
---|---|---|
Security configuration |
|
|
Server Protection |
|
|
Container protection |
|
|
Policy management |
Policy management includes asset management, baseline inspection, intrusion detection, and self-protection policies. The intrusion detection policy is disabled by default. You can enable them as needed. If the configuration of a policy does not meet your requirements, you can modify it as needed. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot