AI7.6:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
'''Risk Association Control Activities:'''<br> | '''Risk Association Control Activities:'''<br> | ||
<br> | <br> | ||
::'''1. Risk: | ::'''1. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.'''<br> | ||
:::a. SOX. | :::a. [[SOX.1.10:|'''SOX.1.10''']] Obtain a listing of key system development and maintenance projects and, for a sample, obtain evidence that each project is properly tested and approved.<br> | ||
[[Image:Key-control.jpg]]<br> | |||
::'''2. Risk: Controls provide reasonable assurance that the systems are appropriately tested and validated prior to being placed into production processes, and associated controls operate as intended and support financial reporting requirements.'''<br> | |||
:::a. [[SOX.5.4:|'''SOX.5.4''']] A testing strategy is developed and followed for all significant changes in applications and infrastructure technology, which addresses unit, system, integration and user-acceptance-level testing so that deployed systems operate as intended.<br> | |||
<br> | <br> | ||
::''' | ::'''3. Risk: Application or system changes may disrupt business processes or corrupt production data stores.'''<br> | ||
:::a. SOX.1. | :::a. [[SOX.6.1.8:|'''SOX.6.1.8''']] Only properly authorized and tested changes are migrated to the production environment.<br> | ||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
| Line 57: | Line 60: | ||
'''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]] 10:57, 23 June 2006 (EDT) | |||
Latest revision as of 14:57, 23 June 2006
AI 7.6 Testing of Changes
Control Objective:
Ensure that changes are tested in accordance with the defined acceptance plan and based on an impact and resource assessment that includes performance sizing in a separate test environment by an independent (from builders) test group before use in the regular operational environment begins. Parallel or pilot testing should be considered as part of the plan. The security controls should be tested and evaluated prior to deployment, so the effectiveness of security can be certified. Fallback or back out plans should also be developed and tested prior to promotion of the change to production.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.
- a. SOX.1.10 Obtain a listing of key system development and maintenance projects and, for a sample, obtain evidence that each project is properly tested and approved.
- a. SOX.1.10 Obtain a listing of key system development and maintenance projects and, for a sample, obtain evidence that each project is properly tested and approved.
- 1. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.
- 2. Risk: Controls provide reasonable assurance that the systems are appropriately tested and validated prior to being placed into production processes, and associated controls operate as intended and support financial reporting requirements.
- a. SOX.5.4 A testing strategy is developed and followed for all significant changes in applications and infrastructure technology, which addresses unit, system, integration and user-acceptance-level testing so that deployed systems operate as intended.
- a. SOX.5.4 A testing strategy is developed and followed for all significant changes in applications and infrastructure technology, which addresses unit, system, integration and user-acceptance-level testing so that deployed systems operate as intended.
- 2. Risk: Controls provide reasonable assurance that the systems are appropriately tested and validated prior to being placed into production processes, and associated controls operate as intended and support financial reporting requirements.
- 3. Risk: Application or system changes may disrupt business processes or corrupt production data stores.
- a. SOX.6.1.8 Only properly authorized and tested changes are migrated to the production environment.
- a. SOX.6.1.8 Only properly authorized and tested changes are migrated to the production environment.
- 3. Risk: Application or system changes may disrupt business processes or corrupt production data stores.
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 10:57, 23 June 2006 (EDT)