There are two common configuration modes in modern cloud computing architectures without server (Serverless) and containers. They have some common points and differences in terms of security. The following is

　　Both servers and containers belong to the two types of configuration modes in the modern cloud computing architecture. In terms of security, the two have some common points and differences. The specifics are as follows:

　　No server security understanding:

　　Reduce the attack surface

　　Temporary computing environment is usually used when no server architecture, which helps reduce the attack surface on the server because the server will automatically close after the request is completed.

　　Automatic scaling

　　The server -free architecture can automatically expand and shrink according to the load, which helps prevent overload attacks.

　　Certification and authorization

　　Ensure that the access to the server -free function is appropriately verified and authorized, and prevents unauthorized access.

　　Function isolation

　　Each serviceless function should be isolated from each other, and the security vulnerability of a function affects other functions.

　　Audit and monitoring

　　Real -time monitoring and auditing activities without server applications, discover abnormal behaviors in time.

　　Protect environment variables

　　Make sure that sensitive information (such as API key and invoices) will not be exposed to no server functions.

　　Knowledge of container safety:

　　Mirror safety

　　Ensure that the container image is verified and safe, avoid using unwanted or unclear mirrors.

　　Container isolation

　　There should be enough isolation between the containers to prevent improper containers from affecting others.

　　Minimum authority

　　The container should run with minimized permissions, and the container avoids excess permissions.

　　Continuous monitoring

　　Continuous monitoring of the container environment, detect abnormal activities and respond in time.

　　Network isolation

　　Control the communication between containers and containers and external networks to reduce the risk of horizontal attacks.

　　Patch management

　　Update the software in the container and the container to repair the known security loopholes.

　　There is no server and container in common

　　Audit and monitoring

　　Real -time monitoring and audit of the server -free and container environment discovered potential security threats.

　　Safety Training

　　Training developers and operation and maintenance teams allow them to understand the risks of the best practice and security loopholes.

　　Persistent safety

　　Throughout the development of the life cycle, pay attention to continuous security, and continuously test and repair safety.

　　Taken together, no server and container have their own advantages and disadvantages. In the choice of the two, many factors need to be considered, such as application code, infrastructure, network, and data. Safety is also continuously updated and optimized, and the latest security defense technology must be used in time to ensure its safety.