Discussion on:

6
Comments

Join the conversation!

Follow via:
RSS
Email Alert
0 Votes
+ -
This is a wonderful article. However, compliance on current systems was required by 12-31-04. New systems must be documented and tested as they are procured or created.

This would have been excellent guidance for when I started my process in the middle of 2003.

Thank you.
0 Votes
+ -
Still timely
wordworker 24th Jan 2005
I agree this is a very useful article. However I must point out that it is still very timely for firms for whom the Sox compliance deadline is still to come -- public companies under $75 Mln, some with overseas operations, and some whose fiscal 2004 doesn't end until 2005.
0 Votes
+ -
The date by which a company has to be compliant is driven by their fiscal calendar. This isn't Y2K where all systems needed to be compliant by a common date.

There are many companies still undergoing testing and remediation.
0 Votes
+ -
...Compliance isn't a once-and-out exercise. S-Ox audits are with us for the long run. Every year auditors will come looking for evidence of remediation and to make sure no new issues have arisen.
One item mentioned repeatedly was effectivness. Get real! There is never enough time or money to do it right. Get it done - get us in compliance and we'll worry about tomorrow later.
0 Votes
+ -
Pls visit www.approva.net and take a look at their product offerings for enterprise controls management
Keyboard Shortcuts:
Prev
Next
Toggle
Join the conversation
Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

Join the TechRepublic Community and join the conversation! Signing-up is free and quick, Do it now, we want to hear your opinion.