Task-bound access
An agent Worker acts with a token scoped to its Role’s Permissions and its Task’s Nouns, expiring with the Task or Mandate.
Satisfies
| Criterion | Text |
|---|---|
| SOC2 CC6.1 | The entity implements logical access security software, infrastructure and architectures over protected information assets. |
| SOC2 CC6.3 | The entity authorizes, modifies or removes access based on roles, least privilege and segregation of duties. |
| ISO27001 A.5.15 | Rules control physical and logical access to information and assets, based on business and security requirements. |
| HIPAA 164.308(a)(4) | Access to electronic protected health information is authorized consistent with the minimum necessary. |
| HIPAA 164.312(a)(1) | Systems that hold electronic protected health information allow access only to authorized persons or software. |
Implemented by
Test
| Step | Rule |
|---|---|
| Kind | Preventive: it stops the failure before it happens. |
| Select | Every Action by an agent Worker in the report period. |
| Assert | Each ran under an unexpired token whose scope lies inside both its Role’s Permissions and its Task or Mandate. |
Owner
Security Engineer, Engineering Team.
Example
An Agent reconciling one Customer's month gets a token scoped to that Customer's Transactions. When the Task closes, the token expires.