View source for AI6.3:

'''AI 6.3 Emergency Changes'''
<br>
<br>
'''Control Objective:'''
<br>
<br>
Controls provide reasonable assurance that system changes of financial reporting significance are authorized and appropriately tested before being moved to production. 
<br>
<br>
In addition, establish a process for defining, raising, assessing and authorizing emergency changes that do not follow the established change process. Documentation and testing should be performed, in some instances, after implementation of the emergency change.
<br> 
<br>
'''Applicability:'''
<br>
<br>
:: '''Sarbanes-Oxley'''
:: HIPAA
:: GLBA
:: PCI
:: FISMA
:: NIST SP 800-66
:: Ditscap
:: Control Exception
:: User Defined
<br>
'''Risk Association Control Activities:'''
<br>
<br>
[[Image:Key-control.jpg]]<br>
::'''1.	Risk: Controls provide reasonable assurance that policies and procedures that define required acquisition and maintenance processes have been developed and are maintained, and that they define the documentation needed to support the proper use of the applications and the technological solutions put in place.'''
:::a.	[[SOX.6.1.1:|'''SOX.6.1.1''']] The organization has policies and procedures regarding program development, '''''program change''''', access to programs and data, and computer operations, which are periodically reviewed, updated and approved by management.
<br>
<br>
[[Image:Key-control.jpg]]<br>
::'''2.	Risk: System integrity and availability is compromised because emergency changes are made without management approval.'''
:::a.	[[SOX.6.1.4:|'''SOX.6.1.4''']] Emergency change requests are documented and subject to formal change management procedures. 
<br>
<br>

'''Implementation Guide:'''
<br>
Confirm that the organization has policies and procedures that are reviewed and updated regularly for changes in the business. When policies and procedures are changed, determine if management approves such changes. Select a sample of projects and determine that user reference and support manuals, systems documentation and operations documentation were prepared. Consider whether drafts of these manuals were incorporated in user acceptance testing. Determine whether any changes to proposed controls resulted in documentation updates.
<br>
<br>
'''Process Narrative'''
<br>
Insert a description of the process narration that is applicable to the existing control statement this narrative refers to.
<br>
<br>
'''Process Illustration'''
<br>
Insert a process diagram, flowchart or other visual representation here to illustrate the process narrative.
<br>
<br>
[[Image:Someimage.jpg]]
<br>
<br> 
'''Control Commentary'''
<br>
Insert a description of the control that is applicable to the existing control statement this commentary refers to.
<br>
<br>
'''Control Exception Commentary'''
<br>
Insert a description of the control exception that is applicable to the existing control statement this commentary refers to.
<br>
<br>
'''Evidence Archive Location'''
<br>
Insert Evidence Description Here.
<br> 
<br>
'''Control Status and Auditors Commentary'''
<br>
Describe the condition of the applicable control and its effectiveness. Set the color icon to a redlock.jpg, yellowlock.jpg or greenlock.jpg.
<br>
<br>
[[Image:redlock.jpg]]
<br>
<br>
'''Remediation Plan'''
<br>
Insert remediation plan, applicability, or any information that indicates what needs to be done.
<br>
<br>
'''Supplemental Information:'''
<br>
ITIL Service Support, Change Management.
<br>

ITIL 8.2 Scope of change management Service Support.
<br>

ITIL Change Management.
<br>

ITIL 8.3.2 Change advisory board.
<br>

ISO 8.1 Operational procedures and responsibilities 10.5 Security in development and support processes.
<br>
<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>

--[[User:Mdpeters|Mdpeters]] 15:02, 22 June 2006 (EDT)