← Back to catalogue
Published

Access, delegation and secret metadata

EM-RSK-03 · em-rsk-03

Account, access role, permission, delegation, access review and key metadata. Credential values are not part of the registry.

Enterprise profiles Enterprise subject EnterpriseRSK

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 9 questions

Accounts and roles Digital accounts, the people behind them and the roles they hold.

Account binding

An account linked to a person without being the person.

Account and person

The link between an account and the person or system that uses it.

  1. Which person or system uses this account, and on which basis?
  2. Is the account shared, personal, technical or a service identity?

Role and permission

An access role with its permissions, separate from a job position.

  1. Which permissions does the role grant, and on which resources?
  2. Is the role granted by a condition such as a position, or by a separate justification?
Delegation, review and secrets Temporary and delegated rights, their review and key metadata.

Delegation and review

Delegations with scope and expiry, and periodic access reviews.

Delegation scope

A delegated right bounded by the delegator's own rights and time.

  1. Does the delegation stay within the delegator's own rights?
  2. When does the delegated or temporary right expire?
  3. Which grants should be revoked when an assignment changes?

Secret metadata

Metadata and protected references for keys and credentials.

Credential lifecycle

Creation, rotation and revocation of a key without its value.

  1. When was the key created, rotated and revoked?
  2. Is only a protected reference stored instead of the secret value?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseRSK
Industry
Cross-industry
Tags
EM-RSK-03W1subjectDigitalAccountAccessRolePermissionGrantDelegationAccessReview

What it is Filled

Account, access role, permission, delegation, access review and key metadata. Credential values are not part of the registry.

Why it exists Filled

Account, access role, permission, delegation, access review and key metadata. Credential values are not part of the registry.

Distinguishing features Filled

  • An access role is not a job position; a position may condition a grant but never is the grant.
  • Delegation cannot extend beyond the delegator's original rights or term.
  • The registry holds metadata and protected references only, never credential values.
  • Distinct from the person or employee record, which an account is linked to but not equal to.

What robots and AI may and may not do Filled

Must not

  • Grant access to all HR data because a person holds a manager position.
  • Read, store, print or pass a secret or credential value.
  • Create a delegation wider than the delegator's own rights.
  • Grant itself or another agent access rights.
  • Treat an account as identical to a person.

Only with a human decision

  • Granting privileged or sensitive access.
  • Approving an exception to an access review result.
  • Revoking a key that production services depend on.

May

  • Report which grants depend on a position and which have separate justification.
  • Flag expired delegations and accounts with no linked owner.
  • Prepare an access review list for a role or a resource.
  • Show key rotation and revocation dates from metadata.

Moral aspects Filled

  • Excess access exposes personal and confidential data of employees and customers.
  • Leaked secrets can cause financial and operational harm at scale.
  • Access reviews must not become covert monitoring of individuals.

Who is affected

  • Employees and contractors
  • Data subjects whose records are accessed
  • Security and audit teams

Owners Filled

Steward

The risk owner, the information security lead or internal audit, depending on the record.

Master systems

  • GRC platform
  • Identity and access management system
  • SIEM
  • Service desk

Links to other meta-models Filled

references

  • WM-PER-002 - conceptual-candidate
  • WM-XCT-002 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Accounts are identified by directory identifier and system; grants, delegations and keys have their own identifiers and validity periods.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record names an account, a role, a resource and a validity period.
  • Often confused with the employee record or the organisational position.

Capabilities and actions required Filled

  • Conditioned grants can be revoked automatically when the condition ends.
  • Key revocation can be attested without disclosing the key.

Hazards and failure modes required Filled

  • Privilege creep when grants outlive the role change that justified them.
  • Secret leakage through logs, exports or projections.
  • Orphaned accounts after people leave.

Standards and interfaces required Filled

  • IETF SCIM, RFC 7643 and RFC 7644, for identity provisioning.
  • IETF OAuth 2.0, RFC 6749, for delegated authorisation.
  • NIST SP 800-63 Digital Identity Guidelines.

Context of use required Filled

  • Used by identity and access management, security and audit functions.
  • Covers people, service accounts, agents and machine identities.

Sources Filled

  1. NIST CSF/AI RMF: governance and risk functions
  2. ODRL/PROV: authority, grounds and evidence
  3. GRC/IAM/BCM practice and NIST SP 800-34 for recovery
  4. W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
  5. NIST SP 800-53 Rev. 5: Security and Privacy Controls - Checked live (HTTP 200) on 2026-10-07.
  6. OASIS XACML Version 3.0 - Checked live (HTTP 200) on 2026-10-07.
  7. NIST SP 800-57 Part 1 Rev. 5: Recommendation for Key Management - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to link an account and a Person without equating them?
  • How do temporary and delegated rights operate?
  • How to attest key revocation without disclosing the key?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-rsk-03/brief.json, ver-cy/world-models/card-supplements/em-rsk-03.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.