Question 500
A risk review at a retail network focuses on preventing this issue again: A FortiSASE monthly report shows no events for one region because the analyst used the wrong user-group filter rather than the region's identity cohort. Which recurring control is most suitable?
Explanation
Correct Answer
Review intended population and filter settings before sharing compliance reports. This control reduces recurrence of the documented mechanism: Report scope filters can suppress valid events without a telemetry outage. It creates a repeatable check around the needed response: Correct the report group and time filters to include the intended protected users.
Incorrect Answers
Reconcile aggregate report totals to source logs during report template approval. That safeguard addresses another potential failure: A weekly report labels a user as the top bandwidth consumer but totals its sessions twice because overlapping traffic report categories were combined. It is not the most targeted recurring control for the described cause: Report scope filters can suppress valid events without a telemetry outage.
Review custom report definitions after major SASE policy changes. That safeguard addresses another potential failure: A scheduled report continues showing outdated policy category names after a FortiSASE rule restructuring, confusing auditors despite accurate event counts. It is not the most targeted recurring control for the described cause: Report scope filters can suppress valid events without a telemetry outage.
Review report destinations and recipients at every operations staffing change. That safeguard addresses another potential failure: A scheduled SOC summary is not delivered because its email recipient list still points to an abandoned security distribution mailbox. It is not the most targeted recurring control for the described cause: Report scope filters can suppress valid events without a telemetry outage.