Question 70
At fictional Cedar Stores, an endpoint security engineer responsible for retail workstations is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.1-018). The observed endpoint management issue is: A workstation fails FortiClient registration after its clock drifts far outside valid certificate times, and support blames user password entry. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to alert on endpoint clock drift and expiring trusted management certificates. It mitigates the actual failure: A workstation fails FortiClient registration after its clock drifts far outside valid certificate times, and support blames user password entry. A suitable correction is to inspect endpoint time synchronization, certificate validity and TLS negotiation before changing user accounts; its proof is that registration succeeds after clock correction while authorized certificate checks remain enabled.
Incorrect Answers
“Document emergency access to EMS host diagnostics under controlled administrator credentials” checks a different ongoing risk rather than the reported failure: a workstation fails FortiClient registration after its clock drifts far outside valid certificate times, and support blames user password entry. The relevant mechanism is tLS authentication can fail due to client time or certificate validity independent of identity credentials. The directly matched preventive control is “Alert on endpoint clock drift and expiring trusted management certificates”.
“Add EMS transport to the documented required-communications acceptance matrix” checks a different ongoing risk rather than the reported failure: a workstation fails FortiClient registration after its clock drifts far outside valid certificate times, and support blames user password entry. The relevant mechanism is tLS authentication can fail due to client time or certificate validity independent of identity credentials. The directly matched preventive control is “Alert on endpoint clock drift and expiring trusted management certificates”.
“Verify deployment tool service-account permissions in a pilot before rollout” checks a different ongoing risk rather than the reported failure: a workstation fails FortiClient registration after its clock drifts far outside valid certificate times, and support blames user password entry. The relevant mechanism is tLS authentication can fail due to client time or certificate validity independent of identity credentials. The directly matched preventive control is “Alert on endpoint clock drift and expiring trusted management certificates”.