Study guide

6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access

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.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access

Key Takeaways Explain This Topic AI

Access control models are governance patterns for deciding who may use an object, under what conditions, and with what evidence.

RBAC simplifies administration through job roles, while ABAC adds context and attributes for more granular policy decisions.

MAC and DAC reflect different ownership assumptions: central labels for MAC and owner discretion for DAC.

Risk-based access adds dynamic signals, but it must be governed so convenience does not bypass least privilege.

Last updated: May 2026

Choosing an Access Control Model

An access control model is a way to express and enforce who can access an object and what operation is allowed. The object may be a file, database row, SaaS function, network segment, API method, lab room, or cloud resource. The subject may be a person, process, device, service account, or federated identity. The model should make policy repeatable, understandable, and auditable.

Role-based access control assigns permissions to roles, then assigns subjects to those roles. It is useful when job functions are stable and repeatable, such as nurse, teller, payroll analyst, developer, or database administrator. RBAC reduces one-off permissions and makes reviews easier because the reviewer can ask whether the person still performs that role. RBAC becomes risky when roles grow too broad or exceptions accumulate without cleanup.

Mandatory access control uses centrally managed labels and clearances. The subject has a clearance or category, the object has a classification or label, and the system enforces the access rule. MAC is common in highly regulated, military, intelligence, or sensitive compartmented environments where the owner of a file should not casually grant access. MAC provides strong control, but it can be expensive to administer and may slow collaboration if classification discipline is poor.

Discretionary access control lets an object owner decide who receives access. It is common in file shares, collaboration platforms, and project workspaces. DAC supports flexibility because the owner can share with a colleague quickly. Its weakness is that users may overshare, grant access to groups they do not understand, or fail to remove access after the business need ends. DAC needs education, default restrictions, monitoring, and periodic review.

Attribute-based access control uses attributes about the subject, object, action, and environment. A policy might allow a doctor assigned to a patient to view records from a managed device during an active treatment relationship. Attributes can include department, location, sensitivity, device posture, data owner, transaction amount, time, or risk score. ABAC is powerful, but it depends on accurate attribute sources and disciplined policy design.

Risk-based access evaluates context at decision time. A normal login from a managed laptop may be allowed with existing authentication, while a login from a new country may require step-up MFA or be blocked. Risk-based access is especially useful for cloud, remote work, and consumer-facing services because risk changes constantly. It should supplement least privilege, not replace it. A high-risk signal should tighten access; a low-risk signal should not grant access that policy never allowed.

  • Model Best fit Strength Watch point
  • RBAC Stable job functions Simple assignment and review Role explosion and excessive baseline access

MAC Highly sensitive classified data Central control and label enforcement Administrative burden and rigid workflows

  • DAC Collaboration and owner-managed sharing Flexible and familiar Oversharing and weak recertification
  • ABAC Context-rich policy decisions Fine-grained and adaptive Attribute quality and policy complexity
  • Risk-based Dynamic access decisions Responds to changing threat signals Must not become an unmanaged bypass

The access model also shapes separation of duties. A role that allows vendor creation should not automatically include vendor payment approval. A risk-based policy that allows emergency access should require monitoring and later review. An ABAC rule that checks department must also consider transaction authority. Access control is not only about entry; it is about preventing a single subject from completing a harmful action without oversight.

CISSP-level design starts with business classification and data ownership. Highly sensitive intellectual property may require labels, explicit approval, strong logging, and limited export paths. Routine project files may use DAC with guardrails. Enterprise applications may use RBAC for standard work and ABAC for exceptions such as region, customer assignment, or data sensitivity. Administrative access should usually be separate, more strongly authenticated, and time limited.

A common mistake is treating RBAC as a one-time setup project. Roles must be engineered, tested, reviewed, and retired. If every exception becomes a new role, the organization suffers role explosion. If exceptions are added directly to users, the organization loses visibility. The better approach is to define baseline roles, document controlled exception paths, set expiration dates, and run access reviews that challenge accumulated entitlements.

Another mistake is adopting ABAC before the organization can trust its attributes. If department codes are stale, manager records are wrong, device posture is spoofable, or data labels are incomplete, the policy engine will make precise decisions from bad inputs. Attribute governance includes authoritative sources, change ownership, validation, monitoring, and failure behavior. If an attribute is missing, the policy should usually fail closed for sensitive access.

Model Selection Workflow

Classify the asset and identify the owner.

Define allowed actions and business roles.

Identify duty conflicts, sensitivity labels, and regulatory requirements.

Choose the simplest model that enforces the required control.

Add contextual or risk-based conditions only where they reduce real risk.

Test access paths, logging, exception handling, and deprovisioning.

Review assignments and policies on a schedule based on criticality.

Least privilege should remain the anchor regardless of model. The organization should be able to explain why a subject has access, what condition allows it, who owns the decision, how misuse would be detected, and when the access will be removed. A model that cannot answer those questions may be technically functional, but it is not strong governance.