Access Control Models & Administration

CISSP CISSP · Identity and Access Management (IAM)

By Abu Anns · Last updated 20 November 2026Exam version: April 2024 outline (current until 15 April 2027)

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.

ModelWho decides accessTypical use
DACThe resource ownerFile systems, general-purpose OS
MACCentral policy based on labelsMilitary, government classified systems
RBACRole assignmentLarge enterprises, most common model
ABACAttributes of user, resource, environmentModern policy engines, cloud, zero trust
Rule-basedGlobal 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.

Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

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?

Report an error

Q4.A system administrator needs elevated privileges for a two-hour database maintenance task. According to privileged access management best practice, what should happen?

Report an error

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?

Report an error

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?

Report an error

Q7.A firewall rule that blocks unauthorised inbound traffic is an example of which type of control?

Report an error

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?

Report an error