on 2015 Apr 01 4:54 PM
Hello,
I am facing one weird issue in SoD ruleset. Whenever I am generating the SoD rules, critical permission value is being inserted in to the function.
Lets say If I generate the SoD rules in system automatically under Permissions tab the permission group !^ZQF0RM is adding to GL01 function and
!^FEBA_BANK_DEPOSIT is adding to FI03 function which it causes to enable the risks in SoD report at user level. FEBA_BANK_DEPOSIT or ZQF0RM are not tcodes.
Please let me know if anyone is facing the same issue.
Regards,
Kesava
Help others by sharing your knowledge.
AnswerRequest clarification before answering.
Hi Kesava,
What procedure are you following for rule set modification.
at front end side. you first add permission group in action tab. it reflects all the permissions(auth. object) under permission tab. there you can make changes in the permission values or insert a new permission.
Direct insertion of permission under permission tab gives the ^!permission error. you need to delete the that permission from permission tab and follow the above process.
you can check the permission table in se16.(table GRAC*PERMISSION*)
For critical Z risk., create a Zfunction, assign critical permission group to that function. create a Z risk, assign the Z function. save it and generate the rule set.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe there is a customer-configured SU24 entry for one of the tcodes in the functions? I highly recommend using permission-level rules; otherwise you will get thousands of false-positives.
-Ken
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kesava,
it is because of special characters
Check the below NOTE
2130951 - Explanation of ^! characters in Permission Only rules
Regards
Baithi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
Thanks for your response. I have checked the note 2130951 it explained how the special char ‘^!’ was introduced to distinguish between Action level/SoD risks and “Critical Permission” Risks.
In our case we have not defined any permission level risk intentionally. Whenever we generate the sod rules, these permission group with special characters have been auto inserted in to functions without any manual intervention. which we really don't required this critical permission. Though we have manually deleted it several times.
Regards,
Kesava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.