Question 180
A risk review at a distributed branch estate focuses on preventing this issue again: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. Which recurring control is most suitable?
Explanation
Correct Answer
Require application and temporal context before escalating bandwidth anomalies as threats. This control reduces recurrence of the documented mechanism: High traffic volume alone does not prove a security incident. It creates a repeatable check around the needed response: Drill down to the relevant user, application, source, destination and session details before attributing the traffic.
Incorrect Answers
Maintain per-member utilization dashboards with cost thresholds. That safeguard addresses another potential failure: An operations dashboard shows an unexpected surge on cellular backup but a report aggregates all WAN members, obscuring the affected interface. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.
Monitor NTP drift and preserve timezone metadata in security log analysis. That safeguard addresses another potential failure: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.
Review link saturation metrics and health-check measurements in combined WAN performance reports. That safeguard addresses another potential failure: A branch link becomes congested yet a report labels all sessions as normal because the dashboard tracks bytes and not interface drops or SLA degradation. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.