Question 320
Original unofficial Palo Alto Networks NetSec-Architect scenario: A contractor group uses cloud single sign-on but network policy sees anonymous sessions because SAML and identity mapping were designed independently. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A contractor group uses cloud single sign-on but network policy sees anonymous sessions because SAML and identity mapping were designed independently. Governing principle: Successful login does not guarantee the enforcement layer received a usable user mapping. The most defensible design response is: Coordinate SAML assertion attributes, authenticated principal formats, and downstream User-ID mapping. Validation: The access log ties the federated session to the intended contractor identity and policy group. Sustained assurance: Regression-test attribute changes from the identity provider
Incorrect Answers
“Review break-glass use and rotate credentials immediately after each activation.” concerns the separate design topic: recommend user identification and authentication methods including saml. It would not fix the described weakness: a contractor group uses cloud single sign-on but network policy sees anonymous sessions because SAML and identity mapping were designed independently. Successful login does not guarantee the enforcement layer received a usable user mapping.
This alternative is linked to the architecture category: architect strata cloud manager, strata logging service and cloud identity engine. The actual problem is that a contractor group uses cloud single sign-on but network policy sees anonymous sessions because SAML and identity mapping were designed independently; the controlling distinction is: successful login does not guarantee the enforcement layer received a usable user mapping.
The proposed design “Recertify external identity group scope at contract expiration.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that a contractor group uses cloud single sign-on but network policy sees anonymous sessions because SAML and identity mapping were designed independently. Successful login does not guarantee the enforcement layer received a usable user mapping.