Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Attribute-based access control (ABAC) is a mechanism that decides access by conditions such as department and time. It lines up who is doing what, to what, and in which situation as conditions, and permits the action only when the rules match. NIST's SP 800-162 describes it as a logical access control method that decides by applying rules to the attributes involved in a request.
How does attribute-based access control work?
Take an office entry gate as an example. It looks at the department on a staff card, what time it is, and which entrance the person came from, and decides on the spot whether to open. Even when the people change, the rules do not need to change.
NIST calls the information used in a decision an attribute, and divides it into attributes of the user, attributes of the object, the operation, and environment conditions. As examples of environment conditions it lists the threat level, the location of the user or object, the authentication method, and the time.
RBAC, which decides by role alone, is in NIST's explanation a method that decides on a single attribute, the role. ABAC differs in that it can write rules that combine several attributes. Where to draw the line on who sees what is set out in broken access control. If you want help thinking about rules for your member site, contact us.
Why does attribute-based access control matter?
Because it can take in conditions such as time and place, it can draw lines that roles alone express poorly. An example is a rule such as: an accounting staff member can view billing data only from an in-house device during business hours. NIST says ABAC enables fine-grained access control.
On the other hand, a mechanism adds things to decide. NIST's document says to make clear who assigns attributes and to keep them consistent with policy. You also need a way to confirm that the content of attributes is correct. When you think about adopting it, deciding the following first makes it easier.
- Which attributes to use: list department, job title, device type, time, and so on.
- Who assigns attributes, and who changes them.
- Write the rules down in text so anyone can read them.
- Make a procedure to check the range affected when a rule is changed.
For a small site, roles alone are often enough. Adding ABAC when it becomes necessary is the realistic way to proceed.
Related terms
- Role-based access control: decides the usable range for each role
- Least privilege: the idea of narrowing rights to what the work needs
- Broken access control: a flaw that lets people see data they must not see
- Privileged access management: a mechanism that controls strong accounts especially tightly
Frequently asked questions
Which should I choose, RBAC or ABAC?
NIST's SP 800-162 says it is not a document that compares ABAC with other methods. It focuses on the challenges of implementing ABAC. RBAC suits giving the same permissions to people in the same role, and ABAC suits deciding in detail by conditions such as time and place.
What does "attribute" mean in ABAC?
NIST calls the information used in a decision an attribute, and divides it into conditions of the user, the object, the operation, and the environment. Department and job title are user attributes, the confidentiality level of a document is an object attribute, and time and place are environment conditions.
Next step
Problems that arise from badly drawn permission lines are in broken access control, and deciding by roles is covered in role-based access control. The free URL check shows only what is visible from outside, and for rule design, contact us.
Frequently asked questions
Which should I choose, RBAC or ABAC?
NIST's SP 800-162 says it is not a document that compares ABAC with other methods. It focuses on the challenges of implementing ABAC. RBAC suits giving the same permissions to people in the same role, and ABAC suits deciding in detail by conditions such as time and place.
What does "attribute" mean in ABAC?
NIST calls the information used in a decision an attribute, and divides it into conditions of the user, the object, the operation, and the environment. Department and job title are user attributes, the confidentiality level of a document is an object attribute, and time and place are environment conditions.