Question 280
During a post-incident review at a research campus, the original problem was: A cloud log shows repeated IPS detections for an untrusted destination, but staff ignore the action field and assume every signature event was blocked. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Review configured IPS actions and resulting event disposition during alert triage. This control reduces recurrence of the documented mechanism: An IPS alert does not itself establish that prevention was enforced. It creates a repeatable check around the needed response: Inspect the matching IPS signature, severity and actual block or monitor disposition for the user session.
Incorrect Answers
Retain authenticated user and SaaS session fields for data-exfiltration investigations. That safeguard addresses another potential failure: A compliance investigation needs to identify which sanctioned SaaS user moved sensitive files, but the SOC looks only at source public IP shared by many remote clients. It is not the most targeted recurring control for the described cause: An IPS alert does not itself establish that prevention was enforced.
Review unusual denied connection bursts prior to allowing new protocols. That safeguard addresses another potential failure: A remote user's FortiSASE log records many denied SSH connection attempts to Internet hosts but a rule-change request asks to permit all SSH to make alerts stop. It is not the most targeted recurring control for the described cause: An IPS alert does not itself establish that prevention was enforced.
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: An IPS alert does not itself establish that prevention was enforced.