Question 600
In the following Fortinet incident—A user sees the right SASE portal but cannot access a SaaS platform after an identity provider signs assertions for a different audience—what concern should the team explicitly mitigate?
Explanation
Correct Answer
The operational danger arises from this condition: SaaS SSO federation needs accurate relying-party audience and trusted issuer context. The appropriate control is to correct approved SAML assertion audience and service-provider trust mapping; successful evidence is: A valid user signs in to the intended SaaS resource without replaying an assertion elsewhere.
Incorrect Answers
The option would apply to “A security team places a broad allow policy before the intended malware inspection rule in a FortiSASE policy set”. This is the most direct failure mode to prevent. This question instead requires “A wrong SAML audience can cause denials or unsafe trust assumptions”.
The related but distinct situation is “A web policy blocks a new phishing site for FortiClient users but traffic from an agentless proxy user reaches it”. The operational danger arises from this condition: Security policy parity must be validated across different SIA onboarding modes. For the stated problem, “A wrong SAML audience can cause denials or unsafe trust assumptions” addresses the central condition.
This alternative addresses the separate case “A remote employee accesses an internal web app using agentless ZTNA but the proxy exposes a certificate-name mismatch”. The operational danger arises from this condition: Agentless HTTPS private access needs valid proxy TLS identity and suitable application publication. The deciding requirement here is “A wrong SAML audience can cause denials or unsafe trust assumptions”.