Change management policy

Overview

Nevercode standardizes and automates configuration management through the use of automation scripts as well as documentation of all changes to production systems and networks. All Nevercode configuration changes are reviewed, whether it is performed via automated or manual configuration.

Policy Statements

1. All changes made to the production environment must go through a review and approval process and all automated controls and monitors must be passing before release.
2. Each production change must be fully tested before general adoption.
3. Before releasing a change to production, a rollback plan must be established in case of an issue.
4. Access to implement changes is restricted to authorized personnel only.
5. Once a change has been approved and pushed to production, there must be documentation maintained that outlines at least the following information related to the change:
   • Author
   • Approver
   • Release date
   • Original rationale