Default Oracle Roles? Why Worry About Them?

Default Oracle Roles? Why Worry About Them?

What are Oracle’s Default Roles?

Each application in Oracle Fusion has a number of out-the-box Roles, including a ‘Manager’ or ‘Administrator’ Role for each process. These highly privileged Roles give access to all the key functionality for that process, along with some of the other access from other processes that it might need. Each process may consist of a number of applications – for example, the purchase-to-pay process includes Self Service Procurement, Procurement and Payables modules, each of which will have their own ‘Manager’ or ‘Administrator’ Role. As an example, the Payables Role is ‘Accounts Payable Manager’. This Role is a perfect example of one that triggers lots of Segregation of Duties conflicts, with it having the ability to record and approve invoices, prepare payments, manage purchase-to-pay business process configuration, including key configurable controls, and open and close accounting periods. Additionally it has access to enter and post journals without requiring approval (see the bitesize whitepaper on Subledger Journal Entries functionality).

We would recommend that organisations regularly review their list of Roles assigned to users, and if any of these are noted they should each be questioned and revoked down to something that’s segregated.

Which modules should you focus on?

I’d normally ask myself the question “what’s the risk I’m worried about?” If you are more focussed on financial risk (such as where organisations only use Fusion Financials) then I’d ignore default Roles relating to HCM Cloud, Marketing Cloud, etc, as long as they have not been assigned to users though if your focus is on confidentiality, then I’d definitely include HCM data in scope, along with greater focus on who has access to BI Administrator and BI Author Roles. When Systems Risk Services acted as the risk and controls lead for an implementation of Oracle HCM Cloud, we certainly made sure that access controls were restricted and that automated business process controls were implemented in the process, such as using HCM Data Roles to restrict the set of HR records that users could see.

What else should I be looking for?

From our experience, implementers often base their Oracle Roles on the out-the-box Roles – and many have been known to ‘tailor client access’ simply by creating a new Role that inherits the out-the-box Role, with no access removed. Based on this, the System Risk Services Access Analytics service includes a report to pick up users that have been assigned either the ‘default’ Roles, or where they have been assigned a ‘custom’ Role that inherits the out-the-box Roles. The report shows you which default Roles is the equivalent to the new one – and it’s always interesting reading.