PO4.3:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
:: NIST SP 800-66 | :: NIST SP 800-66 | ||
:: Ditscap | :: Ditscap | ||
:: Control Exception | :: Control Exception | ||
:: User Defined | :: User Defined | ||
| Line 27: | Line 26: | ||
::'''2. Risk: Business needs may not be met or adequate data safeguards may not be implemented or considered.'''<br> | ::'''2. Risk: Business needs may not be met or adequate data safeguards may not be implemented or considered.'''<br> | ||
:::a. [[SOX.1.7:|'''SOX.1.7''']] The SDLC methodology includes requirements that information systems be designed to include application controls that support complete, accurate, authorized and valid transaction processing.<br> | :::a. [[SOX.1.7:|'''SOX.1.7''']] The SDLC methodology includes requirements that information systems be designed to include application controls that support complete, accurate, authorized and valid transaction processing.<br> | ||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
| Line 68: | Line 64: | ||
ISO 17799 4.1 Information security infrastructure.<br> | ISO 17799 4.1 Information security infrastructure.<br> | ||
[[KY DOI A.1:|'''KY DOI A.1''']]<br> | |||
<br> | <br> | ||
'''Implementation guidance'''<br> | '''Implementation guidance'''<br> | ||
Revision as of 19:54, 25 June 2006
PO 4.3 IT Steering Committee
Control Objective:
Establish an IT steering committee (or equivalent) composed of executive, business and IT management to: Determine prioritization of IT-enabled investment programs in line with the enterprise’s business strategy and priorities; Track status of projects and resolve resource conflict; Monitor service levels and service improvements.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: nformation security and business requirements may be compromised. Inaccurate results are produced.
- a. SOX.1.1 A formal, documented systems development methodology should be established and implemented by management. This systems development life cycle (SDLC) describes the stages involved in information system development projects, from an initial feasibility study through maintenance of the completed application. Verify that security, availability, and process integrity requirements are included.
- a. SOX.1.1 A formal, documented systems development methodology should be established and implemented by management. This systems development life cycle (SDLC) describes the stages involved in information system development projects, from an initial feasibility study through maintenance of the completed application. Verify that security, availability, and process integrity requirements are included.
- 1. Risk: nformation security and business requirements may be compromised. Inaccurate results are produced.
- 2. Risk: Business needs may not be met or adequate data safeguards may not be implemented or considered.
- a. SOX.1.7 The SDLC methodology includes requirements that information systems be designed to include application controls that support complete, accurate, authorized and valid transaction processing.
- a. SOX.1.7 The SDLC methodology includes requirements that information systems be designed to include application controls that support complete, accurate, authorized and valid transaction processing.
- 2. Risk: Business needs may not be met or adequate data safeguards may not be implemented or considered.
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:
ITIL Service Delivery.
ITIL Service Level Management.
ITIL 4.5 The ongoing process.
ISO 17799 4.1 Information security infrastructure.
KY DOI A.1
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 07:46, 23 June 2006 (EDT)