Access Control Models & Administration
CISSP CISSP · Identity and Access Management (IAM)
Identification, authentication, authorisation, accountability
Domain 5 is built on four concepts that form a sequence. Identification is claiming an identity — presenting a username. Authentication is proving that identity — presenting a password, token, or biometric. Authorisation is determining what the authenticated identity is allowed to do. Accountability is the ability to trace actions back to the identity that performed them, through logging and auditing. The exam tests the order and the distinctions: authentication without authorisation is useless (you know who someone is but not what they may do), and authorisation without accountability is unmanageable (you cannot investigate what happened). A related concept is identification versus authentication in the context of usernames: a username identifies, a password authenticates — and the exam sometimes asks which factor does which.
Authentication factors
Authentication is based on three factor types: something you know (password, PIN, security question), something you have (smart card, hardware token, mobile phone, one-time password generator), and something you are (fingerprint, iris, face, voice). Multi-factor authentication (MFA) requires two or more factors from different categories — a password plus a one-time code from a phone app, for example. Two passwords are not MFA, because they are the same factor type. The exam also tests the strength of each factor: passwords are the weakest (they can be guessed, phished, or stolen), hardware tokens are stronger, and biometrics are strong but irrevocable. Password policy is a recurring topic: current NIST guidance (SP 800-63B) favours long passphrases over complex short passwords, recommends checking new passwords against lists of known-compromised passwords, and no longer recommends forced periodic password changes unless there is evidence of compromise — a point that surprises candidates who learned the older rules. Account lockout after failed attempts defends against brute force but can be abused for denial of service, so lockout thresholds and durations are a balance.
Access control models
Access control models define how authorisation decisions are made, and the exam tests each one. Discretionary Access Control (DAC) lets the owner of a resource decide who may access it — the standard model in most operating systems and file systems, where a file's owner sets its permissions. It is flexible but risky: owners can grant access inappropriately, and there is no central enforcement. Mandatory Access Control (MAC) is the opposite: access is determined by centrally defined policy based on classification labels, and users cannot override it — the model used in military and high-security environments, and the basis for Bell-LaPadula enforcement. Role-Based Access Control (RBAC) assigns permissions to roles (such as "database administrator" or "accounts payable clerk") and users to roles; it scales well in large organisations and is the most common enterprise model. Attribute-Based Access Control (ABAC) makes decisions based on attributes of the user, the resource, and the environment (such as time of day, location, or device state) — the most flexible model, and the basis for modern policy engines. Rule-Based Access Control uses global rules (such as "no access outside business hours") applied to all users. The exam's key distinctions: DAC is owner-controlled, MAC is system-enforced by labels, RBAC is role-driven, ABAC is attribute-driven.
| Model | Who decides access | Typical use |
|---|---|---|
| DAC | The resource owner | File systems, general-purpose OS |
| MAC | Central policy based on labels | Military, government classified systems |
| RBAC | Role assignment | Large enterprises, most common model |
| ABAC | Attributes of user, resource, environment | Modern policy engines, cloud, zero trust |
| Rule-based | Global rules (e.g. time, location) | Firewalls, time-based restrictions |
Access control administration
Access must be managed through its lifecycle: provisioning (granting access when someone joins or changes role), review (periodically verifying that access is still appropriate — access recertification), and deprovisioning (removing access promptly when someone leaves or changes role). The exam's most important administrative point is that deprovisioning must be immediate and complete: orphaned accounts and lingering privileges from old roles are among the most common audit findings and a frequent attack path. Access creep (or privilege creep) is the gradual accumulation of access as people change roles without losing their old permissions; the countermeasures are role-based provisioning (access follows the current role, not the person's history) and regular access reviews. Onboarding and offboarding checklists, integrated with HR processes so that access changes are triggered automatically by employment events, are the practical implementation. The exam also tests segregation of duties in access administration: the person who requests access should not be the person who approves it.
Privileged access management
Privileged accounts — administrators, root, service accounts — are the highest-value targets in any environment, and the exam treats their management as a distinct discipline. Privileged Access Management (PAM) includes: vaulting privileged credentials (storing them in a secure vault and checking them out for use, with automatic rotation afterwards), just-in-time (JIT) access (granting elevated privilege only for the duration of a specific task, then revoking it), session recording (logging everything a privileged user does), and least privilege for administrators (administrators use standard accounts for daily work and elevate only when needed). Service accounts deserve special attention: they often have broad permissions, their passwords are rarely changed, and they are frequently shared — the exam expects you to know they should have minimal permissions, managed credentials, and no interactive login. Break-glass accounts are emergency administrator accounts kept for situations where normal authentication is unavailable; their use must be heavily monitored and their credentials sealed.
Access control types and mechanisms
Controls can be classified by their function: preventive (stop an unwanted action — a firewall rule, an access control list), detective (identify that an action occurred — logging, intrusion detection), corrective (fix the damage — restoring from backup, patching), deterrent (discourage the action — warning banners, visible cameras), compensating (an alternative control used when the primary control cannot be implemented), and directive (policy that tells people what to do). The exam tests this classification across all domains, not just IAM. Common access control mechanisms include access control lists (ACLs) (lists of permissions attached to an object), capability tables (lists of objects a subject may access, attached to the subject), and access control matrices (the full table of subjects, objects and permissions). Constrained user interfaces (such as menus that only show authorised options) and content-dependent controls (which decide based on the data itself, such as a database view that hides salary columns) are less common but appear on the exam.
Exam mindset for access control
Access control questions reward the principle of least privilege applied consistently: the right answer is usually the option that grants the minimum access necessary, removes access promptly, and separates the roles of requester and approver. When a question asks which model fits a scenario, identify who decides access — the owner (DAC), the system (MAC), the role (RBAC), or the attributes (ABAC) — and the answer follows.
Exam traps to watch for
- Calling two passwords multi-factor authentication — MFA requires factors from different categories (know, have, are).
- Confusing DAC and MAC: DAC lets the owner decide; MAC enforces centrally defined labels that users cannot override.
- Forgetting deprovisioning: the exam treats prompt access removal on termination or role change as one of the most important controls.
- Granting standing privileged access instead of just-in-time access: administrators should elevate only for the task at hand.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A large organisation has 2,000 employees across 40 departments. Permissions are currently assigned individually to each user, and access reviews take months. Which access control model would MOST improve manageability?
Explanation: RBAC scales because permissions are defined once per role and users gain or lose access by changing roles — access reviews become a check of role assignments rather than thousands of individual permissions. DAC would make the problem worse by distributing decisions to owners. MAC is designed for classified environments and is inflexible for a general enterprise. Rule-based access control applies global rules (such as time restrictions) but does not organise permissions by job function.
Exam objective: CISSP Domain 5: Understand access control models (RBAC)
Q2.A user authenticates with a password and then enters a one-time code from an authenticator app on their phone. Which statement is correct?
Explanation: MFA requires factors from different categories: the password is something you know, and the authenticator app on the phone is something you have. The one-time code is not a second password — it is a time-based code generated by a device the user possesses, and it is not derived from the password. Two passwords would be single-factor because they are the same category.
Exam objective: CISSP Domain 5: Understand authentication factors and MFA
Q3.An employee has changed roles four times in three years and now has access to systems from every previous role, including the finance system they no longer need. What is this problem called, and what is the BEST long-term fix?
Explanation: Privilege creep (access creep) is the accumulation of access across role changes when old permissions are never removed. Role-based provisioning with regular access reviews fixes it structurally: access is tied to the current role, and reviews catch anything that lingers. Separation of duties concerns dividing tasks between people, not accumulated access. Logging improves accountability but does not remove excess access. Removing all access and re-granting from scratch is disruptive and does not prevent the problem recurring.
Exam objective: CISSP Domain 5: Understand access control administration (privilege creep, reviews)
Q4.A system administrator needs elevated privileges for a two-hour database maintenance task. According to privileged access management best practice, what should happen?
Explanation: Just-in-time access grants privilege only for the task duration and revokes it automatically, with session recording providing accountability — this is the PAM best practice. Permanent group membership leaves standing privilege that can be abused or stolen. Sharing the root password destroys accountability (you cannot tell who did what) and the password would then need changing. Using a colleague's account is the worst option: it destroys accountability entirely.
Exam objective: CISSP Domain 5: Understand privileged access management
Q5.In a military system, a user with Secret clearance cannot grant a colleague access to a Secret document, even though the user owns the document. Which access control model is in use?
Explanation: Under MAC, access decisions are made by the system based on centrally defined security labels, and individual users — including the owner — cannot grant or change access. This is the defining feature of MAC and the reason it is used for classified systems. DAC is the opposite: the owner decides. RBAC bases access on roles, not labels. ABAC bases access on attributes evaluated against policy, but the key fact here is that the owner cannot override the label-based decision.
Exam objective: CISSP Domain 5: Understand access control models (MAC)
Q6.An organisation’s password policy requires passwords to be changed every 30 days and to include uppercase, lowercase, numbers and symbols. Users cope by writing passwords on sticky notes. According to current NIST guidance, what is the BEST change?
Explanation: NIST SP 800-63B recommends long, memorable passphrases, screening against compromised-password lists, and ending forced periodic rotation (which drives users to weak, predictable passwords and to writing them down). Shortening the rotation interval and increasing complexity would worsen the behaviour the policy is causing. Banning sticky notes addresses the symptom, not the policy that causes it.
Exam objective: CISSP Domain 5: Understand authentication (password policy)
Q7.A firewall rule that blocks unauthorised inbound traffic is an example of which type of control?
Explanation: A firewall rule that blocks traffic is preventive: it stops the unwanted action before it happens. A detective control would log or alert on the traffic without blocking it. A corrective control fixes damage after an incident. A compensating control is an alternative used when the primary control cannot be implemented — the firewall rule here is the primary control, not a substitute.
Exam objective: CISSP Domain 5: Understand access control types (preventive, detective, corrective)
Q8.A service account used by an application has domain administrator privileges and a password that has not changed in five years. The account can also be used for interactive logon. What is the MOST important remediation?
Explanation: The account has three problems — excessive privilege, stale credentials, and interactive logon — and the best remediation addresses all three: least privilege, vaulted credentials with automatic rotation, and no interactive logon. Changing the password alone leaves domain administrator privileges and interactive logon in place. Renaming the account is security through obscurity. Monitoring is detective, not preventive, and does not reduce the risk.
Exam objective: CISSP Domain 5: Understand privileged access management (service accounts)