AI5.1:: 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: Development and maintenance of system with potential impact to financial reporting bypass processes for identifying business requirements, risks, and for designing needed controls.'''<br> | ||
:::a. SOX.1. | :::a. [[SOX.1.14:|'''SOX.1.14''']] Controls provide reasonable assurance that systems with potential impact to financial reporting are developed and maintained in a controlled manner through the use of a development methodology.<br> | ||
<br> | <br> | ||
::'''2. Risk: New program developments and/or changes may be made that are unnecessary or inappropriate.'''<br> | ::'''2. Risk: New program developments and/or changes may be made that are unnecessary or inappropriate.'''<br> | ||
:::a. SOX.6.1.3: Request for new applications or changes to existing applications should be appropriately considered and processed.<br> | :::a. [[SOX.6.1.3:|'''SOX.6.1.3''']] Request for new applications or changes to existing applications should be appropriately considered and processed.<br> | ||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
Revision as of 17:39, 21 June 2006
AI 5.1 Procurement Control
Control Objective:
Develop and follow a set of procedures and standards that is consistent with the business organization’s overall procurement process and acquisition strategy to ensure that the acquisition of IT-related infrastructure, facilities, hardware, software and services satisfies business requirements.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Development and maintenance of system with potential impact to financial reporting bypass processes for identifying business requirements, risks, and for designing needed controls.
- a. SOX.1.14 Controls provide reasonable assurance that systems with potential impact to financial reporting are developed and maintained in a controlled manner through the use of a development methodology.
- a. SOX.1.14 Controls provide reasonable assurance that systems with potential impact to financial reporting are developed and maintained in a controlled manner through the use of a development methodology.
- 1. Risk: Development and maintenance of system with potential impact to financial reporting bypass processes for identifying business requirements, risks, and for designing needed controls.
- 2. Risk: New program developments and/or changes may be made that are unnecessary or inappropriate.
- a. SOX.6.1.3 Request for new applications or changes to existing applications should be appropriately considered and processed.
- a. SOX.6.1.3 Request for new applications or changes to existing applications should be appropriately considered and processed.
- 2. Risk: New program developments and/or changes may be made that are unnecessary or inappropriate.
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.