Study guide

10.4 Identity & Access Management Solutions (Domain 4.7)

Certified Cloud Security Professional CCSP

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current CCSP Exam Facts 1.2 CAT Format, Scoring & Logistics 1.3 Eligibility, Experience & Certification Maintenance

2 Domain 1: Cloud Concepts & Architecture Foundations

2.1 Cloud Computing Concepts (Domain 1.1) 2.2 Cloud Reference Architecture (Domain 1.2) 2.3 Security Concepts Relevant to Cloud (Domain 1.3)

3 Domain 1: Secure Design, CSP Evaluation & AI/ML

3.1 Design Principles of Secure Cloud Computing (Domain 1.4) 3.2 Evaluate Cloud Service Providers (Domain 1.5) 3.3 AI/ML in Cloud Security (Domain 1.6)

4 Domain 2: Data Concepts, Storage & Protection Technologies

4.1 Cloud Data Concepts (Domain 2.1) 4.2 Cloud Data Storage Architectures (Domain 2.2) 4.3 Data Security Technologies & Strategies (Domain 2.3)

5 Domain 2: Discovery, Classification & Information Rights Management

5.1 Data Discovery (Domain 2.4) 5.2 Data Classification (Domain 2.5) 5.3 Information Rights Management (Domain 2.6)

6 Domain 2: Retention, Auditability & AI/ML Data Protection

6.1 Retention, Deletion & Archiving (Domain 2.7) 6.2 Auditability, Traceability & Accountability (Domain 2.8) 6.3 AI/ML Data Protection (Domain 2.9)

7 Domain 3: Infrastructure Components, Data Center & Risks

7.1 Cloud Infrastructure Components (Domain 3.1) 7.2 Secure Data Center Design (Domain 3.2) 7.3 Infrastructure & Platform Risks (Domain 3.3)

8 Domain 3: Security Controls & Business Continuity / Disaster Recovery

8.1 Security Controls Implementation (Domain 3.4) 8.2 Business Continuity & Disaster Recovery (Domain 3.5)

9 Domain 4: Application Security Awareness & Secure SDLC

9.1 Application Security Training & Awareness (Domain 4.1) 9.2 Secure SDLC Process (Domain 4.2) 9.3 Apply Secure SDLC (Domain 4.3)

10 Domain 4: Software Assurance, Architecture & IAM

10.1 Cloud Software Assurance & Validation (Domain 4.4) 10.2 Verified Secure Software (Domain 4.5) 10.3 Cloud Application Architecture (Domain 4.6) 10.4 Identity & Access Management Solutions (Domain 4.7)

11 Domain 5: Build, Operate & Operational Controls

11.1 Build Physical & Logical Infrastructure (Domain 5.1) 11.2 Operate & Maintain Infrastructure (Domain 5.2) 11.3 Operational Controls & Standards (Domain 5.3)

12 Domain 5: Forensics, Stakeholder Communication & Security Operations

12.1 Digital Forensics Support (Domain 5.4) 12.2 Communication with Relevant Parties (Domain 5.5) 12.3 Manage Security Operations (Domain 5.6)

13 Domain 6: Legal Requirements, Privacy & Audit

13.1 Legal Requirements & Cloud Risks (Domain 6.1) 13.2 Privacy Requirements (Domain 6.2) 13.3 Audit Processes for Cloud (Domain 6.3)

14 Domain 6: Enterprise Risk Management & Cloud Contracts

14.1 Cloud Implications for Enterprise Risk (Domain 6.4) 14.2 Outsourcing & Cloud Contract Design (Domain 6.5)

10.4 Identity & Access Management Solutions (Domain 4.7)

Key Takeaways Explain This Topic AI

Domain 4.7 designs IAM solutions for cloud apps: federated identity, Identity Providers (IdP), Single Sign-On (SSO), Multi-Factor Authentication (MFA), Cloud Access Security Broker (CASB), and secrets/key/certificate management.

Federation and SSO centralize authentication policy and improve UX while requiring careful trust configuration, claim mapping, and session controls.

MFA (preferably phishing-resistant for privileged users) materially reduces account takeover risk for interactive access.

CASB provides visibility and control over sanctioned and unsanctioned cloud service usage (inline, API, or log modes) aligned to data and access policies.

Secrets, keys, and certificates need vaulting, rotation, least-privilege access, short-lived credentials where possible, and monitoring—hardcoding is an architectural failure.

Last updated: July 2026

Identity and Access Management Solutions

Domain 4.7 asks you to design appropriate Identity and Access Management (IAM) solutions . The August 2026 outline lists: federated identity , Identity Providers (IdP) , Single Sign-On (SSO) , Multi-Factor Authentication (MFA) , Cloud Access Security Broker (CASB) , and secrets, key, and certificate management . In cloud application security, identity is often the real perimeter: networks are software-defined and APIs are reachable; who can call what dominates risk.

IAM Building Blocks (Exam Precision)

  • Concept Meaning
  • Identity Unique representation of a user, service, device, or workload
  • Authentication (AuthN) Proving the identity claim
  • Authorization (AuthZ) Deciding allowed actions on resources
  • Administration Joiner-mover-leaver, roles, reviews
  • Audit Evidence of AuthN/AuthZ and admin changes
  • Federation Trusting identities asserted by another domain/IdP
  • SSO One authenticated session enables access to multiple relying parties

Domain 3.4 introduced identification/authentication/authorization for infrastructure; Domain 4.7 applies IAM design to application and SaaS access patterns and the material (secrets/certs) that underpins machine trust.

Why IAM Design Dominates Cloud Apps

  • Driver Implication
  • API-first access Tokens and service identities replace castle-and-moat VPN assumptions
  • SaaS sprawl Users authenticate to many clouds; consistency requires federation/SSO
  • Automation Pipelines and microservices need non-human identities
  • Remote workforce Strong MFA and conditional access beat password-only VPN mental models
  • Breach patterns Credential stuffing and token theft are common initial access paths

Exam framing: When a breach starts with a stolen password to a console or SaaS app, preferred designs emphasize federation + MFA + least privilege + monitoring , not only a new network ACL.

Federated Identity

Federated identity allows a relying party (application, cloud platform, SaaS) to accept authentication assertions from an external Identity Provider under a trust relationship. Users authenticate once to their home organization; the app trusts the IdP’s claims (subject, groups, MFA strength, tenant ID).

How Federation Works (Conceptual)

User attempts to access the application (service provider / relying party).

App redirects to the configured IdP (or discovers it via email domain).

User authenticates to the IdP (password, MFA, passkey, etc.).

IdP issues a signed assertion/token (SAML assertion, OpenID Connect ID token, etc.).

App validates signature, issuer, audience, lifetime, and maps claims to local authorization.

App establishes an application session or API access token as designed.

Security Properties and Risks

  • Benefit Risk if misconfigured
  • Centralized AuthN policy Over-broad claim → role mapping grants admin everywhere
  • Fewer local passwords Token theft / session fixation if app session weak
  • Faster offboarding via IdP disable Orphaned local accounts if non-federated backdoors remain
  • Consistent MFA enforcement at IdP Trusting wrong issuer or skipping signature validation
  • Easier audit of workforce sign-in Shadow IdPs and unsanctioned apps
  • Design Practices

Explicit trust: pin issuers, metadata certificates, and endpoints; prefer automated but integrity-protected metadata refresh.

Audience restriction: tokens must be for this app.

Least-privilege claims mapping: map groups to roles carefully; deny by default.

Session controls: app session lifetime, refresh rotation, logout (including federated logout where supported).

Break-glass: emergency local admin accounts tightly controlled and monitored—not many standing local passwords.

Workload federation: cloud roles assumed via OIDC from CI systems (short-lived), reducing static keys.

Federation vs Directory Synchronization

Federation trusts assertions at login time . Directory sync copies identities into another system. Many enterprises use both (sync for identity lifecycle + federation for AuthN). On the exam, federation is about cross-domain trust for authentication , not merely copying user rows.

Identity Providers (IdP)

An Identity Provider authenticates users (and sometimes devices) and issues identity assertions to relying parties. Cloud architectures may include:

  • IdP type Role
  • Enterprise workforce IdP Employees/contractors into SaaS and cloud consoles
  • Customer IdP / CIAM External customers of your application
  • Social IdPs Consumer login via third parties (with privacy tradeoffs)
  • Cloud platform IdP Native identities for a specific cloud
  • Partner IdPs B2B federation for supplier portals
  • IdP Security Responsibilities
  • Control Why
  • Strong authenticator policies MFA, phishing-resistant options for privileged
  • Hardened admin plane IdP admin compromise is catastrophic
  • Lifecycle automation SCIM or equivalent for joiner-mover-leaver
  • Conditional access Risk-based signals: device posture, location, impossible travel
  • Logging Sign-in logs to SIEM; alert on impossible patterns
  • High availability IdP outage is a business outage—design resilience
  • Key/cert management for signing Protect token signing keys
  • Choosing and Integrating IdPs

Prefer centralized workforce IdP for employee access to multi-cloud and SaaS.

Separate customer identity from workforce identity stores when populations and risk differ.

For multi-tenant SaaS products you build, support customer IdP federation (SAML/OIDC) as an enterprise feature—and validate every tenant’s metadata carefully to prevent cross-tenant federation mix-ups.

Avoid each application inventing its own password database when federation is feasible.

Exam trap: Treating “we have an IdP” as complete IAM. Authorization design, secrets for workloads, and SaaS shadow IT still remain.

Single Sign-On (SSO)

Single Sign-On lets a user authenticate once and access multiple applications without separate logins for each. SSO is commonly implemented via federation protocols (SAML, OpenID Connect) or enterprise SSO portals.

Benefits and Tradeoffs

  • Benefit Tradeoff / residual risk
  • Better user experience One compromised session may broaden access—mitigate with MFA and short sessions
  • Central policy (MFA, password) IdP becomes critical dependency
  • Faster offboarding Must cover all SSO-connected apps
  • Reduced password fatigue / reuse Token and cookie security become paramount
  • Consistent audit of AuthN App-level AuthZ still decentralized if poorly designed
  • SSO Design Checklist

Protocol choice fit: OIDC for modern apps; SAML still common for enterprise SaaS.

MFA at SSO —do not allow password-only for privileged or sensitive apps.

Application onboarding process —every SSO app registered with correct ACS/redirect URIs (open redirect risks).

Session management —idle timeouts, absolute timeouts, step-up auth for sensitive actions.

Logout behavior —local logout vs single logout expectations documented.

Non-SSO exceptions —service accounts and break-glass inventoried.

Mobile and API patterns —SSO for users; OAuth flows for delegated API access; never embed user passwords in mobile apps.

SSO vs Federation Wording on Exams

Federation emphasizes trust between security domains and assertion acceptance.

SSO emphasizes user experience of one login → many apps .

They often co-occur: federation enables SSO across domains. A single web app with one local login is not enterprise SSO.

Multi-Factor Authentication (MFA)

MFA requires two or more independent factors from categories such as something you know, have, or are (and modern phishing-resistant device-bound authenticators).

Factor Quality

  • Factor class Examples Notes
  • Knowledge Password, PIN Phishable; insufficient alone for privileged cloud access
  • Possession (basic) OTP apps, SMS OTP SMS is weaker (SIM swap); better than password-only
  • Possession (stronger) Push (with number matching), hardware tokens
  • Phishing-resistant FIDO2/WebAuthn passkeys, smart cards Prefer for admins and high-risk
  • Inherence Biometrics Often unlocks a device factor; understand presentation attacks
  • MFA Architecture Practices

Enforce MFA for workforce cloud consoles, email, VPN/ZTNA, and sensitive SaaS.

Step-up MFA for high-risk transactions inside applications (payments, wire, bulk export).

Conditional MFA based on risk signals without creating easy bypasses.

Protect recovery paths —account recovery is a frequent MFA bypass if weak.

Service accounts: MFA does not apply the same way; use workload identity and secret controls instead of shared human MFA devices.

Measure coverage —MFA registration gaps are findings.

MFA Failures the Exam Likes

  • Failure Why
  • MFA only on “important” apps while SSO password opens email reset for all Bypass via weaker app
  • Infinite session after MFA without reauth Token theft window large
  • MFA fatigue push spam without number matching Users approve attacks
  • Shared MFA devices among admins Breaks accountability

Bottom line: MFA is one of the highest-value IAM controls for interactive users; design quality of factors and recovery matters as much as “MFA on” checkboxes.

Cloud Access Security Broker (CASB)

A Cloud Access Security Broker is a security enforcement point between consumers and cloud service providers that applies enterprise security policies to cloud use. CASB addresses SaaS and cloud service visibility/control gaps that traditional network firewalls miss—especially for managed devices and sanctioned apps, and sometimes for shadow IT discovery.

CASB Deployment Modes (Conceptual)

Mode How it works Strength Limitation

Inline / proxy (forward or reverse) Traffic passes through broker Real-time block/allow, DLP inline Needs traffic steering; TLS inspection complexity; remote user challenges

API mode Connects to SaaS APIs out-of-band Deep SaaS control (sharing, malware scan) without inline path Near-real-time not always instantaneous; app must offer APIs

Log collection Ingests IdP/SaaS/firewall logs Discovery and analytics Limited active prevention

Many programs combine modes.

CASB Policy Capabilities

  • Capability Example
  • Shadow IT discovery Find unsanctioned file-sharing usage
  • Data Loss Prevention Block credit card numbers uploaded to personal SaaS
  • Access control Allow managed-device only to CRM
  • Threat detection Malware in cloud storage; anomalous downloads
  • Compliance reporting Usage of services by residency or risk tier
  • Encryption / tokenization gateways (where offered) Protect data before it reaches SaaS
  • UEBA-style analytics Detect compromised accounts in SaaS
  • CASB in the IAM Architecture

CASB complements IdP/SSO/MFA:

IdP authenticates the user.

SSO delivers access to SaaS.

MFA strengthens AuthN.

CASB enforces what users do with data in cloud services and discovers unmanaged services.

Secrets management protects keys used by integrations CASB may monitor.

Exam discrimination: CASB is not a substitute for application secure coding of your software; it is a control for cloud service consumption and SaaS security posture . If the stem is about your developers’ API BOLA, CASB is usually the wrong primary answer; if the stem is about employees uploading PII to unsanctioned storage, CASB fits.

Secrets, Key, and Certificate Management

Cloud apps depend on secrets (API tokens, passwords, connection strings), cryptographic keys , and certificates . Managing them is an IAM-adjacent control plane for machine and application trust .

Secrets Management

  • Practice Detail
  • Central secret store / vault Controlled access, audit logs, dynamic secrets where possible
  • No secrets in source or images Scan repos and pipelines; block commits
  • Short-lived credentials Prefer workload identity and temporary tokens over static keys
  • Least privilege retrieval Runtime roles fetch only needed secrets
  • Rotation Regular and emergency rotation procedures
  • Segmentation Different secrets per environment (dev/stage/prod)
  • Injection at runtime Orchestrator/secret store mounts or SDK retrieval
  • Detection Alert on secret exfil patterns and plaintext in logs
  • Key Management
  • Practice Detail
  • Use managed KMS/HSM-backed keys for master keys
  • Envelope encryption Data keys encrypt data; KMS protects data keys
  • Key policies Separate who can administer vs use keys
  • Customer-managed keys when threat model requires
  • Rotation and versioning Application support for key versions
  • Dual control / M-of-N for highly sensitive root keys where required
  • Regional and residency alignment Keys and data jurisdiction
  • Certificate Management
  • Practice Detail
  • Inventory all TLS and mTLS certs Include service mesh and gateway certs
  • Automated issuance/renewal Avoid outages from expiry
  • Private PKI or public CA as appropriate Internal services often private CA
  • Protect private keys HSM/KMS; never in world-readable shares
  • Certificate transparency / monitoring for public sites
  • Revocation strategy CRL/OCSP or short-lived certs
  • Pinning caution Mobile pinning needs update strategy
  • Unified Lifecycle View
  • Stage Secrets Keys Certificates
  • Create Generate in vault Generate in KMS Issue via CA
  • Distribute Runtime inject Policy-based use Deploy to edge/services
  • Use App retrieves Encrypt/decrypt/sign TLS/mTLS
  • Rotate On schedule/incident Key version rotate Renew before expiry
  • Revoke Invalidate token Disable key version Revoke cert
  • Audit Access logs Key usage logs Issuance/renewal logs
  • Anti-Patterns

Long-lived access keys in Git history.

One shared production secret for all microservices.

Manual cert renewal on a sticky note calendar.

Granting developers permanent decrypt on all CMKs.

Copying production secrets into lower environments with weaker controls.

Leaving default certificates on appliances and gateways.

End-to-End IAM Design Scenario

A multi-cloud enterprise: workforce uses a central IdP with phishing-resistant MFA for admins; SSO/federation into cloud consoles and SaaS; CASB API mode on major SaaS for DLP and sharing controls; applications validate OIDC tokens and enforce RBAC; microservices use workload identities—not static keys; secrets live in a vault with rotation; TLS certificates auto-renew at the gateway and mesh. Developers never store cloud access keys in repos. That architecture hits every Domain 4.7 bullet.

Putting Domain 4.7 Together for the Exam

AuthN path: IdP → MFA → federation/SSO → app session/token validation.

AuthZ path: claims/roles → least privilege in app and cloud IAM—never skip object-level checks.

SaaS consumption: CASB for visibility/control beyond pure AuthN.

Machine trust: secrets/keys/certs lifecycle with short-lived credentials preferred.

Prefer centralized identity policy over per-app password silos for workforce access.

Common Traps

Confusing SSO with authorization (login ≠ permission).

Federation without validating token signatures/audience.

MFA checkbox with weak SMS-only for global admins and weak recovery.

Calling any proxy a CASB without policy/visibility functions.

Excellent human MFA while hardcoding cloud keys in CI.

Forgetting certificate expiry as an availability and security incident.

Assuming CASB fixes vulnerabilities in your custom application code.