AI3.4:: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 20: | Line 20: | ||
<br> | <br> | ||
::'''1. Risk: The transfer of programs into the live environment may not be appropriately controlled.'''<br> | ::'''1. Risk: The transfer of programs into the live environment may not be appropriately controlled.'''<br> | ||
:::a. SOX.1.3: | :::a. [[SOX.1.3:|'''SOX.1.3''']] Post implementation reviews are performed to verify that controls are operating effectively.<br> | ||
<br> | |||
[[Image:Key-control.jpg]]<br> | |||
::'''1. Risk: Production processes, and associated controls operate as intended and support financial reporting requirements.'''<br> | |||
:::a. [[SOX.1.21:|'''SOX.1.21''']] Interfaces with other systems are tested to confirm that data transmissions are complete, accurate and valid.<br> | |||
<br> | <br> | ||
::'''2. Risk: Application and/or program changes may not meet all control requirements or may negatively impact existing processing.'''<br> | ::'''2. Risk: Application and/or program changes may not meet all control requirements or may negatively impact existing processing.'''<br> | ||
:::a. SOX.6.1.4: Application and/or program changes should be tested to ensure that they achieve the necessary application, business, and user control requirements and that they do not negatively impact existing processing.<br> | :::a. [[SOX.6.1.4:|'''SOX.6.1.4''']] Application and/or program changes should be tested to ensure that they achieve the necessary application, business, and user control requirements and that they do not negatively impact existing processing.<br> | ||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
| Line 57: | Line 61: | ||
'''Implementation guidance'''<br> | '''Implementation guidance'''<br> | ||
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.<br> | Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.<br> | ||
--[[User:Mdpeters|Mdpeters]] 09:02, 23 June 2006 (EDT) | |||
Latest revision as of 13:02, 23 June 2006
AI 3.3 Infrastructure MaintenanceAI 3.4 Feasibility Test Environment
Control Objective:
Establish development and test environments to support effective and efficient feasibility and integration testing of applications and infrastructure in the early stages of the acquisition and development process. Consider functionality, hardware and software configuration, integration and performance testing, migration between environments, version control, test data and tools, and security.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: The transfer of programs into the live environment may not be appropriately controlled.
- a. SOX.1.3 Post implementation reviews are performed to verify that controls are operating effectively.
- a. SOX.1.3 Post implementation reviews are performed to verify that controls are operating effectively.
- 1. Risk: The transfer of programs into the live environment may not be appropriately controlled.
- 1. Risk: Production processes, and associated controls operate as intended and support financial reporting requirements.
- a. SOX.1.21 Interfaces with other systems are tested to confirm that data transmissions are complete, accurate and valid.
- a. SOX.1.21 Interfaces with other systems are tested to confirm that data transmissions are complete, accurate and valid.
- 1. Risk: Production processes, and associated controls operate as intended and support financial reporting requirements.
- 2. Risk: Application and/or program changes may not meet all control requirements or may negatively impact existing processing.
- a. SOX.6.1.4 Application and/or program changes should be tested to ensure that they achieve the necessary application, business, and user control requirements and that they do not negatively impact existing processing.
- a. SOX.6.1.4 Application and/or program changes should be tested to ensure that they achieve the necessary application, business, and user control requirements and that they do not negatively impact existing processing.
- 2. Risk: Application and/or program changes may not meet all control requirements or may negatively impact existing processing.
Implementation Guide:
Process Narrative
Insert a description of the process narration that is applicable to the existing control statement this narrative refers to.
Process Illustration
Insert a process diagram, flowchart or other visual representation here to illustrate the process narrative.
File:Someimage.jpg
Control Commentary
Insert a description of the control that is applicable to the existing control statement this commentary refers to.
Control Exception Commentary
Insert a description of the control exception that is applicable to the existing control statement this commentary refers to.
Evidence Archive Location
Insert Evidence Description Here.
Control Status and Auditors Commentary
Describe the condition of the applicable control and its effectiveness. Set the color icon to a redlock.jpg, yellowlock.jpg or greenlock.jpg.
File:Redlock.jpg
Remediation Plan
Insert remediation plan, applicability, or any information that indicates what needs to be done.
Supplemental Information:
Implementation guidance
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.
--Mdpeters 09:02, 23 June 2006 (EDT)