Question 610
At Westmoor Finance, an infrastructure review by the SD-WAN architecture team is evaluating cross-border collaboration across a multinational advisory firm WAN after an audit of cloud access (FT-D-01-02). The review finds that a remote laptop installs FortiClient but never registers in the intended FortiSASE tenant. Any correction must respect this operating requirement: client data respects approved regional egress and retention. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Track unregistered or misassigned endpoint enrollments weekly; make it a repeatable part of Westmoor Finance's change assurance (FT-D-01-02). It sustains the corrective action, provide the approved installer and enrollment assignment including tenant and identity integration, and must preserve the requirement that client data respects approved regional egress and retention.
Incorrect Answers
The source case reports that a remote laptop installs FortiClient but never registers in the intended FortiSASE tenant. That ongoing review concerns: Review source identity and browser restrictions for unmanaged devices; schedule a recorded review after topology changes. The governing risk here is: Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant. Maintain “Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant” as the case-specific check.
The source case reports that a remote laptop installs FortiClient but never registers in the intended FortiSASE tenant. The alternative is a useful recurring check for: Perform canary upgrades and retain a rollback plan; include a negative-authorization regression case. The present failure instead depends on: Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant. The targeted safeguard is “Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant”.
The source case reports that a remote laptop installs FortiClient but never registers in the intended FortiSASE tenant. That ongoing review concerns: Maintain separate test cases for private TCP and UDP use cases; include explicit primary and alternate path tests. The governing risk here is: Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant. Maintain “Track unregistered or misassigned endpoint enrollments weekly; use a measured acceptance threshold where relevant” as the case-specific check.