Mandatory access control grants access by comparing a label on the data with the user's clearance, and users cannot pass access on. Discretionary access control lets the owner decide who gets access. Role-based grants permissions through job roles, attribute-based evaluates attributes of the user, object and environment, and rule-based changes privileges automatically when a rule's condition is met.
Mandatory vs discretionary
The NIST glossary defines mandatory access control (MAC) as restricting access based on the sensitivity of information, shown by a label, and the user's formal clearance. A subject with access cannot pass the information on, grant its privileges to others, or change security attributes. A central authority decides, not the owner.
Discretionary access control (DAC) leaves access to the discretion of the object's owner, who decides who gets access and what rights they have. A subject with access can pass information on or grant its privileges to others.
Role-based and attribute-based
SP 800-53 Rev. 5 describes role-based access control (RBAC) as enforcing access based on the subject's defined role, that is, job function. Users assigned to a role inherit its privileges, so privileges are not assigned to each user directly.
SP 800-162 defines attribute-based access control (ABAC) as granting or denying requests based on attributes of the subject, attributes of the object, environment conditions, and a policy written in terms of those attributes.
Rule-based changes
SP 800-53 control AC-2(6), dynamic privilege management, describes changing user privileges by dynamic rules instead of editing individual user profiles. Its examples include adjusting privileges when users work outside normal hours or when systems are under duress. A rule that strips remote access from every account when the threat level is severe fits this description.
Where the exam catches people
Believing the data owner controls access under MAC: labels and clearances decide, and users cannot grant access to others.
Believing role-based and rule-based are the same: roles map job functions to permissions, while rules change privileges when a condition is met, for every account the rule covers.
Believing DAC means no control: the owner sets access, and holders can pass rights on, which is exactly what MAC prevents.
Believing ABAC looks only at the user: it evaluates subject attributes, object attributes and environment conditions together.