Question 450
At fictional Timberline Services, an endpoint security engineer responsible for contractor fleets is reviewing EMS, endpoint and secure-access troubleshooting during a security policy acceptance test (FCT-7.4-4.2-113). The observed endpoint management issue is: A branch uses security posture tags in FortiGate policy but an endpoint lacks tags after a malware scan and is incorrectly marked compliant. Which corrective engineering action best addresses the specific problem?
Explanation
Correct Answer
The targeted correction is to recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together. The diagnosed issue is: A branch uses security posture tags in FortiGate policy but an endpoint lacks tags after a malware scan and is incorrectly marked compliant. Evidence of success is: Noncompliant test endpoints remain denied until the relevant verified posture requirements are met. The underlying endpoint-security principle is that security access should require positively evaluated current posture, not an assumption from missing events.
Incorrect Answers
“Confirm FortiClient is currently managed and its identity or ZTNA certificate prerequisites are satisfied” would address a different implementation objective; the stated problem is a branch uses security posture tags in FortiGate policy but an endpoint lacks tags after a malware scan and is incorrectly marked compliant. The actual control boundary is security access should require positively evaluated current posture, not an assumption from missing events. The directly responsive action is “Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together”.
“Correct the deployed FortiClient feature set and validate its licensed protection module state” would address a different implementation objective; the stated problem is a branch uses security posture tags in FortiGate policy but an endpoint lacks tags after a malware scan and is incorrectly marked compliant. The actual control boundary is security access should require positively evaluated current posture, not an assumption from missing events. The directly responsive action is “Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together”.
“Correct the EMS registration target in the approved package or onboarding workflow and retry after DNS validation” would address a different implementation objective; the stated problem is a branch uses security posture tags in FortiGate policy but an endpoint lacks tags after a malware scan and is incorrectly marked compliant. The actual control boundary is security access should require positively evaluated current posture, not an assumption from missing events. The directly responsive action is “Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together”.