GRC: Integrated Risk Management On-Demand Course for Xanadu - Create manual and group factors issue

Sentinel
Kilo Expert

Hi all,

I am currently doing the Xanadu version for the IRM on-demand course. I have completed the same course in older versions such as Washington with no issues however I have ran into a full stop with the Xanadu version and suspect that the simulation instance is not working as intended.

After I enable advanced risk assessment as the system admin and impersonate Reem Abbott I can not access the Risk Assessment Methodologies page at all. Additionally it seems that the required role to access the RAM page ( sn_risk_advanced.ara_admin ) does not exist in the instance, check screenshots below:

I am hard stuck and can't proceed with the course and I am not sure how to fix it. I can try to delete the instance and re-do the course from start once again but I am afraid that it will yield the same result as everything seems to have went bananas after advanced risk assessments was activated as the roles are not created in the system (even though the RAM page specifically requires the role!)

Has anyone of you also stumbled upon the same issue, and do you maybe have a fix for it?

Thank you in advance!

1 ACCEPTED SOLUTION

Sentinel
Kilo Expert

In case anyone stumbles upon the same issue, terminating instance and requesting a new one worked wonders for me.

View solution in original post

5 REPLIES 5

Community Alums
Not applicable

Hi @Sentinel ,

Since you have Admin access, no need to worry about roles which enables you to see the module !! What is important here is whether you have checked "Migrate to Advanced Risk Assessments" under Properties or not :

SandeepDutta_0-1731903630212.png

Then, you can see the RAM Module populating below Properties , like below:

SandeepDutta_1-1731903686742.png

 

Hi Sandeep,

I tried creating a new lab instance and activate advanced risk assessment right away and get the following error:

Access to api 'setValue(sys_app_module.active)' from scope 'sn_risk' has been refused due to the api's cross-scope access policy.
Write operation against 'sys_app_module' from scope 'sn_risk' has been refused due to the table's cross-scope policy.

Any suggestions?

Sentinel
Kilo Expert

In case anyone stumbles upon the same issue, terminating instance and requesting a new one worked wonders for me.

Brett_W
Tera Contributor

I find myself completely stuck on this step now too. Is there a step by step guide  on how to do this? Also, it seems I was able to complete this in the Utah version of the lab without problems.