Technical Change Management

Question 1

Allow list/deny list

Answer 1

Allow list - nothing runs unless it’s approved, very restrictive list. Controlled by security policy.
Deny list- more flexible than allow list,you can run every application you would like except this specifically named no the deny list, may be identified by anty-malware.

Question 2

Restricted activities

Answer 2

Specifically defined in scope of change, anything else cannot be changed

Question 3

Downtime during change

Answer 3

Downtime is the time when services are unavailable. But during change time services can be just disruptive. That’s why change usually is scheduled during non-production hours. Downtime should be prevent, when you are working 24/7 during change it is good to switch to the secondary system, upgrade primarily system then switch back. To minimize downtime - change process should be automates as much as possible, switch back to secondary system if issue paper must be secured. . Should be a part of the backout plan

Question 4

Downtime during change

Answer 4

Downtime is the time when services are unavailable. But during change time services can be just disruptive. That’s why change usually is scheduled during non-production hours. Downtime should be prevent, when you are working 24/7 during change it is good to switch to the secondary system, upgrade primarily system then switch back. To minimize downtime - change process should be automates as much as possible, switch back to secondary system if issue paper must be secured. . Should be a part of the backout plan

Question 5

Legacy applications change

Answer 5

Legacy apps are running by long time , often no longer supported by the developer, for example WindowsXP,