Professor Messers Security+ 1.3 Videos

Change approval process

Complete request form

Reason for change

How much will change

Date & time of change

Affected/impacted systems

Analyze risk

Get approval from control board

Get end user acceptance

Stakeholders

People/departments that are impacted by the change

Impact analysis

Determines the risk value whether we change or dont (high,medium,low)

Sandbox test

lets you perform many test without effecting the system; duplicate system

backout plan

a plan to revert back or to something similar before the change

maintenance window

when will change happen, not during workday but rather late or early

standard operating procedure

Process must be well documented & follow company standards

allow/deny list

applicants that can or cant be allowed in a network due to danger or acceptance

restricted activites

you are only allowed to make changes to what is approved unless your change requires modification to something else

Downtime

when services wont be available/non production hours; you could switch to a secondary system then apply upgrade to your primary system

what are legacy applications?

applications that have been running for a long time & no one knows how to change it; COULD be changed to new system

dependencies

make a change to one service before you can change the other

are documents required after updates?

yes, this allows for updated addresses, diagrams & policies/procedures

what is version control?

keeps track of all data,codes & files installed; gives a way to revert to old system if you have a problem