Which setting is configurable when editing a Falcon cloud security posture policy?

Question

Options

• AAssigning priority levels to specific misconfiguration rules.
• BActivating Falcon sensors for unmanaged endpoints.
• CEnabling real-time detection for malware in S3 buckets.
• DAdjusting the logging level of cloud provider APIs.

• A
  92% (35)
• C
  3% (1)
• D
  5% (2)

Explanation

Option A: When editing a cloud security posture policy, administrators can assign priority levels or severities (e.g., critical, high, medium, low) to specific rules. This helps in categorizing and addressing misconfigurations based on their impact on security and compliance. Option B: Falcon sensors are activated and managed separately from cloud security posture policies. The policies focus on cloud configuration assessments, not endpoint management. Option C: Falcon cloud security posture policies are focused on misconfigurations and compliance, not real-time malware detection. Real-time malware scanning in S3 buckets would be managed by a separate feature or service. Option D: Cloud provider API logging levels are managed in the respective cloud provider's settings, not within Falcon's cloud security posture policy configurations.

No community discussion yet for this question.