Organisations should treat segregation of duties and sensitive access as design requirements, not after-the-fact audit findings. Teams need to map critical business processes, identify where conflicting access could occur, and confirm controls before go-live. The goal is to prevent users from combining incompatible privileges, reduce overexposure, and ensure the implementation can pass compliance review without redesign.
How to frame SoD and sensitive access before ERP cloud go-live
Before go-live, organisations should talk about segregation of duties and sensitive access as design constraints that shape the ERP configuration, role model, and approval flow. The conversation should focus on where conflicts can arise in core business processes, which access is genuinely necessary, and how the implementation will prove those choices before production use begins.
The useful question is not whether access is technically possible, but whether the proposed role design prevents one user, or one account, from completing an incompatible end-to-end process. That means examining business scenarios, exception handling, and privileged functions together, rather than treating access review as a late-stage sign-off.
For a structured starting point, the SoD model should be mapped to the ERP process flow, then checked against the identity and role model that will exist at go-live. NHIMG’s Segregation of Duties (SoD) Guide is useful here because it ties SoD rulesets to conflicts, mitigations, and ERP access patterns.
What should be reviewed in the role and process design?
The review should start with the business processes that create the highest exposure: procurement, vendor setup, payments, journal entries, master data changes, access administration, and emergency access. Those are the areas where SoD conflicts are most likely to create fraud, error, or control failure if a single role can initiate and approve the same activity.
Teams should then test the design against the actual roles, not the job titles. A role that looks harmless in isolation can become risky when combined with inherited access, composite roles, temporary elevation, or shared support functions. The practical test is whether the role model still preserves independent review at each critical step.
Where organisations are still building the access model, it helps to anchor the discussion in broader identity and governance concepts first. IAM and IGA Basics provides the baseline language for entitlements, role design, access reviews, and governance of people and machines.
For sensitive access specifically, the review should distinguish ordinary business access from elevated access to high-risk functions, configuration areas, and sensitive data sets. A role can be acceptable for day-to-day operations while still being too broad for production support, finance close, or ERP administration.
That is where design principles matter. The access model should reflect least privilege and separation of duties as complementary controls, not competing ones. Core Security Principles Guide is relevant because it frames SoD as a core design principle rather than a compliance afterthought.
How do you prove the controls are ready before go-live?
Proof comes from testing the control design against real access scenarios before production cutover. Organisations should validate whether conflicting access is blocked, whether mitigating controls are documented where conflicts cannot be removed, and whether the approval and review workflow can produce evidence for auditors and control owners.
That validation should include access recertification, exception handling, emergency access, and the use of any compensating control. If a control depends on manual review, the review path must be clear, timely, and owned by someone who can actually deny or revoke access. Otherwise the control exists only on paper.
Cloud ERP programmes also need to consider the hosting and identity boundary, not just the application itself. Multi-Cloud Identity Guide is useful when access decisions span multiple cloud services, federated identities, and shared administrative patterns.
A good pre-go-live checkpoint is whether the team can answer three questions cleanly: who can do what, who approved it, and how will the organisation detect drift after launch. If those answers are not stable before go-live, the implementation is likely to shift the control problem into the production support phase.
Risk and Threat Considerations
Weak SoD design creates both fraud exposure and operational exposure. If the same person can create a vendor, approve a payment, and reconcile the ledger, the ERP environment can turn a process control weakness into a direct financial loss path. In a cloud deployment, broad access can also persist through inherited roles, making the risk harder to spot after cutover.
Failure mechanism: Conflicting entitlements, overbroad roles, or unmanaged emergency access allow one identity to bypass an intended control boundary, especially when testing focuses on transactions rather than end-to-end business authority.
Impact: The organisation may ship with preventable fraud paths, unusable compensating controls, audit findings, or a forced redesign after go-live when access changes are more disruptive and more expensive.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-5 — Separation of Duties | SoD is the core control issue in ERP role design and conflict prevention. |
| AC-6 — Least Privilege | Sensitive ERP access should be limited to the minimum permissions needed for each job function. | |
| Recommendation — Define conflicting duties and enforce role boundaries before production access is granted. Restrict ERP roles to the minimum access needed for each business task. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | ERP go-live access design depends on documented access control rules and approvals. |
| Recommendation — Document and enforce access control rules for ERP users and privileged functions. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | ERP go-live requires controlled account provisioning, access review, and restriction of sensitive access. |
| CIS-5 — Account Management | ERP role readiness depends on correct account lifecycle handling and privileged access assignment. | |
| Recommendation — Review, restrict, and remove ERP access that creates avoidable conflict or overexposure. Validate account assignments and remove unnecessary administrative access before go-live. | ||
Practitioner Guidance
What to verify: Confirm that every high-risk ERP process has an identified conflict matrix, an owner, and an approved treatment for any unavoidable overlap. If the team cannot explain the SoD rule in business terms, the rule is probably not ready for operational use.
Decision rule: If a role grants both execution and approval authority, treat it as a design exception that needs mitigation, not as a normal operating role. If an exception is temporary, define the expiry and the evidence required to remove it.
What good looks like: The go-live checklist shows that access has been tested against real business scenarios, sensitive roles are narrowly defined, and every remaining conflict has a named control owner and documented rationale.
Practitioner takeaway: The strongest pre-go-live programmes treat SoD as part of the system design, because controls are much harder to retrofit once business users begin relying on production access.
Related resources from NHI Mgmt Group
- How should security teams implement ERP access governance before go-live?
- How should security teams govern Oracle ERP Cloud access after go-live so controls do not drift out of date?
- Why do Oracle Cloud ERP access reviews often miss real segregation of duties risk?
- How should security teams extend segregation of duties controls across cloud procurement apps and ERP environments?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org