Question 420
At fictional Cedar Stores, an endpoint security engineer responsible for retail workstations is reviewing EMS architecture, operating-system support and server management during a managed endpoint onboarding exercise (FCT-7.4-1.1-105). The observed endpoint management issue is: An analyst believes endpoint security posture tags are manually edited device names rather than evaluated endpoint state attributes. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to include positive and negative endpoint posture test cases whenever tag rules change. It mitigates the actual failure: An analyst believes endpoint security posture tags are manually edited device names rather than evaluated endpoint state attributes. A suitable correction is to configure appropriate EMS security posture rules and inspect the resulting dynamic device classification; its proof is that a compliant endpoint receives a matching posture tag while an endpoint missing the required attribute does not.
Incorrect Answers
“Test roaming registration from controlled external networks and check published management service exposure” checks a different ongoing risk rather than the reported failure: an analyst believes endpoint security posture tags are manually edited device names rather than evaluated endpoint state attributes. The relevant mechanism is posture tag membership can reflect evaluated endpoint conditions and can drive integrated security decisions. The directly matched preventive control is “Include positive and negative endpoint posture test cases whenever tag rules change”.
“Review FortiCloud ownership, backup administrators and license access during quarterly checks” checks a different ongoing risk rather than the reported failure: an analyst believes endpoint security posture tags are manually edited device names rather than evaluated endpoint state attributes. The relevant mechanism is posture tag membership can reflect evaluated endpoint conditions and can drive integrated security decisions. The directly matched preventive control is “Include positive and negative endpoint posture test cases whenever tag rules change”.
“Attach entitlement and feature matrix to each EMS architecture decision” checks a different ongoing risk rather than the reported failure: an analyst believes endpoint security posture tags are manually edited device names rather than evaluated endpoint state attributes. The relevant mechanism is posture tag membership can reflect evaluated endpoint conditions and can drive integrated security decisions. The directly matched preventive control is “Include positive and negative endpoint posture test cases whenever tag rules change”.