Study guide
6.3 Federation, SSO, MFA, Passwordless, and Session Management
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
6.3 Federation, SSO, MFA, Passwordless, and Session Management
Key Takeaways Explain This Topic AI
Federation extends trust across organizations and systems, so metadata, claims, keys, and contracts must be governed.
SSO improves usability and central control, but it concentrates risk in the identity provider and session handling.
MFA and passwordless approaches should be selected by phishing resistance, recoverability, user population, and operational fit.
Session management must control token lifetime, revocation, reauthentication, device state, and logout behavior.
Last updated: May 2026
Trust Beyond One Application
Federation allows one identity provider to authenticate a subject and provide assertions or tokens to another system. A workforce user may sign in through a corporate identity provider and access a SaaS application. A customer may use a social or government identity to access a service. A partner may use its own identity system to reach a business portal. The security issue is not only protocol support. It is whether the relying party should trust the identity provider, which claims are accepted, and how trust is monitored.
Single sign-on centralizes authentication so users do not maintain separate passwords for every application. SSO can improve security by reducing password reuse, enabling consistent MFA, and giving security teams one place to disable access. It can also increase impact because a compromised identity provider session may unlock many services. SSO needs strong administration, resilient availability, secure recovery, careful application onboarding, and monitored token use.
Common federation patterns use standards such as SAML for browser-based enterprise assertions, OpenID Connect for identity information built on OAuth 2.0 flows, and OAuth 2.0 for delegated authorization. A CISSP does not need to memorize packet fields to make sound decisions. The key is understanding which party authenticates, which party consumes claims, which scopes or attributes are released, how keys are managed, and how replay or token theft is reduced.
MFA requires more than one type of evidence. A password plus a one-time code is stronger than a password alone, but it may still be vulnerable to phishing or real-time proxy attacks. Push approval can be effective but may suffer from approval fatigue if users are trained to tap accept. Phishing-resistant methods such as FIDO-based security keys or platform passkeys bind authentication to the legitimate site and device in stronger ways.
Passwordless authentication removes the traditional shared secret from the sign-in ceremony. It may use passkeys, smart cards, certificates, device-bound credentials, or cryptographic authenticators. Passwordless can reduce help desk resets and credential stuffing risk, but rollout must address enrollment, device loss, shared workstations, accessibility, recovery, and user populations that cannot use the same devices every day.
Session management controls what happens after authentication. A session token, cookie, refresh token, or access token may remain valid after the original login. If tokens live too long, attackers gain more time to use stolen sessions. If lifetimes are too short, users may create workarounds or suffer productivity loss. Good design ties session duration to sensitivity, device trust, location, user behavior, and transaction risk.
Control area Security decision Good practice
Federation trust Which IdPs and relying parties are trusted? Formal onboarding, signed metadata, key rotation, owner approval
- Claims and scopes What identity data is released? Minimum necessary attributes and documented mapping
- SSO How broad is one login's reach? Strong IdP controls, conditional access, rapid disablement
- MFA What factor strength is needed? Phishing-resistant MFA for privileged and high-risk access
- Sessions How long does trust persist? Shorter lifetimes for sensitive actions and revocation support
Federation failures often appear as business integration problems, but they are governance problems. A SaaS application may request excessive attributes. A partner may not terminate users promptly. A relying party may accept tokens signed with stale keys. An application may map every federated user to a high-privilege default role. The security team should require documented trust agreements, data minimization, test plans, and a way to terminate or suspend trust quickly.
Step-up authentication is a practical way to balance usability and risk. A user may open a low-risk dashboard with an existing session, but changing payroll data, exporting customer records, registering a new MFA device, or granting admin privilege should require fresh authentication. Step-up controls should consider transaction value and potential harm, not just login time. The most sensitive actions may also require approval or dual control.
Recovery is part of authentication strength. If the primary login is phishing resistant but the recovery process only asks for weak knowledge questions, attackers will target recovery. Account recovery should use verified channels, trusted devices, help desk identity proofing, fraud monitoring, and delayed high-risk changes. Recovery events should be logged and reviewed because they are often the point where control strength collapses.
Logout and revocation are also policy decisions. Users expect logout to end access, but distributed applications may keep refresh tokens or downstream sessions alive. The organization should define whether logout is local or global, how quickly token revocation takes effect, and which systems must honor emergency termination. High-risk environments may need continuous access evaluation so changes in user status or device risk affect active sessions.
Federation and Session Review Checklist
Confirm each relying party has a business owner, data owner, and approved trust purpose.
Release only the claims and attributes needed for the application function.
Protect identity provider administration with separate accounts, phishing-resistant MFA, and strong monitoring.
Use stronger MFA and shorter sessions for privileged, remote, regulated, and high-impact actions.
Test account disablement, group removal, token revocation, and logout behavior end to end.
Monitor unusual token use, impossible travel, repeated MFA prompts, and new device enrollment.
The CISSP view is that SSO and federation are not automatically safer. They become safer when trust is explicit, administrative surfaces are protected, claims are minimized, sessions are bounded, and lifecycle events propagate reliably. The business benefit is simplified access, but the security requirement is disciplined control of the trust chain.