Question 520
During a post-incident review at a research campus, the original problem was: A weekly report labels a user as the top bandwidth consumer but totals its sessions twice because overlapping traffic report categories were combined. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Reconcile aggregate report totals to source logs during report template approval. This control reduces recurrence of the documented mechanism: Combining overlapping report views can double count a traffic population. It creates a repeatable check around the needed response: Use a supported unique-session or nonoverlapping aggregation basis and re-run the report.
Incorrect Answers
Classify report sensitivity and enforce audience-specific data minimization. That safeguard addresses another potential failure: A FortiSASE report used for an audit exposes individual browsing URLs to a broad executive distribution although the approved report should contain aggregates only. It is not the most targeted recurring control for the described cause: Combining overlapping report views can double count a traffic population.
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: Combining overlapping report views can double count a traffic population.
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: Combining overlapping report views can double count a traffic population.