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:
2 Members
0 Online
830 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Points: 3


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: 92 total

Must be a Topic member to contribute
View All »
Books
Posted by ISACA 11 days ago
Research
Posted by ISACA 56 days ago
Books
Computer crimes call for forensics specialists, people who know how to find and follow the evidence.
Posted by ISACA 57 days ago
Books
Aimed at both the novice and expert in IT security and industrial control systems (ICS), this book will help readers gain a better understanding of protecting ICSs from electronic threats.
Posted by ISACA 57 days ago

Events & Online Learning: 10 total

7 May 2012
ISACA International Event
Orlando, Florida, USA
Get the knowledge you need to stay one step ahead of the competition and keep up with changing professional trends at ISACA’s North America CACS Conference.
15 May 2012
ISACA International Event
Washington, DC, USA
12 Jun 2012
ISACA International Event
Dallas, Texas, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
7 Aug 2012
ISACA International Event
Chicago, Illinois, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
10 Sep 2012
ISACA International Event
Munich, Germany
EuroCACS/ISRM is a multidimensional event featuring audit, security, governance and risk content, and the audit and security programs, tools and the resources you need to be responsive to industry changes.
11 Sep 2012
ISACA International Event
San Francisco, California, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.

Journal Articles: 295 total

Volume 3, 2012
by Kai-Uwe Ruhse, CISA, PCI QSA, and Maria Baturova
This article describes real cloud computing project case studies, which show that moving to the cloud is an important strategic decision for IT managers.
Volume 3, 2012
by Steve Markey
Once thought of as a technology solely for academia, non-RDBMS are now reaching critical mass in industry.
Volume 2, 2012
by Kerry A. Anderson, CISA, CISM, CRISC, CGEIT, CISSP, ISSMP, ISSAP, CSSLP, CFE
The closer alignment between RIM and information security may provide an approach to managing increasing data protection concerns and tough privacy regulations rather than maintaining the separation between these critical compliance functions.
Volume 2, 2012
by Tommie W. Singleton, Ph.D., CISA, CGEIT, CITP, CPA
This article addresses some of the IT audit issues associated with data transfers.
Volume 2, 2012
by Robbie Sauerberg, Weston Smith and Jonathan Tudor, CCNA
This article first describes the benefits of CRM systems and identifies risk areas inherent in CRM systems that threaten the benefits an organization can receive from a CRM system.
Volume 2, 2012
by Alex Berson and Larry Dubov | Reviewed by Bright Munongwa
This book is a reference guide that looks at the topics of MDM and data governance from multiple perspectives.

Wikis: 2 total

Blog Posts: 19 total

The main idea I am trying to advocate with these posts is a simple one.  Compare a database you are auditing against a database that you know already meets the standards required by the organisation you are auditing. This is achieved by creating “CSV ty...
Posted By : Ian Cooke | 1 comments
We have covered most of the core items that should be consider when performing an Oracle database audit in previous posts, however there a number of other items that I would typically look into. Database Links A database link is an object in one database...
Posted By : Ian Cooke | 0 comments
The company you are auditing should have a policy on what is being audited within your Oracle database.  The level of auditing will almost certainly be affected by the sensitivity of the data. Good examples and bench marks for auditing may be seen in the...
Posted By : Ian Cooke | 0 comments
Typically application access to an Oracle 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 individ...
Posted By : Ian Cooke | 1 comments
Before we get into auditing Oracle privileges a reminder of a few definitions might be helpful. A user privilege is the right to run a particular type of SQL statement, or the right to access an object belonging to another user, run a PL/SQL package, and...
Posted By : Ian Cooke | 1 comments
7 Mar 2012
To share various espects in cloud computing viz; history, availability, deployment, integrity, availability, confidentiality, security, cloud sharing etc.
Posted By : MoizB583519 | 2 comments