PO9.1:: Difference between revisions

From HORSE - Holistic Operational Readiness Security Evaluation.
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 20: Line 20:
<br>
<br>
[[Image:Key-control.jpg]]<br>
[[Image:Key-control.jpg]]<br>
::'''2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.'''<br>
::'''1. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.'''<br>
:::a. [[SOX.2.7.1:|'''SOX.2.7.1''']] End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.<br>
:::a. [[SOX.2.7.1:|'''SOX.2.7.1''']] End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.<br>
<br>
<br>

Latest revision as of 14:10, 8 August 2006

PO 9.1 IT and Business Risk Management Alignment

Control Objective:

Integrate the IT governance, risk management and control framework with the organization’s (enterprise’s) risk management framework. This includes alignment with the organization’s risk appetite and risk tolerance level.

Applicability:

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


Risk Association Control Activities:


1. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.
a. SOX.2.7.1 End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.


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.

Image:Processimage.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:

  • ITIL ICT Infrastructure Management.
  • ITIL Annex 3B, Risk Management Plan Service Delivery.
  • ITIL Availability Management.
  • ITIL 8.9.3 Central Computer and Telecommunications Agency (CCTA) Risk Analysis and Management Method (CRAMM) Service Delivery.
  • ITIL IT Service Continuity Management.
  • ITIL 7.3.2 Requirements analysis and strategy definition.


  • ISO 177993.1 Information security policy.
  • ISO 177993 4.1 Information security infrastructure.


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