SOX.1.3:: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
[[Image:Key-control.jpg]] | [[Image:Key-control.jpg]] | ||
<br> | <br> | ||
::'''1. Risk: The transfer of programs into the live environment | ::'''1. Risk: The transfer of programs into the live environment is not appropriately controlled.'''<br> | ||
:::a. [[SOX.1.3:|'''SOX.1.3''']] | :::a. [[SOX.1.3:|'''SOX.1.3''']] IT management implements system software that does not jeopardize the security of the data and programs being stored on the system. | ||
<br> | |||
<br> | <br> | ||
<br> | <br> | ||
| Line 11: | Line 12: | ||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | <blockquote style="background: white; border: 1px solid black; padding: 1em;"> | ||
1. Determine that a risk assessment of the potential impact of changes to system software is performed. | 1. Determine that a risk assessment of the potential impact of changes to system software is performed. | ||
<br> | |||
2. Review procedures to test changes to system software in a development environment before they are | 2. Review procedures to test changes to system software in a development environment before they are | ||
applied to production. | applied to production. | ||
<br> | |||
3. Verify that backout procedures exist. | 3. Verify that backout procedures exist. | ||
</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 19:58, 23 June 2006
- 1. Risk: The transfer of programs into the live environment is not appropriately controlled.
- a. SOX.1.3 IT management implements system software that does not jeopardize the security of the data and programs being stored on the system.
Testing Procedures
1. Determine that a risk assessment of the potential impact of changes to system software is performed.
2. Review procedures to test changes to system software in a development environment before they are applied to production.
3. Verify that backout procedures exist.
Testing Frequency
Annually
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.