Question 580
A risk review at a financial services branch focuses on preventing this issue again: An investigator generates a cloud report for a specific day but compares it with branch logs in another timezone, creating apparently inconsistent access counts. Which recurring control is most suitable?
Explanation
Correct Answer
Specify timestamps, timezone and cutoffs explicitly for cross-platform reports. This control reduces recurrence of the documented mechanism: Time zone offsets can shift events across reporting day boundaries. It creates a repeatable check around the needed response: Align report and FortiGate log time ranges and timezones to the same absolute interval.
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: Time zone offsets can shift events across reporting day boundaries.
Maintain approved user-attribution data sources and privacy access controls for incident reports. That safeguard addresses another potential failure: A user activity report identifies only egress addresses and application names while investigators require an authorized account-level trace for a confirmed DLP event. It is not the most targeted recurring control for the described cause: Time zone offsets can shift events across reporting day boundaries.
Use report types aligned to the underlying control, not generic bandwidth summaries. That safeguard addresses another potential failure: Managers request a list of users blocked by DLP policy, but the standard Internet traffic summary contains only successful requests. It is not the most targeted recurring control for the described cause: Time zone offsets can shift events across reporting day boundaries.