Study guide

6.1 Identity Proofing, Authentication, Authorization, and Accountability

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.1 Identity Proofing, Authentication, Authorization, and Accountability

Key Takeaways Explain This Topic AI

IAM starts with reliable identity proofing, then carries that trust through authentication, authorization, and accountable use.

Authentication verifies a subject, authorization decides what the subject may do, and accountability preserves evidence of what happened.

Assurance level, enrollment method, credential strength, and monitoring depth should be selected from risk and business context.

Least privilege is effective only when access decisions are tied to lifecycle governance, ownership, and periodic review.

Last updated: May 2026

The IAM Chain of Trust

Identity and access management begins before a password, token, badge, or biometric is issued. The organization first decides how much confidence it needs that a subject is who it claims to be. That subject may be an employee, contractor, customer, partner, device, workload, or service account. The proofing method should match the harm that could occur if the identity is wrong.

Identity proofing is the enrollment decision. It may use government documents, HR records, in-person checks, verified business sponsorship, device attestation, or automated evidence validation. The key governance question is not whether proofing is convenient. The key question is whether the proofing process creates enough identity assurance for the business process being protected.

Authentication is the later act of proving control of an enrolled identity. It uses factors such as something known, something possessed, something inherent, somewhere present, or something behaviorally observed. Strong authentication reduces impersonation risk, but it does not decide whether the authenticated subject should access a record, approve a payment, or administer a server.

Authorization is the policy decision after identity is known with sufficient confidence. It maps subjects to permissions through roles, attributes, labels, risk signals, ownership rules, and business approvals. Authorization should be specific enough to support least privilege and separation of duties. Broad grants are easy to operate, but they create toxic combinations, standing privilege, and poor audit defensibility.

Accountability is the ability to trace actions to the responsible identity or process. It depends on unique accounts, synchronized time, reliable logs, tamper resistance, and review. Shared accounts, generic administrator IDs, and missing audit trails destroy accountability even if authentication was strong. A control that cannot be attributed is weaker during investigations, compliance reviews, and disciplinary processes.

IAM function Main question Common evidence Governance risk

Identity proofing Should this identity exist? HR record, sponsor approval, document check, device attestation False identity or duplicate identity

Authentication Is this the enrolled subject? MFA event, certificate use, authenticator health Impersonation or credential replay

Authorization What may this subject do now? Role, entitlement, policy decision, approval Excess privilege or duty conflict

Accountability Can actions be traced and reviewed? Logs, session recording, ticket reference Repudiation or weak investigation

A mature IAM program treats identity as a lifecycle object. A new hire may be proofed by HR, assigned baseline access through a role, elevated through manager approval, monitored through logs, and removed when employment ends. A contractor may need stricter expiration, sponsor recertification, and limited access because the relationship is temporary. A production administrator may need privileged access management, just-in-time elevation, and session recording.

The authentication strategy should also reflect threat and usability. Password-only access to a payroll system is weak because a stolen credential can expose sensitive data and enable fraud. MFA with phishing-resistant authenticators is stronger for administrative and high-value access. Adaptive controls may step up authentication when the login comes from a new device, impossible travel pattern, risky network, or unusual time.

Authorization must be owned by the business as well as security. Security teams can design policy engines and control frameworks, but data owners and process owners know which access is appropriate. The best pattern is clear ownership, documented approval criteria, automated enforcement, and review evidence. The worst pattern is ticket approval without context, where managers approve access they do not understand.

Least privilege is not simply the smallest technical permission set. It is the minimum access needed for a defined business purpose, for the right duration, under the right conditions, with monitoring proportional to risk. A developer who needs production logs for two hours does not need permanent shell access to every production host. A finance analyst who approves vendors should not also create vendors unless a compensating control exists.

A CISSP answer often turns on separating the steps. If a user is authenticated but cannot access a file, the issue is likely authorization. If an action cannot be tied to a person because an admin account is shared, the issue is accountability. If a remote contractor was issued an account without sponsor validation, the issue began at proofing. Good IAM governance names the failed step and fixes it at the source.

Lifecycle Control Checklist

Establish identity proofing requirements by role, data sensitivity, and transaction risk.

Require unique identities for people and managed non-human subjects unless a formally approved exception exists.

Use MFA for privileged, remote, sensitive, and high-impact access, with stronger methods for higher risk.

Assign access through roles or policies where possible, then handle exceptions with owner approval and expiration.

Log authentication, authorization, privilege elevation, and sensitive actions with enough detail for investigation.

Review access regularly, remove stale entitlements, and test termination workflows.

The managerial view is to avoid confusing a technology with the control objective. Biometrics, smart cards, certificates, passwords, and passkeys are mechanisms. The objective is trustworthy identity, appropriate authorization, reliable accountability, and timely lifecycle change. When an organization can explain why each identity exists, why each entitlement is needed, who approved it, and when it will be reviewed, IAM becomes a governance system instead of an account database.