Question 500
In the following Fortinet incident—FortiSASE threat logs record a malicious destination but no device context because the endpoint identifier was stripped during export—what concern should the team explicitly mitigate?
Explanation
Correct Answer
That risk should be controlled as part of the approved change. The reason is: Security-event correlation depends on preserving authorized device and user identifiers. The safer action is: Repair the log transformation so required identity attributes are retained safely. Validation: A controlled blocked event can be attributed to the correct managed endpoint.
Incorrect Answers
The option would apply to “A report shows zero DLP violations and management concludes no sensitive uploads are taking place”. This hazard is more relevant than general operational concerns because missing alerts may reflect missing inspection, policy scope or log delivery rather than zero risky behavior. This question instead requires “Stripped metadata can prevent response teams from locating an affected device”.
The related but distinct situation is “The engineering team is reviewing A dashboard reports normal average internet latency but a few sites experience severe packet-loss spikes”. The reason is: Averages can conceal outliers that break application SLAs for individual branches. For the stated problem, “Stripped metadata can prevent response teams from locating an affected device” addresses the central condition.
This option serves the scenario “A security analyst sees an allowed web request in FortiAnalyzer but cannot tell which SD-WAN rule and member carried it”. This is the most direct failure mode to prevent. The present scenario is distinguished by “Stripped metadata can prevent response teams from locating an affected device”.