Join our Newsletter — 33% off our NHI Course

Could HANA still miss Cross-App Segregation Of Duties?

 

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

TL;DR: Cross-application Segregation of Duties remains fragmented as SAP GRC for HANA modernizes SAP governance, with Pathlock noting the control boundary still sits inside ERP. Cross-application risk stays split across SAP, SaaS, and non-human identities, so audit evidence has to span more than one system.

Editorial analysis by NHI Mgmt Group, based on content published by Pathlock: “Beyond the Upgrade: Is SAP GRC for HANA Enough?”.

Key questions

Q: Why do non-human identities need separate governance attention in platform roadmaps?

A: Because service accounts, tokens, and automated access do not behave like human logins.

Q: When should organisations prioritise cross-application governance over an SAP-only upgrade?

A: When key business processes already depend on SAP plus SaaS applications, external workflows, or machine identities, cross-application governance should come first.

Q: What breaks when SAP GRC stays SAP-only in a multi-application estate?

A: Cross-application Segregation of Duties breaks first.

Practitioner guidance

  • Map your governance boundary Document which business processes, applications, and identity types sit inside SAP-only controls and which already rely on external identity systems.
  • Test cross-application SoD coverage Run SoD scenarios that span SAP and at least one SaaS application, then verify whether the violation is visible without manual spreadsheet correlation.
  • Separate non-human identity governance Create distinct lifecycle, certification, and evidence requirements for service accounts, API credentials, AI agents, and bots rather than reusing human review cadences.

Bottom line: SAP GRC for HANA modernizes SAP governance mechanics, but the architectural question is whether the enterprise still lives inside an SAP-only control boundary.

Glossary terms: Cross-App Segregation Of Duties, Non-Human Identity Lifecycle, Governance architecture, SAP Authorization

Explore further

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


This topic was modified 7 days ago by NHI Mgmt Group

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

Architecture migration is the real decision, not product replacement: This article is not about whether SAP GRC for HANA is newer. It is about whether an ERP-native governance model still matches an enterprise where the control surface now spans SAP, SaaS, bots, and AI agents. That mismatch matters because architecture defines what can be governed without manual reconciliation. Practitioners should treat the migration as a boundary decision, not a technical refresh.

A question worth separating out:

Q: How do you know whether a governance platform is covering the full identity estate?

A: You know it is covering the full estate only if it can prove control over SAP, SaaS, elevated access, and non-human identities with the same audit trail. If evidence still depends on exports, connectors, or separate tools, coverage is fragmented.

👉 Read our full editorial: SAP GRC for HANA leaves cross-application governance unresolved


This post was modified 7 days ago by NHI Mgmt Group

   
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.