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
2708 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!


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

Must be a Topic member to contribute
View All »
Books
Posted by ISACA 130 days ago
Exam Preparation
Posted by ISACA 130 days ago
Downloads
Posted by ISACA 130 days ago
Books
Posted by ISACA 136 days ago

Events & Online Learning: 3 total

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!
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: 43 total

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 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.
Volume 4, 2012
by Haris Hamidovic, CIA, ISMS IA, ITIL, IT Project+
Deterring cybercrime is an integral component of a national cybersecurity and critical information infrastructure protection strategy.
Volume 1, 2012
by Rama Lingeswara Satyanarayana Tammineedi, CISA, BCCE, CBCP, CISSP, PMP
Business continuity management (BCM) is a holistic process to ensure uninterrupted availability of all key business resources required to support critical business activities, whether manual or IT-enabled, in the event of business disruption.
Volume 5, 2011
by Tommie W. Singleton, Ph.D., CISA, CGEIT, CITP, CPA
This article provides the IT auditor with concepts, techniques, processes and structures that can mitigate the change management risk associated with AppDev.
Volume 4, 2011
by Steven J. Ross, CISA, CISSP, MBCP
BCM and CMP can be dissociated from DRP, but data disruptions ripple through entire organizations.

Wikis: 2 total

Blog Posts: 5 total

Must be a Topic member to view blog posts
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
Security is one of the major concerns which hold enterprises from embracing the cloud. But some think that this is manageable and as such have started adopting cloud based SaaS applications. Cloud based Enterprise solutions like Sales Force, Service Now, ...
Posted By : Kannan | 0 comments
Es importantísimo reconocer que la banca móvil y pagos móviles han llegado para quedarse y que aquellos bancos que no se ocupen ahora en prepararse tendrán grandes problemas en el largo plazo y esta es una opinión compartida con el equipo de BITS (Financi...
Posted By : Diego San Esteban | 0 comments
17 Aug 2011
Posted By : masarker | 0 comments
El País de ayer abría en portada con la siguiente noticia relacionada con las elecciones catalanas: "La 'caza' de inmigrantes da puntos en el videojuego del PP". Os adelanto que no voy a hablar de política, así que, los que hayáis llegado hasta aquí por e...
Posted By : Antonio Ramos | 0 comments