Authorization decides what an identified and authenticated subject may do. Being recognized by a system does not mean having permission to use every resource: the system must still decide which objects the subject may access, which actions are allowed, and under what conditions. section 8.3 section 8.3.3 section 8.2
An access request has three parts: a subject, such as a person or process making the request; an object, such as a file or database being protected; and rules that allow or deny the requested action. Permissions specify actions such as reading, writing, or executing. Privileges cover a broader range of capabilities, including sensitive actions such as changing system settings or other users’ permissions. section 8.2 section 8.3.3
|
Description
|
Examples
|
|
|
Subjects
|
Entities that initiate a request for access to a resource.
|
• A user logging into a system
• A script querying database for data
• A device connecting to a network
|
|
Objects
|
A resource of services that subjects attempt to access.
|
• Printers
• Servers
• Files
• Databases
|
|
Rules
|
Conditions that define if a subject can access an object
or not.
|
• IT personnel cannot access financial records
• HR can only access employee-related files
|
Compare the examples of subjects, objects, and rules to see what an access decision evaluates. section 8.2
The right person, the wrong resource
An HR employee may need personnel records to do their job but not access to financial systems. A customer may be allowed to view their own account information, not another customer’s. In each case, authorization limits access according to the request and the person’s business responsibilities. section 8.1
Authorization also applies outside computer systems. Before admitting a visitor, a receptionist or guard can check both the visitor’s identity and whether entry is allowed. Visitor rules may limit which areas the person can enter or require an escort. section 9.3.1
Good access decisions remain appropriate over time:
- Grant only the access needed for the task. Least privilege limits unnecessary permissions, while need-to-know requires a business reason for sensitive information. section 8.10 section 8.7
- Review permissions when responsibilities change, and revoke access when it is no longer needed. Identity and Access Management (IAM) can standardize this lifecycle. section 8.4
- Record sensitive activity so actions can be traced to a user. Elevated privileges warrant close monitoring and a documented business reason. section 8.3 section 10.4.4
Authentication and authorization remain separate even with single sign-on. An application may accept a valid sign-in token, then apply its own rules to determine the user’s level of access. This distinction helps protect information from unauthorized disclosure or changes while keeping resources available to people who need them. section 10.3.2 section 8.1





































