Which of the following is not a required step to configure the Falcon CWPP Image Scanning Script for automated vulnerability scanning in a CI/CD pipeline?

Question

Options

• ADefine scanning exclusions based on organization-specific policies.
• BRegister the container registry with the Falcon platform for continuous scanning.
• CInstall the Falcon Image Scanning Script on the CI/CD build server.
• DMap the scanning script's output directory to a shared location in the CI/CD environment.

• A
  14% (6)
• B
  48% (20)
• C
  7% (3)
• D
  31% (13)

Explanation

Option A: Defining exclusions allows organizations to tailor the scan to their unique requirements, ignoring vulnerabilities that are deemed low-risk or acceptable. While optional, this step is commonly implemented for effective vulnerability management. Option B: The Falcon Image Scanning Script does not require you to register the container registry with the Falcon platform for CI/CD pipeline integration. Instead, the script operates by pulling images directly from the registry or receiving image references as input. Continuous registry scanning is a separate feature and not a prerequisite for CI/CD pipeline integration. Option C: Installing the script on the build server is a necessary step to ensure the CI/CD environment can execute scans on container images during the pipeline process. Option D: Mapping the output directory is essential to store scan results and reports where they can be accessed by subsequent pipeline steps or developers for review.

No community discussion yet for this question.