5.8 Explain the basics of change management procedures - Paiet/Tech-Journal-for-Everything GitHub Wiki

5.8 Explain the basics of change management procedures

• Used to make sure all changes are approved by proper
  personnel and are done in a safe and logical way
• Document reason for a change
  • Included in change request
• Change request
  • Configuration procedures
    • Steps required
    • Devices involved
  • Rollback process
    • Must be planned for
    • Allow to recover from adverse effects
  • Potential impact
    • Best effort to identify impact of change
    • Determine what needs to be monitored closely
  • Notification
    • System owners and department heads
• Approval process
  • Should be approved by range of personnel
    • IT personnel
    • Management
    • Security team
  • Assure changes are approved, tested and documented
  • Periodic change status reporting
• Maintenance window
  • Time system(s) will be unavailable during the change
    implementation
  • Consider if changes can be made during business hours
• Authorized downtime
  • Approved time when the change will occur
• Notification of change
  • Stakeholders are notified that change is complete
  • After time has elapsed to find any issues
• Documentation
  • Network configurations
  • Additions to network
  • Physical location changes