Join our Newsletter — 33% off our NHI Course
Home› Guides› Access Governance vs Access Management: Who Decides Access…
Guide Identity Governance (IGA)

Access Governance vs Access Management: Who Decides Access and Who Enforces It

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 15 min read
On this page

Many organisations believe single sign-on and MFA mean their access is under control, when those tools only enforce whatever access someone already granted, right or wrong. Access governance and access management are two halves of one control loop. Governance decides who should have which access, records why, and proves it is still right. Management authenticates the identity at the moment of use and enforces the decision. When one half is missing, you get either well-documented access that nobody enforces, or strongly enforced access that nobody has checked. This guide compares the two as planes of control, not product categories: what each owns, how they connect, where each fails, and how both extend to service accounts, API keys and AI agents. It is for IAM leads, security architects and auditors deciding where a requirement belongs. For the wider split between PAM, IGA and NHI programmes see PAM vs IGA vs NHI Management; this page goes deeper on the governance and enforcement boundary only.

Key takeaways

  • Governance is the decision plane, management is the enforcement plane. Governance answers "should this identity hold this entitlement, and who approved it?"; access management answers "is this really that identity, and does policy allow this request now?".
  • SSO does not replace IGA. SSO enforces the entitlements it is given. Without joiner, mover and leaver automation, reviews and separation of duties, SSO lets accumulated and orphaned access in quickly and reliably.
  • IGA does not replace access management. A perfectly certified entitlement is still abused if the session token is stolen, MFA is weak or authorisation is checked only at login.
  • The connectors are where risk sits. Provisioning (SCIM and connectors), policy distribution and signals back from enforcement (usage, risk, session events) decide whether the two planes agree.
  • Non-human identities need both planes too. Service accounts, API keys and agents need an owner, a purpose and a review (governance) and workload authentication, scoped tokens and runtime policy (management).

The short answer

Access governance, usually delivered as identity governance and administration (IGA), owns the lifecycle and the justification of access: joiner, mover and leaver processing, access requests and approvals, role and entitlement models, separation of duties (SoD) rules, periodic and event-driven access reviews, and the audit evidence. Access management (AM) owns the runtime: identity providers, authentication and MFA, single sign-on and federation, session management, and authorisation decisions at the application, API or gateway. In NIST terms, access management hosts the policy decision point, which NIST SP 800-162 describes as the component that calculates access decisions from applicable policies, and the policy enforcement point, which enforces those decisions when a subject requests a protected object. Governance supplies the inputs those decisions rely on: who holds which roles, groups, attributes and entitlements.

See IAM and IGA Basics for definitions and Authentication vs Authorisation for the runtime distinction inside access management.

Side-by-side comparison

DimensionAccess governance (IGA)Access management (AM)
Core questionShould this identity have this access, who approved it, is it still needed?Is this the right identity, and is this request allowed now?
Time horizonDays to months: lifecycle events, campaignsMilliseconds to hours: logins, tokens, sessions
Main capabilitiesJML automation, access requests, role mining, SoD, certifications, entitlement catalogue, reportingDirectory and IdP, MFA, SSO, federation, session control, conditional access, token issuance, runtime authorisation
Source of truthHR system and authoritative owners; entitlement catalogueDirectory and IdP configuration; policy engine rules
Typical standardsSCIM (RFC 7644) for provisioning; NIST SP 800-53 AC-2, AC-5, AC-6(7)SAML, OpenID Connect, OAuth 2.0; NIST SP 800-63-4 assurance levels; AC-3, IA-2, IA-9
Failure looks likeOrphaned accounts, privilege creep, rubber-stamped reviews, SoD conflictsSession hijack, MFA bypass, apps outside SSO, authorisation checked once at login
EvidenceApproval records, certification decisions, SoD exceptions, leaver timelinessAuthentication logs, policy decision logs, session and token events
Usual ownerIdentity governance team with business and application ownersIAM engineering or identity platform team
NHI coverageOwnership, purpose, review and decommissioning of service accounts, keys, apps and agentsWorkload authentication, client credentials, token scopes, workload identity federation, runtime policy

How the two planes connect

Treat the integration as three flows. Most real gaps sit in one of them rather than in either platform.

  • Provisioning (governance to enforcement): approved access becomes accounts, group memberships, roles and attributes in the IdP and in applications, through SCIM or connectors. SCIM is defined in RFC 7644 as an HTTP-based protocol for managing identities across domains such as an enterprise and its cloud providers. See SSO vs SCIM.
  • Policy (governance to enforcement): role definitions, SoD rules and attribute meanings that the policy engine evaluates. When authorisation is written as code, governance must own its review; see the Policy-as-Code for Authorisation Guide.
  • Signals (enforcement to governance): last login, last use of each entitlement, risk events and session revocations. Without them, reviewers certify access they cannot see being used. OpenID Continuous Access Evaluation Profile 1.0 (published 29 August 2025, a profile of the Shared Signals Framework) defines event types such as session-revoked, credential-change, token-claims-change and risk-level-change that let one system tell another to restrict access.

A useful test: when HR records a leaver, how many minutes until every session and token for that person stops working? Governance removes the entitlement; only access management can kill the live session. Both must act, and the measure should cover both.

"Do I need IGA if I have SSO?"

For a small organisation with one IdP, a few dozen SaaS apps and HR-driven provisioning built into the IdP, the IdP's own lifecycle and review features may be enough governance for now. The answer changes when any of these is true:

  • Entitlements live inside applications: SSO controls whether you can sign in, not what role you hold in the ERP, database or cloud console. Fine-grained entitlements need a catalogue and reviews.
  • SoD is a regulatory requirement: financial reporting and payment processes need conflict rules evaluated before grant, not only detection after.
  • Apps sit outside SSO: local accounts, legacy systems and shadow SaaS are invisible to the IdP; see the SSO Coverage Guide.
  • Movers accumulate access: SSO adds new access on a role change but rarely removes the old.
  • Non-human identities outnumber staff: they have no HR record, so nothing in an HR-driven IdP flow creates, reviews or removes them.

The reverse question, "do I need strong access management if I have IGA?", always gets a yes. Governance cannot stop a stolen session. The CircleCI Breach 2023 page describes malware stealing an engineer's SSO session cookie that had already passed two-factor authentication; the access itself was legitimately granted, and the control that mattered was session binding and token lifetime at the enforcement plane.

Threat model, failure modes and controls for each plane

Access governance

  • Threat model: insiders and attackers who benefit from access that should not exist: leavers' accounts, privilege creep from moves, toxic combinations, approvals granted without context, and owners who no longer exist.
  • Failure modes: reviews approved in bulk without usage data; leaver feeds that miss contractors; role models that grow until every role holds everything; exceptions with no expiry; entitlements never catalogued, so never reviewed.
  • Controls: HR-driven JML with contractor and partner sources; access requests with business justification and expiry; SoD rules checked at request time; usage-informed reviews with revocation applied automatically; NIST SP 800-53 AC-2 account management, AC-2(3) disabling inactive accounts, AC-5 separation of duties, AC-6(7) review of privileges.
  • Decision criterion: a requirement belongs here if it is about whether access should exist, for how long and who is accountable for it.

Access management

  • Threat model: attackers who use valid access: credential phishing, MFA fatigue, session token theft, token replay, consent abuse and weak authorisation checks in applications and APIs.
  • Failure modes: MFA methods below the assurance the resource needs; long session and refresh token lifetimes; authorisation done once at login and never re-evaluated; apps that accept local passwords alongside SSO; broken object-level authorisation in APIs.
  • Controls: phishing-resistant authentication matched to NIST SP 800-63-4 authentication assurance levels; conditional access on device and risk; short token lifetimes and continuous evaluation; central policy decision with consistent enforcement points; NIST SP 800-53 AC-3 access enforcement, IA-2 for users and IA-9 for services.
  • Decision criterion: a requirement belongs here if it is about proving identity or allowing a specific request at a specific time.

For how runtime authorisation can be centralised, see Centralised vs Embedded Authorisation.

Extending both planes to NHIs and AI agents

Machine identities break the assumptions of both planes. Governance assumes an HR event starts and ends access; management assumes an interactive login with MFA. Neither holds for a CI/CD token or an agent. The OWASP Non-Human Identities Top 10 (2025) lists risks that map directly to each plane.

OWASP NHI riskPlane that owns the fixControl
NHI1:2025 Improper OffboardingGovernanceNamed human owner per NHI; ownership transfer on the owner's leaver event; decommission on project end
NHI5:2025 Overprivileged NHIGovernance, informed by enforcementEntitlement reviews using last-used permission data; right-sizing campaigns
NHI10:2025 Human Use of NHIBothGovernance forbids it in policy and review; enforcement detects interactive use and blocks it
NHI4:2025 Insecure AuthenticationManagementWorkload identity federation, certificate or private key JWT client authentication instead of shared secrets
NHI7:2025 Long-Lived SecretsManagement, with governance setting the policyShort-lived tokens issued at runtime; maximum credential age set and reviewed by governance
NHI9:2025 NHI ReuseBothOne identity per workload registered in the inventory; enforcement rejects use outside the expected workload context

Governance for NHIs: the trigger is creation by code, a pipeline or a platform, not HR. Register each NHI with owner, purpose, environment and expiry; review with usage evidence; reassign ownership when owners leave. See How to Run an Access Review for Service Accounts and NHI lifecycle automation.

Management for NHIs: authenticate the workload, not a stored password; issue scoped, short-lived tokens; evaluate each request against policy. NIST SP 800-63-4 states that it does not explicitly address machine-to-machine authentication, so do not assume human assurance levels map onto workloads.

AI agents: governance records which humans may deploy or delegate to an agent, which tools and data it may reach, and who reviews it; management enforces delegated, task-scoped tokens and per-action authorisation at tool and API boundaries. See Identity Governance for AI Agents Guide and the AI Agent Authorisation Guide.

Worked scenario: a finance analyst and a reporting service account

An analyst moves from accounts payable to financial reporting. A reporting job runs under a service account created by a developer who has since left.

  1. Governance without enforcement signals: the move adds reporting roles through the IGA workflow, but the payables approval role is never removed because the application's local role is not in the entitlement catalogue. The quarterly review approves it because the reviewer sees no usage data. Result: an SoD conflict between creating and approving payments.
  2. Enforcement without governance: SSO and phishing-resistant MFA protect the analyst's sign-in perfectly, and so they reliably admit a user holding a toxic combination.
  3. The service account: it authenticates with a static password stored in the job's configuration. The IdP has no record of it. The IGA tool shows it as owned by a leaver, so no one reviews it.
  4. Fix in governance: catalogue the payables role, add the SoD rule so the mover event triggers removal, assign a new owner to the service account and set an expiry and review cadence.
  5. Fix in management: move the job to a workload identity with a short-lived token scoped to read reporting data; enforce at the data platform that the identity can read but not write; send last-used data back to IGA.
  6. Measure both: mover access removed within the SLA, SoD violations at zero, the service account's credential age under the policy limit.

Decision guidance and ownership

RequirementPrimary planeSupporting plane
Quarterly certification of ERP rolesGovernanceEnforcement supplies last-used data
Phishing-resistant MFA for administratorsManagementGovernance defines who is an administrator
Leaver access removed within one hourGovernance triggersManagement revokes sessions and tokens
SoD between payment creation and approvalGovernance (preventive at request)Management can enforce at transaction level
Block access from unmanaged devicesManagementNone
Owner and expiry for every API keyGovernanceManagement issues and expires the credential
Agent may call payments API only for approved tasksManagement (runtime policy)Governance approves the agent's scope and reviews it

Ownership: one accountable owner per plane, with a joint service owner for the connectors. Application owners and data owners make governance decisions; the identity platform team runs enforcement. Small organisations often run both planes in one IdP; make the split explicit in process even if the tool is shared. Large organisations usually run a dedicated IGA platform beside one or more IdPs and policy engines; the risk there is drift between catalogue and reality, so reconcile continuously. See the IGA Buyer's Guide and IAM vs PAM for where privileged access sits.

How to implement: phased approach

  1. Map the planes: list every system that grants access (IGA, IdP, application admin consoles, cloud IAM) and every system that enforces it. Mark where they disagree.
  2. Connect authoritative sources: HR for employees, a contractor and partner source, and an NHI inventory for machine identities.
  3. Close the leaver loop first: governance removes entitlements; management revokes sessions and refresh tokens. Test with a pilot group and measure end to end.
  4. Bring signals back: feed last login and last entitlement use from the IdP and applications into reviews before the next campaign.
  5. Add SoD and request-time checks for the highest-risk applications, in report-only mode, then preventive.
  6. Extend to NHIs: register owners, set maximum credential ages, move workloads to federated identity, then include NHIs in reviews.
  7. Roll back safely: if automated revocation removes needed access, restore it through a time-bound emergency grant recorded in governance, not by disabling the automation.

Detection and measurement

Monitor: sign-ins by accounts IGA marks as terminated; access to applications by identities with no catalogued entitlement; policy decision denials that spike after role changes; interactive sign-ins by service accounts; tokens used after a session-revoked event. See Access Reviews vs Continuous Access Monitoring.

  • Leaver time to zero access: minutes from HR event to last successful authentication or token use, covering both planes.
  • Reconciliation drift: accounts or entitlements present in applications but absent from the governance catalogue.
  • Review revocation rate: share of reviewed entitlements revoked; near zero suggests rubber-stamping.
  • SoD violations open: count and age of unmitigated conflicts.
  • NHIs with an owner: percentage of service accounts, keys and agents with a current, named owner.
  • SSO coverage: percentage of applications enforcing access through the IdP.

Common failure patterns

  • SSO treated as governance: strong login on top of unreviewed entitlements.
  • Governance that stops at the IdP group: application-local roles never catalogued, so never reviewed.
  • Leaver removes the account, not the session: live tokens keep working for hours; the CircleCI Breach 2023 shows how much a valid session is worth.
  • Reviews without usage data: reviewers approve everything because they cannot tell what is used.
  • NHIs outside both planes: no owner in governance and static secrets in enforcement.
  • Policy changed in the engine, not in governance: runtime rules drift from approved roles with no review.

Framework mapping

FrameworkGovernance planeManagement plane
NIST SP 800-53 Rev 5AC-2 Account Management; AC-2(3) Disable Accounts; AC-5 Separation of Duties; AC-6(7) Review of User PrivilegesAC-3 Access Enforcement; IA-2 Identification and Authentication (Organizational Users); IA-9 Service Identification and Authentication
NIST CSF 2.0PR.AA-05 access permissions defined, managed, reviewed; GV.RR-02 roles and responsibilitiesPR.AA-01 identities and credentials managed; PR.AA-03 users, services and hardware authenticated
ISO/IEC 27001:2022 Annex AA.5.16 Identity management; A.5.18 Access rightsA.5.15 Access control; A.8.5 Secure authentication
CIS Controls v8.1Control 5 Account Management; Control 6 access granting and revoking processesControl 6 MFA and centralised access control
OWASP NHI Top 10 (2025)NHI1, NHI5NHI4, NHI7

Practitioner checklist

  • Write down which team owns the decision plane and which owns the enforcement plane, and who owns the connectors.
  • Measure leaver time to zero access across entitlements, sessions and tokens.
  • Catalogue application-local roles for your top 20 applications so they can be reviewed.
  • Feed last-used data from the IdP and applications into every review campaign.
  • Enforce SoD at request time for payment and financial reporting processes.
  • Give every NHI an owner, purpose and expiry, and include NHIs in reviews.
  • Replace static secrets for workloads with federated identity and short-lived tokens.
  • Route runtime policy changes through governance review.

Standards and references

Related NHI Mgmt Group resources: PAM vs IGA vs NHI Management · Data Access Governance Guide · Joiner-Mover-Leaver Guide · Identity Provider and SSO Security Guide · Segregation of Duties vs Least Privilege

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.