Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:a:authorized_resource [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:a:authorized_resource [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Authorized Resource ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Authorized Resource is a resource for which an identified actor or process has permission to perform one or more specified operations. | ||
| + | |||
| + | The resource may include: | ||
| + | |||
| + | * A file | ||
| + | * A directory | ||
| + | * An [[public: | ||
| + | * An Infrastructure Configuration | ||
| + | * A Machine Image | ||
| + | * A data set | ||
| + | * A repository | ||
| + | * A computing resource | ||
| + | * A storage resource | ||
| + | * A network resource | ||
| + | * A service | ||
| + | * A removable storage device | ||
| + | |||
| + | Authorization applies within a defined context. The authorization may identify: | ||
| + | |||
| + | * The authorized actor or process | ||
| + | * The authorized resource | ||
| + | * The permitted operation | ||
| + | * The applicable purpose | ||
| + | * The permitted source or destination | ||
| + | * The effective period | ||
| + | * The applicable conditions | ||
| + | * The authorizing authority | ||
| + | |||
| + | Permitted operations may include: | ||
| + | |||
| + | * Access | ||
| + | * Read | ||
| + | * Create | ||
| + | * Modify | ||
| + | * Execute | ||
| + | * Copy | ||
| + | * Transfer | ||
| + | * Deploy | ||
| + | * Delete | ||
| + | |||
| + | A resource does not become authorized merely because an actor can technically access it. Authorization requires permission granted through an applicable authority, policy, role, rule, or decision. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //resource for which an identified actor or process has permission to perform specified operations under defined conditions// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Authorization may differ among actors, processes, operations, purposes, environments, | ||
| + | |||
| + | A resource authorized for reading is not necessarily authorized for modification, | ||
| + | |||
| + | Authorization does not by itself establish that the resource is: | ||
| + | |||
| + | * Authentic | ||
| + | * Accurate | ||
| + | * Approved | ||
| + | * Compliant | ||
| + | * Free from malicious content | ||
| + | * Suitable for the intended operation | ||
| + | |||
| + | Separate controls establish those characteristics. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A deployment process has permission to retrieve an identified Machine Image from a designated repository and deploy it within a specified Infrastructure Environment. The Machine Image is an Authorized Resource for that process and deployment operation. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||