The Components Of GRC 5.1: Questions

5434 Words 22 Pages
Register to read the introduction… Which SOX rules got inherited in SAP GRC? 17. How many types of Background job you are familiar with? Why Role/Profile & U ser Sync. job is required? 18. Where from can we change the default expiration time for mitigating controls …show more content…
From a security perspective it automa tes monitoring of SoD's, allows automated provisioning of emergency access and a utomation of the user provisioning process Security Q's: Explain the authorisation concept in detail Explain how config relates to security Explain why SU53 is not always accurate GRC Q's: Explain in detail how the different components of the Access Controls suite inte grate with each other Explain the key problem areas in implementation of RAR Explain the key problem areas in implementation of CUP Some GRC Questions: 1. What are the components of GRC? 2. What are the upgrades happened in GRC 5.3 from GRC 5.2? 3. Is it possible to have a request type by which we can change the validity per iod of a user? If possible, then what are the actions? 4. What's the latest Support Pack for GRC 5.3? How it differs from the previous one? 5. What are the issues faced by you in ERM & CUP after golive? 6. Can we change Single roles, objects & Profile description through mass mainte nance of role? If yes, how? 7. What are the prerequisites for creating a workflow for user provisioning? 8. How will you control GRC system if you have multiple rulesets activated? 9. Can we view the changes of a role, happened in PFCG, through GRC? 10. How will you mitigate a user against an authorization object which is decide d as sensitive by Business? 11. Give an example of SOD with object level control & also decide the Risk impl ication from …show more content…
8)Difference b/w su22 and su24 ? 9)what is the landscape of GRC? 10)What is the difference between Template role & Derive role? 1. we can create roles , transport , copy , download,modifications , all these thing done from pfcg tcode. 2.parameters : when ever user want some defaults values when ever he/she excute the t-code we can mainatian some pid's by taking help of abapers. group : based on user roles and responsibiltes security admin can asssign to particular group. personalization : this data provides by sap itself based on t-codes which are maintained at menu tab. 3. using mini apps we can add some third party functionality 6.remedy tools and some comapny internal tools used for geeting issues from client side . 7.lsmw is used for creating large number of user at a time . 8.su22 is maintaind standard t-codes and thier standard autorisation object ( usobx and usobt ). su24 : here we can mainatin customer related t-code and their authorisation objects ( usobx_c and usobt_c ). 9.grc land scape develop and production . 9. tempaltes rrole : it is provided by sap it self. dervide role : a role which is derived from a master role it can inherit the menu structure t-codes and all but it cant inherit the organisation level , here we can maintain orgnisation levels only . 4) Change documents cannot be displayed in transaction 'SUIM' after they are transported to the production system because we do not have the 'befor input' method for the

Related Documents