Question 1040
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A branch's security service alerts on a controlled test threat yet the exported SIEM reports a different timestamp, causing poor incident correlation. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a branch's security service alerts on a controlled test threat yet the exported SIEM reports a different timestamp, causing poor incident correlation. The relevant technical mechanism is: Transported log events can be misinterpreted through parser or time conversion errors. The most direct diagnostic or implementation action is: Check log timezone, ingest delay and parsing between FortiSASE and the downstream collector. A useful verification is: Both systems show the event in the same normalized timeline with its source intact. An ongoing safeguard is: Run log format and timestamp regression checks after SIEM updates. This is the INTENDED choice for the most useful ongoing preventive control. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
The suggested review tracks a different technical risk: Threat significance depends on reputation and behavior, not traffic volume alone. Here the sustained control must address: Transported log events can be misinterpreted through parser or time conversion errors. Choose “Run log format and timestamp regression checks after SIEM updates”.
That safeguard is relevant to: Authentication failures alone may reflect typos, travel or malicious guessing. The current failure instead follows from: Transported log events can be misinterpreted through parser or time conversion errors. Its prevention measure is “Run log format and timestamp regression checks after SIEM updates”.
This routine guards against another mechanism: Aggregate reports can summarize trends but not prove instantaneous session conditions. The recurring exposure in the current case is: Transported log events can be misinterpreted through parser or time conversion errors. The matching preventive check is “Run log format and timestamp regression checks after SIEM updates”.