Which of the following steps is required to successfully integrate the Falcon CWPP Image Scanning Script with a CI/CD pipeline for image assessment?

Question

Options

• AModify the pipeline script to execute the Image Scanning Script during the post-deployment phase.
• BInstall the Falcon CWPP agent on all developer machines.
• CSchedule the script to run daily on the production environment's container images.
• DUse the Falcon API to fetch a unique API token and store it in the pipeline configuration file.

• A
  3% (1)
• B
  3% (1)
• C
  10% (3)
• D
  83% (25)

Explanation

Option A: Image scanning should occur before deployment to identify vulnerabilities early in the development lifecycle. Running the script post-deployment defeats the purpose of proactive security measures. Option B: While the Falcon CWPP agent is part of the larger CrowdStrike solution, it is not required for the Image Scanning Script's integration into a CI/CD pipeline. The scanning process is executed during pipeline stages and doesn't depend on agents on developer machines. Option C: Image assessments should be part of the CI/CD pipeline to detect vulnerabilities during development. Running scans on production images introduces unnecessary risk and is not the intended use case of the Image Scanning Script. Option D: To authenticate the Image Scanning Script with the Falcon platform, a unique API token is required. This token allows secure communication between the CI/CD pipeline and the Falcon API, enabling image assessments to occur seamlessly. Failure to include this step results in authentication issues, causing the script to fail.

No community discussion yet for this question.