Question 260
A risk review at a retail network focuses on preventing this issue again: An SOC receives a FortiSASE Web Filter log for a blocked phishing category but labels it as an antivirus malware detection. Which recurring control is most suitable?
Explanation
Correct Answer
Require profile type and disposition fields in threat case triage. This control reduces recurrence of the documented mechanism: Different FortiSASE security profiles generate different evidence about threats. It creates a repeatable check around the needed response: Classify the event by actual log type, profile, category and action before raising an incident.
Incorrect Answers
Define forensic attribution and privacy requirements before selecting log anonymization settings. That safeguard addresses another potential failure: The SOC receives an external log copy with missing source identities due to anonymization settings and assumes all events came from the same user. It is not the most targeted recurring control for the described cause: Different FortiSASE security profiles generate different evidence about threats.
Require actual DLP enforcement action and session outcome before assigning incident severity. That safeguard addresses another potential failure: A DLP violation is reported for a synthetic payment identifier, but the SOC incorrectly concludes the file was exfiltrated without checking the enforcement action. It is not the most targeted recurring control for the described cause: Different FortiSASE security profiles generate different evidence about threats.
Review configured IPS actions and resulting event disposition during alert triage. That safeguard addresses another potential failure: A cloud log shows repeated IPS detections for an untrusted destination, but staff ignore the action field and assume every signature event was blocked. It is not the most targeted recurring control for the described cause: Different FortiSASE security profiles generate different evidence about threats.