Sarbanes-Oxley (SOX) Impact on Security In Software
The following chart is an example of an security assessment matrix that may be used to evaluate security impact of various regulations to software development projects. This is just an example for use in the case of Sarbanes-Oxley. Most of the countermeasures are commonly known. By using this matrix approach, it is possible to get a rough understanding of possible requirements to expect from customers/end users.
Read the Complete Paper
Current Tags:
None
Add Tags:
|
Current Rating:
 (0 votes)
Add Rating:
|
Similar content:
The Impact of the Sarbanes-Oxley Act on IT Security, in
Sarbanes Oxley
Security and Sarbanes-Oxley, in
Sarbanes Oxley
The Role of IT Security in Sarbanes-Oxley Compliance, in
Sarbanes Oxley
An Overview of Sarbanes-Oxley for theInformation Security Professional, in
Sarbanes Oxley
Sarbanes, Oxley and You, in
Sarbanes Oxley
Post Comment
Cite in Modern Language Association (MLA) Style
"Sarbanes-Oxley (SOX) Impact on Security In Software" www.developer.com, , UTC.
04 Jul 2008, 11:13
<http://www.developer.com/security/print.php/3320861>
Cite in Chicago Style
, "Sarbanes-Oxley (SOX) Impact on Security In Software," http://www.developer.com/security/print.php/3320861 (accessed
Jul 04, 2008
).
