Access control answers a simple question that is hard to answer well: should this request be allowed? Role-based systems answer it by checking whether the user holds a role that includes the permission. That works for stable organisations with clear job functions, and it strains when rules depend on conditions that roles cannot express. A manager may approve expenses only up to a limit, a clinician may view only the records of patients assigned to them, and a contractor may connect only from a managed device during a project. Attribute-based access control handles such rules by making the decision from attributes rather than from membership of a role. It is one of the approaches that underlie zero trust architectures and modern authorisation services.
How does ABAC decide?
Each request is described by four kinds of attribute. Subject attributes describe the requester, such as department, clearance and employment status. Resource attributes describe the data or system being accessed, such as classification, owner and customer. Action attributes describe what is being attempted, for example read, edit or delete. Environment attributes describe the circumstances, such as time, location, network and device health. A policy is a set of rules that combines these attributes, for instance allowing a user to edit a document when the user's department matches the document's owner and the device is managed. The system evaluates the rules for each request and returns allow or deny, so permissions follow from facts that can change without anyone editing a role.
What are the components of an ABAC system?
A typical architecture separates concerns. A policy enforcement point sits in front of the resource and intercepts requests. It asks a policy decision point, which evaluates the rules against the attributes and returns a verdict. Attributes come from sources such as the identity directory, human resources systems, device management tools and the data's own metadata, brought together by an information point. Policy administration tools let authors write, review and version the rules. Standards such as XACML described this model, and newer policy engines use languages designed for developers, with policies stored as code, tested automatically and deployed through the same pipelines as software. Separating policy from application code keeps access rules consistent across many systems.
Why context matters, and what it costs
Contextual attributes make decisions adaptive. A request from a managed device on a trusted network may be allowed, while the same user on an unfamiliar device may be asked for stronger authentication or limited to read-only access. This supports continuous, risk-based evaluation rather than a single login check. The price is complexity. Policies can interact in surprising ways, so they need testing and review, and an attribute that is wrong or out of date produces wrong decisions without any visible error. Performance matters, since every request triggers an evaluation, and many organisations combine ABAC with roles, using roles for broad entitlements and attributes for fine-grained conditions.
Why it matters
Good access control is central to limiting the damage from stolen credentials and insiders, and rigid models tend to be bypassed or over-granted. ABAC offers a way to express precise rules that follow the actual conditions of a request. Its value depends on trustworthy attributes, clear ownership of policies and testing before changes are deployed. With those in place, it gives organisations flexible control that scales as their systems and rules grow.
Roles describe who someone is. Attributes describe the situation, and the situation is what an attacker changes.