SOX.1.2:: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
<br> | <br> | ||
</blockquote> | </blockquote> | ||
<br> | |||
'''Testing Frequency''' | '''Testing Frequency''' | ||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | <blockquote style="background: white; border: 1px solid black; padding: 1em;"> |
Latest revision as of 13:39, 22 June 2006
- 1. Risk: Business requirements are not met or inadequately tested. Systems produce inaccurate results or do not meet usability requirements. A project that does not meet business requirements for internal controls at a milestone may continue without review and approval.
- a. SOX.1.2: IT management involves users in the design of applications, selection of packaged software and the testing thereof, to maintain a reliable environment.
Testing Procedures
Review the SDLC methodology to determine if it addresses application controls. Consider whether there are appropriate steps so that application controls are considered throughout the development or acquisition life cycle, e.g., application controls should be included in the conceptual design and detailed design phases.
Testing Frequency
This should be an integral part of development in house. During the planning stages of development security, availability, and processing integrity must be considered.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
Provide control steward commentary indicating the formal methodology in place.
Control Steward – Jane Manager
Process Illustration
Replace this test by inserting a process diagram, flowchart or other visual representation to illustrate the process narrative as necessary. Include a brief description of the process illustration.
Control Status and Auditors Commentary
The control is effective.
File:Greenlock.jpg
Status is acceptable.
Control Exception Commentary
Status is acceptable.
Remediation Plan
Remediation is not required at this time.