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.

AI6.5 - Change Closure and Documentation

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 AI6.5 - Change Closure and Documentation is contained within Process Popup Manage Changes.

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:
6 Members
0 Online
4601 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer


Change Closure and Documentation

Whenever changes are implemented, update the associated system and user documentation and procedures accordingly.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • An agreed-upon and standardised approach for documenting changes
  • Formally defined expectations
  • Consistent change and documentation procedures
  Risk Drivers
  • Increased dependence on key individuals
  • Configuration documentation failing to reflect the current system configuration
  • Lack of documentation of business processes
  • Failure of updates for hardware and software changes

View Control Practices  help

Hide Control Practices  help

  1. Ensure that documentation—including operational procedures, configuration information, application documentation, help screens and training materials—follows the same change management procedure and is considered to be an integral part of the change.
  2. Consider an appropriate retention period for change documentation and pre- and post-change system and user documentation.
  3. Update business processes for changes in hardware or software to ensure that new or improved functionality is used.
  4. Subject documentation to the same level of testing as the actual change.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 12 total

Must be a Topic member to contribute
View All »
Books
Posted by ISACA 828 days ago
Research
Posted by ISACA 1131 days ago
Downloads
Posted by ISACA 1339 days ago
Books
Posted by ISACA 1371 days ago

Events & Online Learning: 1 total

13 Aug 2018
ISACA International Event
Nashville, Tennessee, US
2018 GRC Conference - 13-15 August , Nashville, TN. Explore the future of Governance Risk and Control through expert-led workshops and sessions developed by the IIA and ISACA. Register early for our GRC learning tracks.

Journal Articles: 34 total

Volume 1, 2018
by Ian Cooke, CISA, CGEIT, CRISC, COBIT Assessor and Implementer, CFE, CPTE, DipFM, ITIL Foundation, Six Sigma Green Belt
Innovative technologies such as VMs and the cloud help the efficiency and effectiveness of backup and recovery plans, but they do not replace the need to plan, document, or test and test again.
Volume 1, 2018
by Chris Poulin
While today everyone worships their smartphones as if the device itself demands their constant and public attention, there’s a new transformative technology that’s even more pervasive...
Volume 5, 2017
by T. Sean Kelly
Certain steps can be taken to build a strong respect for and practice of security into the cultural fabric of any organization, across all departments and areas of the business.
Volume 4, 2017
by Mathew Nicho, Ph.D., CEH, CIS, ITIL Foundation, RWSP, SAP, Shafaq Khan, Ph.D., CIS, PMBOK, PMP, SAP and Ram Mohan, CRISC, CISM, CGEIT, ISO 27001
The Emirates National Oil Company embarked on an initiative to realize value out of IT assets through Information Technology Infrastructure Library (ITIL) process implementation.
Volume 2, 2017
by Ed Moyle
To understand how the business side of any organization intersects with technology, ask an internal auditor. This might sound counterintuitive at first, but think about what auditors need to know to do their job...
Volume 5, 2016
by Steven J. Ross, CISA, CISSP, MBCP
Still having a base in IS/IT auditing, ISACA now encompasses consultants, educators, IS security professionals, risk professionals, chief information officers and internal auditors

Wikis: 2 total

Blog Posts: 8 total

“Enterprise architecture is now a strategic componentof every forward-thinking organization around the world.”Source: http://feapo.org/press-release-ea-perspectives-white-paper/ Related Article: Common Perspective on Enterprise Architecture: http://feapo....
Posted By : SA | 1 comments
  Rob Stroud is the New York based Vice President of Strategy and Innovation at CA Technologies and is the current President for the 2014-15 administrative term.  I caught up with Rob in Australia when he visited Canberra in June 2014...
Posted By : Rob Hanson | 2 comments
Agile technique in software development has been around for quite some time. There have been efforts to adopt the agile techniques for strategic planning, alignment and execution. Following are some of the relevant articles/blog posts in this area. The to...
Posted By : SA | 0 comments
13 Nov 2014
Posted By : masarker | 4 comments
Enterprise Architecture (EA) is about holistic understanding of the enterprise including the business side. I had to stress on the business side as sometimes the EA is taken as IT Architecture. EA is a combination of IT and Business Architectures. It take...
Posted By : SA | 0 comments
28 Jan 2014
Welcome to my blog which will be dedicated to views and discussions on Enterprise Architect (EA) and Business-IT Alignment (BITA). I encourage the colleagues to join the ISACA topic group for "Strategic Planning/Alignment" for initiating and promoting...
Posted By : SA | 0 comments