RAR connections and background job setup

[Former Member]

Hi,

I am considering connecting my SAP DEV environment to my PRD RAR instance for role testing purposes.

I am wondering is it normal setup to connect SAP DEV systems to PRD RAR?

Also I dont want to run background jobs against SAP DEV (as users have board access) and only want to run these against certain SAP production systems. However there doesn't seem to be a way to specify multiple systems in the background jobs. It is either one system or all. Can anybody advise on best practice in this area?

Thanks,

[Rich_Turnquist · Accepted solution]

I would normally agree not to point to prod RAR from Dev, but if you use ERM and create your roles in your DEV system, you need to have all your system connections the same (Prod and Dev). So we use prod RAR to run risk analysis on our new roles in Dev (from ERM).

Is this the exception to the rule?

thanks,

Peggy

[koehntopp · Accepted solution]

Pointing DEV to Prod. RAR is completely standard if you either use ERM and/or Risk Terminator for role changes.

You just want to make sure you keep it out of management reports by not including the systems in background analysis jobs.

Frank.

[Former Member · Accepted solution]

Peggy,

For this case, our Dev RAR is connected to DEV ERM and Prod and Dev rulesets are in sync. We use a sandbox for all the ruleset, mitigation and Support pack testing.

Alpesh

[Former Member · Accepted solution]

Thank you all for your feedback on this. Yes the reason that I want to connect DEV SAP to PRD GRC is to be able to analyse role changes. I was concerned about the performance impacts if I could not restrict the management reports from running against DEV SAP systems. However as this is possible, it allows me just to run these against the production systems.

Thanks,

Gary

Edited by: Gary McSherry on May 25, 2010 10:49 AM