Question 240
At fictional Vista Research, an endpoint security engineer responsible for research workstations is reviewing FortiGate integration, posture tags, ZTNA and containment during an approved recovery drill (FCT-7.4-3.1-060). The observed endpoint management issue is: A FortiGate security rule references a tag that applies to every device because the EMS posture rule has no restrictive conditions. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to include negative device-posture cases before deploying security-tag firewall policies. It mitigates the actual failure: A FortiGate security rule references a tag that applies to every device because the EMS posture rule has no restrictive conditions. A suitable correction is to tighten the EMS security posture rule to the approved security conditions and verify affected endpoint membership; its proof is that a compliant test endpoint matches the tag while an intentionally noncompliant one does not.
Incorrect Answers
“Verify device identifiers against current IP assignments in quarantine approvals” checks a different ongoing risk rather than the reported failure: a FortiGate security rule references a tag that applies to every device because the EMS posture rule has no restrictive conditions. The relevant mechanism is dynamic authorization depends on correctly defined posture predicates and evaluated attributes. The directly matched preventive control is “Include negative device-posture cases before deploying security-tag firewall policies”.
“Review connector trust after EMS certificate renewals and migrations” checks a different ongoing risk rather than the reported failure: a FortiGate security rule references a tag that applies to every device because the EMS posture rule has no restrictive conditions. The relevant mechanism is dynamic authorization depends on correctly defined posture predicates and evaluated attributes. The directly matched preventive control is “Include negative device-posture cases before deploying security-tag firewall policies”.
“Check endpoint membership on both EMS and FortiGate after tag rule updates” checks a different ongoing risk rather than the reported failure: a FortiGate security rule references a tag that applies to every device because the EMS posture rule has no restrictive conditions. The relevant mechanism is dynamic authorization depends on correctly defined posture predicates and evaluated attributes. The directly matched preventive control is “Include negative device-posture cases before deploying security-tag firewall policies”.