How do you Run Risk Analysis on more than one open requests for same user?

[jonathon_sells3]

For example, User1 requests RoleA and RoleB together a single request. The Risk analysis is run against both roles.

Then say later on, the  User1 requests another role. So they proceed to request RoleC. Now there are 2 separate requests in GRC.

So how can these 2 separate requests be grouped automatically during the Run Risk Analysis?

To clarify further, if a role owner has to run the risk analysis on RoleA, the system will take RoleB into consideration because it's on the same requests but how do we force any and all other open requests to be processed in the RA for the same user?

Thank you

Jon

[jonathon_sells3]

SAP IDM does have it's benefits. In addition to SAP ABAP and Java provisioning, IDM allows you to provision to non SAP systems like Active Directory, HANA, Operating Systems, Databases, Email Servers and other various Cloud Services. It's very customizable.

After discussing with my GRC team, the limiting of a single open request per system would not be effective in our large landscape. They mentioned several unintended consequences with the biggest concern of how long open requests take to fulfill.

So this issue of In Process GRC requests was an issue here when we used CUP and would still be an issue with ARM.

Granted multiple Business Roles were grouped in CUP when requested at the same time, but we still had users request business roles over time that were in flight resulting in multiple in process requests.

[Former Member]

Jonathon Sells wrote:



After discussing with my GRC team, the limiting of a single open request per system would not be effective in our large landscape. They mentioned several unintended consequences with the biggest concern of how long open requests take to fulfill.

Jon,

Why does it take so long for requests to go through your approval process? Not enough role approvers/ lack of backup role approvers? Easily correctable. Role approval required for many roles that are display only/ not really sensitive? Not difficult to remedy. Role approvers sit on the requests too long? Funny thing is, when the managers and requesters start calling up the role approvers and asking them what the heck  is taking so long for them  to make a decision, role approvers start taking action on requests more timely.  What else causes slow processing of requests? We have found that a lot of it is training issues, and most of our multi-system GRC requests are closed and provisioned in 24 hours or less, unless there are SOD exceptions to be mitigated.

Cheers,

Gretchen