Find Resources & Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

You must be logged in to join this group.

DS4.1 - IT Continuity Framework

This topic is intended to enable collaboration and sharing of information to facilitate a better understanding and approach to implementing this COBIT control objective based on the risk, value and guidance provided by its corresponding control practices.

COBIT Control Objective DS4.1 - IT Continuity Framework is contained within Process Popup Ensure Continuous Service.

Learn more about COBIT and related publications.

Click “Join This Community” to be able to actively participate in discussions and contribute content. You must be an ISACA member to join this topic. Join ISACA now.

This Topic Has:
40 Members
0 Online
5091 Visits

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer

IT Continuity Framework

Develop a framework for IT continuity to support enterprisewide business continuity management using a consistent process. The objective of the framework should be 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 organisational structure for continuity management, covering the roles, tasks and responsibilities of internal and external service providers, their management and their customers, and the planning processes that create 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, noting key dependencies, the monitoring and reporting of the availability of critical resources, alternative processing, and the principles of backup and recovery.

View value and Risk Drivers  help

Hide value and Risk Drivers help

Value Drivers

  • Continuous service across IT
  • Consistent, documented IT continuity plans
  • Governed services for business needs
  • Achieved short- and long-range objectives supporting the organisation’s objectives
  Risk Drivers
  • Insufficient continuity practices
  • IT continuity services not managed properly
  • Increased dependency on key individuals

View Control Practices  help

Hide Control Practices  help

  1. Assign responsibility for and establish an enterprisewide business continuity management process. This process should include an IT continuity framework to ensure that a business impact analysis (BIA) is completed and IT continuity plans support business strategy, a prioritised recovery strategy, necessary operational support based on these strategies and any compliance requirements.
  2. Ensure that the continuity framework includes:
    • The conditions and responsibilities for activating and/or escalating the plan
    • Prioritised recovery strategy, including the necessary sequence of activities
    • Minimum recovery requirements to maintain adequate business operations and service levels with diminished resources
    • Emergency procedures
    • Fallback procedures
    • Temporary operational procedures
    • IT processing resumption procedures
    • Maintenance and test schedule
    • Awareness, education and training activities
    • Responsibilities of individuals
    • Regulatory
    • Critical assets and resources and up-to-date personnel contact information needed to perform emergency, fallback and resumption procedures
    • Alternative processing facilities as determined within the plan
    • Alternative suppliers for critical resources
    • Chain of communications plan
    • Key resources identified
  3. Ensure that the IT continuity framework addresses:
    • Organisational structure for IT continuity management as a liaison to organisational continuity management
    • Roles, tasks and responsibilities defined by SLAs and/or contracts for internal and external service providers
    • Documentation standards and change management procedures for all IT continuity-related procedures and tests
    • Policies for conducting regular tests
    • The frequency and conditions (triggers) for updating the IT continuity plans
    • The results of the risk assessment process (PO9)

Discussions: 2 total

Must be a Topic member to contribute
Hello to you all,I need your help on the under listed. A colleague and i been assigned a financial institution to audit ICT Service Continuity   and Business continuity Management respectively as separate audits.I wish to request for guidance from this gr...
Bevan | 10/13/2016 3:24:49 AM | COMMENTS(0)
Hello All, Last week I came across a term called IT/ Application Compaonent Level Disaster Recovery and Disaster Recovery Automation. Anybody knows about this or had an experience. Please, share your views/ thoughts on this. Thanks, NItesh Sawant
Nitesh012 | 5/5/2013 8:25:37 AM | COMMENTS(0)

Documents & Publications: 67 total

Must be a Topic member to contribute
View All »
Posted by ISACA 526 days ago
Posted by ISACA 792 days ago
Posted by ISACA 855 days ago

Events & Online Learning: 12 total

Journal Articles: 165 total

Volume 3, 2107
by Jayakumar Sundaram, CISA, ISO 27001 LA
The SoA is a continuously updated and controlled document that provides an overview of information security implementation.
Volume 2, 2018
by Joshua McDermott, CISA, CEH, CISSP, PMP
Over the past several years, big data has emerged as one of the top strategic technology priorities for organizations.
Volume 2, 2018
by Ian Cooke, CISA, CGEIT, CRISC, COBIT Assessor and Implementer, CFE, CPTE, DipFM, ITIL Foundation, Six Sigma Green Belt
Innovation is defined as the introduction of something new or a new idea, method or device; therefore, introducing something new to a process is innovating.
Volume 2, 2018
by Steven J. Ross, CISA, CISSP, MBCP
In this era of multi-modal technology, many disaster recovery issues are solved, some are simply transferred and a few are made worse.
Volume 2, 2018
by Rassoul Ghaznavi-Zadeh, CISM, COBIT Foundation, SABSA SCF, TOGAF 9
A top-down approach to enterprise security architecture can be used to build a business-driven security architecture.
Volume 1, 2018
by Mike Van Stone, CISA, CISSP, CPA, and Ben Halpert
Ever-changing laws continue to increase the risk and cost of noncompliance when unintentional data losses occur.

Wikis: 2 total

Blog Posts: 39 total

Have you experienced ransomware attack so far and, if yes, what did you do to resolve? I set up Twitter poll here: It lasts for seven days. Thank you for taking part in the poll.
Posted By : Dragan Pleskonjic | 5 comments
My personal thoughts after listening to C-level executives at the CxO Roundtable Series sponsored by Intel, IBM, HyTrust & ReedSmith. For an invite, please reach out to me. Data Protection under the GDPR For past few months, I’ve been helping to org...
Posted By : Thomas152 | 1 comments
Information Security and Privacy is hot issue at present time. Number of security breaches is rapidly increasing.  In case of late detection, costs of breaches are skyrocketing. In the same time Artificial Intelligence (AI), Machine Learning (ML) are fast...
Posted By : Dragan Pleskonjic | 0 comments
My previous blog under name "Dragan on Security" was at location: It was active from August 28, 2005 to October 3, 2012. By beginning of 2017 it is moved to new location With possibility to...
Posted By : Dragan Pleskonjic | 0 comments
28 Sep 2017
Recently, I witnessed an interesting webcast by Scopism, an UK-based consulting and training company. They announced the publication of the SIAM(c) Foundation Body of Knowledge, available for free through their website Service Integration...
Posted By : Peter873 | 0 comments
The real success story is adoption of technology, and adoption is possible if the team which is implementing the Tech solution have vision and purpose of that solution to be adoptable by larger users / stake holders. We always do not get green field proje...
Posted By : Gopal207 | 0 comments