Parent folderOpen Confluence

RWS Architecture article

Identity Governance and Administration

Identity Governance and Administration is the product-neutral architecture building block for identity lifecycle governance, entitlement review, and access administration. It state

  1. Typeabb
  2. Statuscandidate
  3. Domainsecurity
On this page
  1. ABB Identity Governance and Administration
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Identity Governance and Administration

Summary

Identity Governance and Administration is the product-neutral architecture building block for identity lifecycle governance, entitlement review, and access administration. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides identity lifecycle governance, entitlement review, and access administration.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the identity and access management ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Access must be attributable to managed identities and reviewed according to governance policy.
  • SBBs must integrate with authoritative identity sources and avoid unmanaged local entitlement stores.

Service Description

This ABB offers an identity-governance service that manages identity lifecycle, access requests, approvals, certification, and entitlement traceability. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Identity Governance and Administration.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud landing zone in ODC-Amsterdam, following the RWS ICT Strategy 2025-2030 private-cloud direction.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Identity lifecycle and provisioning APIs.
  • SCIM, LDAP, workflow, and approval interfaces as applicable.
  • Audit, reporting, and federation integrations.

Dependencies

  • Depends on federated-authentication for a supporting capability or integration boundary.
  • Implemented by midpoint as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • midpoint - midPoint is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.