Scenario I: Image Security Protection
With container technology being adopted, service containers are started based on images. It is paramount to perceive image security risks and ensure that the service can be launched safely.
Advantages
Strong compatibility: compatible with mainstream image repositories on the market, as well as mainstream operating systems, including domestic image OSs such as localized EulerOS and Kylin.
Comprehensive detection: in-depth detection of security risks such as software components, vulnerabilities, malicious files, software licenses, and sensitive information based on multiple vulnerability sources and virus libraries.
Risk blocking: prevention of risky images from going online based on multiple dimensions such as privileged startup, vulnerabilities, software, files, and environment variables.
Scenario Diagram
Scenario II: Container Security Protection
The container bears the service processes. Once the container is captured or attacked based on service logic, it causes unpredictable risks. For this reason, while enjoying the convenience brought by containers, it is paramount to focus on the security of the container and the service security.
Advantages
Full coverage of all ATT&CK stages: Provide security detection policies in multiple dimensions such as service command execution, file reading and writing, network activities, and host risks. These policies can customized. Cover all stages of ATT&CK to ensure timely detection of risks.
Strong asset/risk linkage: You can view any assets associated with one asset. When a risk is found, the system also provides the attack chain and associated data details to assist in judgment.
Immediate disposing of determined risks: Once a risk is determined, you can isolate, restart, or suspend the container for the risky service container. Then, trace the risk source through historical information.
Scenario Diagram
