Question 680
A security analyst investigates this Fortinet environment: The SOC receives a FortiSASE IPS alert for a high-priority signature but cannot find the affected user in the event record. Before changing policy, which diagnostic observation should be collected first?
Explanation
Correct Answer
The first diagnostic step is to inspect source IP, authenticated identity, proxy or tunnel context, application, and policy rule ID. The critical symptom is that the SOC receives a FortiSASE IPS alert for a high-priority signature but cannot find the affected user in the event record. This narrows the failing policy, inspection or management stage before an administrator changes unrelated settings. Once verified, the appropriate next action is to correlate security event fields with user and device records before assigning response ownership; jumping straight to that change without checking the stated evidence increases the chance of a misleading result.
Incorrect Answers
Review event action, file hash or name, matched antivirus profile, and download session status. The check concerns event action, file hash or name, matched antivirus profile, and download session status, not inspecting source IP, authenticated identity, proxy or tunnel context, application, and policy rule ID.
Review event-time device identity, historical user mapping, and current FortiClient registration records. This assesses event-time device identity, historical user mapping, and current FortiClient registration records; it does not determine the reported condition—the SOC receives a FortiSASE IPS alert for a high-priority signature but cannot find the affected user in the event record.
Review event severity, protected asset importance, signature confidence, and correlated sessions. The case-specific requirement is inspecting source IP, authenticated identity, proxy or tunnel context, application, and policy rule ID, which that option does not establish.