ERP SECURITY & SEGREGATION OF DUTIES
Control access without making the ERP impossible to use.
Security design should reduce fraud and audit risk while preserving workable business roles. In D365, it should also account for license implications.
Role & access review
Understand who can do what today and whether access reflects actual job responsibility.
SoD conflict analysis
Identify combinations of access that create unacceptable control risk across finance and operations.
Remediation design
Remove unnecessary access, redesign roles, or establish documented mitigating controls where separation is impractical.
Audit readiness
Build repeatable evidence, ownership, review cadence, and change control instead of reconstructing security decisions during audit.
D365 license awareness
Review role assignments with an understanding that access design can affect license tier and cost.
Governance
Establish joiner/mover/leaver process, periodic access review, privileged-access control, and ownership.
THE GOAL
Security that survives both an audit and a Tuesday afternoon.
Overly permissive roles create risk. Overly restrictive roles drive users into shared logins, workarounds, or repeated access exceptions. Good ERP security is specific enough to control risk and practical enough to become the normal way of working.
NEXT STEP
Worried about an SoD or access-control gap?
Start with the current role design, known conflicts, audit pressure, and how users actually perform their jobs.