Question 700
An operations group at a manufacturing plant resolved: A scheduled report continues showing outdated policy category names after a FortiSASE rule restructuring, confusing auditors despite accurate event counts. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Review custom report definitions after major SASE policy changes. This control reduces recurrence of the documented mechanism: Report presentation and filter metadata may outlive the policy structure they describe. It creates a repeatable check around the needed response: Update report template labels and filters to match the approved current security policy taxonomy.
Incorrect Answers
Include PoP and user-path dimensions in recurring SASE experience reports. That safeguard addresses another potential failure: A branch performance dashboard claims a cloud PoP is at fault during slow browsing but includes no per-PoP user experience or latency segmentation. It is not the most targeted recurring control for the described cause: Report presentation and filter metadata may outlive the policy structure they describe.
Align report retention and archive requirements with audit lookback obligations. That safeguard addresses another potential failure: A compliance lead assumes the lack of an old web security event in a current report proves it never occurred, despite a shorter log retention period. It is not the most targeted recurring control for the described cause: Report presentation and filter metadata may outlive the policy structure they describe.
Require data source and inclusion criteria notes on every custom report. That safeguard addresses another potential failure: An operator builds a custom report from a filtered set of denied sessions and presents it as total Internet traffic volume for management. It is not the most targeted recurring control for the described cause: Report presentation and filter metadata may outlive the policy structure they describe.