As security is such a major theme on the Act, many organizations are using the international ISO standards. The ISO 27001 Portal outlines these. A copy of the standards, and security policies, can be obtained via the ISO 17799 Toolkit.
Our server logs indicate some interesting mis-spellings: Sarbannes Oxley, Sorbane Oxley, Sarbanne Oxley, Sarbaines Oxley, Sarbanesoxley, Sorbanes Oxley, Sabanes Oxley, Sarbane Oxley, and Sarbanes Oaxley, to name but a few!
Sarbanes-Oxley Act Forum: Forums
The Sarbanes Oxley Act :: View topic - SOD on release management
Posted: Fri Jun 15, 2012 4:36 am Post subject: SOD on release management
I'm working for the operation management department for a manufacturer. I have a question about reducing the cost for the segregation of duties for the release management.
This is the rule that has been instituted at my company:
-Separate the developers from the people who are releasing program for the live environments
We have some operators who release our programs to the live environments. Sometimes the programmers request the operators to release their program at night or upon immediate request. These requests increase our operation costs a lot. How do you achieve the SOD using release management but do so at a reasonable cost?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Trademarks referenced on the SOX Act Forum are property of their respective owners. Comments are property of their respective posters. Sarbanes-Oxley Act Implementation Portal: Sarbanes Oxley compliance, information, software, & internal audit committee resources. Sarbox. Site source is copyright nuke (c)2003, and is Free Software under the GNU / GPL licence agreement. All Rights Are Reserved.