Question 760
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A business applies a generic application control profile but SaaS file-sharing actions need different treatment for uploads and downloads. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a business applies a generic application control profile but SaaS file-sharing actions need different treatment for uploads and downloads. The relevant technical mechanism is: Identifying a SaaS application is not identical to controlling every user action within it. The most direct diagnostic or implementation action is: Use supported application or inline CASB controls scoped to the sanctioned SaaS activity. A useful verification is: Allowed viewing remains available while a prohibited upload action is blocked or logged as configured. An ongoing safeguard is: Regression-test critical SaaS activities when control signatures change. This is the INTENDED choice for the most useful ongoing preventive control. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
That safeguard is relevant to: Cloud activity controls require action-specific verification beyond generic network reachability. The current failure instead follows from: Identifying a SaaS application is not identical to controlling every user action within it. Its prevention measure is “Regression-test critical SaaS activities when control signatures change”.
The suggested review tracks a different technical risk: Detection and blocking are distinct configured actions rather than interchangeable outcomes. Here the sustained control must address: Identifying a SaaS application is not identical to controlling every user action within it. Choose “Regression-test critical SaaS activities when control signatures change”.
That safeguard is relevant to: Agentless identity verification does not inherently establish device compliance at managed-agent depth. The current failure instead follows from: Identifying a SaaS application is not identical to controlling every user action within it. Its prevention measure is “Regression-test critical SaaS activities when control signatures change”.