How does an administrator secure container environments in Amazon AWS from newly emerged security threats?

Comprehensive and Detailed Explanation From FortiOS 7.6, FortiWeb 7.4 Exact Extract study guide:

According to theFortiOS 7.6 Docker Administration Guideand thePublic Cloud Securitystudy materials, container security is addressed through granular visibility into container-specific protocols.

Application Control for Containers (Option A):FortiOS includes a dedicated set of application control signatures specifically forDocker traffic. These signatures allow the FortiGate-VM to identify and control specific actions within a container environment, such as:

Docker_Pull.Blob / Docker_Pull.Manifest:Identifying when a container image is being pulled from a registry.

Docker_Push.Blob / Docker_Push.Manifest:Monitoring when images are uploaded to a registry.

Enforcing Security Policies:By using these Docker-related signatures, an administrator can create firewall policies that only allow container pulls fromknown clean, private registrieswhile blocking traffic from unauthorized or public registries that may contain vulnerable or malicious images.5

Defense-in-Depth:While traditional network-related signatures (Option C) or AWS-specific infrastructure signatures (Option B) protect the underlying network and cloud services, they do not provide the necessary visibility into theDocker API callsand manifest transfers required to secure the container lifecycle itself. FortiGate further enhances this by scanning the actual payload of these transfers using theIntrusion Prevention Service (IPS)andAdvanced Malware Protection (AMP).