AI2.6:
AI 2.6 Major Upgrades to Existing Systems
Control Objective:
Follow a similar development process as for the development of new systems in the event of major changes to existing systems that result in significant change in current designs and/or functionality. Issues to consider include impact analysis, cost/benefit justification and requirements management.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability, performance and resilience requirements.
- a. SOX.6.1.1 The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability performance and resilience requirements.
- a. SOX.6.1.1 The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability performance and resilience requirements.
- 1. Risk: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability, performance and resilience requirements.
- 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.
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:19, 23 June 2006 (EDT)