Question 360
During a post-incident review at a logistics office, the original problem was: Cloud security events show successful login attempts from an unexpected country, yet the team closes the case because no web filter block occurred. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Include identity events and location anomalies in FortiSASE threat hunting. This control reduces recurrence of the documented mechanism: Login anomalies can matter independently of content filtering categories. It creates a repeatable check around the needed response: Correlate authentication events, geolocation policy and session access outcomes for the affected identity.
Incorrect Answers
Require profile type and disposition fields in threat case triage. That safeguard addresses another potential failure: An SOC receives a FortiSASE Web Filter log for a blocked phishing category but labels it as an antivirus malware detection. It is not the most targeted recurring control for the described cause: Login anomalies can matter independently of content filtering categories.
Retain user/device attribution and response fields for cloud malware detections. That safeguard addresses another potential failure: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. It is not the most targeted recurring control for the described cause: Login anomalies can matter independently of content filtering categories.
Require endpoint confirmation before escalating download detections to executed-malware claims. That safeguard addresses another potential failure: A FortiSASE report lists an endpoint as risky after a prohibited download, but response staff cannot determine whether the antivirus engine blocked the file before execution. It is not the most targeted recurring control for the described cause: Login anomalies can matter independently of content filtering categories.