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.2 - IT Continuity Plans

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.2 - IT Continuity Plans 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:
5 Members
0 Online
2718 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!


IT Continuity Plans

Develop IT continuity plans based on the framework and designed to reduce the impact of a major disruption on key business functions and processes. The plans should be based on risk understanding of potential business impacts and address requirements for resilience, alternative processing and recovery capability of all critical IT services. They should also cover usage guidelines, roles and responsibilities, procedures, communication processes, and the testing approach.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Continuous service across IT, addressing the requirements for critical IT resources
  • Defined and documented guidelines, roles and responsibilities
  • Achieved short- and long-range objectives supporting the organisation’s objectives
  Risk Drivers
  • Failure to recover IT systems and services in a timely manner
  • Failure of alternative decision-making processes
  • Lack of required recovery resources
  • Failed communication to internal and external stakeholders

View Control Practices  help

Hide Control Practices  help

  1. Create an IT continuity plan, including:
    • 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 requirements
    • 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
  2. Define underlying assumptions (e.g., level of outage covered by the plan) in the IT continuity plan and which systems (i.e., computer systems, network components and other IT infrastructure) and sites are to be included. Note alternative processing options for each site.
  3. Ensure that the IT continuity plan includes a defined checklist of recovery events as well as a form for event logging.
  4. Establish and maintain detailed information for every recovery site, including assigned staff and logistics (e.g., transport of media to the recovery site). This information should include:
    • Processing requirements for each site
    • Location
    • Resources (e.g., systems, staff, support) available at each location
    • Utility companies on which the site depends
  5. Define response and recovery team structures, including reporting requirements roles and responsibilities as well as knowledge, skills and experience requirements for all team members. Include contact details of all team members, and ensure that that they are maintained and readily available (e.g., offsite team, backup managing team).
  6. Define and prioritise communication processes and define responsibility for communication (e.g., public, press, government). Maintain contact details of relevant stakeholders (e.g., crisis management team, IT recovery staff, business stakeholders, staff), service providers (e.g., vendors, telecommunications provider) and external parties (e.g., business partners, media, government bodies, public).
  7. Maintain procedures to protect and restore the affected part of the organisation, including, where necessary, reconstruction of the affected site or its replacement. This also includes procedures to respond to further disasters while in the backup site.
  8. Create emergency procedures to ensure the safety of all affected parties, including coverage of occupational health and safety requirements (e.g., counselling services) and co-ordination with public authorities.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 105 total

Must be a Topic member to contribute
View All »
Downloads
Experienced business and IT professionals know that optimizing their use of big data as a resource will deliver real business value to the enterprise stakeholders.
Posted by ISACA 63 days ago
Downloads
Advanced persistent threat (APT) has been a term used frequently during security threat discussion; however, confusion exists as to what an APT is and how to manage the risk associated with it.
Posted by ISACA 87 days ago
Exam Preparation
Posted by ISACA 131 days ago
Books
Posted by ISACA 131 days ago

Events & Online Learning: 6 total

29 Oct 2012
ISACA International Event
New York, NY, USA
16 Sep 2013
ISACA International Event
London, England
Stay on top of the trends and opportunities of the dynamic technology industry at EuroCACS/ISRM 2013 in Berlin—the leading European conference for IT audit, assurance, security and risk professionals. Save over US $200 when you register by 22 July!
30 Sep 2013
ISACA International Event
Medellín, Colombia
La Conferencia Latinoamericana CACS/ISRM 2013 en Medellín, Colombia es la conferencia principal latinoamericana para los profesionales de auditoría, riesgo y seguridad de la información. Ahorre más de EE.UU. $ 100 si se inscribe antes del 7 de agosto!
14 Oct 2013
ISACA International Event
Boston, MA, USA
6 Nov 2013
ISACA International Event
Las Vegas, NV, USA
North America ISRM is a multidimensional event featuring security and risk content, and the security programs, tools and the resources you need to be responsive to industry changes.

Journal Articles: 305 total

Volume 3, 2013
by Kumar Setty, CISA, and Rohit Bakhshi
Big data not only encompasses the classic world of transactions, but also includes the new world of interactions and observations.
Volume 2, 2013
by Ganapathi Subramaniam, CISA, CISM
How do you audit the effectiveness of a command centre of a crisis management plan in the context of business continuity planning?
Volume 1, 2013
by Steven J. Ross, CISA, CISSP, MBCP
Emerging cyberattacks against the US’s critical infrastructures are rapidly outstripping the ability of security and risk management professionals to maintain high availability and uptime assurances.
Volume 6, 2012
by Klaus Julisch, Ph.D. and Damian Walch
This article presents a practice-tested framework that structures and prioritizes the assessment of DR programs, testing the most business-critical aspects first.
Volume 5, 2012
by Rico Barrasso and Matt Wallace
Cloud-based storage is significantly transforming the manner in which businesses protect, access and restore their critical data and information.
Volume 5, 2012
by Haris Hamidovic, CIA, ISMS IA, ITIL, IT Project+
Risk that is not identified, or at least not identified with the scale and intensity it presents, can produce a crisis.

Wikis: 2 total

Blog Posts: 29 total

Grupos de Estudio para Acreditaciones de JUNIO, SEPTIEMBRE Y DICIEMBRE 2013. Para los que esten interesados en la presentación del exámen de certificación CISA y CISM  o para cualquiera que desee comenzar a prepararse para estas o las próximas pruebas, pu...
Posted By : Alexander Osorio | 0 comments
DISCLAIMER :- Below information is just for knowledge sharing purpose and reference. Personally or on behalf of any organization; I do not recommend any specific / particular tool listed below. These are the ones which I have come across. there may be t...
Posted By : prathameshkarekar | 0 comments
Information security has been and remains a very specialized subject. Its early beginnings can be traced to the study of advanced mathematics and cryptography. even today the real theoretical advances happen in University Research Departments, Computer La...
Posted By : Dr Vishnu | 1 comments
During an audit you may find that shell scripts are used to connect to your Oracle database (these are often scheduled jobs).  In many instances this represents a security risk as the Oracle database password is hardcoded into the script.  This means th...
Posted By : Ian Cooke | 0 comments
As with configurations the company you are auditing should have a policy on password controls.  We have previously discussed that SQL Server allows two methods of authenticating to the database – Mixed Mode and Windows Authentication (see http://www.isa...
Posted By : Ian Cooke | 0 comments
Typically application access to a SQL Server database is via one of two methods.  Either all users access the same database using a single (proxy) user which is defined in an initialisation (.INI) file, registry etc. Or the users access the database ...
Posted By : Ian Cooke | 2 comments