Skip to main content Accessibility help
×
Hostname: page-component-848d4c4894-75dct Total loading time: 0 Render date: 2024-06-12T13:13:40.073Z Has data issue: false hasContentIssue false

S - Sarbanes-Oxley Act of 2002 (SOX) to Structured design methodologies

Published online by Cambridge University Press:  17 May 2010

Robert Plant
Affiliation:
University of Miami
Stephen Murrell
Affiliation:
University of Miami
Get access

Summary

Definition: The Sarbanes-Oxley Act of 2002 was enacted to “protect investors by improving the accuracy and reliability of corporate disclosures made pursuant to the securities laws, and for other purposes” (Sarbanes-Oxley Act of 2002, Report 107-610).

Overview

The Sarbanes–Oxley Act of 2002 was a response to the financial reporting and disclosure problems associated with companies such as Enron, whose 2001 collapse was the largest bankruptcy in US history. This large and complex act pertains to corporate governance practices in public companies and contains eleven titles:

  1. Public company accounting oversight board

  2. Auditor independence

  3. Corporate responsibility

  4. Enhanced financial disclosures

  5. Analyst conflicts of interest

  6. Commission resources and authority

  7. Studies and reports

  8. Corporate and criminal fraud accountability

  9. White-collar crime penalty enhancements

  10. Corporate tax returns

  11. Corporate fraud and accountability

While the act is wide-reaching in scope and focuses on corporate and executive accountability for financial data, the maintenance of internal control structures, and the role of accounting firms in the audit process, for the CIO or IT professional it does not contain any specific systems requirements and in fact never even mentions the word computer in its 66 pages. However, it is clear that technology and information systems will be central to corporate compliance with the act.

The eleven titles of the act contain 69 sections, several of which are regarded as key from a CIO's perspective, including the following.

Type
Chapter
Information
An Executive's Guide to Information Technology
Principles, Business Models, and Terminology
, pp. 289 - 314
Publisher: Cambridge University Press
Print publication year: 2007

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

Hwang, K. (1992). Advanced Computer Architecture: Parallelism, Scalability, Programmability (New York, McGraw-Hill).Google Scholar
Day, K. (2003). Inside the Security Mind: Making the Tough Decisions (Englewood Cliffs, NJ, Prentice-Hall).Google Scholar
Day, K. (2003). Inside the Security Mind: Making the Tough Decisions (Englewood Cliffs, NJ, Prentice-Hall).Google Scholar
Chellis, J., Perkins, C., and Strebe, M. (2000). MCSE: Networking Essentials, Study Guide (Alameda, CA, Sybex Press).
Gralla, P. (2004). How the Internet Works (Indianapolis, IN, Que).Google Scholar
Groth, D. (2003). A+ Complete (Hoboken, NJ, Sybex–John Wiley and Sons).Google Scholar
Sommerville, I. (2004). Software Engineering (New York, Addison-Wesley).Google Scholar
R. Plant and R. Gamble (2003). “Methodologies for the development of knowledge-based systems 1982–2002,” Knowledge Engineering Review, Volume 18, No. 1.
Fenton, N. (1991). Software Metrics (London, Chapman and Hall).Google Scholar
Hollander, N. (2000). A Guide to Software Package Evaluation and Selection: The R2 ISC Method (New York, American Management Association).Google Scholar
Zdziarski, J. (2005). Ending Spam: Bayesian Content Filtering and the Art of Statistical Language Classification (San Francisco, CA, No Starch Press).Google Scholar
Muris, T., Thompson, M., Swindle, O., Leary, T., and Harbour, P. (2004). National Do Not Email Registry: A Report to Congress (Washington, DC, Federal Trade Commission).Google Scholar
B. Schneier (2004). “Customers, passwords, and web sites,” IEEE Security and Privacy, Volume 2, No. 4.
Associated terminology: Phishing, Virus, Trojan horse, Worm.
E. Schultz (2003). “Pandora's box: spyware, adware, autoexecution, and NGSCB,” Computers and Security, Volume 22, No. 5.
Associated terminology: Advertising, Virus, Trojan horse, Phishing.
Yourdon, E. (1979). Classics in Software Engineering (New York, Yourdon Press).Google Scholar
Myers, G. (1974). Reliable Software through Composite Design (New York, Mason and Lipscomb Publishers).Google Scholar

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×