Sarbanes-Oxley: Difference between revisions
From ETHW
No edit summary |
m (Text replace - "[[Category:Computers_and_information_processing" to "[[Category:Computing and electronics") |
||
| Line 18: | Line 18: | ||
[[Category:Management]] | [[Category:Management]] | ||
[[Category:Organizational_aspects]] | [[Category:Organizational_aspects]] | ||
[[Category: | [[Category:Computing and electronics]] | ||
[[Category:Software_&_software_engineering]] | [[Category:Software_&_software_engineering]] | ||
[[Category:Capability_maturity_model]] | [[Category:Capability_maturity_model]] | ||
Revision as of 16:15, 22 July 2014
Sarbanes-Oxley & Data Management
Introduced in 2002 in response to a spate of billion dollar bodgy high tech company crashes, the Sarbanes-Oxley governance requirements is directed toward accountancy and management practices, It also has significant impacts to computer data staorge, security and the data management.
Dissappointingly, this is often still fresh news to many IT specialists in 2009.
Sarbanes Oxley Overview for Technologists
Assurance Roles
For those technologists undertaking IT assurance and technology audit roles, many jurisdictions have introduced 'Auditor Independence' laws, in Australia this is known as CLERP 9. Other countries will have related laws.
