3.4.7 Change Release Management
| No: 43028139 | Date(g): 4/11/2021 | Date(h): 29/3/1443 |
Effective from 2021-11-04 - Nov 03 2021
To view other versions open the versions tab on the right
Principle
Change release management process should be defined to ensure that system changes are adequately planned and released to the production environment in a strictly controlled manner.
Control Requirements
| 1. | The release management process should be defined, approved, implemented and communicated. | |
| 2. | The release management process should be monitored and periodically evaluated. | |
| 3. | The release management process should address the following, but not limited to: | |
| a. | change release strategy and approach; | |
| b. | roles and responsibilities to carry out change releases; | |
| c. | change release schedule and logistics; | |
| d. | change roll-out and roll-back procedures; and | |
| e. | data migration, where applicable. | |
| 4. | The changes should be released in the corresponding system in disaster recovery site upon successful implementation of changes in the production environment at main site. | |
| 5. | Change should be introduced as part of an agreed change window, exceptions has to have their own approval process and seldom allowed without compelling reasons. | |