Question 320
At Dovetail Commerce, an infrastructure review by the retail security team is evaluating remote checkout and store systems across a multichannel storefront organization during a regional modernization (FT-C-17-02). The review finds that one business application works from a FortiClient user but fails from a branch on-ramp because policies were assumed identical. Any correction must respect this operating requirement: cardholder systems stay behind effective security policy. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Maintain cross-user-type test cases before a shared application launch; make it a repeatable part of Dovetail Commerce's change assurance (FT-C-17-02). It sustains the corrective action, validate identity source network path and service entitlements for each approved user type, and must preserve the requirement that cardholder systems stay behind effective security policy.
Incorrect Answers
The source case reports that one business application works from a FortiClient user but fails from a branch on-ramp because policies were assumed identical. The alternative is a useful recurring check for: Review exception approvals and security impact during resiliency drills; document the result for the next audit cycle. The present failure instead depends on: Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case. The targeted safeguard is “Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case”.
The source case reports that one business application works from a FortiClient user but fails from a branch on-ramp because policies were assumed identical. That ongoing review concerns: Require hub policy signoff when publishing new SPA applications; confirm this in the next branch rollout checklist. The governing risk here is: Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case. Maintain “Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case” as the case-specific check.
The source case reports that one business application works from a FortiClient user but fails from a branch on-ramp because policies were assumed identical. The alternative is a useful recurring check for: Exercise log-delivery failure and recovery for the central collector; use a measured acceptance threshold where relevant. The present failure instead depends on: Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case. The targeted safeguard is “Maintain cross-user-type test cases before a shared application launch; include a negative-authorization regression case”.