CISSP Domain 5: Single Sign-On, Federated Identity & Access Management — Mindmap Review Study Guide
═══════════════════════════════════
PART 1: MERMAID MINDMAP
═══════════════════════════════════
mindmap
root((Domain 5 SSO and FIM))
Single Sign-on SSO
Single set of credentials
Internal applications only
Kerberos Protocol
Authentication via tickets
Symmetric encryption only
User or Client
Key Distribution Center KDC
Authentication Service AS
Ticket Granting Ticket TGT
Ticket Granting Service TGS
Service Tickets
Sesame Protocol
Symmetric and Asymmetric encryption
Solves scalability and key distribution
Federated Identity Management FIM
External and internal applications
Trust Relationship
Principal or User
Identity Provider IdP
Active Directory
Relying Party or Service Provider SP
SaaS applications
SAML Protocol
Security Assertion Markup Language
Tokens instead of tickets
Assertions written in XML
Extensible Markup Language
Profiles
Bindings
Protocol component
Assertion component
Other Federated Protocols
WS-Federation Protocol
OpenID Protocol
OAuth Protocol
═══════════════════════════════════
PART 2: TECHNICAL DEFINITIONS & CONCEPTS
═══════════════════════════════════
Single Sign-on SSO
Single Sign-on (SSO) — Allows users to access multiple systems with a single set of credentials, authenticating once to access all applications. It is designed to work strictly within one organization for internal applications.
Federated Identity Management (FIM) / Federated Access — Allows users to access both internal and externally managed applications (e.g., cloud SaaS) using a single set of credentials. It looks identical to SSO from the user’s perspective but extends across organizational boundaries.
Comparison: SSO vs. FIM
| Feature | Single Sign-on (SSO) | Federated Identity Management (FIM) |
|---|---|---|
| Scope | Internal applications only | Internal and externally managed applications |
| Example Use | Internal corporate systems | Cloud SaaS applications |
Kerberos Protocol
Kerberos — A major protocol enabling Single Sign-on that provides authentication via tickets over an insecure network. By default, it only supports symmetric key cryptography.
User / Client — The individual who wants to gain access to services through the Kerberos protocol.
Key Distribution Center (KDC) — The core component of Kerberos that contains both the Authentication Service and the Ticket Granting Service.
Authentication Service (AS) — A component within the KDC that verifies a user exists. If valid, it sends the user two tickets, one of which is the Ticket Granting Ticket (TGT).
Ticket Granting Ticket (TGT) — A ticket issued by the Authentication Service. It is passed to the Ticket Granting Service along with messages indicating which service the client wants to access.
Ticket Granting Service (TGS) — A component within the KDC that verifies the requested service exists and that the user is authorized to access it. If valid, it creates and sends a Service Ticket to the user.
Service Tickets — The final ticket sent by the user to an application to gain access. The user caches this ticket for future access while it remains valid and unexpired.
Symmetric Key Cryptography Limitation — Kerberos relies exclusively on symmetric encryption by default. This creates significant limitations regarding scalability and key distribution, as many symmetric keys must be securely distributed among components.
Comparison: Kerberos vs. Sesame
| Feature | Kerberos | Sesame |
|---|---|---|
| Encryption Types | Symmetric encryption only | Supports both symmetric and asymmetric encryption |
| Key Distribution | Requires secure distribution of many symmetric keys | Solves key distribution problems via asymmetric encryption |
| Scalability | Limited by symmetric key management | Solves scalability issues |
Sesame Protocol
Sesame — A protocol that supports both symmetric and asymmetric cryptography. It was designed to solve the major symmetric key cryptography problems found in Kerberos, specifically scalability and key distribution.
Federated Identity Management FIM
Trust Relationship — The foundational concept of federated access relying on trust between three entities: the user, the identity provider, and the service provider. The service provider must trust the authentication performed by the identity provider in order to authorize the user to access the service.
Principal / User — The individual seeking access to the service in a federated identity relationship.
Identity Provider (IdP) — The entity that authenticates the user and verifies their identity via knowledge, ownership, or characteristic. In many organizations, this is implemented using Active Directory.
Relying Party / Service Provider (SP) — The application or service the user wants to access. It is often owned and managed by a third-party vendor rather than the user’s organization (e.g., SaaS applications for helpdesk, travel, or expenses).
Comparison: Identity Provider vs. Service Provider
| Entity | Primary Role | Typical Ownership / Example |
|---|---|---|
| Identity Provider (IdP) | Authenticates the user via knowledge, ownership, or characteristic | Often internal (e.g., Active Directory) |
| Relying Party / Service Provider (SP) | The application the user wants to access | Often external/vendor-owned (e.g., SaaS apps) |
SAML Protocol
SAML (Security Assertion Markup Language) — The major protocol enabling Federated Access. It functions similarly to Kerberos by using tokens instead of tickets to grant access.
⚠️ EXAM TIP: SAML is explicitly called out as the major federated access protocol you need to know for the exam.
Tokens — The SAML equivalent of Kerberos tickets. They contain assertion statements that grant access to services.
Assertions / Assertion Statements — Statements contained within a SAML token that include details such as the user ID, Service ID, timestamp, and lifetime of the token.
XML (Extensible Markup Language) — The markup language used to write the assertion statements contained within SAML tokens.
Profiles — A SAML component that defines how SAML can be used for different business use cases, such as Web single sign-on or through LDAP.
Bindings — A SAML component that maps SAML onto different communication protocols (e.g., HTTP), allowing it to communicate across different types of networks.
Protocol — A SAML component that defines how entities send and respond to requests.
Assertion — A SAML component that defines the authentication, authorization, and other such attributes.
Other Federated Protocols
WS-Federation — A federated access protocol that provides both Authentication and Authorization capabilities.
OpenID — A federated access protocol that provides Authentication capabilities only.
OAuth — A federated access protocol that provides Authorization capabilities only.
⚠️ EXAM TIP: You must recognize WS-Federation, OpenID, and OAuth, specifically knowing which provides Authentication vs. Authorization, as they are commonly confused.
Comparison: Federated Access Protocols
| Protocol | Authentication | Authorization |
|---|---|---|
| WS-Federation | Yes | Yes |
| OpenID | Yes | No |
| OAuth | No | Yes |