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.

AI7.8 - Promotion to Production

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 AI7.8 - Promotion to Production is contained within Process Popup Install and Accredit Solutions and 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:
4 Members
0 Online
0 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Promotion to Production

Following testing, control the handover of the changed system to operations, keeping it in line with the implementation plan. Obtain approval of the key stakeholders, such as users, system owner and operational management. Where appropriate, run the system in parallel with the old system for a while, and compare behaviour and results.

View value and Risk Drivers  help

Hide value and Risk Drivers help

Value Drivers

  • An agreed-upon and standardised approach for promoting changes into production in an efficient and effective manner
  • Formally defined expectations and performance measurement
  • Consistent change procedure
  Risk Drivers
  • Segregation of duties violations
  • Systems exposed to fraud or other malicious acts
  • No rollback to previous application system version possible

View Control Practices  help

Hide Control Practices  help

  1. Ensure that a formal process for application, system and configuration transfer from testing to the production environment exists. Ensure that the process is in accordance with organisational change management standards.
  2. Ensure that the approval process clearly identifies effective dates for promotion to production of new systems, applications or infrastructure, as appropriate. Ensure that the approval process clearly identifies effective dates for retirement of old systems, applications or infrastructure, as appropriate.
  3. Ensure that the approval process includes a formal documented sign-off from business process owners, third parties and IT stakeholders, as appropriate (e.g., development group, security group, database management, user support and operations group).
  4. Consider the extent of parallel processing of the old and new system in line with the implementation plan.
  5. Promptly update all copies of system documentation and configuration information, including backup copies stored offsite, for software, hardware, operating personnel and system users before a new or modified system is implemented. Promptly update relevant contingency plan documents, as appropriate.
  6. Ensure that all source program libraries are updated promptly with the version of the program being transferred from testing to the production environment. Ensure that the existing version and its supporting documentation are archived. Ensure that promotion to production of systems, application software and infrastructure is under configuration control.
  7. In high-risk environments, consider obtaining from the testing function the media used for implementation to ensure that the software implemented is unchanged from what has been tested.
  8. Where distribution of systems or application software is conducted electronically, control automated software distribution to ensure that users are notified and distribution occurs only to authorised and correctly identified destinations. Implement checks in the distribution process to verify that the destination environment is of the correct standard implementation and version prior to the new software being installed and to ensure implementation on the approved effective date. Include in the release process backout procedures to enable the distribution of software changes to be reviewed in the event of a malfunction or error.
  9. Where distribution takes physical form, keep a formal log of what software and configuration items have been distributed, to whom, where they have been implemented, and when each has been updated. Implement a procedure to ensure the log’s integrity and completeness. Ensure that there are checks in the physical distribution process to ensure implementation on the approved effective date.
  10. Update all program copies in use in the production environment with the version being transferred from testing to the production environment in accordance with the implementation plan.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 42 total

Must be a Topic member to contribute
View All »
Posted by ISACA 623 days ago
Posted by ISACA 952 days ago
ICQs and Audit Programs
Posted by ISACA 1402 days ago
Posted by ISACA 1463 days ago

Events & Online Learning: 7 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: 150 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 3, 2018
by Giuliano Pozza, CGEIT, e-CF Plus (CIO), ITIL v3
The world of information and data management is changing faster than anyone could have predicted a few years ago, and attention to sensitive data protection is growing, as the new GDPR is clearly proving.
Volume 3, 2018
by Jen Hajigeorgiou, Editor
The ISACA Journal has a proud tradition of serving our community for more than 40 years, evolving to meet the needs and interests of practitioners amid the ever-changing technology landscape.
Volume 3, 2018
by Chip Jarnagin, CISSP, CSM, PMP, and Sonja Hammond, CISSP, ITIL Foundation, PCI-ISA
The exposure of data for up to 14 million of Verizon’s customers in July 2017 was an enormous embarrassment, particularly for an organization that presents itself as a premium cybersecurity consultancy.
Volume 3, 2018
by T. Sean Kelly
Proactive IG requires collaboration among legal, compliance, security and IT teams to take an incremental, measurable approach to deal with today’s enterprise data challenges.
Volume 3, 2018
by Ofir Eitan, CISM, CCSK, CTI
One of the major challenges chief information security officers (CISOs) face in almost any organization is prioritizing information security interests with regard to IT interests.

Wikis: 2 total

Blog Posts: 28 total

5 Jun 2018
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 | 2 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
Mi primer acercamiento real al Framework (o Marco de Referencia) de ISACA COBIT 5, fue a mediados del año pasado (2016) cuando decidí tomar un curso de examinación para la certificación de COBIT® 5 Foundation (Fundamentos de COBIT 5). La jerga técnica me ...
Posted By : MNUNEZA | 0 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
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