DS4.1:
DS 4.1 IT Continuity Framework
Control Objective:
Develop a framework for IT continuity to support enterprise wide business continuity management with a consistent process. The objective of the framework is to assist in determining the required resilience of the infrastructure and to drive the development of disaster recovery and IT contingency plans. The framework should address the organizational structure for continuity management, covering the roles, tasks and responsibilities of internal and external service providers, their management and their customers, and the rules and structures to document, test and execute the disaster recovery and IT contingency plans. The plan should also address items such as the identification of critical resources, the monitoring and reporting of the availability of critical resources, alternative processing, and the principles of backup and recovery.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Management may not be able to trace, review, or monitor systems development effectively.
- a. SOX.1.6: Obtain a copy of the organization's Systems Development Life Cycle (SDLC) methodology. Review the methodology to determine that it addresses security, availability and processing integrity requirements. Consider whether there are appropriate steps to ensure that these requirements are considered throughout the development or acquisition life cycle.
- 1. Risk: Management may not be able to trace, review, or monitor systems development effectively.
- 2. Risk: IT function does not meet the organizational needs.
- a. SOX.2.0.1: Organizational policies and management procedures are in place to ensure the IT function is controlled properly.
- 2. Risk: IT function does not meet the organizational needs.
- 3. Risk: Operational failures may not be identified and resolved in an appropriate, timely manger
- a. SOX.2.4.1: There should be appropriate procedures to ensure that operational failures (e.g., disk drive problems, program amends, and other emergencies) are identified, resolved in a timely manner, and, where appropriate, approved retrospectively.
- 3. Risk: Operational failures may not be identified and resolved in an appropriate, timely manger
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 IT Service Continuity Management
ITIL 7.3 The business continuity life cycle
ISO 4.1 Information security infrastructure
ISO 11.1 Aspects of business continuity management
