Skip to Content
0
Former Member
May 07, 2013 at 09:29 PM

S_Develop and Debug Implications and Risks

2439 Views

Can anyone provide some more specific examples of implications/risks of this access?

I have seen lots of comments about how authorization object S_Develop with debug object type is not allowed in production in order to deal with us lovely auditors. I haven't seen any discussion about the potential implications, how a user could exploit these issues, etc...

I found that users can edit tables via SE16N if they have debug access. I've also seen that it allows users to bypass standard authorizations. There has to be some big, easily identifiable implications. I would just like to understand some other scenarios, if possible. Thank you.