Join our Newsletter — 33% off our NHI Course

Does Veza-ServiceNow approval determinism hold at scale?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Automated access fulfilment can speed requests, but it also concentrates governance risk in catalog design, approval logic, and identity resolution, according to Veza. Workflow determinism and catalog synchronisation need to stay tight as request volumes grow.

Editorial analysis by NHI Mgmt Group, based on content published by Veza: “Automating Veza Access Requests for the Enterprise: Integrating Veza with ServiceNow”.

Key questions

Q: Why do identity mapping errors matter in automated access workflows?

A: Because the request is only as trustworthy as the join between the request record and the identity record.

Q: How do teams know if automated access reviews are actually working?

A: Automated reviews are working when exception rates fall, reviewer overrides become rare, and access decisions are grounded in clean role definitions rather than ad hoc exceptions.

Q: What breaks when access automation creates duplicate or missing approvals?

A: The workflow stops being auditable because request state no longer proves who authorised access or whether authorisation happened once.

Practitioner guidance

  • Validate approval path determinism Map every catalog item to a single expected approval chain and disable overlapping business rules that can create duplicate or missing approvals.
  • Test identity matching with real records Use production-like requester data to verify email normalisation, identity lookup, and profile matching before enabling automated provisioning.
  • Treat catalog sync as a control Review how often access profiles and catalog items are refreshed so decommissioned profiles do not remain requestable after the entitlement model changes.

Bottom line: Automated access fulfilment can improve speed, but it also concentrates governance risk into catalog design, approval logic, and identity resolution.

Glossary terms: Approval Determinism, Identity Resolution, Catalog Synchronisation, Requested Item Workflow

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Access automation changes the governance burden, not the governance requirement: moving approvals and provisioning into workflow logic does not remove control obligations, it relocates them into catalog design, rule logic, and identity mapping. The risk shifts from manual inconsistency to automated inconsistency at scale. IAM teams should read this as a control-design problem, not a workflow problem.

A question worth separating out:

Q: Should organisations keep manual checks when access requests are automated?

A: Yes, but only where the risk profile justifies them. Automation is appropriate for standard access paths, while sensitive entitlements may still need a human review step or separate admin approval. The decision should be based on privilege level, data sensitivity, and how confidently the identity system maps the requester to the right entitlement.

👉 Read our full editorial: ServiceNow access automation raises new identity governance questions



   
ReplyQuote
Share:

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.