SSCP Access Controls Practice Question
A company is implementing a Single Sign-On (SSO) solution that uses XML-based assertions to exchange authentication and authorization data between an identity provider and a service provider. Which protocol is being used?
⚠ Common exam trap
The trap is confusing SAML with OAuth or OIDC, especially since all are used for SSO, but only SAML uses XML assertions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
SAML
SAML (Security Assertion Markup Language) is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). It uses XML assertions to convey user identity and attributes, making it the correct protocol for this scenario.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Kerberos
Why it's wrong here
Kerberos issues binary tickets over TCP/UDP, not XML assertions, so it cannot exchange the described SAML-style data between identity and service providers. It is tempting because Kerberos is a genuine SSO protocol, and would be correct for Windows domain single sign-on using a Key Distribution Centre and ticket-granting tickets.
- ✓
SAML
Why this is correct
SAML exchanges authentication and authorisation data as XML assertions between an identity provider and a service provider, exactly the flow described. Its assertion-based, XML-encoded token format is the defining characteristic distinguishing it from other SSO protocols.
- ✗
OAuth 2.0
Why it's wrong here
OAuth 2.0 conveys authorisation as JSON access tokens over HTTPS, not XML assertions, and delegates access rather than authenticating the user to the service provider. It is tempting because OAuth 2.0 underpins many SSO deployments, and would be correct when an application needs delegated API access without asserting user identity.
- ✗
OpenID Connect
Why it's wrong here
OpenID Connect carries identity data as signed JSON Web Tokens over REST, not XML assertions, so it does not match the described exchange. It is tempting because OpenID Connect is a genuine SSO protocol layered on OAuth 2.0, and would be correct for modern web or mobile single sign-on using JWT ID tokens.
Go deeper
Related to this question
About these practice questions
One of 971 original SSCP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISC2 exam blueprint
This SSCP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSCP exam.