PO10.9:: Difference between revisions

From HORSE - Holistic Operational Readiness Security Evaluation.
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
Line 19: Line 19:
'''Risk Association Control Activities:'''<br>
'''Risk Association Control Activities:'''<br>
<br>
<br>
::'''1. Risk: Business requirements are not met or inadequately tested.'''<br>
[[Image:Key-control.jpg]]<br>
:::a. SOX.1.16: Controls provide reasonable assurance that systems with potential impact to financial reporting are designed to minimize risk.<br>
::'''1. Risk: Controls provide reasonable assurance that policies and procedures that define required acquisition and maintenance processes have been developed and are maintained.'''<br>
:::a. [[SOX.1.16:|'''SOX.1.16''']] The organization develops its systems and applications in accordance with its supported, documented policies and procedures.<br>
<br>
<br>
::'''2. Risk: Security and business requirements are not check listed adequately, enforced, and tested. Project checkpoints may fail as a result.'''<br>
::'''2. Risk: Security and business requirements are not check listed adequately, enforced, and tested. Project checkpoints may fail as a result.'''<br>
:::a. SOX.1.17: Controls provide reasonable reassurance that project risks are managed.<br>
:::a. [[SOX.1.17:|'''SOX.1.17''']] Controls provide reasonable reassurance that project risks are managed.<br>
<br>
<br>
'''Implementation Guide:'''<br>
'''Implementation Guide:'''<br>
Line 57: Line 58:
'''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:37, 23 June 2006 (EDT)

Latest revision as of 12:37, 23 June 2006

PO 10.9 Project Risk Management

Control Objective:

Eliminate or minimize specific risks associated with individual projects through a systematic process of planning, identifying, analyzing, responding to, monitoring and controlling the areas or events that have the potential to cause unwanted change. Risks faced by the project management process and the project deliverable should be established and centrally recorded.

Applicability:

Sarbanes-Oxley
HIPAA
GLBA
PCI
FISMA
NIST SP 800-66
Ditscap
Control Exception
User Defined


Risk Association Control Activities:


1. Risk: Controls provide reasonable assurance that policies and procedures that define required acquisition and maintenance processes have been developed and are maintained.
a. SOX.1.16 The organization develops its systems and applications in accordance with its supported, documented policies and procedures.


2. Risk: Security and business requirements are not check listed adequately, enforced, and tested. Project checkpoints may fail as a result.
a. SOX.1.17 Controls provide reasonable reassurance that project risks are managed.


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:37, 23 June 2006 (EDT)