Question 510
At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing FortiGate integration, posture tags, ZTNA and containment during a security policy acceptance test (FCT-7.4-3.3-128). The observed endpoint management issue is: A company enables user identity checks but uses no endpoint posture condition for a high-risk finance application. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to test user-versus-device condition combinations before publishing finance access. It mitigates the actual failure: A company enables user identity checks but uses no endpoint posture condition for a high-risk finance application. A suitable correction is to combine the applicable user authentication and managed endpoint posture conditions in authorized ZTNA policy; its proof is that only the intended user on a compliant device can access the protected finance service.
Incorrect Answers
“Revalidate tagging conditions against the organization's current endpoint protection requirements” checks a different ongoing risk rather than the reported failure: a company enables user identity checks but uses no endpoint posture condition for a high-risk finance application. The relevant mechanism is identity and device trust are complementary access signals rather than interchangeable checks. The directly matched preventive control is “Test user-versus-device condition combinations before publishing finance access”.
“Include bypass-route checks and protected FQDN tests in ZTNA acceptance” checks a different ongoing risk rather than the reported failure: a company enables user identity checks but uses no endpoint posture condition for a high-risk finance application. The relevant mechanism is identity and device trust are complementary access signals rather than interchangeable checks. The directly matched preventive control is “Test user-versus-device condition combinations before publishing finance access”.
“Keep a validated component responsibility and data-flow diagram for incident operations” checks a different ongoing risk rather than the reported failure: a company enables user identity checks but uses no endpoint posture condition for a high-risk finance application. The relevant mechanism is identity and device trust are complementary access signals rather than interchangeable checks. The directly matched preventive control is “Test user-versus-device condition combinations before publishing finance access”.