Vulnerability Discussion

The container platform runtime must be carefully monitored for vulnerabilities, and when problems are detected, they must be remediated quickly. A vulnerable runtime exposes all containers it supports, as well as the host itself, to potentially significant risk. Organizations should use tools to look for Common Vulnerabilities and Exposures (CVEs) vulnerabilities in the runtimes deployed, to upgrade any instances at risk, and to ensure that orchestrators only allow deployments to properly maintained runtimes.

Check

Review documentation and configuration to determine if the container platform registry inspects and contains the latest approved vendor repository images containing security-relevant updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

If the container platform registry does not contain the latest image with security-relevant updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs), this is a finding.

The container platform registry should help the user understand from where the code in the environment was deployed and must provide controls that prevent deployment from untrusted sources or registries.

Fix

Configure the container platform registry to use an approved vendor repository to ensure the latest images containing security-relevant updates are installed within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).