CrowdStrike Falcon Cloud Workload Protection (CWP) offers runtime protection for containerized workloads. Which feature or approach best helps identify unassessed images running in production?

Question

Options

• AImage Scanning in Development Pipelines
• BRuntime Inventory of Running Containers
• CIntegration with CI/CD for Build-Time Analysis
• DManual Configuration of Image Repositories

• A
  5% (2)
• B
  82% (32)
• C
  10% (4)
• D
  3% (1)

Explanation

Option A: This option refers to pre-deployment scanning of images in CI/CD pipelines. While important, it doesn't address images that bypass these pipelines and are directly deployed to production without being assessed. Option B: CrowdStrike Falcon provides runtime inventory capabilities, allowing users to identify and monitor container images currently running in production environments. This feature is critical for detecting unassessed or unverified images because it directly analyzes the live runtime environment, bypassing any gaps left during development or build phases. Option C: This focuses on build-time security and does not account for runtime environments. Unassessed images might still appear in production if they are manually deployed or come from external sources. Option D: Manually configuring image repositories might ensure compliance with certain policies, but it doesn't provide real-time visibility into running containers or unassessed images in production environments.

No community discussion yet for this question.