Question 30
At Summit Hospitality, an infrastructure review by the guest connectivity group is evaluating hotel staff service applications across a regional resort branch fabric during a regional modernization (FT-E-10-01). The review finds that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. Any correction must respect this operating requirement: guest and staff traffic must use separate security boundaries. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Maintain consistent time sources and user identifiers across logging domains; make it a repeatable part of Summit Hospitality's change assurance (FT-E-10-01). It sustains the corrective action, correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session, and must preserve the requirement that guest and staff traffic must use separate security boundaries.
Incorrect Answers
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. “Retain relevant SLA history and synchronize device clocks; document the result for the next audit cycle” maintains another technical control: Retain relevant SLA history and synchronize device clocks; document the result for the next audit cycle. It does not directly prevent this case’s specific recurrence, for which “Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control” addresses: Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control.
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. The alternative is a useful recurring check for: Maintain incident triage checklists by symptom and log class; use a measured acceptance threshold where relevant. The present failure instead depends on: Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control. The targeted safeguard is “Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control”.
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. “Stage template updates by region with rollback evidence; use a measured acceptance threshold where relevant” maintains another technical control: Stage template updates by region with rollback evidence; use a measured acceptance threshold where relevant. It does not directly prevent this case’s specific recurrence, for which “Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control” addresses: Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control.