PO10.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: In-House and | [[Image:Key-control.jpg]]<br> | ||
:::a. SOX.4.3.1 | ::'''1. Risk: In-House and or Package applications may not meet all business and application control requirements.'''<br> | ||
:::a. [[SOX.4.3.1:|'''SOX.4.3.1''']] The organization acquires and or develops systems software in accordance with its acquisition, development and planning process.<br> | |||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
| Line 54: | Line 55: | ||
'''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]] 08:10, 23 June 2006 (EDT) | |||
Latest revision as of 12:10, 23 June 2006
PO 10.6 Project Phase Initiation
Control Objective:
Ensure that initiation of major project phases is formally approved and communicated to all stakeholders. Approval of the initial phase should be based on program governance decisions. Approval of subsequent phases should be based on review and acceptance of the deliverables of the previous phase, and approval of an updated business case at the next major review of the program. In the event of overlapping project phases, an approval point should be established by program and project sponsors to authorize project progression.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: In-House and or Package applications may not meet all business and application control requirements.
- a. SOX.4.3.1 The organization acquires and or develops systems software in accordance with its acquisition, development and planning process.
- a. SOX.4.3.1 The organization acquires and or develops systems software in accordance with its acquisition, development and planning process.
- 1. Risk: In-House and or Package applications may not meet all business and application control 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
All accounts that remain following the comparison to current system accounts should be investigated as they are most likely policy violations and the result of a breakdown with segregation of duties or possibly an instance of collusion.
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 08:10, 23 June 2006 (EDT)