change management

how to make a change

upgrade software, patch an application, change firewall configuration, modify switch ports

have clear policies with frequency, duration, installation process and rollback procedures

sometimes can be difficult to implement

change approval process

formal process for managing change avoids downtime, confusion, and mistakes

complete teh request forms, determine the purpose of the change, identify the scope of the change, schedule a date and time of the change, determine affected systems and hte impact, analyze the risk associated with the change, get approval form the change control board, get end user acceptance after the change is complete

ownership

individual or entity needs to make a change so they own the process and dont usually perform the actual change

the owner manages the process as updates are provided to them and they ensure the process is followed and acceptable

stakeholders

impacted by the change proposed

impact analysis

determine risk value

risks can be minor or far reaching

test results

sandbox testing environment that has no connection to the real world or production system and is a technological safe space

sandbox can’t consider every possibility

backout plan

a way to revert your changes

always have backups

maintenance window

when is the change happening

overnight are better choices

time of the year may also be considered

standard operation procedure

process must be well documented and available on the internet with frequent updates