A valid and recommended reason for adding base images into Falcon Cloud Security is toreduce duplicate findings when a base image is used multiple times. Base images are commonly shared across many application images, meaning vulnerabilities, secrets, or detections present in the base layer can appear repeatedly across derived images.
By onboarding base images directly into Falcon Cloud Security, the platform can more efficiently track and correlate vulnerabilities at their source. This allows security teams to remediate issues once at the base image level rather than addressing the same findings across every downstream image. As a result, vulnerability management becomes more accurate, scalable, and operationally efficient.
The other options are incorrect and potentially dangerous assumptions. Base image CVEscan absolutely be exploitedby adversaries, and base image vulnerabilities are not inherently less risky than other CVEs. In many cases, unpatched base images are a primary attack vector in containerized environments.
CrowdStrike’s container image strategy emphasizes reducing noise, improving prioritization, and enabling faster remediation. Adding base images supports these goals by minimizing duplicate alerts and providing clearer insight into risk inheritance across image hierarchies. Therefore, the correct answer isReduce duplicates when a base image is used multiple times.
