Question 340
At fictional Elmstone Transit, an endpoint security engineer responsible for field terminals is reviewing FortiGate integration, posture tags, ZTNA and containment during a supervised production migration (FCT-7.4-3.2-085). The observed endpoint management issue is: A company assumes a FortiClient Web Filter profile alone provides the same device isolation as a formal EMS quarantine action. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to verify the actual containment scope during incident response tabletop and live tests. It mitigates the actual failure: A company assumes a FortiClient Web Filter profile alone provides the same device isolation as a formal EMS quarantine action. A suitable correction is to apply the supported quarantine function when complete endpoint containment is authorized rather than adjusting URL categories; its proof is that test network traffic is restricted according to the quarantine behavior, not merely selected web sites.
Incorrect Answers
“Keep the operating-system quarantine support matrix in incident response runbooks” checks a different ongoing risk rather than the reported failure: a company assumes a FortiClient Web Filter profile alone provides the same device isolation as a formal EMS quarantine action. The relevant mechanism is content filtering limits particular applications while quarantine can restrict the endpoint more broadly. The directly matched preventive control is “Verify the actual containment scope during incident response tabletop and live tests”.
“Include backend service health and route tests when commissioning ZTNA applications” checks a different ongoing risk rather than the reported failure: a company assumes a FortiClient Web Filter profile alone provides the same device isolation as a formal EMS quarantine action. The relevant mechanism is content filtering limits particular applications while quarantine can restrict the endpoint more broadly. The directly matched preventive control is “Verify the actual containment scope during incident response tabletop and live tests”.
“Include negative device-posture cases before deploying security-tag firewall policies” checks a different ongoing risk rather than the reported failure: a company assumes a FortiClient Web Filter profile alone provides the same device isolation as a formal EMS quarantine action. The relevant mechanism is content filtering limits particular applications while quarantine can restrict the endpoint more broadly. The directly matched preventive control is “Verify the actual containment scope during incident response tabletop and live tests”.