Access-Control Requests and Identity
Learn how identities, accounts, authenticators, and permissions relate to the subject–object–operation structure of an access-control request.
The Parts of an Access-Control Request
What access control governs
Access control determines which people, devices, and software processes may use an organization’s resources and what actions they may perform. Identity management supports these decisions by establishing identities, managing accounts and credentials, and keeping access current as people and systems change.
Keep four related terms distinct: an identity represents an entity, such as an employee, service, or device; an is a system-specific record associated with that identity; an helps prove control of the ; and a specifies an allowed action. They describe different things—not four names for a user or a login.
Describe a request
A request can be described with three parts: the (who or what requests access), the (the resource), and the (the requested action). Keeping these parts separate makes the request clear; a specifies whether an action is allowed.
Hypothetical application: An employee asks to read a file. The employee is the , the file is the , and reading is the . The employee’s identity represents them; an is the system’s record associated with that identity, and an may help prove control of that . Whether the read is allowed depends on the applicable . This description does not assume that access is granted.