Question 170
In a Fortinet troubleshooting exercise, FortiSASE cloud security logs show a blocked private application even though the user is in the correct identity group. Which interpretation best fits the evidence?
Explanation
Correct Answer
The best diagnosis is: Private access can require matching identity, posture, application and routing controls. The subsequent targeted action is: Correlate SPA authorization decision with device tag and private app policy. A passing acceptance test shows: Only the approved compliant user reaches the designated private service.
Incorrect Answers
This alternative addresses the separate case “A user sees the right SASE portal but cannot access a SaaS platform after an identity provider signs assertions for a different audience”. The condition is explained by the following rule: SaaS SSO federation needs accurate relying-party audience and trusted issuer context. The deciding requirement here is “Private access can require matching identity, posture, application and routing controls”.
The option would apply to “FortiSASE logs show blocked uploads but the administrator cannot tell whether web filtering or data loss prevention caused the result”. The technical interpretation follows from: Security services have distinct decision records and enforcement criteria. This question instead requires “Private access can require matching identity, posture, application and routing controls”.
This is a nearby Fortinet issue, not the current one. It deals with a remote user can resolve a private application name but TCP connections time out despite successful SASE authentication. The correct answer to the stated case is: Private access can require matching identity, posture, application and routing controls.