Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Jim Wells, I didn't know how difficult will be to work with SOD's conflicts. The worst part is that the client still doesn't believe that he is never going be free of SOD conflicts and that we as Security Admin don't have SOD's manual or document to follow. I explained to the customer that the best option for them is to install GRC. The client was expecting me to give them a good solution to their problem and to maintain the system free of SOD conflicts. Thank you very much for your input on this matter. Sincerely, Lord Vader ---------------Original Message--------------- From: james.wells Sent: Thursday, July 08, 2010 4:20 PM Subject: How to remediate issues with Segregation of Duties > Well let's start with the first thing you need to do. You must either gather a group of people using the applications or find a "canned" set of SOD issues that your client trusts. SOD parameters are like anything else in IT, they are often fluid and changing, and due to that fact while there are some pretty hard and fast rules, there is no list that will work entirely for your client. This is the most difficult part of SOD resolution. For making roles it is a good idea to put a lot of the SOD parameters into their own role, so as people move around in the company it is easier to confront the "new" SOD issues with the change of people's job roles. I am sorry I have to stop here. Great questions! Jim Wells | __.____._ Copyright © 2010 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Related Content White Papers In the Spotlight _.____.__ |