A security administrator is configuring pre-runtime protection in CrowdStrike Falcon to ensure that only trusted container images from specific registries are scanned and allowed for deployment. What

Question

Options

• ASet up registry connections using only the default Falcon registry settings without modifications.
• BAdd all public and private container registries without authentication to ensure maximum
• CSpecify the registry URL, enable authentication if required, and configure scanning policies for
• DDisable scanning for images from private repositories since they are already trusted and internally

• A
  5% (1)
• B
  5% (1)
• C
  71% (15)
• D
  19% (4)

Explanation

Option A: Default Falcon registry settings may not cover all organizational needs. Custom configurations should be made to ensure alignment with security policies. Option B: Allowing all registries without authentication increases security risks, as unauthorized or malicious images can be pulled and deployed. Option C: To ensure pre-runtime protection, administrators should define registry connection details, specify the registry URL, enable authentication (if needed), and set image scanning policies for security compliance. Option D: Private repositories are not automatically secure. Vulnerabilities can still exist in private images, making it critical to enable scanning even for internal sources.

No community discussion yet for this question.