A security team wants to configure scheduled reports in CrowdStrike to track cloud security risks and compliance over time. Which of the following is a requirement for successfully setting up and using scheduled reports?

Configuring a scheduled report in the CrowdStrike Falcon platform is a multi-step process that requires specific parameters to be defined for it to function correctly. The user must select a report template that defines the data source (e.g., cloud security posture, detections), establish a time frame for the data to be included, set a recurring schedule (e.g., daily, weekly), and specify the delivery method, which typically involves designating email recipients and the report format (e.g., PDF, CSV). These configuration steps are mandatory to ensure the automated generation and delivery of relevant and timely reports for tracking security risks and compliance.

B. Permissions for reports are managed via Role-Based Access Control (RBAC); specific roles, not only full administrators, can be granted privileges to configure or receive reports.
C. The scheduled reports feature is designed for visibility and analysis. It provides data on security posture but does not perform any automated mitigation or remediation actions.
D. This statement describes manual, on-demand reporting. The primary purpose of the "scheduled reports" feature is to automate report generation, eliminating the need for manual intervention.

1. CrowdStrike Falcon® Platform Documentation: Investigate and Respond, Reports. This official documentation details the process for creating and scheduling reports. It explicitly outlines the required configuration steps, including selecting a report type, setting a schedule and time range, and configuring delivery options such as recipients and format. The guide confirms that these settings are essential for the feature's operation.

2. CrowdStrike Falcon® Platform Documentation: User Management, Managing Roles and Users. This section explains the Falcon platform's RBAC model. It specifies that permissions, including those for creating, viewing, and managing reports, can be assigned to various user roles, demonstrating that access is not limited solely to users with full administrative privileges. For instance, a custom role can be created with only reporting permissions.