Sign in
|
Help
Search
Harry Waldron - Corporate IT Security
Security Developments, Software Updates and Best Practices
RSS for Posts
Atom
RSS for Comments
Home
Contact
Community
Home
Blogs
Media
Groups
Email Notifications
Go
Archives
July 2009 (6)
June 2009 (26)
May 2009 (23)
April 2009 (34)
March 2009 (22)
February 2009 (22)
January 2009 (23)
December 2008 (21)
November 2008 (21)
October 2008 (22)
September 2008 (30)
August 2008 (23)
July 2008 (21)
June 2008 (22)
May 2008 (22)
April 2008 (26)
March 2008 (20)
February 2008 (21)
January 2008 (23)
December 2007 (27)
November 2007 (31)
October 2007 (40)
September 2007 (23)
August 2007 (32)
July 2007 (42)
June 2007 (34)
May 2007 (31)
April 2007 (27)
March 2007 (24)
February 2007 (25)
January 2007 (41)
December 2006 (42)
November 2006 (76)
October 2006 (32)
September 2006 (22)
August 2006 (33)
July 2006 (33)
June 2006 (46)
May 2006 (22)
April 2006 (31)
March 2006 (33)
February 2006 (22)
January 2006 (32)
December 2005 (36)
November 2005 (36)
October 2005 (20)
September 2005 (21)
August 2005 (43)
July 2005 (52)
June 2005 (30)
May 2005 (20)
April 2005 (25)
March 2005 (29)
February 2005 (63)
January 2005 (51)
December 2004 (20)
November 2004 (27)
October 2004 (26)
September 2004 (27)
August 2004 (43)
July 2004 (61)
June 2004 (106)
May 2004 (63)
April 2004 (31)
Personal Links
Recent Work Photo
Blue Ridge CPCU webmaster
Harry Waldron - MVP Profile
July 2007 - Technet Article
Jan 2008 - Technet Article
Sarbanes-Oxley - General Recommendations on how to achieve SOX compliancy
Posted
Tue, Jun 27 2006 20:44
by
Harry Waldron
Below is an updated list of recommendations, shared in the
Sarbanes-Oxley forums
... To me, the cornerstones for success include: Planning, Training, and Commitment ... Wishing all those companies who must adapt these standards, the upmost success
SOME GENERAL RECOMMENDATIONS FOR SOX IMPLEMENTATION
1. Set up a
Project Plan
for meeting SOX compliancy requirements (Research and explore what is needed prior to doing anything). Good planning will pay dividends for establishing this process.
2. Get
training
right away. The core team and especially the leader of the process should invest a week or so in training. Consider attending a formal seminar away from work where you can focus and interact with other participants. This will create a good foundation for what's required.
3. Perform an
inventory of all your IT applications.
Identify all of your financial systems and look for any indirect relationships.
4. In conjunction with the inventory,
examine the workflow
and human factors surrounding financial processing.
5. After the inventory, perform a
Risk Management study on all your financial applications
(looking at possibilities that someone could either accidently or alter financial records)
6. Look at ways of
strengthening the Financial process
and implement new controls (e.g., versioning, change management, and security)
7. Evaluate random sampling controls and requirements for your financial applications to setup a
testing/sampling program
on controls each quarter or month, depending on the needs.
8. Evaluate the
SOX 404 standards
for best practices associated with
IT control improvements
. Set up a plan to implement and improve standards. Evaluate the
COBIT 4.0
standards for IT controls over financial applications (note that COBIT 3.0 is the minimal acceptance level)
9. Work closely with both
internal and external auditors
and gain their approvals for the work that will be done.
10. Setup an
e-Library
(electronic documentation library) to include all your SOX documents, test plans, communications, etc.
11. Make sure you
obtain senior management support
for the process. It is an important aspect for implementing change. They must also support the additional work, human resources, and costs that will be needed to gain compliancy.
12. After the initial process is implemented,
continue to improve the SOX controls
and keep up-to-date with changes in business and legal requirements.