CCCS-203B practice question 33 of 35

A company using CrowdStrike Falcon Cloud Security wants to ensure that all container images deployed in their cloud environment are scanned for vulnerabilities before deployment. Which image assessment policy should they implement?

Full set: 300 questions

Domain Detect and Investigate Cloud Threats

Answer options
A: Enforce pre-deployment scanning to block images with critical vulnerabilities from being deployed. Correct answer
B: Allow all container images to be deployed, regardless of vulnerabilities, but notify administrators if an image contains high-severity vulnerabilities.
C: Only assess images manually when security teams request a scan.
D: Enable post-deployment scanning to assess vulnerabilities after an image has already been running in 2/192 production.
Correct Answer:
A. Enforce pre-deployment scanning to block images with critical vulnerabilities from being deployed.
Explanation

The most effective security posture for containerized environments involves implementing "shift-left" principles, where security is integrated early in the development lifecycle. Enforcing pre-deployment scanning ensures that container images are assessed for vulnerabilities before they are introduced into a production environment. A policy that blocks images with critical vulnerabilities from being deployed is a preventative control that directly addresses the company's requirement to prevent vulnerable images from running, thereby minimizing the attack surface. This is a core function of CrowdStrike Falcon Cloud Security's image assessment capabilities.

Why Incorrect

B. This is a detective control, not a preventative one. It allows a potentially vulnerable image to be deployed, creating a window of risk before administrators can react to the notification.
C. A manual, on-demand process is not scalable or comprehensive. It fails to ensure that all images are scanned systematically, leaving significant gaps in security coverage.
D. Post-deployment scanning assesses vulnerabilities in running containers. While valuable for runtime protection, it is a reactive measure that does not prevent the initial deployment of a vulnerable image.

References

1. CrowdStrike Falcon® Cloud Security Documentation: The official documentation details the configuration of Image Assessment policies. It specifies that policies can be configured to scan images in container registries (pre-deployment) and apply enforcement actions. The "Prevent" action, often integrated with a Kubernetes admission controller, blocks the deployment of images that violate the policy, such as those containing critical vulnerabilities. (Reference: CrowdStrike Falcon Console -> Cloud Security -> Image Assessment -> Policies section).

2. CrowdStrike Technical Documentation, "Image Scanning for Pre-deployment Security": This document outlines the best practice of scanning images stored in a registry before they are deployed. It explains that Falcon policies can be set to "Detect" (alert only) or "Prevent" (block deployment), with the latter being the recommended approach for high-severity vulnerabilities to enforce a secure baseline. (Reference: CrowdStrike Support Portal, Document ID: CS-FS-WP-1023, "Container Security Best Practices", Section 3.1 "Image Scanning").

Scroll to Top